CLF-C02 Practice Question 118: Latency Routing

With latency-based routing, you create latency records for resources in multiple AWS Regions. When Route 53 receives a DNS query, it checks which of those Regions gives the user the lowest latency and answers with that Region's record. In AWS's own example, with load balancers in Oregon and Singapore, a user in London is sent to whichever Region currently has lower latency from London. Route 53 uses latency data measured over time, so the chosen Region can change as network conditions change.

Option A, failover routing, sends all traffic to a primary resource and switches to a secondary only when a health check shows the primary is unhealthy. It doesn't consider latency. Option C, simple routing, returns the same record for every query, with no Region selection. Option D, weighted routing, splits traffic between records in proportions you set, for example 70/30. It ignores where each user is and which Region would be faster for them.

Reference: Latency-based routing