Examkin

Question

Difficulty: MediumRoute 53 Routing Policies and DNS Failover Strategies

A company hosts a critical e-commerce web application at the apex domain `example.com`. The primary infrastructure is deployed behind an Application Load Balancer (ALB) in the `us-east-1` Region. To implement a disaster recovery plan, the company deploys a warm standby version of the application behind another ALB in the `us-west-2` Region. The company wants to configure Amazon Route 53 to route all traffic to `us-east-1` under normal conditions and automatically fail over to `us-west-2` if the primary application becomes unhealthy.

Which TWO configuration steps must a solutions architect take in Route 53 to meet these requirements? (Select TWO.)

  1. Create a Failover Alias record for the apex domain pointing to the primary ALB, configure it as Primary, and set Evaluate Target Health to Yes.Answer
  2. Create a Failover Alias record for the apex domain pointing to the standby ALB, configure it as Secondary, and set Evaluate Target Health to Yes.Answer
  3. C
    Create a CNAME record for the apex domain pointing to the DNS name of the primary ALB, and configure a secondary CNAME record with a Failover policy pointing to the standby ALB.
  4. D
    Create Latency Alias records pointing to both ALBs, and configure Route 53 to route 100% of the traffic to the primary region during normal operations.
  5. E
    Create a Failover record for the primary ALB, and configure a Route 53 health check that monitors the RDS PostgreSQL read replica in us-west-2 to trigger failover upon database promotion.

Answer

To configure active-passive failover at the apex domain, create a primary Failover Alias record pointing to the primary ALB, and a secondary Failover Alias record pointing to the standby ALB. For both records, set 'Evaluate Target Health' to 'Yes' to enable automatic health evaluation of the ALBs.
To set up active-passive failover for an apex domain pointing to Application Load Balancers, Route 53 requires two Failover Alias records (one Primary and one Secondary) sharing the same record name. The apex domain (example.com) cannot use CNAME records due to DNS specifications, so Alias records must be used. Setting 'Evaluate Target Health' to Yes on these Alias records allows Route 53 to automatically inherit the health status of the load balancers without requiring manual health check configurations.

Step-by-Step Solution

1
Select the apex domain in the Route 53 hosted zone and create a new record set.
A record set configuration window is opened for the zone apex (example.com).
The apex domain requires direct configuration of Alias records since CNAME records cannot exist at the zone apex.
2
Configure the primary record as an Alias to the primary Application Load Balancer in us-east-1, set the routing policy to Failover, select Primary as the failover type, and enable 'Evaluate Target Health'.
The primary record is configured to route all traffic to the us-east-1 ALB under normal operating conditions and monitor its health.
This establishes the active path and ensures Route 53 is aware of the health of the primary region's ALB.
3
Configure the secondary record as an Alias to the standby Application Load Balancer in us-west-2, set the routing policy to Failover, select Secondary as the failover type, and enable 'Evaluate Target Health'.
The secondary record is configured to receive traffic only when the primary record is determined to be unhealthy.
This establishes the passive failover path to the warm standby region when the primary region is unavailable.

Key Concept

Route 53 active-passive DNS failover configuration at the zone apex requires Primary and Secondary Failover Alias records pointing to the respective regional resources, with health evaluation enabled.
Estimated Time:2m 0s
Rate this question

Topics

Route 53 Routing Policies and DNS Failover Strategies

More questions from this topic