Examkin

Question

Difficulty: EasyAWS Elastic Beanstalk

A developer is configuring a deployment strategy for a web application running on AWS Elastic Beanstalk. The application must maintain full capacity (100%100\%) throughout the deployment process to handle steady traffic, and the developer wants to avoid performing any DNS routing changes or CNAME swaps. Which two deployment policies satisfy these requirements? (Select TWO.)

  1. Rolling with additional batchAnswer
  2. ImmutableAnswer
  3. C
    Rolling
  4. D
    All at once
  5. E
    Blue/Green deployment via CNAME swap

Answer

Rolling with additional batch and Immutable are the correct deployment policies.
The correct options are 'Rolling with additional batch' and 'Immutable'. 'Rolling with additional batch' maintains full capacity by launching a new batch of instances before taking existing ones out of service. 'Immutable' maintains full capacity by deploying a temporary Auto Scaling group next to the original one and only cleaning up the old instances once the new ones pass health checks. Neither policy requires DNS or CNAME swaps.

Step-by-Step Solution

1
Analyze capacity requirements during deployment.
The application requires maintaining full capacity (100%100\%) at all times, meaning the deployment must not take any active instances out of service without first replacing their capacity.
This rules out the standard Rolling policy, which takes batches offline, and the All at once policy, which takes all instances offline.
2
Analyze DNS and routing requirements.
The developer wants to avoid DNS changes or CNAME swaps.
This rules out Blue/Green deployment, which relies on swapping the URLs of two separate environments (a DNS-level change).
3
Evaluate the remaining Elastic Beanstalk deployment policies.
Rolling with additional batch launches new instances first to maintain capacity, and Immutable creates a temporary parallel Auto Scaling group to test the new version before replacing the old one. Neither requires DNS changes.
Both of these options satisfy both the full capacity and no-DNS-swap constraints.

Key Concept

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

Topics

AWS Elastic Beanstalk

More questions from this topic