A developer is configuring a deployment for a web application running on an Auto Scaling group of four Amazon EC2 instances using AWS CodeDeploy. The deployment must meet the following constraints:
- The application must experience zero downtime, meaning at least some instances must remain online and healthy to serve traffic at all times.
- Due to strict budget limitations, no additional EC2 instances can be provisioned during the deployment.
Which two AWS CodeDeploy default deployment configurations satisfy these requirements? (Select two.)
- CodeDeployDefault.OneAtATimeCevap
- CodeDeployDefault.HalfAtATimeCevap
- CCodeDeployDefault.AllAtOnce
- DA CodeDeploy Blue/Green deployment
- ECodeDeployDefault.ECSLinear10PercentEvery1Minute
Cevap
The correct configurations are CodeDeployDefault.OneAtATime and CodeDeployDefault.HalfAtATime.
The correct configurations are CodeDeployDefault.OneAtATime and CodeDeployDefault.HalfAtATime. Because the deployment must not launch additional EC2 instances, it must be performed in-place. To prevent downtime, the deployment configuration must ensure that some instances remain online and healthy during the update. CodeDeployDefault.OneAtATime updates one instance at a time (keeping three online), and CodeDeployDefault.HalfAtATime updates two instances at a time (keeping two online). Both options satisfy the zero-downtime and zero-additional-cost constraints.
Adım Adım Çözüm
Anahtar Kavram
AWS CodeDeploy in-place deployment configurations for EC2 that balance fleet capacity and update progress without provisioning new instances.