Q28 — AWS SAA-C03 Ch.10

Question 28 of 100 | ← Chapter 10

Q628. A company wants to direct its users to a backup static error page if he 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 actve-active configuration with the ALB and an Amazon EC2 instance that hosts a static error page as endpoints. Configure Route 53to 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

Correct Answer: 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

Explanation

To meet the requirements of directing users to a backup static error page when the primary website is unavailable while minimizing changes and infrastructure overhead, the most suitable solution would be: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. Option B provides a simple and efficient solution to direct users to a backup static error page when the primary website is unavailable. Here's how it works:\1. Set up a Route 53 active-passive failover configuration: This configuration allows you to define a primary endpoint (the ALB) and a secondary endpoint (the static error page hosted in an S3 bucket). \2. Route 53 health checks: Configure health checks for the ALB. Route 53 will periodically check the health of the ALB endpoint.\3. Direct traffic to the static error page: When Route 53 health checks determine that the ALB endpoint is unhealthy, Route 53 will automatically direct traffic to the secondary endpoint, which is the static error page hosted in the S3 bucket. This ensures that users are served the error page when the primary website is unavailable.Option A is not the best choice:A. Using a latency routing policy and adding a static error page hosted in an S3 bucket to the Route 53 records would not directly handle the scenario of the primary website being unavailable. The latency routing policy is used to direct traffic to the most responsive endpoints based on latency, but it doesn't address the failover requirement.Option C is not the best choice either:C. Setting up a Route 53 active-active configuration with the ALB and an EC2 instance hosting a static error page as endpoints would introduce additional infrastructure overhead and complexity. It would require managing and maintaining an EC2 instance solely for hosting the static error page, which is not necessary for the given requirements.Option D is not the best choice either:D. Using a multivalue answer routing policy and creating a health check to direct traffic to the website or the static error page based on the health check result would require more manual configuration and maintenance. It would involve setting up and managing the health check, and the multivalue answer routing policy may not be the most efficient solution for this specific scenario. Therefore, the most suitable solution for directing users to a backup static error page when the primary website is unavailable, while minimizing changes and infrastructure overhead, is to set up a Route 53 active-passive failover configuration and direct traffic to a static error page hosted in an S3 bucket when Route 53 health checks determine that the ALB endpoint is unhealthy (option B).