A solutions architect is deploying a complex Java application with a MySQL database. The Java application must run on Apache Tomcat and be highly available. What should the solutions architect do to meet these requirements?

AWS Elastic Beanstalk is ideal for deploying Java applications on Apache Tomcat, as it automates environment provisioning, load balancing, and auto-scaling, ensuring high availability. A load-balanced environment distributes traffic across multiple instances, and a rolling deployment policy updates the application without downtime. Deploying to Lambda is incorrect because the application is a complex Java application requiring Apache Tomcat, which is not a serverless function. Migrating the database to ElastiCache is incorrect because ElastiCache is an in-memory cache, not a relational database like MySQL, and doesn't address the application deployment requirement. Manually setting up EC2 instances, even with an Auto Scaling group, is less efficient than Elastic Beanstalk, which handles much of the operational overhead automatically.