This website uses cookies to ensure you get the best experience.
Learn more.
An EC2 CodeDeploy release increases errors after traffic reaches the new revision. Operations needs automatic mitigation and a usable prior release. Which practices support this? Select 2 answers.
Published
- Assume a code rollback reverses every external transaction automatically.
- Delete all previous revisions before observing the new application.
- Disable error alarms so the deployment appears successful.
- Retain the prior compatible revision and account for state changes that a code rollback cannot undo automatically.
- Configure relevant alarms and automatic rollback for the deployment group.
Comments — 0
Sign in to comment