A weather tracking system is designed to track weather conditions of any particular flight route. Flight travellers all over the world make use of this information prior to booking their flights. Travellers expect quick turnaround time in which the weather display & flight booking will happen which is critical to their business. You have designed this website and are using AWS Route 53 DNS. The routing policy that you will apply to this website is

Answer options:

A.GeoLocation routing policy
B.Failover routing policy
C.Multivalueanswer routing policy
D.Latency based routing policy

Answer: D
On reading the scenario carefully, we can see here that the website`s performance is of prime importance to its users. It gives them a lot of business value, enabling them to choose their flight paths and make flight bookings on time. So, “Latency based routing” is the best answer to this scenario.
Option A is incorrect because GeoLocation routing is often used to localize content and present the website in the language of its users. Geolocation routing lets you choose the resources that serve your traffic based on your users` geographic location, meaning the location that DNS queries originate from. For example, you might want all queries from Europe to be routed to an ELB load balancer in the Frankfurt region irrespective of latency in that region.
Option B is incorrect because Failover routing is usually used in Disaster Recovery scenarios where an Active-Passive Disaster recovery configuration is present & the Passive resource that was originally the Backup resource has now become the Active resource due to the original Active resource being unhealthy.
Option C is incorrect sinceMultivalve answer routing provides the ability to return multiple health-checkable IP addresses which is a way to use DNS to improve availability and load balancing.
Option D is CORRECT since Latency based routing always routes DNS queries to the best performing website (region) irrespective of what happens in the Amazon infrastructure, Internet. Going back to our scenario, if we have ELB load balancers in the US West (Oregon) region and the Asia Pacific(Mumbai) region for the Weather tracking & Airline Ticketing website and if a user from London enters the name of your domain in a browser, the following things will happen:
DNS routes the query to a Route 53 name server.
Route 53 refers to its data on latency between London and the Mumbai region and between London and the Oregon region.
If latency is lower between the London and Oregon regions, Route 53 responds to the query with the Oregon load balancer`s IP address. If latency is lower between London and the Mumbai region, Route 53 responds with the Mumbai load balancer`s IP address.
References:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-latency
https://youtu.be/BtiS0QyiTK8