Examkin

Question

Difficulty: Very hardDeployment Strategies

A developer is configuring a deployment pipeline for a containerized application running on Amazon ECS (Fargate). The ECS service has a desired task count of 1010. The deployment must comply with the following operational constraints:

- At least 88 tasks must remain healthy and actively serve traffic at all times during the deployment to prevent service degradation.
- Due to strict account resource quotas in the target AWS Region, no more than 1212 tasks for this service can run concurrently at any point during the deployment.
- The system must automatically roll back to the previous stable version if the new container version fails to launch or fails to pass its container health checks.

Which deployment strategy and configuration should the developer implement to satisfy these requirements?

  1. An ECS rolling update with the minimum healthy percent set to 8080%, the maximum percent set to 120120%, and the ECS deployment circuit breaker enabled with rollback.Answer
  2. B
    An ECS rolling update with the minimum healthy percent set to 100100%, the maximum percent set to 150150%, and the ECS deployment circuit breaker enabled with rollback.
  3. C
    An AWS CodeDeploy blue/green deployment using the CodeDeployDefault.ECSAllAtOnce configuration, with automated rollbacks configured via CloudWatch alarms.
  4. D
    An AWS CodeDeploy blue/green deployment using a custom canary configuration (ECSCanary10Percent5Minutes) to limit task provisioning, with automated rollbacks configured via CloudWatch alarms.

Answer

An ECS rolling update with the minimum healthy percent set to 8080%, the maximum percent set to 120120%, and the ECS deployment circuit breaker enabled with rollback.
The correct option is the ECS rolling update with the minimum healthy percent set to 8080% and the maximum percent set to 120120%. This configuration ensures that at least 88 tasks (8080% of 1010) are always healthy and serving traffic, and restricts the ECS scheduler from running more than 1212 tasks (120120% of 1010) concurrently, satisfying the regional quota limit. Enabling the ECS deployment circuit breaker with rollback allows ECS to automatically roll back to the last stable deployment revision if the new tasks fail to reach a steady state, meeting all requirements natively.

Step-by-Step Solution

1
Calculate the minimum healthy task count and maximum task limit based on the percentage parameters.
A minimum healthy percent of 8080% requires at least 88 tasks to remain healthy (10×0.8=810 \times 0.8 = 8). A maximum percent of 120120% limits the total concurrent tasks to 1212 (10×1.2=1210 \times 1.2 = 12).
To verify compliance with the resource quotas and availability constraints specified in the scenario.
2
Evaluate AWS CodeDeploy blue/green deployment capabilities for ECS under task capacity limitations.
All CodeDeploy blue/green deployments for ECS require provisioning a full replacement task set (1010 tasks) before any traffic is shifted, requiring a total of 2020 tasks (200200% capacity).
To determine if CodeDeploy can satisfy the constraint of having at most 1212 concurrent tasks.
3
Verify the configuration needed for automated rollback in the chosen deployment model.
The native ECS deployment circuit breaker automatically monitors task launch and health check failures, triggering an automated rollback to the last stable task definition revision if the deployment fails.
To meet the requirement for automated rollback on container launch or health check failure without manual intervention.

Key Concept

ECS Rolling Updates vs CodeDeploy Blue/Green task provisioning constraints and native deployment circuit breaker rollbacks.
Estimated Time:3m 0s
Rate this question

Topics

Deployment Strategies

More questions from this topic