AWS DevOps Engineer Professional Practice Test

What setting should be adjusted in Elastic Beanstalk to avoid premature deployment failures for applications that take a long time to pass health checks?

1. Minimum Instances Count

2. Command Timeout

3. Scaling Delay

4. Instance Lifecycle Period

The correct answer is: Command Timeout

Adjusting the command timeout setting in Elastic Beanstalk is crucial for applications that require an extended duration to complete their health checks. By increasing the command timeout, you allow more time for the deployment processes, like application initialization and environment configuration, to finish successfully before Elastic Beanstalk deems the deployment unsuccessful. When dealing with applications that have a long startup time or that need to go through several pre-conditions before they are healthy, the default timeout may not be sufficient, leading to a failure in premature deployment. By configuring the command timeout appropriately, it allows for the health check to validate that the application is indeed up and running before any failure is declared. This is particularly important in environments where services depend on each other and various startup activities need to be completed to achieve a healthy state. The other options are relevant in different contexts but do not directly address premature deployment failures caused by lengthy health checks. For instance, minimum instance count influences scaling but doesn't affect individual health checks during deployment, while scaling delay pertains to the time Elastic Beanstalk waits before scaling out new instances after a health check failure. Instance lifecycle period relates to the lifecycle of instances but does not provide a direct solution for deployment-related timeout issues.