An organization is using AWS Elastic Beanstalk for a web application.
The Developer needs to configure the Elastic Beanstalk environment with deployment methods to create new instances and deploy code to those instances. Which methods will deploy code ONLY to new instances? Choose 2 answers from the options given below.
Click on the arrows to vote for the correct answer
A. B. C. D. E.Answer - B and E.
The AWS Documentation mentions the following.
Immutable deployments perform an immutable update to launch a full set of new instances running the new version of the application in a separate Auto Scaling group, alongside the instances running the old version.
Immutable deployments can prevent issues caused by partially completed rolling deployments.
If the new instances don't pass health checks, Elastic Beanstalk terminates them, leaving the original instances untouched.
And with Blue Green deployments, you can have a separate deployment environment as well.
Option A is incorrect because All at once deployment deploys 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 C is incorrect because Rolling deployment deploys 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.
Option D is incorrect because there is no Linear deployments.
For more information on Deployment options, please refer to the below Links-
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rolling-version-deploy.html https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.CNAMESwap.htmlOut of the given deployment methods, Immutable deployment and Blue/Green deployment will deploy code ONLY to new instances.
Immutable Deployment: Immutable deployment is a deployment method in which new instances are created before the code deployment. The deployment process involves creating a new set of instances, deploying code to them, and then directing traffic to the new instances. The old instances are terminated once the new instances are up and running. This method ensures that there is no downtime and eliminates the possibility of rollback. In an immutable deployment, the original instances are not updated; instead, new instances are created with the updated code.
Blue/Green Deployment: Blue/Green deployment is another deployment method that involves the creation of a new environment with the updated code. In this method, the new environment is created alongside the existing environment. The new environment is identical to the old environment, except for the updated code. Once the new environment is ready, traffic is directed to it, and the old environment is terminated. This deployment method ensures zero downtime and enables a quick rollback if there are any issues.
The other deployment methods given in the options, All at once deployment, Rolling deployment, and Linear deployment, do not deploy code only to new instances.
All at Once deployment: In this method, the deployment process updates all instances in the environment at once. This method is the fastest but also carries the highest risk since it can result in downtime if there are any issues with the deployment.
Rolling Deployment: In this method, the deployment process updates a percentage of instances at a time, allowing for a gradual update of the environment. This method reduces the risk of downtime but still carries some risk since some instances may be updated while others are not.
Linear Deployment: Linear deployment is similar to rolling deployment, but it updates instances in a linear fashion. In this method, a fixed number of instances are updated at a time until all instances are updated. This method also reduces the risk of downtime but still carries some risk since some instances may be updated while others are not.
In summary, Immutable deployment and Blue/Green deployment methods are the only two methods that will deploy code only to new instances. The other deployment methods update existing instances as well.