An ecommerce company uses Amazon Route 53 as its DNS provider. The company hosts its website on premises and in the AWS Cloud. The company's on-premises data center is near the us-west-1 Region. The company uses the eu-central-1 Region to host the website. The company wants to minimize load time for the website as much as possible. Which solution will meet these requirements?

The correct solution is to set up a geolocation routing policy. This policy type allows you to route traffic based on the geographic location of your users. By directing users near us-west-1 to the nearby on-premises data center and users near eu-central-1 to the AWS resources in eu-central-1, the company minimizes latency and improves load times for both user groups. A simple routing policy would not provide the desired geographic-based traffic distribution. A latency routing policy would route all traffic to the endpoint with the lowest latency, which might not always be the geographically closest or desired endpoint for all users, especially with distinct on-premises and cloud deployments. A weighted routing policy distributes traffic based on assigned weights, not user location, and would not guarantee optimal latency for geographically dispersed users.