Questions 4 to 6

Explanations for questions 4 to 6

We'll cover the following

Question 4

A website runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The website’s DNS records are hosted in Amazon Route 53 with the domain name pointing to the ALB. A solution is required for displaying a static error page if the website becomes unavailable.

Which configuration should a solutions architect use to meet these requirements with the least operational overhead?

  1. Create a Route 53 Alias record for an Amazon CloudFront distribution, and specify the ALB as the origin. Create custom error pages for the distribution.
  2. Create a Route 53 active-passive failover configuration. Create a static website using an Amazon S3 bucket that hosts a static error page. Configure the static website as the passive record for failover.
  3. Create a Route 53 weighted routing policy. Create a static website using an Amazon S3 bucket that hosts a static error page. Configure the record for the S3 static website with a weighting of zero. When an issue occurs, increase the weighting.
  4. Set up a Route 53 active-active configuration with the ALB and an Amazon EC2 instance hosting a static error page as endpoints. Route 53 will only send requests to the instance if the health checks fail for the ALB.

Correct Answer: 1

Explanation: Using Amazon CloudFront as the front-end provides the option to specify a custom message instead of the default message. To specify the file that you want to return and the errors for which the file should be returned, you need to update your CloudFront distribution to specify those values.

For example, the following is a customized error message:

Level up your interview prep. Join Educative to access 70+ hands-on prep courses.