A developer is planning an update for a non-critical internal application deployed on AWS Elastic Beanstalk. Because the application has low usage, the developer wants to minimize deployment duration and is comfortable with the environment's capacity being temporarily reduced or offline during the update. Which two Elastic Beanstalk deployment strategies will result in a temporary reduction of active instance capacity during the deployment? (Select TWO).
- All-at-onceCevap
- RollingCevap
- CRolling with additional batch
- DImmutable
- ETraffic splitting
Cevap
All-at-once and Rolling
The correct strategies are All-at-once and Rolling. The All-at-once strategy deploys the update to all instances at the same time, which temporarily takes all instances out of service and reduces active capacity to zero. The Rolling strategy updates the environment in batches, taking one batch of instances out of service at a time, which temporarily reduces the overall active capacity of the environment.
Adım Adım Çözüm
Anahtar Kavram
Understanding the impact of AWS Elastic Beanstalk deployment strategies on environment capacity and instance count.