Examkin

Question

Difficulty: MediumRoute 53 DNS Failover

A company hosts its primary web application using an Amazon Route 53 Alias record at the zone apex pointing to an Amazon CloudFront distribution. The company wants to configure an active-passive disaster recovery solution that automatically routes traffic to a secondary static backup website hosted on an Amazon S3 bucket if the primary CloudFront distribution becomes unavailable. During configuration, the SysOps Administrator observes that the 'Evaluate Target Health' option is not supported for the CloudFront Alias record.

Which two configuration steps must the SysOps Administrator perform to establish this failover mechanism? (Select TWO.)

  1. Create an Amazon Route 53 health check that monitors the primary website endpoint via HTTPS, and associate this health check with the primary CloudFront Alias record.Answer
  2. Create a secondary Alias A record at the zone apex pointing to the Amazon S3 static website endpoint, select the Failover routing policy, and set the Failover Record Type to Secondary.Answer
  3. C
    Create a Route 53 health check that monitors the primary website endpoint, and associate this health check with the secondary Amazon S3 Alias record.
  4. D
    Create a secondary CNAME record at the zone apex pointing to the Amazon S3 static website endpoint, select the Failover routing policy, and set the Failover Record Type to Secondary.
  5. E
    Configure a secondary Alias record pointing to an Amazon RDS Read Replica at the zone apex, and configure Route 53 to promote the Read Replica to primary when the main record becomes unhealthy.

Answer

The correct configuration requires creating a Route 53 health check to monitor the primary website endpoint and associating it with the primary CloudFront Alias record, and creating a secondary Alias A record at the zone apex pointing to the Amazon S3 static website endpoint with the Failover routing policy set to Secondary.
To configure active-passive DNS failover at the zone apex when using a CloudFront distribution as the primary endpoint, the administrator must create a Route 53 health check that directly monitors the primary endpoint and associate it with the primary Alias record (since CloudFront does not support the 'Evaluate Target Health' option). Additionally, the secondary record must be an Alias A record pointing to the S3 bucket website endpoint because CNAME records are not permitted at the zone apex.

Step-by-Step Solution

1
Analyze the Route 53 Alias record constraints for CloudFront distributions.
Recognize that 'Evaluate Target Health' is not supported for CloudFront distribution targets.
Determines that a custom Route 53 health check must be created to monitor the primary application endpoint.
2
Define the routing policy and record type for the primary and secondary endpoints.
Assign the Failover routing policy to both records, configuring the primary record as Primary and the secondary record as Secondary.
Establishes the active-passive relationship between the main site and the backup site.
3
Select the correct DNS record type for the zone apex.
Configure an Alias A record for the S3 static website endpoint instead of a CNAME.
Ensures compliance with DNS specifications, which prohibit CNAME records at the zone apex.

Key Concept

Route 53 Active-Passive Failover with CloudFront and S3 at the Zone Apex
Rate this question

Topics

Route 53 DNS Failover

More questions from this topic