AWS - Auto ScalingAn Auto Scaling group is not scaling out despite high CPU usage. Which of the following is a likely misconfiguration?AScaling policy threshold is set higher than current CPU usageBMinSize is set higher than MaxSizeCDesiredCapacity is set to zeroDCooldown period is set to zeroCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand scaling triggersScaling out happens when CPU usage exceeds the policy threshold.Step 2: Check threshold vs actual CPUIf threshold is higher than current CPU, scaling won't trigger despite high usage.Final Answer:Scaling policy threshold too high prevents scaling out -> Option AQuick Check:Threshold > CPU blocks scaling [OK]Quick Trick: Scaling triggers only if metric exceeds threshold [OK]Common Mistakes:Confusing MinSize and MaxSize settingsAssuming cooldown zero disables scalingThinking DesiredCapacity zero stops scaling out
Master "Auto Scaling" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes API Gateway - CORS configuration - Quiz 8hard AWS Lambda - Lambda handler function structure - Quiz 2easy AWS Lambda - Lambda layers for shared code - Quiz 3easy Auto Scaling - Scaling policies (target tracking, step, simple) - Quiz 3easy CloudWatch - CloudWatch metrics - Quiz 12easy CloudWatch - Why monitoring matters - Quiz 4medium Elastic Load Balancing - Health checks configuration - Quiz 15hard RDS and Relational Databases - Read replicas for performance - Quiz 8hard RDS and Relational Databases - RDS supported engines - Quiz 12easy RDS and Relational Databases - Multi-AZ deployment for high availability - Quiz 3easy