Soru

Zorluk: ZorDeployment Strategy Design

A logistics company is launching a new high-transaction transit-tracking application. The infrastructure is provisioned using AWS CloudFormation, with the application running on Amazon EC2 instances managed by an Auto Scaling group behind an Application Load Balancer (ALB). The business requirements dictate that all application updates must be deployed using a canary pattern to limit exposure to a subset of users, and the system must support instant rollbacks to the previous version without any traffic interruption or capacity degradation if post-deployment anomalies are detected. Which two configurations should the solutions architect combine to meet these requirements? (Select two.)

  1. Configure AWS CodeDeploy to manage a blue/green deployment for the Auto Scaling group, using a traffic-shifting canary configuration to redirect a percentage of traffic to the new instances via the Application Load Balancer.Cevap
  2. Create Amazon CloudWatch alarms that monitor application error rates and Application Load Balancer 5XX counts, and associate these alarms with the CodeDeploy deployment group to automatically trigger a rollback.Cevap
  3. C
    Configure the CloudFormation template's UpdatePolicy attribute on the Auto Scaling group resource to use AutoScalingRollingUpdate with WaitOnResourceSignals enabled.
  4. D
    Deploy duplicate CloudFormation stacks for the new and old versions of the application, and use Amazon Route 53 weighted routing policies to shift traffic between the two load balancer endpoints.
  5. E
    Configure the CloudFormation template's UpdatePolicy attribute on the Auto Scaling group resource to use AutoScalingReplacingUpdate to replace the entire Auto Scaling group on updates.

Cevap

Configure AWS CodeDeploy to manage a blue/green deployment for the Auto Scaling group with a traffic-shifting canary configuration, and create CloudWatch alarms for application metrics to associate with the deployment group for automated rollback.
The correct options implement a CodeDeploy blue/green deployment style for the Auto Scaling group and integrate CloudWatch alarms for automatic rollbacks. CodeDeploy deploys a new green Auto Scaling group, shifts traffic using a canary pattern, and keeps the original blue Auto Scaling group running. If the CloudWatch alarms trigger, CodeDeploy instantly redirects traffic back to the blue group, achieving a zero-downtime instant rollback.

Adım Adım Çözüm

1
Evaluate the rollback and zero-downtime requirements.
Identify that the solution requires instant rollbacks without capacity degradation or traffic interruption.
This rules out in-place rolling or replacing updates because their rollbacks are rolling processes that require time and capacity changes.
2
Determine the traffic-shifting mechanism.
Choose AWS CodeDeploy blue/green deployments over DNS-based routing (Route 53 weighted).
Route 53 DNS changes are delayed by client/resolver DNS caching, whereas CodeDeploy manages traffic shifting instantly at the Application Load Balancer target group level.
3
Configure the automated rollback triggers.
Create CloudWatch alarms for key application metrics (5XX counts, error rates) and link them to the CodeDeploy deployment group.
CodeDeploy monitors these alarms during the traffic-shifting phase and will automatically execute an instant rollback if any alarm is triggered.

Anahtar Kavram

AWS CodeDeploy Blue/Green Deployment with Canary traffic shifting offers instant, zero-downtime rollback capabilities by keeping the original Auto Scaling group active during the deployment verification period, which is superior to CloudFormation rolling updates or Route 53 DNS-based routing for strict SLA requirements.
Bu soruyu puanla