ANS-C01 Question 411
Select 1A company needs to ensure high availability for its web application using Amazon Route 53. They have deployed the application in two AWS Regions: us-east-1 and ap-southeast-1. The company wants to route traffic to the region with the lowest latency but only if the health checks for the resources in that region are passing. If the health checks fail in one region, traffic should automatically failover to the other region. Which Route 53 configuration will meet these requirements?
- A
Create two latency-based record sets, each pointing to the endpoint in one region, and associate health checks with both records.
- B
Create two weighted record sets with equal weights, each pointing to the endpoint in one region, and associate health checks with both records.
- C
Create two failover record sets with the primary pointing to one region and the secondary pointing to the other region, and associate health checks with both records.
- D
Use a geolocation-based routing policy to distribute traffic between the two regions and associate health checks with the records.
- E
Create one latency-based record set pointing to one region and configure a failover record set for the other region.
Show answer and explanation
Correct answer: A
Explanation
Latency-based routing combined with health checks is the optimal solution for this scenario. It directs traffic to the region with the lowest latency while ensuring that traffic is routed away from unhealthy endpoints. This configuration provides high availability and minimizes latency for users accessing the application.
- A. Correct.
This is the correct configuration. Latency-based routing ensures traffic is directed to the region with the lowest latency, while the health checks ensure traffic is only routed to healthy endpoints.
- B. Incorrect.
Weighted routing does not prioritize latency and would not ensure traffic is routed to the region with the lowest latency. This option is incorrect.
- C. Incorrect.
Failover routing alone does not account for latency and is not designed for multi-region deployments where latency-based routing is required. This option is incorrect.
- D. Incorrect.
Geolocation routing directs traffic based on the geographic location of the user, not latency. This does not meet the requirement to route based on the lowest latency. This option is incorrect.
- E. Incorrect.
Combining a single latency-based record with a failover record does not meet the requirement to dynamically route traffic to the lowest latency region in an active-active setup. This option is incorrect.