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.)
- 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.Cevap
- 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.Cevap
- CCreate 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.
- DCreate 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.
- ECreate 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.
Cevap
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.
Adım Adım Çözüm
Anahtar Kavram
Routing zone apex traffic using Route 53 Alias records and Latency routing policies.
Tahmini Süre:2m 0s