Amazon Route 53 Routing Policy for Preferential Web Server Selection in Multiple Regions

Preferential Routing Policy

Question

An IT firm has a web server deployed in the us-east-1 region which caters to web traffic for all users in North America.

Recently they have added a new high-performance web server in the us-west-1 region.

As per instructions from the IT manager, a new web server deployed at the us-west-1 region should be preferred by most of the users, but it should not incur additional latency to users. Which Amazon Route 53 routing policy can be implemented to meet this requirement?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Correct Answer: A.

Geoproximity routing policy routes traffic to a resource based upon user and resource location.

It uses bias value to determine the geographical area from which user traffic will be routed to a resource.

For the above case, a Geoproximity routing policy can be implemented, and bias needs to be adjusted in such a way so that maximum users would prefer web servers in the us-west-1 region without much impact on latency.

Option B is incorrect as the Geolocation routing policy will consider user location while routing traffic to web servers.

It would not prefer a particular web server while routing traffic.

Option C is incorrect as the latency-based routing policy will consider latency from user to web server.

It would not prefer a particular web server while routing traffic.

Option D is incorrect as with Multivalue answer routing policy, users might use any of the servers out of the two which is not as per requirement.

For more information on routing policies with Amazon Route 53, refer to the following URL,

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

To meet the requirement of having a new high-performance web server in the us-west-1 region be preferred by most users without incurring additional latency, the recommended Amazon Route 53 routing policy is the Latency-based routing policy (option C).

The Latency-based routing policy routes traffic based on the lowest network latency for the end user, which is determined by the region with the lowest latency between the end user and the web server. This policy is suitable for scenarios where the user's experience and the network latency are critical factors in the decision-making process.

In this case, the Latency-based routing policy would route users to the us-west-1 region if it has lower latency than the us-east-1 region, which would be the preferred option based on the instructions from the IT manager. However, if the latency between the end user and the us-east-1 region is lower than that of the us-west-1 region, then the policy would route the user to the us-east-1 region instead. This ensures that users are not negatively impacted by additional latency while still prioritizing the new high-performance web server in the us-west-1 region.

The other options are not suitable for this scenario.

  • Geoproximity routing policy (option A) would route traffic based on the user's geographic location and the location of the resources. However, this option does not account for latency, which is important in this case.

  • Geolocation routing policy (option B) routes traffic based on the user's geographic location, but it does not consider latency between the user and the resources.

  • Multivalue answer routing policy (option D) returns multiple IP addresses in response to DNS queries. This policy is useful when the resources are redundant and can handle the traffic load, but it does not prioritize one resource over the other based on latency.