A company is migrating its primary website at the zone apex (example.com) from an on-premises web server to an Amazon CloudFront distribution. A SysOps Administrator needs to configure Amazon Route 53 to gradually shift 10% of the traffic to the CloudFront distribution, while keeping 90% of the traffic routed to the on-premises web server's public IP address. Which two configurations should the administrator use to achieve this? (Select TWO.)
- Create a Weighted A record for the zone apex (example.com) with a weight of 90, targeting the on-premises web server's public IP address.Cevap
- Create a Weighted Alias A record for the zone apex (example.com) with a weight of 10, targeting the CloudFront distribution domain name.Cevap
- CCreate a Weighted CNAME record for the zone apex (example.com) with a weight of 10, targeting the CloudFront distribution domain name.
- DCreate a Weighted CNAME record for the zone apex (example.com) with a weight of 90, targeting the on-premises web server's public IP address.
- ECreate a Failover routing policy for the zone apex (example.com), specifying the on-premises server as the primary target with a failover threshold of 90%.
Cevap
To gradually shift traffic at the zone apex, create a Weighted A record targeting the on-premises server's IP address with a weight of 90, and a Weighted Alias A record targeting the CloudFront distribution with a weight of 10.
To route traffic to the zone apex (example.com) while splitting traffic, the administrator must use A records. Since the CloudFront distribution uses a domain name, Route 53 Alias A records must be used for the zone apex because CNAME records are not allowed at the zone apex. The on-premises server uses a static IP address, so a standard A record is appropriate. By setting both as Weighted records with weights of 90 and 10, the traffic is split accordingly.
Adım Adım Çözüm
Anahtar Kavram
Using Weighted Routing Policies and Alias Records at the Zone Apex
Tahmini Süre:1m 30s