Examkin

Soru

Zorluk: OrtaDeployment Strategy Design

A company is designing a deployment pipeline for a payment processing API running on Amazon ECS with AWS Fargate behind an Application Load Balancer (ALB). The business requires that any new release must minimize the blast radius by initially directing 10% of production traffic to the new version. If the system remains healthy, the pipeline must increase traffic to the new version by 10% every 10 minutes until 100% is reached. If an Amazon CloudWatch alarm for HTTP 5xx errors is triggered at any point, the deployment must automatically roll back to the previous version with zero downtime. Which deployment configuration and strategy will meet these requirements?

  1. A
    Amazon ECS rolling update deployment with the minimum healthy percent set to 90% and maximum percent set to 100%, relying on ECS deployment circuit breaker to trigger automatic rollback.
  2. B
    AWS CodeDeploy blue/green deployment with the CodeDeployDefault.ECSCanary10Percent10Minutes traffic-routing configuration, using CloudWatch alarms configured for the deployment group to trigger automatic rollback.
  3. AWS CodeDeploy blue/green deployment with the CodeDeployDefault.ECSLinear10PercentEvery10Minutes traffic-routing configuration, using CloudWatch alarms configured for the deployment group to trigger automatic rollback.Cevap
  4. D
    AWS CodeDeploy blue/green deployment with the CodeDeployDefault.ECSAllAtOnce traffic-routing configuration, using Application Load Balancer target group health checks to trigger automatic rollback.

Cevap

AWS CodeDeploy blue/green deployment using the CodeDeployDefault.ECSLinear10PercentEvery10Minutes traffic-routing configuration with CloudWatch alarms configured for automatic rollback.
The correct option is the one specifying the AWS CodeDeploy blue/green deployment with the linear routing configuration. Under this configuration, CodeDeploy shifts 10% of traffic to the new target group, and then adds 10% more every 10 minutes until the full shift is complete. Using CloudWatch alarms attached to the deployment group ensures that if HTTP 5xx errors increase, the deployment is immediately halted and rolled back to the original task set without causing downtime.

Adım Adım Çözüm

1
Analyze the traffic shifting pattern requirement.
The requirement demands starting at 10% traffic and increasing by 10% every 10 minutes, which represents a linear, incremental progression rather than a two-phase canary shift.
This rules out Canary and AllAtOnce routing configurations.
2
Evaluate the capabilities of Amazon ECS rolling updates.
Rolling updates replace tasks but do not support fine-grained ALB-weighted traffic routing or automated rollbacks triggered directly by application HTTP 5xx metrics.
This rules out standard ECS rolling updates for granular traffic routing needs.
3
Confirm the CodeDeploy blue/green linear configuration and rollback integration.
The CodeDeployDefault.ECSLinear10PercentEvery10Minutes configuration shifts traffic in equal 10% increments. Integrating CloudWatch alarms with the CodeDeploy deployment group enables automated, zero-downtime rollbacks when threshold-based errors occur.
This satisfies all business constraints, including the rollback criteria.

Anahtar Kavram

Selecting and configuring AWS CodeDeploy linear traffic routing configurations for ECS Fargate services to control blast radius and automate rollbacks.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Deployment Strategy Design

Bu konudan daha fazla soru