AWS Certified CloudOps Engineer Associate SOA-C03 Practice Question

Latency-based routing selects the record whose Region gives the client the lowest RTT. By creating two latency alias A records-one that targets the us-east-1 ALB and another that targets the eu-west-1 ALB-clients are sent to the fastest Region. Enabling Evaluate Target Health on each alias makes Route 53 stop returning the record when the underlying ALB reports itself unhealthy, causing all queries to fail over to the other Region until the load balancer is healthy. A pure failover policy satisfies resiliency but not latency distribution. Weighted routing distributes traffic but ignores latency. Geolocation approximates location-based routing and does not guarantee the lowest latency for every user.