A developer is designing a deployment strategy for a containerized web application running… — AWS Certified Developer - Associate

A developer is designing a deployment strategy for a containerized web application running on Amazon ECS (Fargate) behind an Application Load Balancer. The service currently runs with a desired task count of $8$ . The deployment must satisfy the following constraints:

* The application must maintain $100\%$ of its capacity (at least $8$ healthy tasks) during the deployment process.
* The AWS account has a strict service quota that prevents running more than $10$ concurrent tasks for this service.
* If the new container version fails to launch or fails container health checks, the deployment must automatically roll back to the previous version without manual intervention or DNS changes.

Which two configurations should the developer use to meet these requirements? (Select two.)

Configure the ECS service rolling update parameters with a minimum healthy percent of $100\%$ and a maximum percent of $125\%$ .Cevap
Enable the ECS deployment circuit breaker with the rollback feature enabled on the service.Cevap
C
Configure the ECS service rolling update parameters with a minimum healthy percent of $50\%$ and a maximum percent of $100\%$ .
D
Configure AWS CodeDeploy to perform a blue/green deployment using an ECS Canary deployment configuration.
E
Configure an Amazon Route 53 weighted routing policy to route traffic between two separate ECS services.

Cevap

Configure the ECS service rolling update parameters with a minimum healthy percent of

100\%

and a maximum percent of

125\%

, and enable the ECS deployment circuit breaker with the rollback feature enabled on the service.

To maintain

100\%

capacity during the deployment of a service with

8

desired tasks, at least

8

tasks must remain healthy, which translates to a minimum healthy percent of

100\%

. To not exceed

10

tasks total (which is

125\%

8

), the maximum percent must be set to

125\%

. In this configuration, ECS will launch

2

new tasks, wait for them to pass health checks, and then terminate

2

old tasks, repeating the process. Enabling the ECS deployment circuit breaker with rollback ensures that if these new tasks fail to launch or fail health checks, the deployment is automatically canceled and the service rolls back to the previous stable task definition without manual effort or DNS changes.

Adım Adım Çözüm

Calculate the capacity and task count boundaries based on the constraints.

The minimum healthy task count must be at least

8

(

100\%

of desired). The maximum concurrent tasks cannot exceed

10

, which represents

125\%

of the desired

8

tasks (

10 / 8 = 1.25

This establishes the mathematical bounds for the ECS service's minimumHealthyPercent and maximumPercent configurations.

Determine the correct deployment mechanism that respects the task limit.

An ECS rolling update starts a batch of new tasks (up to

2

tasks, which is

25\%

of desired) before stopping the old ones. A CodeDeploy blue/green deployment requires launching an entire second task set (

8

tasks), which violates the

10

task limit.

This rules out blue/green deployment options in favor of an ECS rolling update.

Select the appropriate automated rollback mechanism that doesn't rely on DNS.

Enable the ECS deployment circuit breaker with rollback. This built-in ECS feature detects launch or health check failures and automatically rolls back the deployment to the last stable state.

This fulfills the requirement of automatic, rapid rollback without manual intervention or DNS routing updates.

Anahtar Kavram

ECS Rolling Update parameters (minimumHealthyPercent and maximumPercent) control task capacity during deployment, while ECS deployment circuit breaker provides automated rollbacks without DNS modifications.

Tahmini Süre:2m 30s

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular

Bu konudan daha fazla soru