A global multi-Region deployment exists for production services. The administrator needs to route traffic according to the geographic location of the resources. Which Route 53 routing policy should be used to steer traffic based on resource locations?

The Geoproximity routing policy routes traffic based on the geographic location of users and resources. You can optionally bias traffic towards a specific resource or away from it by configuring a "bias" value. This is ideal for a global multi-Region deployment where traffic needs to be steered according to resource locations. Geolocation routing policy routes traffic based on the geographic location of the user's DNS query, not the resource itself, and doesn't allow for biasing. Latency-based routing policy routes traffic to the resource that provides the lowest latency for the user, which might not align with the desired geographic distribution of resources. Multivalue answer routing policy returns up to eight healthy records, which isn't designed for location-based traffic steering.