AWS Certified Advanced Networking – Specialty (ANS-C01)Network DesignHard
A global manufacturing company has deployed a new application across multiple AWS Regions. They need to implement a DNS strategy that routes users to the application endpoint in the Region that provides the lowest network latency. Additionally, if an endpoint in a preferred Region becomes unhealthy, traffic should automatically fail over to a healthy endpoint in another Region. Which Route 53 routing policies should they combine to achieve this?
- ASimple Routing Policy with Weighted Routing Policy.
- BWeighted Routing Policy with Geoproximity Routing Policy.
- CLatency Routing Policy with Failover Routing Policy.
- DGeolocation Routing Policy with Multivalue Answer Routing Policy.
Show answer & explanationAnswer & explanation
Correct answer: C. Latency Routing Policy with Failover Routing Policy.
Latency Routing Policy directs users to the Region with the lowest network latency to the client. When combined with Failover Routing Policy and Route 53 health checks, it ensures that if the lowest-latency endpoint becomes unhealthy, traffic automatically fails over to a healthy endpoint in another Region, satisfying both requirements.
Why the other options are wrong
- A. Simple Routing does not incorporate latency or health checks, and Weighted Routing distributes traffic based on weights, not latency or automatic failover.
- B. Weighted routing distributes traffic based on defined weights, and Geoproximity routes based on geographic location and optional bias, neither directly combines lowest latency with automatic failover based on health checks across regions.
- D. Geolocation routes based on the user's geographic location, not necessarily lowest network latency, and Multivalue Answer returns multiple healthy IPs but doesn't provide prioritized failover for DR.
Route 53 Latency & Failover
Combining Latency routing for performance and Failover routing for high availability in a multi-region DNS strategy.
- Latency routing directs to the lowest-latency healthy endpoint.
- Failover routing ensures automatic redirection upon unhealthiness.
- Requires Route 53 health checks for failover functionality.
Memory trick: Route 53 helps users find the fastest route, and if it's down, it automatically reroutes.