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? (Choose two.)
Jonfernz
Highly Voted 2 years, 1 month agoChungies
Most Recent 4 months agorsn
1 year, 4 months agozWarez
1 year, 9 months agoJohnPi
2 years, 1 month agoJohnPi
2 years, 1 month agoNaj_64
2 years, 1 month agoJohnPi
2 years, 1 month agoJohnPi
2 years, 1 month agognic
2 years, 3 months agorockc
2 years, 5 months ago[Removed]
2 years, 6 months agotitleone
2 years, 6 months agouser0001
2 years, 7 months agohfeng95
2 years, 6 months agoBigbearcn
2 years, 7 months agoshailurtm2001
2 years, 7 months ago