Examkin

Question

Difficulty: HardAmazon Route 53 DNS Configuration and Routing Policies

A company hosting its main corporate portal at the zone apex (corporateportal.com) needs to implement an active-passive disaster recovery strategy. The primary infrastructure is fronted by an Application Load Balancer (ALB) in the us-east-1 Region, and the secondary disaster recovery site is fronted by an ALB in the us-west-2 Region. The DNS configuration must ensure that user traffic is automatically directed to the standby site only when the primary ALB or its registered targets become unhealthy. Which configuration should a SysOps Administrator implement to meet these requirements?

  1. Create primary and secondary Alias records for the zone apex (corporateportal.com) using the Failover routing policy. Point the primary record to the us-east-1 ALB and the secondary record to the us-west-2 ALB. Set "Evaluate Target Health" to Yes for both records.Answer
  2. B
    Create primary and secondary CNAME records for the zone apex (corporateportal.com) using the Failover routing policy. Point the primary record to the DNS name of the us-east-1 ALB and the secondary record to the DNS name of the us-west-2 ALB. Associate a Route 53 health check with the primary record.
  3. C
    Create primary and secondary Alias records for the zone apex (corporateportal.com) using the Failover routing policy. Point the primary record to the us-east-1 ALB and the secondary record to the us-west-2 ALB. Set "Evaluate Target Health" to No for both records, and rely on the ALB target groups' health checks to trigger Route 53 failover.
  4. D
    Create primary and secondary Alias records for the zone apex (corporateportal.com) using the Weighted routing policy. Set the weight of the primary record pointing to the us-east-1 ALB to 100, and the weight of the secondary record pointing to the us-west-2 ALB to 0. Disable "Evaluate Target Health" to prevent unnecessary DNS lookups.

Answer

Create primary and secondary Alias records for the zone apex (corporateportal.com) using the Failover routing policy, pointing to the respective ALBs, with "Evaluate Target Health" set to Yes for both records.
Creating Alias records at the zone apex with a Failover routing policy and enabling 'Evaluate Target Health' allows Route 53 to automatically redirect traffic to the standby ALB when the primary ALB or its targets are detected as unhealthy.

Step-by-Step Solution

1
Evaluate the zone apex requirements
Identify that a CNAME record cannot be used at the zone apex (corporateportal.com) due to DNS RFC limitations, making Route 53 Alias records necessary.
Alias records allow mapping the zone apex to AWS resources like Application Load Balancers directly without violating DNS standards.
2
Select the appropriate routing policy
Choose the Failover routing policy to establish an active-passive configuration.
Failover routing directs traffic to a primary resource when it is healthy, and to a secondary standby resource when the primary is unhealthy.
3
Configure health checking for the Alias records
Enable 'Evaluate Target Health' on both the primary and secondary Alias records.
Enabling 'Evaluate Target Health' allows Route 53 to check the health of the Application Load Balancer and its registered targets automatically, triggering failover when the primary becomes unhealthy.

Key Concept

Configuring Route 53 Failover Routing Policies with Alias records at the zone apex
Estimated Time:2m 0s
Rate this question

Topics

Amazon Route 53 DNS Configuration and Routing Policies

More questions from this topic