AWS Certified CloudOps Engineer Associate SOA-C03 Practice Question

Failover routing is designed specifically for active-passive architectures. You designate one record as PRIMARY and one as SECONDARY and associate a health check with the primary record. While the primary health check is healthy, Route 53 returns only the primary record. If the health check fails, Route 53 automatically returns the secondary record until the primary becomes healthy again. Latency-based, weighted, and geolocation policies can each attach health checks, but they continue to serve traffic according to latency metrics, weight values, or user location, meaning some requests could still go to an unhealthy endpoint. Only the failover policy guarantees an all-or-nothing switch to the standby endpoint.