SOA-C02 Question #481: Real Exam Question with Answer & Explanation

Question

A company has an application that runs behind an Application Load Balancer (ALB) in the us- west-2 Region. An Amazon Route 53 record set contains an alias record for app.anycompany.com that references the ALB in us-west-2 and uses a simple routing policy. The application is experiencing an increase in users from other locations in the world. These users are experiencing high latency. Most of the new users are close to the ap-southeast-2 Region. The company deploys a copy of the application to ap-southeast-2. A SysOps administrator must implement a solution that automatically routes requests to the lowest latency endpoint for users without changing the URL. Which solution will meet these requirements?

Options

• AAdd a new value to the existing alias record for app.anycompany.com with the DNS name of the
• BChange the existing alias record to use a geolocation routing policy. Create two geolocation
• CChange the existing alias record to use a latency routing policy. Create two latency records, one
• DChange the existing alias record to use a multivalue routing policy Add the DNS name of each

Explanation

Option C is correct because Route 53's latency routing policy is specifically designed to route users to the AWS Region that provides the lowest network latency - exactly what the question requires. You create two records with the same DNS name (app.anycompany.com), each pointing to the ALB in its respective Region (us-west-2 and ap-southeast-2), and Route 53 automatically directs each user to whichever endpoint responds fastest for them.

Why the distractors fail:

• A is wrong because a single alias record can only reference one endpoint; you cannot add multiple values to an alias record the way you can with standard records, and simple routing doesn't consider latency at all.
• B (Geolocation) is wrong because geolocation routes by where the user is physically located, not by which endpoint is actually faster - a user in Southeast Asia could still have lower latency to us-west-2 in edge cases, and unmatched locations fall through to a default or return no answer.
• D (Multivalue) is wrong because multivalue routing returns up to 8 healthy records and lets the client pick randomly - it has no latency awareness and is essentially a basic health-checked round-robin.

Memory tip: Match the key phrase in the question to the policy name - "lowest latency endpoint" → Latency routing. If the question said "route European users to Europe," that would be Geolocation. The exam almost always telegraphs the right policy in the requirement wording.

No community discussion yet for this question.