Examkin

Question

Difficulty: Very hardAmazon Route 53 DNS Configuration and Routing Policies

A SysOps administrator must configure DNS for a global web application hosted at the zone apex domain (example.com). The application is deployed across two AWS Regions: a primary active stack in us-east-1 fronted by an Application Load Balancer (ALB), and a passive disaster recovery (DR) stack in us-west-2 fronted by another ALB. The administrator must implement an active-passive failover configuration that automatically redirects all traffic to the DR stack if the primary ALB or its backend targets become unhealthy. Which two Route 53 configuration steps should the administrator implement to meet these requirements? (Select TWO.)

  1. Create an Alias record at the zone apex (example.com) pointing to the ALB in us-east-1 with a Failover routing policy, set the Failover Record Type to Primary, and enable Evaluate Target Health.Answer
  2. Create an Alias record at the zone apex (example.com) pointing to the ALB in us-west-2 with a Failover routing policy, set the Failover Record Type to Secondary, and enable Evaluate Target Health.Answer
  3. C
    Create a CNAME record at the zone apex (example.com) pointing to the DNS name of the ALB in us-east-1 with a Failover routing policy, set the Failover Record Type to Primary.
  4. D
    Create an Alias record at the zone apex (example.com) pointing to the ALB in us-east-1 with a Failover routing policy, set the Failover Record Type to Primary, and disable Evaluate Target Health.
  5. E
    Create two Latency routing policy Alias records for the zone apex (example.com) pointing to the respective ALBs in us-east-1 and us-west-2, and define a default failover target.

Answer

Create an Alias record at the zone apex pointing to the primary ALB in us-east-1 using a Failover routing policy (Primary) and enable Evaluate Target Health, and create a corresponding Alias record pointing to the secondary ALB in us-west-2 (Secondary) with Evaluate Target Health enabled.
The correct configuration requires creating two Failover routing policy Alias records at the zone apex pointing to the respective Application Load Balancers. The record pointing to the primary ALB in us-east-1 must be set as Primary, while the record pointing to the DR ALB in us-west-2 must be set as Secondary. In both records, 'Evaluate Target Health' must be set to Yes so Route 53 can dynamically monitor the health of the backend targets and automatically shift traffic if the primary region fails.

Step-by-Step Solution

1
Select the zone apex domain within the Route 53 hosted zone and choose to create a new record.
Initiates the DNS record creation process for the base domain without subdomains.
The requirement specifically specifies hosting at the zone apex (example.com).
2
Configure an Alias record pointing to the Application Load Balancer in the primary region (us-east-1).
Routes zone apex traffic directly to the AWS ALB resource without incurring standard DNS query costs or violating DNS specs.
Zone apex domains cannot use CNAME records; Route 53 Alias records must be used.
3
Set the routing policy to Failover, configure the us-east-1 record as Primary, and set Evaluate Target Health to Yes.
Enables Route 53 to automatically monitor the health of the ALB's target groups and designate this as the default path.
Allows Route 53 to detect target failures and trigger failover to the standby region.
4
Create a second Alias record at the zone apex pointing to the ALB in us-west-2, configure the routing policy to Failover, set it as Secondary, and set Evaluate Target Health to Yes.
Establishes the passive failover destination that receives traffic only when the primary region is unhealthy.
Completes the active-passive failover configuration.

Key Concept

Route 53 Failover Routing with Alias Records at the Zone Apex
Rate this question

Topics

Amazon Route 53 DNS Configuration and Routing Policies

More questions from this topic