Examkin

Question

Difficulty: MediumAWS Elastic Beanstalk

A developer needs to update a production web application hosted on AWS Elastic Beanstalk. The application runs on multiple Amazon EC2 instances behind an Application Load Balancer. The deployment must satisfy the following criteria:
- There must be zero application downtime.
- The environment must maintain 100%100\% of its provisioned capacity throughout the deployment process to handle high traffic.
- The deployment must support a fast and clean rollback mechanism with minimal impact if any issues occur.
- Double-allocation cost is acceptable for the duration of the deployment.

Which two Elastic Beanstalk deployment policies should the developer select to meet these requirements?

  1. ImmutableAnswer
  2. Rolling with additional batchAnswer
  3. C
    Rolling
  4. D
    All at once
  5. E
    Linear 10% every 10 minutes

Answer

Immutable and Rolling with additional batch
The Immutable deployment policy satisfies the constraints by deploying the new version to a temporary Auto Scaling group, ensuring full capacity is maintained during health checks and allowing an instant rollback if needed. The Rolling with additional batch policy also meets the criteria by launching a new batch of instances first to maintain 100%100\% capacity before updating the existing instances in batches.

Step-by-Step Solution

1
Analyze the capacity requirement
The requirement specifies that 100%100\% of the provisioned capacity must be maintained throughout the deployment. This rules out the standard Rolling policy, which takes instances out of service, and the All at once policy, which takes all instances out of service.
Maintaining full capacity is a strict constraint to handle high traffic without performance degradation.
2
Analyze the downtime and rollback requirements
The Immutable deployment policy launches a separate, temporary Auto Scaling group, meaning the existing environment runs at full capacity until the new version passes health checks. Rollback is immediate (terminating the new Auto Scaling group). The Rolling with additional batch policy launches a new batch first to maintain capacity before rolling the update through the existing instances, ensuring zero downtime.
Both policies satisfy the capacity and zero-downtime requirements by allocating additional temporary resources during the update.
3
Evaluate the non-native option
Linear 10% every 10 minutes is a CodeDeploy-specific configuration and cannot be selected as an Elastic Beanstalk deployment policy.
Only native Elastic Beanstalk deployment policies can be configured within the Elastic Beanstalk console or CLI.

Key Concept

AWS Elastic Beanstalk deployment policies and their impact on environment capacity, downtime, and rollbacks.
Rate this question

Topics

AWS Elastic Beanstalk

More questions from this topic