Examkin

Question

Difficulty: MediumDeployment Strategies and Execution

An organization hosts a production application on AWS Elastic Beanstalk. During updates, the application must maintain full capacity to handle consistent user traffic. Additionally, if the new application version fails health checks, the update must automatically roll back immediately with minimal impact on the production environment. Which two Elastic Beanstalk deployment policies should a SysOps Administrator configure to meet these requirements? (Select TWO.)

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

Answer

The correct options are Immutable and Traffic Splitting.
The correct strategies are Immutable and Traffic Splitting. Immutable deployments launch a secondary Auto Scaling group with the new version, ensuring that the original instances remain untouched and active at 100% capacity. If the deployment fails health checks, Elastic Beanstalk automatically deletes the temporary Auto Scaling group, rolling back immediately. Traffic Splitting deployments also spin up a complete set of new instances and route a portion of traffic to them. If health checks fail during the evaluation period, traffic is shifted back to the original instances, and the new instances are terminated.

Step-by-Step Solution

1
Analyze the capacity requirement.
The application must maintain 100% capacity during updates. This rules out All at once and standard Rolling deployments, both of which take existing instances out of service, reducing capacity below 100%.
Ensuring capacity does not drop protects the system from degradation under traffic spikes.
2
Analyze the rollback requirement.
The rollback must be automatic, immediate, and clean. While Rolling with additional batch preserves capacity, it modifies instances in place. If it fails, rolling back requires a new rolling deployment of the older version, which is slow and not clean.
In-place modifications require inverse modifications to restore the environment, delaying recovery.
3
Identify strategies that satisfy both requirements.
Immutable and Traffic Splitting both provision a complete duplicate set of instances alongside the original environment (maintaining 100% capacity) and can roll back automatically by terminating the new resources if health checks fail.
Deploying to a separate set of resources avoids mutating the running production environment until it is proven stable.

Key Concept

AWS Elastic Beanstalk deployment policies and their capacity vs. rollback trade-offs.
Rate this question

Topics

Deployment Strategies and Execution

More questions from this topic