Examkin

Question

Difficulty: MediumAmazon Route 53 DNS Configuration and Routing Policies

A SysOps Administrator is configuring Amazon Route 53 to route traffic for a company's apex domain (example.com) to a REST API. The API is deployed as regional API Gateway endpoints in both the us-east-1 and us-west-2 Regions. The administrator wants to route client requests to the region that provides the lowest network latency. Which two configurations must the SysOps Administrator implement to meet these requirements? (Select TWO.)

  1. Create an Alias A record for example.com using the Latency routing policy, specifying the us-east-1 Region, and pointing to the API Gateway regional custom domain name in us-east-1.Answer
  2. Create an Alias A record for example.com using the Latency routing policy, specifying the us-west-2 Region, and pointing to the API Gateway regional custom domain name in us-west-2.Answer
  3. C
    Create a CNAME record for example.com using the Latency routing policy, specifying the us-east-1 Region, and pointing to the API Gateway regional custom domain name in us-east-1.
  4. D
    Create a CNAME record for example.com using the Latency routing policy, specifying the us-west-2 Region, and pointing to the API Gateway regional custom domain name in us-west-2.
  5. E
    Create a Failover routing policy configuration with a primary Alias A record pointing to the API Gateway custom domain in us-east-1 and a secondary Alias A record pointing to us-west-2.

Answer

Create an Alias A record for example.com using the Latency routing policy, specifying the us-east-1 Region, and pointing to the API Gateway regional custom domain name in us-east-1; and create an Alias A record for example.com using the Latency routing policy, specifying the us-west-2 Region, and pointing to the API Gateway regional custom domain name in us-west-2.
To route requests to the nearest API Gateway endpoint for the zone apex (example.com), you must create Route 53 Alias A records using the Latency routing policy. Standard CNAME records cannot be configured at the zone apex because the apex requires SOA and NS records, which cannot coexist with a CNAME record under DNS standards. Alias records solve this by mapping the apex directly to the regional API Gateway endpoints without violating DNS specs.

Step-by-Step Solution

1
Determine the DNS record requirements for the zone apex (example.com).
Identify that a CNAME record cannot be used at the zone apex due to DNS RFC limitations.
The zone apex must possess SOA and NS records, and standard DNS rules dictate that a CNAME record cannot share the same name as other record types.
2
Select the correct Route 53 record type to bypass this limitation.
Choose Route 53 Alias A records.
Alias records allow you to map the zone apex to select AWS resources, such as regional API Gateway endpoints, while presenting them as A records to DNS clients.
3
Apply the required routing policy for network performance.
Configure Latency-based routing for both regions.
This configuration allows Route 53 to measure round-trip times from users to each region and resolve queries to the endpoint offering the shortest latency.

Key Concept

Routing zone apex traffic using Route 53 Alias records and Latency routing policies.
Estimated Time:2m 0s
Rate this question

Topics

Amazon Route 53 DNS Configuration and Routing Policies

More questions from this topic