ANS-C01 Question 2
Select 2Your company is deploying a highly available web application across two AWS Regions to serve a global user base. You want to ensure that users are routed to the closest region based on latency while also providing failover capability in case one region becomes unavailable. Which combination of configuration steps would best achieve this goal?
- A
Use Amazon Route 53 with a latency-based routing policy to direct traffic to the closest region.
- B
Configure Route 53 health checks to monitor the health of your application endpoints in each region.
- C
Use an Application Load Balancer (ALB) in each region and configure cross-region load balancing.
- D
Set up AWS Global Accelerator to route traffic between regions based on health and latency.
- E
Deploy a CloudFront distribution and configure origin failover to switch between the regions.
Show answer and explanation
Correct answers: A, B
Explanation
To achieve latency-based routing and failover between AWS Regions, Amazon Route 53 with a latency-based routing policy and health checks is the most appropriate solution. Latency-based routing ensures that users are directed to the closest region, while health checks enable automatic failover in the event of a region becoming unavailable. The other options either do not fully meet the requirements or are intended for different use cases.
- A. Correct.
Using Amazon Route 53 with a latency-based routing policy ensures that users are directed to the AWS Region with the lowest latency, which is essential for optimizing the user experience in a global deployment.
- B. Correct.
Route 53 health checks are necessary to monitor the availability of endpoints in each region. This ensures that traffic is rerouted to the healthy region in case one region becomes unavailable.
- C. Incorrect.
While an Application Load Balancer can balance traffic within a region or between different availability zones, it does not support cross-region latency-based routing or failover directly.
- D. Incorrect.
AWS Global Accelerator provides global traffic routing and failover capabilities, but it is not required in this scenario because Route 53 latency-based routing and health checks are sufficient to meet the requirements.
- E. Incorrect.
CloudFront origin failover is designed for CDN-origin redundancy, not for routing traffic between AWS Regions based on latency or health.