Examkin

Question

Difficulty: EasyDeployment Strategy Design

A web application is deployed on AWS Elastic Beanstalk. The development team wants to update the application using a strategy that maintains full serving capacity during the deployment. Additionally, if the deployment fails, the rollback must be immediate and avoid any modification to the original running instances. Which of the following deployment policies meet these requirements? (Select TWO.)

  1. ImmutableAnswer
  2. Traffic splittingAnswer
  3. C
    Rolling
  4. D
    Rolling with additional batch
  5. E
    All at once

Answer

The Immutable and Traffic splitting deployment policies meet the requirements because they both maintain full capacity and allow an immediate, clean rollback by terminating a temporary Auto Scaling group without modifying active production instances.
The correct policies are the ones that maintain full capacity and do not modify the original instances during deployment, allowing for immediate rollback. Immutable updates create a new Auto Scaling group, deploy the application, and then switch traffic. Traffic splitting also creates a new Auto Scaling group and routes a fraction of traffic to it while keeping the original group at full capacity. Both options keep the original instances untouched until the deployment is successful, allowing for a safe, instant rollback by deleting the new instances or shifting traffic back.

Step-by-Step Solution

1
Analyze the capacity requirement during deployment
The strategy must maintain 100% capacity, ruling out All at once (0% capacity) and Rolling (reduced capacity).
To ensure no performance degradation during updates.
2
Analyze the rollback requirement
The rollback must be immediate and not touch the original instances. This rules out Rolling with additional batch, because failed deployments require another rolling update to revert, affecting the active instances.
To minimize blast radius and ensure zero-downtime recovery.
3
Identify the remaining valid policies
Immutable and Traffic splitting both create a separate, temporary Auto Scaling group, keeping the original instances safe and active, and allowing instant rollback by redirecting traffic or terminating the new group.
These match all constraints perfectly.

Key Concept

AWS Elastic Beanstalk deployment policies and their capacity and rollback characteristics.
Rate this question

Topics

Deployment Strategy Design

More questions from this topic