Examkin

Question

Difficulty: MediumDeployment Strategies and Execution

A SysOps Administrator is managing a production web application deployed on AWS Elastic Beanstalk. The application must maintain its full capacity of 88 running instances at all times to handle peak traffic. The administrator needs to deploy a new application version with zero downtime. The deployment strategy must also support a rapid, automatic rollback to the previous version without requiring a full redeployment of the older application version package if any post-deployment health checks fail. Which deployment strategy should the administrator implement to meet these requirements?

  1. Configure the Elastic Beanstalk environment to use the Immutable deployment policy.Answer
  2. B
    Configure the Elastic Beanstalk environment to use the Rolling with additional batch deployment policy.
  3. C
    Configure the Elastic Beanstalk environment to use the Rolling deployment policy.
  4. D
    Configure a Blue/Green deployment by cloning the environment and performing a CNAME swap, without pre-warming the instances in the new environment.

Answer

Configure the Elastic Beanstalk environment to use the Immutable deployment policy.
The Immutable deployment policy is correct because it launches a parallel, temporary Auto Scaling group with the new application version. It ensures that the original 88 instances continue to serve traffic at full capacity. If health checks fail on the new instances, Elastic Beanstalk terminates the temporary Auto Scaling group immediately. This provides a rapid, one-step rollback without any downtime or the need to redeploy the previous version package.

Step-by-Step Solution

1
Analyze the capacity requirement.
The application must maintain its full capacity of 88 running instances at all times. In-place strategies that reduce capacity during the update (like Rolling) are eliminated.
Maintaining full capacity prevents performance degradation during the deployment process.
2
Evaluate the rollback and downtime requirements.
The deployment must support zero downtime and a rapid, automated rollback that does not require redeploying the previous version. This requires a strategy where the original instances remain untouched until the new version is verified.
In-place rollbacks require redeploying the old application version, which takes time and affects performance.
3
Compare the remaining strategies (Immutable vs. Rolling with additional batch vs. Blue/Green).
Immutable deployments launch a temporary Auto Scaling group to test the new version. If health checks fail, the temporary group is terminated immediately, achieving a rapid, one-step rollback. Rolling with additional batch performs in-place updates on subsequent batches, requiring redeployment to roll back. Blue/Green requires DNS swapping and manually matching capacity, which is prone to capacity mismatch if not configured carefully.
Immutable deployments provide the cleanest rollback mechanism because the original application instances are never modified during the deployment.

Key Concept

AWS Elastic Beanstalk Immutable deployments provide zero-downtime updates and rapid rollbacks by launching a temporary Auto Scaling group alongside the existing one and verifying the new version before terminating the old instances.
Estimated Time:1m 30s
Rate this question

Topics

Deployment Strategies and Execution

More questions from this topic