Answer-first summary for fast verification
Answer: Set up a Route 53 active-passive failover configuration. Direct traffic to a static error page that is hosted in an Amazon S3 bucket when Route 53 health checks determine that the ALB endpoint is unhealthy.
## Explanation **Correct Answer: B** **Why Option B is correct:** 1. **Active-Passive Failover Configuration**: Route 53's failover routing policy is specifically designed for disaster recovery scenarios where you have a primary resource and a secondary backup resource. 2. **Health Checks**: Route 53 can monitor the health of the ALB endpoint using health checks. When the ALB becomes unhealthy, Route 53 automatically redirects traffic to the backup static error page hosted in S3. 3. **Minimizes Changes and Infrastructure Overhead**: This solution requires minimal infrastructure changes - just setting up a failover configuration in Route 53 and hosting a static error page in S3 (which is cost-effective and requires minimal management). 4. **S3 Static Website Hosting**: Amazon S3 is ideal for hosting static error pages as it's highly available, scalable, and cost-effective. **Why other options are incorrect:** **Option A (Latency Routing Policy)**: - Latency routing policy routes traffic based on the lowest network latency, not for failover scenarios. - It doesn't provide automatic failover based on health checks. - Traffic would be distributed between endpoints based on latency, not redirected only when the primary fails. **Option C (Active-Active Configuration with EC2)**: - Using an EC2 instance for a static error page adds unnecessary infrastructure overhead and costs. - EC2 instances require management (patching, scaling, monitoring) compared to S3 static hosting. - Active-active configuration would distribute traffic between both endpoints all the time, not just during failures. **Option D (Multivalue Answer Routing Policy)**: - Multivalue answer routing returns multiple values for a DNS query and can perform health checks, but it's designed for distributing traffic across multiple healthy endpoints. - It doesn't provide a true active-passive failover mechanism where traffic is directed to a backup only when the primary fails. - Clients might receive multiple IP addresses and choose randomly, which doesn't guarantee they'll reach the error page when needed. **Key AWS Concepts:** - **Route 53 Failover Routing Policy**: Designed specifically for disaster recovery scenarios with primary and secondary resources. - **S3 Static Website Hosting**: Perfect for hosting static content like error pages with high availability and low cost. - **Route 53 Health Checks**: Monitor endpoint health and trigger failover when thresholds are breached. This solution provides automatic failover with minimal infrastructure changes and operational overhead, meeting all the requirements specified in the question.
Ultimate access to all questions.
No comments yet.
Author: LeetQuiz Editorial Team
A company wants to direct its users to a backup static error page if the company's primary website is unavailable. The primary website's DNS records are hosted in Amazon Route 53. The domain is pointing to an Application Load Balancer (ALB). The company needs a solution that minimizes changes and infrastructure overhead.
Which solution will meet these requirements?
A
Update the Route 53 records to use a latency routing policy. Add a static error page that is hosted in an Amazon S3 bucket to the records so that the traffic is sent to the most responsive endpoints.
B
Set up a Route 53 active-passive failover configuration. Direct traffic to a static error page that is hosted in an Amazon S3 bucket when Route 53 health checks determine that the ALB endpoint is unhealthy.
C
Set up a Route 53 active-active configuration with the ALB and an Amazon EC2 instance that hosts a static error page as endpoints. Configure Route 53 to send requests to the instance only if the health checks fail for the ALB.
D
Update the Route 53 records to use a multivalue answer routing policy. Create a health check. Direct traffic to the website if the health check passes. Direct traffic to a static error page that is hosted in Amazon S3 if the health check does not pass.