Deploying Applications with Elastic Beanstalk

Answer - C and D.

Since the only requirement is that the infrastructure should maintain its full capacity, So answers should be both C &

D.You can now use an immutable deployment policy when updating your application or environment configuration on Elastic Beanstalk.

This policy is well suited for updates in production environments where you want to minimize downtime and reduce the risk from failed deployments.

It ensures that the impact of a failed deployment is limited to a single instance and allows your application to serve traffic at full capacity throughout the update.

You can now also use a rolling with additional batch policy when updating your application.

This policy ensures that the impact of a failed deployment is limited to a single batch of instances and allows your application to serve traffic at full capacity throughout the update.

Option A is incorrect because All at once is used to deploy the new version to all instances simultaneously.

All instances in your environment are out of service for a short time while the deployment occurs.

Option B is incorrect because Rolling is used to deploy the new version in batches.

Each batch is taken out of service during the deployment phase, reducing your environment's capacity by the number of instances in a batch.

Please refer to the following links for more information.

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rolling-version-deploy.html#environments-cfg-rollingdeployments-method https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environmentmgmt-updates-imm

The correct deployment methods for maintaining full capacity when updates are made to an Elastic Beanstalk application are Rolling and Immutable.

1. Rolling Deployment: Rolling deployment is a deployment method in which a new version of the application is deployed to a subset of instances in the environment, and then gradually rolled out to the remaining instances. This method ensures that the environment maintains full capacity during the deployment.

For example, if an environment has 10 instances, the rolling deployment will first deploy the new version to 2 instances, then 2 more, and so on until all 10 instances are running the new version. This way, the environment always has at least 8 instances running the old version while 2 instances are being updated.

2. Immutable Deployment: Immutable deployment is a deployment method in which a new version of the application is deployed to new instances in the environment, and then the old instances are terminated. This method also ensures that the environment maintains full capacity during the deployment.

For example, if an environment has 10 instances, the immutable deployment will launch 10 new instances with the new version, and then terminate the 10 old instances running the old version. This way, the environment always has 10 instances running the new version.

Option A, All at Once deployment method deploys the new version to all instances at once, which can result in downtime and reduced capacity during the deployment.

Option D, Rolling with additional batch, is a variation of the rolling deployment method where an additional batch of instances is launched before the old instances are terminated. This can be useful in certain scenarios but is not necessary for the requirement mentioned in the question.

Therefore, the correct options for this requirement are Rolling and Immutable deployment methods.