AWS - Auto ScalingYou configured auto scaling to add instances when CPU exceeds 80%, but no new instances launch despite CPU at 90%. What could cause this?AThe minimum instance count is set too highBThe maximum instance limit has been reachedCThe scaling policy threshold is set below 80%DThe instances are in a stopped stateCheck Answer
Step-by-Step SolutionSolution:Step 1: Analyze scaling conditionsScaling triggers when CPU > 80%, but no new instances appear despite 90% CPU.Step 2: Consider limitsIf the maximum number of instances is already running, no scale out occurs.Step 3: Evaluate other optionsMinimum count or threshold settings wouldn't prevent scaling out at high CPU; stopped instances don't affect scaling triggers.Final Answer:The maximum instance limit has been reached -> Option BQuick Check:Max limit blocks scaling out [OK]Quick Trick: Max instance limit stops scaling out [OK]Common Mistakes:Confusing minimum and maximum instance settingsAssuming threshold misconfigurationIgnoring instance state effects
Master "Auto Scaling" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes API Gateway - API keys and usage plans - Quiz 15hard API Gateway - API keys and usage plans - Quiz 3easy AWS Lambda - Event triggers for Lambda - Quiz 9hard CloudWatch - CloudWatch metrics - Quiz 2easy DynamoDB - Creating a DynamoDB table - Quiz 14medium Elastic Load Balancing - Listener rules and routing - Quiz 1easy Elastic Load Balancing - Target groups concept - Quiz 8hard Elastic Load Balancing - Why load balancing matters - Quiz 13medium RDS and Relational Databases - Parameter groups and option groups - Quiz 11easy RDS and Relational Databases - RDS pricing considerations - Quiz 11easy