Examkin

Question

Difficulty: EasyRoute 53 Routing Policies and DNS Failover Strategies

A company wants to configure an active-passive disaster recovery strategy for its web portal. The primary website is hosted behind an Application Load Balancer (ALB) in the us-east-1 Region. If the ALB becomes unhealthy, all traffic must be redirected automatically to a backup static maintenance site hosted on an Amazon S3 website endpoint in the us-west-2 Region. Which configurations must the Solutions Architect implement in Amazon Route 53 to achieve this behavior? (Select TWO.)

  1. Create an Alias A record for the portal domain pointing to the Application Load Balancer, configure it with a Failover routing policy as the Primary record, and enable Evaluate Target Health.Answer
  2. Create an Alias A record for the portal domain pointing to the Amazon S3 website endpoint, and configure it with a Failover routing policy as the Secondary record.Answer
  3. C
    Create a standard CNAME record for the portal domain pointing to the Application Load Balancer DNS name, configure it with a Failover routing policy, and enable Evaluate Target Health.
  4. D
    Create Latency routing records for both the Application Load Balancer and the S3 website endpoint to automatically reroute traffic during latency spikes.
  5. E
    Create a secondary DNS record pointing directly to an Amazon RDS Read Replica in us-west-2 to enable automated database failover.

Answer

Configure a primary Route 53 Alias A record pointing to the Application Load Balancer with a Failover policy and 'Evaluate Target Health' enabled, and configure a secondary Route 53 Alias A record pointing to the Amazon S3 website endpoint with a Failover policy.
To set up active-passive failover to a static website on Amazon S3, you must use Route 53 Failover routing. The primary record must point to the Application Load Balancer using an Alias A record with 'Evaluate Target Health' enabled so that Route 53 can detect load balancer unhealthiness. The secondary record must be an Alias A record pointing to the S3 bucket website endpoint configured as a secondary failover target.

Step-by-Step Solution

1
Configure the primary DNS entry using an Alias record.
An A record with an Alias to the ALB is created.
Alias records are required to map the zone apex or domain name directly to AWS resources like ALBs and enable Route 53's 'Evaluate Target Health' feature.
2
Set up health check monitoring for the primary record by enabling Evaluate Target Health.
Route 53 automatically tracks the health of the ALB and its targets.
Enabling 'Evaluate Target Health' allows Route 53 to inherit the health status of the ALB without needing a custom Route 53 health check configuration.
3
Configure the secondary DNS entry using an Alias record pointing to the S3 bucket website endpoint.
A secondary A record with Failover routing is established.
This record serves as the passive target, which Route 53 will resolve only when the primary target is marked unhealthy.

Key Concept

Route 53 DNS Failover allows solutions architects to implement active-passive architectures using primary and secondary records. It requires Alias records to leverage target health evaluation for AWS resources.
Rate this question

Topics

Route 53 Routing Policies and DNS Failover Strategies

More questions from this topic