Examkin

Question

Difficulty: HardDeployment Strategies and Execution

A SysOps Administrator is planning to deploy an application update to a critical production environment running on AWS Elastic Beanstalk. The environment utilizes an Application Load Balancer (ALB) and an Auto Scaling group with a minimum capacity of 44 instances. The deployment must satisfy the following constraints:

1. The environment must maintain 100%100\% of its current serving capacity (44 instances) at all times to prevent performance degradation.
2. A canary test must be performed by routing exactly 10%10\% of incoming production traffic to the new application version for an evaluation period of 1515 minutes.
3. If any CloudWatch alarms (such as HTTP 5xx5\text{xx} error rates) trigger during the evaluation period, the deployment must immediately roll back with zero downtime.

Which combination of configuration settings and deployment strategies will meet these requirements? (Select TWO.)

  1. Configure the environment deployment policy to Traffic splitting, and set the split percentage to 10%10\% with an evaluation time of 1515 minutes.Answer
  2. Configure environment rollback rules to monitor active CloudWatch alarms, enabling automated rollback if thresholds are exceeded during the evaluation period.Answer
  3. C
    Configure the environment deployment policy to Rolling with additional batch, and configure an Amazon Route 53 weighted routing policy to route 10%10\% of traffic to the new instances.
  4. D
    Configure the environment deployment policy to Immutable, and configure an AWS CodeDeploy deployment group with a canary traffic shifting configuration.
  5. E
    Configure the environment deployment policy to Rolling, configure a minimum healthy percentage of 100%100\%, and apply the update using an AWS Systems Manager (SSM) Patch Baseline.

Answer

The correct configurations are setting the deployment policy to Traffic splitting with a 10%10\% split percentage and a 1515-minute evaluation time, and configuring environment rollback rules to monitor CloudWatch alarms.
The Traffic splitting deployment policy enables a canary deployment by creating a parallel group of instances running the new version and routing a defined percentage of traffic (10%10\%) to them for a trial duration (1515 minutes) while keeping the original instances at full capacity. By combining this policy with CloudWatch alarm monitoring on the Elastic Beanstalk environment, any failure detected during the trial period will trigger an immediate rollback, routing all traffic back to the original healthy instances with zero downtime.

Step-by-Step Solution

1
Analyze the capacity requirement.
Determine that the environment must keep 44 instances active at all times. Standard rolling or all-at-once policies are disqualified since they reduce active capacity unless additional batches are provisioned.
To maintain 100%100\% serving capacity during the update.
2
Evaluate the canary traffic routing requirement.
Identify Traffic splitting as the only native Elastic Beanstalk policy that can route a specific percentage of traffic (10%10\%) to a new version via the load balancer for a timed trial period (1515 minutes).
To ensure client request routing is controlled at the load balancer level, avoiding DNS caching issues.
3
Determine the automatic rollback mechanism.
Select the option to associate CloudWatch alarms with the environment's rollback rules.
This enables Elastic Beanstalk to automatically cancel the deployment and shift all traffic back to the original instances if metrics exceed thresholds during the evaluation period.

Key Concept

AWS Elastic Beanstalk Traffic Splitting deployment policy and CloudWatch alarm-based rollbacks.
Rate this question

Topics

Deployment Strategies and Execution

More questions from this topic