ANS-C01 Question 60
Single answerYour company runs a multi-region application hosted in AWS across two regions, us-east-1 and us-west-2. To ensure high availability, the application uses an Amazon Route 53 health check to monitor an Elastic Load Balancer (ELB) in each region. Recently, users in us-west-2 reported slower response times compared to us-east-1. Upon investigation, you find that Route 53 is routing traffic to the us-east-1 region even for requests originating from us-west-2. How can you optimize Route 53 to ensure users are routed to the closest healthy region while maintaining high availability?
- A
Configure a latency-based routing policy in Amazon Route 53.
- B
Use a geolocation routing policy in Amazon Route 53.
- C
Set up a failover routing policy in Amazon Route 53.
- D
Implement a weighted routing policy in Amazon Route 53.
Show answer and explanation
Correct answer: A
Explanation
Latency-based routing is ideal for this scenario because it routes users to the region or endpoint with the lowest latency. This ensures that users in us-west-2, who are experiencing slower response times, are directed to the closest healthy region (in this case, us-west-2). The other options, such as geolocation and failover routing, do not account for latency and are not suited for performance optimization in this case.
- A. Correct.
Correct. A latency-based routing policy ensures that users are routed to the region with the lowest latency, which optimizes performance for users in us-west-2 while maintaining high availability.
- B. Incorrect.
Incorrect. While geolocation routing routes traffic based on the user's geographic location, it does not consider latency and may not provide the best performance for all users.
- C. Incorrect.
Incorrect. Failover routing is primarily used for disaster recovery scenarios, routing traffic to a secondary resource only when the primary is unavailable, and is not appropriate for optimizing performance in this scenario.
- D. Incorrect.
Incorrect. Weighted routing distributes traffic based on predefined weights, which does not address the issue of optimizing performance based on latency.