Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 582 discussion

The key reasons are: Geolocation routing allows you to route users to the closest endpoint based on their geographic location. This will provide the lowest latency. Routing us-west-1 traffic to the on-premises data center minimizes latency for those users since it is also located near there. Routing eu-central-1 traffic to the eu-central-1 AWS region minimizes latency for users nearby. This achieves routing users to the closest endpoint on a geographic basis to optimize for low latency.

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-geo.html B can be done but definition of "near" is ambiguous C wrong region D wrong solution as splitting evenly does not reduce latency for on-prem server users

not C. Client do not have AWS us-west-1 region. Client have a on prem DC near west-1 not D. 2 people visit the site together near eu-central-1, one of the user may be thrown to west-1 due to load balancing on split even weighted policy. A and B are both valid, latency = how soon user reach the datacenter and received a responses from the DC, round trip. So in short, geolocation or send user to the nearest DC will improve latency.

Geolocation routing policy allows you to route traffic based on the location of your users.

C. Set up a latency routing policy. Associate the policy with us-west-1. Explanation: A latency routing policy directs traffic based on the lowest network latency to the specified AWS endpoint. Since the on-premises data center is near the us-west-1 Region, associating the policy with us-west-1 ensures that users near that region will be directed to the on-premises data center. This allows for optimal routing, minimizing the load time for users based on their geographical proximity to the respective hosting locations (us-west-1 and eu-central-1). Options A, B, and D do not explicitly consider latency or are not optimal for minimizing load time: Option A (geolocation routing policy) would direct traffic based on the geographic location of the user but may not necessarily optimize for the lowest latency.

except I don't think that it should be applied to the west region. If Geolocation is applied and the west is closer to the client, but the west is having intermittent issues at the time, they will have a longer latency even though closer to that region. this is why I would apply latency in a real world solution.

in real world I think it should use latency routing if the main concern is to lower the latency but AWS likes to promote geolocation and if that is in the question I think that will be the answer so I choose A.

The company wants to minimize load time for the website as much as possible… between data Centre and website or between users and website?

Geolocation is the key word

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-geo.html