A company hosts its web application at the zone apex (`example.com`). The application is deployed behind Application Load Balancers (ALBs) in two AWS Regions: `us-east-1` and `eu-west-1`. A SysOps Administrator must configure Amazon Route 53 to route user traffic to the region that provides the lowest network latency. The solution must support automated failover to the other region if the local ALB becomes unhealthy. Which two Route 53 configurations should the SysOps Administrator implement to meet these requirements?
- Create Latency routing Alias A records for `example.com` pointing to the ALB DNS name in each AWS Region.Cevap
- Configure the Evaluate Target Health setting to Yes on the created Alias records.Cevap
- CCreate Latency routing CNAME records for `example.com` pointing to the ALB DNS name in each AWS Region.
- DCreate Failover routing Alias A records for `example.com` with the `us-east-1` ALB as primary and the `eu-west-1` ALB as secondary.
- ECreate Geolocation routing Alias A records for `example.com` pointing to the ALB DNS name in each AWS Region.
Cevap
Create Latency routing Alias A records for the zone apex pointing to the ALB DNS names, and configure the Evaluate Target Health setting to Yes on these Alias records.
To route traffic based on network latency for a zone apex domain, the administrator must use Latency routing Alias A records. Unlike CNAME records, Alias records can be used at the zone apex. Additionally, to support automatic failover, the Evaluate Target Health property must be set to Yes on these Alias records, which leverages ALB health checks to determine resource availability.
Adım Adım Çözüm
Anahtar Kavram
Route 53 Latency routing combined with Alias records and Evaluate Target Health at the zone apex.
Tahmini Süre:1m 30s