Examkin

Question

Difficulty: HardDeployment Strategies and Execution

A SysOps Administrator is designing a deployment pipeline for a production application running on Amazon EC2 instances managed by an Auto Scaling group behind an Application Load Balancer (ALB). The deployment strategy must satisfy the following constraints:
- Deploy the new version with zero downtime.
- Route exactly 10%10\% of live user traffic to the new version for a 10-minute validation period.
- Automatically route the remaining 90%90\% of traffic after the validation period if no CloudWatch alarms are active.
- Support instantaneous rollback to the original version during the validation period.

The administrator discovers that the current AWS CodeDeploy blue/green configuration cannot perform fractional traffic routing for the EC2 Auto Scaling group.

Which strategy should the administrator implement to meet all requirements?

  1. Deploy the application using AWS Elastic Beanstalk and configure a traffic splitting deployment policy with a 10%10\% traffic split and a 10-minute evaluation period.Answer
  2. B
    Modify the CodeDeploy deployment group configuration to use the CodeDeployDefault.LambdaCanary10Percent10Minutes deployment configuration.
  3. C
    Update the AWS CloudFormation template for the Auto Scaling group to use an AutoScalingRollingUpdate policy with a MinSuccessfulInstancesPercent set to 90%90\%.
  4. D
    Use an AWS Systems Manager Automation document to perform an in-place deployment to 10%10\% of the instances first, then deploy to the remaining instances after 10 minutes.

Answer

Deploy the application using AWS Elastic Beanstalk and configure a traffic splitting deployment policy with a 10%10\% traffic split and a 10-minute evaluation period.
The correct strategy is to deploy the application using AWS Elastic Beanstalk with a traffic splitting deployment policy. Elastic Beanstalk supports traffic splitting, which allows a SysOps Administrator to route a small, configurable percentage of traffic (such as 10%) to the new version in a temporary environment. It monitors the health of the new version for a set duration, and if any CloudWatch alarms are triggered, it immediately redirects all traffic back to the original version, providing an instantaneous rollback.

Step-by-Step Solution

1
Identify the limitations of the current deployment tools.
AWS CodeDeploy cannot perform canary or fractional traffic shifting for EC2/On-Premises deployments natively; it only supports this for AWS Lambda and Amazon ECS.
This rules out utilizing CodeDeploy's built-in canary configurations for EC2 instances.
2
Evaluate alternative deployment strategies that support traffic splitting on EC2.
AWS Elastic Beanstalk supports a traffic splitting deployment policy, which handles deploying the application to a new Auto Scaling group and splitting the ALB traffic by a specified percentage.
This matches all key constraints of the deployment scenario: zero downtime, 10% traffic verification, and automatic rollback.
3
Verify rollback mechanisms.
Elastic Beanstalk monitors CloudWatch alarms during the evaluation period and will automatically roll back traffic to the old version instantly if a threshold is crossed.
This guarantees the instantaneous rollback requirement is met.

Key Concept

Deployment Strategies and Traffic Splitting on AWS
Estimated Time:2m 30s
Rate this question

Topics

Deployment Strategies and Execution

More questions from this topic