A company runs a critical web application on AWS Elastic Beanstalk. The application must maintain of its capacity to handle peak traffic during updates. Additionally, if the new version fails post-deployment, the developer must be able to roll back to the previous version immediately with minimal service impact and without triggering a new application deployment.
Which two Elastic Beanstalk deployment strategies meet these requirements? (Select TWO).
- Blue/Green deploymentCevap
- Immutable deploymentCevap
- CRolling with additional batch deployment
- DRolling deployment
- EAll-at-once deployment
Cevap
Blue/Green deployment and Immutable deployment
Blue/Green deployment and Immutable deployment are correct because both strategies keep the original, healthy application instances running at capacity while the new version is deployed and verified. In Blue/Green, a CNAME swap directs traffic to the new environment, and rolling back is as simple as swapping CNAMEs back. In Immutable, a temporary Auto Scaling group is created, and if the deployment fails, the temporary instances are terminated, instantly reverting traffic to the original instances without needing a new deployment.
Adım Adım Çözüm
Anahtar Kavram
Elastic Beanstalk deployment strategies and their trade-offs regarding capacity and rollback mechanics.
Tahmini Süre:1m 30s