A SysOps Administrator is configuring a rolling update deployment strategy for a container… — AWS Certified SysOps Administrator - Associate

A SysOps Administrator is configuring a rolling update deployment strategy for a containerized application running on an Amazon ECS cluster with the Amazon EC2 launch type. The ECS service is configured with a desired task count of $10$ tasks.

The deployment must satisfy the following operational requirements:
* No running tasks from the current version can be terminated until the replacement tasks are verified as healthy.
* The total CPU and memory reservation on the container instances must never exceed $120\%$ of the desired task allocation during the deployment due to tight cluster capacity constraints.
* The application must remain highly available, ensuring that the number of active, healthy tasks never drops below $80\%$ of the desired count.

Which two ECS service definition parameters must the administrator configure to meet these requirements? (Select TWO.)

Set minimumHealthyPercent to $100$ Answer
Set maximumPercent to $120$ Answer
C
Set minimumHealthyPercent to $80$
D
Set maximumPercent to $200$
E
Set minimumHealthyPercent to $120$

Answer

Configure the Amazon ECS service with minimumHealthyPercent set to

100

and maximumPercent set to

120

The correct options are configuring the service with minimumHealthyPercent set to

100

and maximumPercent set to

120

. Setting the minimum healthy percent to

100\%

guarantees that the ECS scheduler will not terminate any existing tasks before new ones are verified as healthy. Setting the maximum percent to

120\%

limits the temporary scale-up capacity during the rolling update to at most

12

tasks (

120\%

of the desired

10

tasks), which prevents exceeding the cluster resource reservation limit.

Step-by-Step Solution

Analyze the constraint that no running tasks can be terminated before replacement tasks are verified as healthy.

Determine that the minimum healthy percent must be at least

100\%

. This ensures the service scheduler launches new tasks first and only terminates older tasks once the new ones are healthy.

Lower values like

80\%

would allow ECS to terminate tasks beforehand to make room, violating the zero-downtime dependency check.

Analyze the capacity constraint that resource reservations must not exceed

120\%

of the desired task allocation.

Determine that the maximum percent must be set to

120\%

. For a desired count of

10

tasks, this limits the total tasks in the RUNNING or PENDING state to at most

12

tasks at any time.

This prevents overloading the cluster's EC2 container instances with excess CPU and memory reservations during the rolling transition.

Verify that the availability requirement (minimum healthy tasks never dropping below

80\%

) is met.

Confirm that keeping the minimum healthy percent at

100\%

maintains exactly

10

healthy tasks (

100\%

) during the deployment, which is greater than the

80\%

(

8

tasks) threshold.

This configuration safely meets all three requirements simultaneously.

Key Concept

Configuring ECS rolling update deployment parameters (minimumHealthyPercent and maximumPercent) to balance application availability and resource capacity.

Estimated Time:2m 30s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic