AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
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?
Other
Community
UAnonymous
A
Set up a geolocation routing policy. Send the traffic that is near us-west-1 to the on-premises data center. Send the traffic that is near eu-central-1 to eu-central-1.
B
Set up a simple routing policy that routes all traffic that is near eu-central-1 to eu-central-1 and routes all traffic that is near the on-premises datacenter to the on-premises data center.
C
Set up a latency routing policy. Associate the policy with us-west-1.
D
Set up a weighted routing policy. Split the traffic evenly between eu-central-1 and the on-premises data center.
Explanation:
Explanation
Correct Answer: A
Why Option A is correct:
- Geolocation routing policy routes traffic based on the geographic location of users (where DNS queries originate).
- This allows the company to send traffic from users near us-west-1 to the on-premises data center, and traffic from users near eu-central-1 to the AWS eu-central-1 Region.
- By directing users to the geographically closest endpoint, this minimizes network latency and thus load time.
Why other options are incorrect:
Option B: Simple routing policy doesn't consider geographic proximity. It would route all traffic to a single endpoint or use round-robin, not based on user location.
Option C: Latency routing policy routes traffic to the endpoint with the lowest network latency, but the description "Associate the policy with us-west-1" is incomplete. Latency routing requires measuring latency from multiple endpoints and doesn't specifically target geographic regions.
Option D: Weighted routing policy splits traffic based on assigned weights, not based on geographic proximity. This would send traffic to both endpoints regardless of user location, potentially increasing load time for distant users.
Key AWS Concepts:
- Geolocation routing: Routes traffic based on user's geographic location
- Latency routing: Routes traffic to the endpoint with the lowest latency
- Simple routing: Basic routing to a single resource or round-robin
- Weighted routing: Splits traffic based on assigned weights
This solution directly addresses the requirement to minimize load time by directing users to the geographically closest endpoint.
Comments
Loading comments...