Free AWS DVA-C01 Actual Exam Questions - Question 5 Discussion
enables automatic rollbacks while deploying a new version of a popular web application from in
place to Amazon EC2.
What occurs it the deployment of the new version fails due to code regression?
This one feels like C for me too. Since it’s an in-place deployment, CodeDeploy can't just switch traffic like in blue/green; it needs to redeploy the last good version, creating a new deployment ID. A talks about snapshots in S3, which doesn’t match how CodeDeploy usually handles rollbacks. B is more about blue/green deployments where Route 53 gets updated, so that doesn’t fit here. D mentions CodePipeline, but this question focuses on CodeDeploy behavior specifically.
C imo. Since it’s an in-place deployment, CodeDeploy can’t just switch traffic like in blue/green, so it has to do a fresh deployment of the stable version, which would mean a new deployment ID. A and B don’t fit the rollback behavior here—no snapshots in S3 or route switching for in-place. D sounds more like something CodePipeline does, but this question focuses on CodeDeploy’s rollback itself. So option C makes the most sense as the automated recovery step after a failed deployment.
Probably C. Since it’s an in-place deployment, a rollback likely means CodeDeploy redeploys the last good version fresh, so a new deployment ID gets generated. A doesn’t sound right because CodeDeploy doesn’t rely on S3 snapshots for rollback. B is more about blue/green, which isn’t the case here. D mentions CodePipeline, but the question focuses on CodeDeploy, so that’s probably unrelated.
B imo. Since the question mentions an in-place deployment, route switching like in blue/green probably doesn’t apply here, so B seems off. Also, CodeDeploy rollback usually means redeploying the last known good version rather than relying on snapshots or DNS changes. D is wrong because CodePipeline isn’t responsible for rollbacks in CodeDeploy. A is unlikely since CodeDeploy doesn’t use S3 snapshots for rollbacks. So C fits best—it redeploys the last successful version with a new deployment ID after failure.
Maybe C. Since CodeDeploy tracks deployment versions, it probably triggers a fresh deployment of the last good version with a new ID rather than just rolling back silently.
Makes sense that it would just redeploy automatically, so C.
If the deployment fails, wouldn’t CodeDeploy just redeploy the last successful version? C