Which combination of actions will improve the access load times?
(Choose two.)
Configure RDS MySQL Multi-AZ to reduce RDS CPU and RAM utilization and distribute queries to multiple Availability Zones.
Modify the EC2 Auto Scaling group so it will scale horizontally when CPU utilization is 50%.
Provision a second production environment in the Asia Pacific Region and use an ALB to distribute cross-Region access.
Provision a second production environment in the Asia Pacific Region and use Amazon Route 53 latency-based routing.
Set up an Amazon CloudFront distribution to handle static content for users accessing it from different geographic locations.
Explanations:
RDS MySQL Multi-AZ provides high availability, but it does not help distribute queries across multiple AZs in a way that would reduce CPU and RAM utilization. Additionally, the RDS instance has sufficient memory and CPU capacity based on the CloudWatch metrics, so there’s no immediate need for this change.
Modifying the EC2 Auto Scaling group to scale at 50% CPU utilization could lead to over-scaling and higher costs. The current scaling policy of 75% CPU utilization seems appropriate given the usage patterns and does not directly address the latency issue in Asia.
Provisioning a second production environment in the Asia Pacific Region would result in increased complexity and cost. Additionally, an ALB cannot distribute traffic across regions, so this solution is not effective for improving access times in Asia.
Using Amazon Route 53 latency-based routing can direct users in Asia to the production environment in the Asia Pacific Region, which reduces latency by routing traffic to the nearest region. This improves access times for users in Asia.
Setting up an Amazon CloudFront distribution will cache static content at edge locations closer to users, reducing the time it takes to load resources for users in different geographic locations, including Asia. This would improve overall access times.