Q65 — AWS SAP-C02 Ch.1

Question 65 of 75 | ← Chapter 1

Q140. A retail company is operating its ecommerce application on AWS.The application runs on Amazon EC2 instances behind an Application Load Balancer (ALB) The company uses an Amazon RDS DB instance as the database backend. Amazon CloudFront is configured with one origin that points to the ALB. Static content is cached.Amazon Route 53 is used to host all public zones.After an update of the application,the ALB occasionally returns a 502 status code (Bad Gateway) error. The root cause is malformed HTTP headers that are returned to the ALB. The webpage returns successfully when a solutions architect reloads the webpage immediately after the error occurs..While the company is working on the problem, the solutions architect needs to provide a custom error page instead of the standard ALB error page to visitors.Which combination of steps will meet this requirement with the LEAST amount of operational overhead? (Select TWO.)

• A. Create an Amazon S3 bucket. Configure the S3 bucket to host a static webpage. Upload the custom error pages to Amazon S3 ✓
• B. Create an Amazon CloudWatch alarm to invoke an AWS Lambda function if the ALB health check response Target.FailedHealthChecks is greater than O Configure the Lambda function to modify the forwarding rule at the ALB to point to a publicly accessible web server.
• C. Modify the existing Amazon Route 53 records by adding health checks. Configure a fallback target if the health check fails. Modify DNS records to point to a publicly accessible webpage
• D. Create an Amazon CloudWatch alarm to invoke an AWS Lambda function if the ALB health check response EIb.InternalError is greater than 0,Configure the Lambda function to modify the forwarding rule at the ALB to point to a public accessible web server
• E. Add a custom error response by configuring a CloudFront custom error page. Modify DNS records to point to a publicly accessible web page ✓

Correct Answer: A. Create an Amazon S3 bucket. Configure the S3 bucket to host a static webpage. Upload the custom error pages to Amazon S3, E. Add a custom error response by configuring a CloudFront custom error page. Modify DNS records to point to a publicly accessible web page

Explanation

Option A allows for hosting a custom error page directly on S3, requiring minimal setup and maintenance overhead. When an error occurs, the ALB can be configured to redirect users to the S3 bucket hosting the custom error page.Option E involves configuring a custom error response using CloudFront, which also requires minimal configuration and ongoing maintenance. This option is particularly useful since CloudFront is already in use to cache static content for the ecommerce application and can therefore help provide faster access to the custom error page.Together, these solutions will allow a custom error page to be displayed to visitors during outage events while minimizing operational overhead.