A regional health department publishes the same API in two Regions and wants citizens steered toward the healthier, lower-latency endpoint. Which Route 53 approach fits?
Select an answer to reveal the explanation.
Short Explanation
Send folks to the clinic line that’s both nearby and actually open. Latency-based Route 53 routing plus health checks does that for regional API endpoints.
Full Explanation
Route 53 latency-based routing directs clients to the Region endpoint with the lowest measured latency, and health checks avoid unhealthy targets. A permanent single simple record or static weights ignore latency and health. Hardcoded Region URLs bypass DNS failover. For multi-Region civic APIs, latency-based routing with health checks improves reliability and user experience.