A DevOps engineer has used Elastic Beanstalk to create a new Java environment with a Classic Load Balancer and an Auto Scaling Group. In the Load Balancer, a health check has been configured with a URL as the Health check path. It also has a Rolling Deployment policy. The development team just released a new feature that had several big changes to the application architecture. During the deployment of the new feature, it has failed and rolled back as the health check did not pass. However, the health check issue is known and as expected. Which approach can be taken so that the deployment can be successful regardless of health status? 

Answer options:

A.In Deployment configurations, enlarge the Health Check Command timeout, such as from 600s to 1200s.
B.Lower down the Healthy threshold from OK to Degraded so that the health check can pass.
C.Modify the deployment policy from Rolling to All at once.
D.In Deployment preferences, specify the Ignore health check option.

Correct Answer – D
Refer to https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rolling-version-deploy.html for the health check related settings in Elastic Beanstalk deployment policies.
For the Rolling deployment type, Elastic Beanstalk waits until all instances in a batch pass the health check before moving on to the next batch. However, if the health check fails, the deployment fails, and this batch is rolled back.
Option A is incorrect: Because the health check still fails. So this option does not help.
Option Bis incorrect: Because even if the threshold is set lower to Degraded, the health check and the deployment still fail.
Option Cis incorrect: Because for All at once deployment, it also needs a health check to pass. So this option does not help the deployment to pass.
Option D is CORRECT: Because health check failures can be ignored during deployment. The configuration is as below: