Q58 — AWS SAA-C03 Ch.16

Question 58 of 100 | ← Chapter 16

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

• A. Create a DNS record with a failover routing policy that routes all primary traffic to eu-central-1.Configure the routing policy to use the on-premises data center as the secondary location.
• B. Create a DNS record with an IP-based routing policy. Configure specific IP ranges to return the value for the eu-central-1 website. Configure all other IP ranges to return the value for the on-premises website.
• C. Create a DNS record with a latency-based routing policy. Associate the record for the on-premises data center with us-west-1. ✓
• D. Create a DNS record with a weighted routing policy. Split the traffic evenly between eu-central-1 and the on-premises data center.

Correct Answer: C. Create a DNS record with a latency-based routing policy. Associate the record for the on-premises data center with us-west-1.

Explanation

The correct answer is C. Create a DNS record with a latency-based routing policy. Associate the record for the on-premises data center with us-west-1.Explanation:The company wants to optimize website load times by routing users to the nearest (lowest-latency) endpoint between:On-premises (near us-west-1)AWS (eu-central-1)Latency-based routing (Route 53) automatically directs users to the endpoint with the lowest network latency for their location.Why Option C is Correct:Latency-based routing measures response times from AWS regions (or associated on-premises locations) and routes traffic accordingly.Associating the on-premises endpoint with us-west-1 allows Route 53 to treat it as a virtual "region" for latency calculations.Optimizes user experience by minimizing latency (faster load times). No traffic splitting or manual IP-based rules--fully automated based on real-time latency.Why the Other Options Are Incorrect:A. Failover routing policy (primary: eu-central-1, secondary: on-premises) Designed for high availability, not performance optimization. Does not consider latency--users may be routed to a slower endpoint. B. IP-based routing policy (specific IP ranges eu-central-1, others on-premises) Static and inflexible--does not adapt to real-time network conditions.Hard to maintain (IP ranges change frequently).May route users to a higher-latency endpoint.D. Weighted routing policy (split traffic 50/50)Distributes traffic evenly, ignoring latency.Some users will experience higher latency, degrading performance. Alternative Consideration (If On-Premises Isn't in Route 53):If the on-premises endpoint cannot be directly associated with us-west-1 in Route 53, another approach could be:Use Amazon CloudFront with origin failover (primary: eu-central-1, secondary: on-premises). However, Option C is the most straightforward Route 53-native solution for latency optimization.Conclusion:Option C is the best choice because:Latency-based routing dynamically selects the fastest endpoint. Associating on-premises with us-west-1 allows Route 53 to include it in latency calculations. Improves load times for all users by minimizing network delay.Final Answer:C