Which combination of solutions will meet these requirements?
(Choose two.)
Launch a second EC2 instance in a second AWS Region. Use a Route 53 failover routing policy to redirect the traffic to the second EC2 instance.
Create and configure an Auto Scaling group to launch private EC2 instances in multiple Availability Zones. Add the instances to a target group behind a new Application Load Balancer.
Migrate the database to an Amazon Aurora MySQL cluster. Create the primary DB instance and reader DB instance in separate Availability Zones.
Create and configure an Auto Scaling group to launch private EC2 instances in multiple AWS Regions. Add the instances to a target group behind a new Application Load Balancer.
Migrate the database to an Amazon Aurora MySQL cluster with cross-Region read replicas.
Explanations:
While launching a second EC2 instance in a different AWS Region with a Route 53 failover routing policy may enhance availability, it does not address scalability or reduce MySQL read latency effectively. Additionally, using a different Region complicates the architecture and could introduce latency for users.
Creating an Auto Scaling group with EC2 instances in multiple Availability Zones increases scalability and availability. By placing the instances behind an Application Load Balancer, the architecture can distribute traffic and automatically adjust the number of running instances based on demand, enhancing both performance and resilience.
Migrating to an Amazon Aurora MySQL cluster improves database performance and availability. By creating the primary and reader DB instances in separate Availability Zones, the architecture allows for horizontal scaling of reads, significantly reducing read latency and providing higher availability through automatic failover.
Configuring an Auto Scaling group with EC2 instances across multiple AWS Regions introduces complexity and latency for inter-region communication. This approach does not provide the needed scalability or high availability effectively for a single application instance.
While migrating to an Aurora MySQL cluster is beneficial, cross-Region read replicas are not necessary for this scenario and can lead to increased latency due to geographic distance. This option also does not improve the primary application’s scalability directly within a single Region.
I plan that the answer is:
Create and configure an Auto Scaling group to launch private EC2 instances in multiple Availability Zones. Add the instances to a target group behind a new Application Load Balancer.