AWS Certified Solutions Architect Professional SAP-C02 Practice Question

The correct answer is that the affected users are likely using DNS resolvers geographically based in North America. Amazon Route 53's latency-based routing determines the lowest latency path from the source of the DNS query, which is the user's DNS resolver, not necessarily the user's actual physical location. If a user in Australia is using a corporate VPN that routes DNS queries through a North American gateway, or a public DNS service like Google DNS (8.8.8.8) that might resolve from a location in the US, Route 53 will correctly determine that us-east-1 provides the lowest latency from the resolver's perspective and route the traffic there.

Incorrect Answers:

• Assigning a lower weight to the ap-southeast-2 records is incorrect because 'weight' is a parameter for Weighted routing policies, not Latency routing policies. These are distinct policy types and do not influence each other in this way.
• The idea that AWS lacks sufficient latency data from Australia is incorrect. AWS maintains a comprehensive, long-standing database of latency information from across the internet to its global regions. Route 53 would not default to a specific region like us-east-1 due to a lack of data.
• A Geolocation policy taking precedence is a plausible but less likely scenario. Geolocation routing and Latency routing are different policies. While complex configurations are possible, the most direct and common cause for the described symptoms is the location of the DNS resolver used by the clients.