Skip to content

Commit f37b8cf

Browse files
fix 186
The question specifies "in-place deployment" - In-place deployment means "the application on each instance in the deployment group is stopped, the latest application revision is installed, and the new version of the application is started and validated." The option identifyed as correct describes blue/green deployment behavior, not in-place deployment behavior In-place deployments don't use "blue" and "green" environments - they update the same instances
1 parent 05f50fe commit f37b8cf

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2236,8 +2236,8 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
22362236
### A company has implemented AWS CodeDeploy as part of its cloud native CI/CD stack. The company enables automatic rollbacks while deploying a new version of a popular web application from in-place to Amazon EC2. What occurs if the deployment of the new version fails due to code regression?
22372237

22382238
- [ ] The last known good deployment is automatically restored using the snapshot stored in Amazon S3.
2239-
- [x] CodeDeploy switches the Amazon Route 53 alias records back to the known good green deployment and terminates the failed blue deployment.
2240-
- [ ] A new deployment of the last known version of the application is deployed with a new deployment ID.
2239+
- [ ] CodeDeploy switches the Amazon Route 53 alias records back to the known good green deployment and terminates the failed blue deployment.
2240+
- [x] A new deployment of the last known version of the application is deployed with a new deployment ID.
22412241
- [ ] AWS CodePipeline promotes the most recent deployment with a SUCCEEDED status to production.
22422242

22432243
**[⬆ Back to Top](#table-of-contents)**

0 commit comments

Comments
 (0)