AWS - ECS and FargateIf an ECS service has a min capacity of 3 and max capacity of 6, and current tasks are 6 with CPU at 30%, what will auto scaling do?AScale in to reduce tasks below 6BScale out to add more tasksCKeep tasks at 6 since max capacity reachedDStop all tasks due to low CPUCheck Answer
Step-by-Step SolutionSolution:Step 1: Analyze CPU usage and scaling limitsCPU is below target, so ECS tries to scale in (reduce tasks).Step 2: Check min and max capacity constraintsCurrent tasks are at max 6, so scaling in is allowed down to min 3.Final Answer:Scale in to reduce tasks below 6 -> Option AQuick Check:Low CPU = scale in (reduce tasks) [OK]Quick Trick: Low CPU triggers scale in, respecting min capacity [OK]Common Mistakes:Trying to scale out when CPU is lowAssuming tasks stay at max capacity alwaysThinking ECS stops tasks automatically
Master "ECS and Fargate" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes Advanced Security - KMS for key management - Quiz 8hard Advanced Security - KMS for key management - Quiz 9hard Advanced Security - AWS Shield for DDoS protection - Quiz 6medium Architecture Best Practices - Multi-tier architecture patterns - Quiz 7medium Architecture Best Practices - Reliability pillar principles - Quiz 11easy CloudFormation - Outputs for cross-stack references - Quiz 7medium Cost Optimization - AWS Trusted Advisor recommendations - Quiz 10hard Cost Optimization - Data transfer cost awareness - Quiz 1easy EKS - EKS networking with VPC CNI - Quiz 1easy Route 53 - Health checks with Route 53 - Quiz 14medium