DOP-C02 · Question #167
A DevOps engineer is using AWS CodeDeploy across a fleet of Amazon EC2 instances in an EC2 Auto Scaling group. The associated CodeDeploy deployment group, which is integrated with EC2 Auto Scaling, is
The correct answer is D. EC2 Auto Scaling launched two new instances while the new deployment had not yet finished,. https://docs.aws.amazon.com/codedeploy/latest/userguide/troubleshooting-auto- scaling.html#troubleshooting-auto-scaling-provision-termination-loo
Question
A DevOps engineer is using AWS CodeDeploy across a fleet of Amazon EC2 instances in an EC2 Auto Scaling group. The associated CodeDeploy deployment group, which is integrated with EC2 Auto Scaling, is configured to perform in-place deployments with CodeDeployDefault.OneAtATime. During an ongoing new deployment, the engineer discovers that, although the overall deployment finished successfully, two out of five instances have the previous application revision deployed. The other three instances have the newest application revision. What is likely causing this issue?
Options
- AThe two affected instances failed to fetch the new deployment.
- BA failed AfterInstall lifecycle event hook caused the CodeDeploy agent to roll back to the previous
- CThe CodeDeploy agent was not installed in two affected instances.
- DEC2 Auto Scaling launched two new instances while the new deployment had not yet finished,
How the community answered
(35 responses)- A14% (5)
- B9% (3)
- C34% (12)
- D43% (15)
Explanation
https://docs.aws.amazon.com/codedeploy/latest/userguide/troubleshooting-auto- scaling.html#troubleshooting-auto-scaling-provision-termination-loo
Topics
Community Discussion
No community discussion yet for this question.