A critical web application currently runs on a single Amazon EC2 instance in a public subnet and uses a MySQL database. DNS is in Route 53. A solutions architect must make the application scalable and highly available and reduce MySQL read latency. Which combination of changes will meet these requirements? (Choose two.)

The correct options address scalability, high availability, and reduced read latency. Creating an Auto Scaling group across multiple Availability Zones with an Application Load Balancer (ALB) makes the application scalable and highly available by distributing traffic and automatically replacing unhealthy instances. Migrating to an Amazon Aurora MySQL cluster with a primary instance and reader instances in separate Availability Zones provides high availability for the database and reduces read latency by offloading read operations to the reader instances. Incorrect options: Launching a second EC2 instance in another region with Route 53 failover provides disaster recovery but doesn't inherently improve scalability or reduce read latency for the current region's users. An Auto Scaling group across multiple AWS Regions is overly complex for the given requirements and typically used for global applications, not just high availability and scalability within a region. Migrating to Aurora with cross-Region read replicas is good for global read latency but doesn't address the primary application's high availability and scalability within its current region.