AWS Certified Advanced Networking – Specialty (ANS-C01)Network DesignEasy
A global enterprise with operations in North America, Europe, and Asia is migrating its critical customer-facing applications to AWS. The applications are hosted in separate VPCs in `us-east-1`, `eu-west-1`, and `ap-southeast-2`. The enterprise needs to ensure that users are always routed to the nearest healthy application endpoint to minimize latency and improve user experience. If an application endpoint in a region becomes unhealthy, traffic should automatically fail over to the next closest healthy region. Which routing strategy should the enterprise implement?
- AGeolocation routing policy with health checks
- BLatency routing policy combined with failover routing policy
- CSimple routing policy with health checks
- DWeighted routing policy with health checks
Show answer & explanationAnswer & explanation
Correct answer: B. Latency routing policy combined with failover routing policy
To achieve both low latency and high availability with automatic failover, a combination of latency-based routing and failover routing policies is necessary. Latency routing directs users to the region with the lowest latency, and failover routing ensures that if the primary endpoint becomes unhealthy, traffic is rerouted to a healthy secondary endpoint.
Why the other options are wrong
- A. Geolocation routing routes users based on their geographic location, which is different from latency, and while it supports health checks, it doesn't automatically fail over to the next closest healthy region based on latency if the primary geo-located endpoint fails.
- C. Simple routing does not provide latency-based routing or automatic failover capabilities.
- D. Weighted routing distributes traffic based on weights, not latency, and while it supports health checks, it doesn't automatically fail over to the next closest healthy region based on latency.
Route 53 Latency & Failover Routing
A combination of Route 53 routing policies to direct users to the lowest latency healthy endpoint, with automatic failover to another healthy endpoint if the primary fails.
- Latency routing minimizes user response times.
- Failover routing ensures high availability.
- Requires health checks for failover to function.
- Useful for global, multi-region deployments.
Memory trick: Latency's fast, failover's a must, for global users, we put our trust!