Examkin

Question

Difficulty: HardDeployment Strategies

A developer is managing a production web application deployed on AWS Elastic Beanstalk. The application experiences consistent high traffic, and the environment's capacity must remain at 100%100\% at all times during updates to prevent performance degradation. In the event of a deployment failure, the application must support an immediate rollback with minimal impact, without requiring a manual rollback deployment. Additionally, to avoid issues with client-side DNS caching, the deployment must not involve swapping DNS CNAMEs or changing Route 53 configurations.

Which Elastic Beanstalk deployment strategy should the developer select?

  1. ImmutableAnswer
  2. B
    Rolling with additional batch
  3. C
    Blue/Green deployment
  4. D
    Rolling

Answer

The immutable deployment strategy
The immutable deployment strategy meets all requirements. It maintains 100%100\% capacity by deploying the new version to a temporary Auto Scaling group alongside the existing one under the same load balancer. If the deployment fails, Elastic Beanstalk immediately deletes the temporary Auto Scaling group, resulting in an immediate rollback with zero downtime. Since it uses the same environment and load balancer, no CNAME swaps or DNS changes are required.

Step-by-Step Solution

1
Analyze capacity constraints.
The requirement to maintain 100%100\% capacity during updates rules out the standard Rolling strategy because it takes active instances out of service, reducing capacity.
To prevent performance degradation on a high-traffic site, capacity cannot drop below the baseline.
2
Evaluate rollback speed and procedure.
The requirement for immediate rollback without a manual rollback deployment rules out Rolling with additional batch.
Rolling with additional batch requires a new deployment of the previous version to revert changes, which is slow and manual.
3
Check DNS and routing constraints.
The requirement to avoid DNS CNAME swapping or Route 53 changes rules out Blue/Green deployment.
Blue/Green deployments rely on switching DNS CNAMEs, which can cause traffic to split due to client-side DNS caching.
4
Identify the matching strategy.
The Immutable strategy satisfies all constraints by deploying to a temporary Auto Scaling group behind the same load balancer, maintaining 100%100\% capacity, and allowing immediate automatic rollback by terminating the new group if health checks fail.
It runs the new version in parallel behind the same load balancer, avoiding DNS changes, and rolls back instantly by deleting the temporary group.

Key Concept

AWS Elastic Beanstalk Deployment Strategies
Estimated Time:2m 30s
Rate this question

Topics

Deployment Strategies

More questions from this topic