[Solved] Given this ECS service auto scaling configuration snippet:{"MinCapacity": 2, "MaxCapacity": 5, "TargetValue": 60}What happens when CPU utilization stays at 70% for a long time? | AWS

AWS - ECS and Fargate

Given this ECS service auto scaling configuration snippet:

{"MinCapacity": 2, "MaxCapacity": 5, "TargetValue": 60}

What happens when CPU utilization stays at 70% for a long time?

AThe service scales up to 5 containers to reduce CPU load

BThe service scales down to 2 containers to save cost

CThe service keeps running 2 containers without change

DThe service crashes due to high CPU

Step-by-Step Solution

Solution:

Step 1: Understand scaling triggers from CPU target
TargetValue 60 means ECS tries to keep CPU near 60%. If CPU is 70%, it needs more containers.
Step 2: Apply min and max capacity limits
Min is 2, max is 5. Scaling up is allowed up to 5 containers to reduce CPU load.
Final Answer:
The service scales up to 5 containers to reduce CPU load -> Option A
Quick Check:
CPU above target scales up containers = The service scales up to 5 containers to reduce CPU load [OK]

Quick Trick: CPU above target scales up, below scales down [OK]

Common Mistakes:

Master "ECS and Fargate" in AWS

9 interactive learning modes - each teaches the same concept differently

More AWS Quizzes

Given this ECS service auto scaling configuration snippet: