An online global game currently serves players from servers in us-west-2 behind an Elastic Load Balancer. To reduce latency, the company will deploy game servers to 11 more AWS Regions. How should the network engineer configure Amazon Route 53 so that players are routed to the game servers that give the best responsiveness?

The correct answer is to use a latency routing policy. This policy routes users to the AWS Region that provides the lowest latency for the user, which directly addresses the goal of reducing latency and ensuring the best responsiveness for players. Route 53 performs latency measurements between viewer networks and AWS Regions to determine the optimal endpoint. Weighted routing is incorrect because it distributes traffic based on predefined weights, not real-time latency, and calculating weights by client count doesn't guarantee the best responsiveness. Multivalue answer routing returns up to eight healthy records, and while the client could test latency, Route 53's latency policy handles this more efficiently at the DNS level. Geolocation routing directs users based on their geographic location, which might not always correspond to the lowest latency, especially for users near regional borders or with complex network paths.