AWS - ECS and FargateAn AWS ECS service is not scaling up when CPU usage is high. What is a likely misconfiguration?AAuto Scaling policy missing or incorrectBTask definition uses too little memoryCContainer image is too largeDService desired count is set to maximumCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand ECS scaling triggersAuto Scaling policies trigger scaling based on metrics like CPU; missing policies prevent scaling.Step 2: Rule out other optionsMemory size and image size do not directly affect scaling; desired count max set prevents scaling up but is not a misconfiguration if intentional.Final Answer:Auto Scaling policy missing or incorrect -> Option AQuick Check:ECS scaling issue = B [OK]Quick Trick: Ensure Auto Scaling policies are configured for scaling [OK]Common Mistakes:Ignoring missing scaling policiesBlaming task memory for scalingConfusing desired count max with misconfiguration
Master "ECS and Fargate" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes Architecture Best Practices - Performance efficiency pillar - Quiz 14medium Architecture Best Practices - Cost optimization pillar - Quiz 13medium Architecture Best Practices - Cost optimization pillar - Quiz 14medium Architecture Best Practices - High availability design patterns - Quiz 7medium CloudFormation - Outputs for cross-stack references - Quiz 1easy Cost Optimization - S3 storage class optimization - Quiz 6medium EKS - Node groups (managed, self-managed, Fargate) - Quiz 13medium Route 53 - Record types (A, AAAA, CNAME, Alias) - Quiz 15hard Route 53 - Route 53 with ELB integration - Quiz 10hard Serverless Architecture - Lambda with DynamoDB Streams - Quiz 13medium