Question

Difficulty: EasyAmazon Route 53 DNS Configuration and Routing Policies

A company is releasing a new version of its web application. The SysOps administrator wants to perform a canary deployment by routing 90%90\% of user traffic to the current production Application Load Balancer (ALB) and 10%10\% of traffic to a new ALB. Which Route 53 configuration should the administrator implement to meet these requirements?

  1. Create two Alias A records for the subdomain, both configured with the Weighted routing policy, assigning a weight of 9090 to the production ALB record and 1010 to the new ALB record.Answer
  2. B
    Create two CNAME records for the subdomain using the Simple routing policy, with one record pointing to each ALB.
  3. C
    Create two Alias A records for the subdomain, both configured with the Failover routing policy, designating the production ALB as primary and the new ALB as secondary.
  4. D
    Create a single CNAME record for the subdomain, and use weighted records within the ALB target groups to split the DNS traffic.

Answer

Create two Alias A records for the subdomain, both configured with the Weighted routing policy, assigning a weight of 9090 to the production ALB record and 1010 to the new ALB record.
The correct configuration uses the Weighted routing policy with two Alias A records. This allows the administrator to split DNS traffic in a 90:1090:10 proportion (by setting weights of 9090 and 1010). Using Alias records rather than CNAMEs is the recommended AWS best practice for mapping domains to load balancers, as they automatically update when the ALB IPs change and do not incur query charges.

Step-by-Step Solution

1
Determine the routing policy required to split traffic based on percentages (90%90\% and 10%10\%).
The Weighted routing policy is selected because it enables routing traffic to multiple resources in user-specified proportions.
Other routing policies like Simple or Failover do not support percentage-based distribution.
2
Select the appropriate record type for the Application Load Balancers.
Alias A records are chosen because they map directly to AWS resources (like ALBs) and are automatically updated when the ALB's underlying IP addresses change.
CNAME records incur standard Route 53 query charges and cannot be used at the zone apex.
3
Configure the weights for the two records.
Assign a weight of 9090 to the record pointing to the production ALB and a weight of 1010 to the record pointing to the new ALB.
This mathematically splits the traffic at a 9:19:1 ratio, corresponding to the required 90%90\% and 10%10\% distribution.

Key Concept

Weighted routing policy and Alias records in Route 53
Rate this question