An organization is deploying updates to a high-traffic web application hosted on AWS Elastic Beanstalk. The application is highly sensitive to performance issues, so the deployment process must maintain of the current instance capacity at all times. Additionally, if the new version fails health checks, the deployment must support an immediate rollback that does not alter or disrupt the active instances in the original environment. Which two Elastic Beanstalk deployment policies will meet these requirements?
- ImmutableCevap
- Traffic SplittingCevap
- CRolling with additional batch
- DRolling
- EAll at once
Cevap
The Immutable and Traffic Splitting deployment policies should be selected.
The Immutable and Traffic Splitting policies both satisfy the constraints. The Immutable policy creates a temporary Auto Scaling group to launch the new version alongside the original one. Once health checks pass, traffic is shifted. Traffic Splitting routes a configured percentage of traffic to a new temporary Auto Scaling group for evaluation. In both cases, the original instances remain untouched, maintaining capacity and enabling instant rollback by simply deleting the temporary resources.
Adım Adım Çözüm
Anahtar Kavram
AWS Elastic Beanstalk deployment policies and their impact on environment capacity, duration, and rollback mechanisms.