AWS - Auto ScalingAn Auto Scaling group is scaling out too often despite a cooldown period set to 180 seconds. What should you check to fix this?AIf the instances have enough CPUBIf the cooldown period is set on the launch configurationCIf the cooldown period is set on the scaling policyDIf the Auto Scaling group has a minimum size of zeroCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand cooldown placementCooldown periods must be set on scaling policies, not launch configurations.Step 2: Identify correct fixCheck if cooldown is correctly set on the scaling policy to control scaling frequency.Final Answer:If the cooldown period is set on the scaling policy -> Option CQuick Check:Cooldown on scaling policy = Correct setup [OK]Quick Trick: Cooldown belongs on scaling policies, not launch configs [OK]Common Mistakes:Setting cooldown on launch configurationIgnoring scaling policy settingsChecking unrelated instance metrics
Master "Auto Scaling" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes AWS Lambda - Lambda concurrency and throttling - Quiz 6medium CloudWatch - Why monitoring matters - Quiz 12easy DynamoDB - Creating a DynamoDB table - Quiz 14medium DynamoDB - Why DynamoDB for NoSQL - Quiz 5medium DynamoDB - DynamoDB Streams overview - Quiz 3easy DynamoDB - Why DynamoDB for NoSQL - Quiz 7medium DynamoDB - DynamoDB capacity modes (on-demand, provisioned) - Quiz 8hard RDS and Relational Databases - RDS supported engines - Quiz 9hard SNS and SQS - Why messaging services matter - Quiz 13medium SNS and SQS - Standard vs FIFO queues - Quiz 13medium