Question

Difficulty: EasyDeployment Strategies

A developer is deploying a new version of a critical web application to AWS Elastic Beanstalk. The application must maintain 100%100\% availability (no downtime) and full capacity during the deployment. If a failure occurs, the deployment must support a rapid rollback to the previous version. The developer has no budget constraints. Which two deployment strategies meet these requirements? (Select TWO.)

  1. Blue/Green deploymentAnswer
  2. Immutable deploymentAnswer
  3. C
    All-at-once deployment
  4. D
    Rolling deployment
  5. E
    Rolling with additional batch deployment

Answer

Blue/Green deployment and Immutable deployment
Blue/Green and Immutable deployments satisfy all requirements. A Blue/Green deployment swaps DNS/CNAME records between two separate environments, maintaining 100%100\% capacity and allowing an instant rollback. An Immutable deployment creates a temporary Auto Scaling group with the new version, ensuring 100%100\% capacity is maintained and allowing a rapid rollback by simply deleting the new group.

Step-by-Step Solution

1
Identify the constraints specified in the deployment scenario.
The key constraints are: zero downtime, 100%100\% capacity maintained, rapid rollback capabilities, and no budget constraints.
This sets up the criteria used to evaluate each Elastic Beanstalk deployment option.
2
Evaluate the impact of each deployment strategy on application capacity and downtime.
All-at-once causes downtime. Rolling reduces capacity during the update. Rolling with additional batch, Immutable, and Blue/Green all maintain 100%100\% capacity and have no downtime.
This narrows the candidate list to strategies that maintain full application availability.
3
Assess the rollback speed of the remaining strategy options.
Rolling with additional batch requires a slow rolling deployment of the older version to roll back. Blue/Green (CNAME swap) and Immutable (terminating the new Auto Scaling group) both support near-instantaneous rollbacks.
This identifies the final two strategies that satisfy the rapid rollback constraint.

Key Concept

AWS Elastic Beanstalk deployment strategies differ in their impact on environment capacity, downtime, and rollback time.
Estimated Time:1m 0s
Rate this question