- A
The scaling policy has a cooldown period that is too long, preventing new scaling activities.
A long cooldown period can delay or prevent scaling actions, even if the metric is high.
- B
The instance type is not supported by the Auto Scaling group's launch configuration.
Why wrong: An unsupported instance type would cause launch failures, not prevent scaling based on CPU.
- C
The CloudWatch alarm is in the ALARM state but the Auto Scaling group has a suspended process for Add instances.
Why wrong: A suspended process would prevent scaling, but the alarm state is irrelevant; the question implies no alarm triggers.
- D
The Auto Scaling group's health check type is set to ELB, causing the instance to be marked unhealthy.
Why wrong: Health check type affects instance health, not scaling based on CPU utilization.
Quick Answer
The answer is that an overly long cooldown period is the most likely cause when Auto Scaling fails to launch new instances despite sustained high CPU utilization. After a scaling activity completes, the Auto Scaling group enters a cooldown period that temporarily blocks all subsequent scaling actions, even if the CloudWatch alarm remains in ALARM state. If this cooldown is set too long—for example, 600 seconds or more—the group simply waits out the timer, ignoring the persistent high load. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this scenario tests your understanding of how cooldowns interact with scaling policies and alarm states; a common trap is assuming the alarm itself is broken or that the metric is misconfigured. Remember the key distinction: a cooldown prevents the policy from executing, not the alarm from triggering. For a quick memory tip, think “Cool Down, No Launch”—the cooldown timer overrides the alarm’s urgency.
SOA-C02 Monitoring, Logging, and Remediation Practice Question
This SOA-C02 practice question tests your understanding of monitoring, logging, and remediation. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A SysOps administrator notices that an EC2 instance's CPU utilization is consistently above 90% during business hours. The instance is part of an Auto Scaling group with a scaling policy based on average CPU utilization. Despite high utilization, no scaling events are triggered. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The scaling policy has a cooldown period that is too long, preventing new scaling activities.
The most likely cause is that the scaling policy has a cooldown period that is too long. After a scaling activity completes, the Auto Scaling group enters a cooldown period that prevents additional scaling activities from being triggered until the cooldown expires. If the cooldown period is set too long (e.g., 600 seconds or more), the group will not launch new instances even if the CloudWatch alarm remains in ALARM state with high CPU utilization, because the scaling policy is blocked from executing.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The scaling policy has a cooldown period that is too long, preventing new scaling activities.
Why this is correct
A long cooldown period can delay or prevent scaling actions, even if the metric is high.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The instance type is not supported by the Auto Scaling group's launch configuration.
Why it's wrong here
An unsupported instance type would cause launch failures, not prevent scaling based on CPU.
- ✗
The CloudWatch alarm is in the ALARM state but the Auto Scaling group has a suspended process for Add instances.
Why it's wrong here
A suspended process would prevent scaling, but the alarm state is irrelevant; the question implies no alarm triggers.
- ✗
The Auto Scaling group's health check type is set to ELB, causing the instance to be marked unhealthy.
Why it's wrong here
Health check type affects instance health, not scaling based on CPU utilization.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume a scaling policy will always trigger when the CloudWatch alarm is in ALARM state, overlooking the cooldown period as a deliberate throttling mechanism that can prevent scaling activities from being initiated.
Detailed technical explanation
How to think about this question
The cooldown period is a configurable setting (default 300 seconds) that helps stabilize the Auto Scaling group by preventing rapid, successive scaling actions. When a scaling policy triggers a scaling activity, the cooldown timer starts, and during that period, any subsequent alarm breaches are ignored for that policy. In real-world scenarios, if the cooldown is set too high (e.g., 900 seconds), the group cannot react quickly to sustained high load, leading to performance degradation. The cooldown applies per scaling policy, not per instance, so even if the alarm remains in ALARM, the policy will not execute until the cooldown expires.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Monitoring, Logging, and Remediation — study guide chapter
Learn the concepts, then practise the questions
- →
Monitoring, Logging, and Remediation practice questions
Targeted practice on this topic area only
- →
All SOA-C02 questions
1,546 questions across all exam domains
- →
AWS Certified SysOps Administrator Associate SOA-C02 study guide
Full concept coverage aligned to exam objectives
- →
SOA-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SOA-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Monitoring, Logging, and Remediation practice questions
Practise SOA-C02 questions linked to Monitoring, Logging, and Remediation.
Reliability and Business Continuity practice questions
Practise SOA-C02 questions linked to Reliability and Business Continuity.
Deployment, Provisioning, and Automation practice questions
Practise SOA-C02 questions linked to Deployment, Provisioning, and Automation.
Security and Compliance practice questions
Practise SOA-C02 questions linked to Security and Compliance.
Networking and Content Delivery practice questions
Practise SOA-C02 questions linked to Networking and Content Delivery.
Cost and Performance Optimization practice questions
Practise SOA-C02 questions linked to Cost and Performance Optimization.
SOA-C02 fundamentals practice questions
Practise SOA-C02 questions linked to SOA-C02 fundamentals.
SOA-C02 scenario practice questions
Practise SOA-C02 questions linked to SOA-C02 scenario.
SOA-C02 troubleshooting practice questions
Practise SOA-C02 questions linked to SOA-C02 troubleshooting.
Practice this exam
Start a free SOA-C02 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SOA-C02 question test?
Monitoring, Logging, and Remediation — This question tests Monitoring, Logging, and Remediation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The scaling policy has a cooldown period that is too long, preventing new scaling activities. — The most likely cause is that the scaling policy has a cooldown period that is too long. After a scaling activity completes, the Auto Scaling group enters a cooldown period that prevents additional scaling activities from being triggered until the cooldown expires. If the cooldown period is set too long (e.g., 600 seconds or more), the group will not launch new instances even if the CloudWatch alarm remains in ALARM state with high CPU utilization, because the scaling policy is blocked from executing.
What should I do if I get this SOA-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more ways this is tested on SOA-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A SysOps administrator notices that an EC2 instance's CPU utilization has been above 90% for the past hour. The instance is part of an Auto Scaling group with a CPU utilization-based scaling policy. However, no new instances have been launched. What is the most likely cause?
easy- ✓ A.The Auto Scaling cooldown period is preventing additional scaling activities.
- B.The EC2 instance is in a private subnet and cannot communicate with the Auto Scaling service.
- C.The CloudWatch alarm is publishing to an S3 bucket that is full.
- D.The scaling policy is based on memory utilization, not CPU.
Why A: The most likely cause is that the Auto Scaling cooldown period is preventing additional scaling activities. When a scaling activity completes, a cooldown period (default 300 seconds) starts during which the Auto Scaling group ignores additional CloudWatch alarms to allow metrics to stabilize. If the instance has been above 90% CPU for an hour but no new instances launched, the cooldown period may have been triggered by a previous scaling event and is still active, blocking further scale-out actions despite sustained high utilization.
Keep practising
More SOA-C02 practice questions
- A company uses an Amazon DynamoDB table with on-demand capacity mode. The table handles a workload with a steady baselin…
- A company uses Amazon CloudWatch Logs to store application logs. The SysOps administrator needs to count the occurrences…
- A SysOps administrator needs to monitor the CPU utilization of an Amazon EC2 instance and send an alert when it exceeds…
- A SysOps administrator needs to monitor the CPU utilization of an Amazon EC2 instance fleet and send an alert when the a…
- A company's security policy requires that all Amazon S3 buckets must have server-side encryption enabled. The SysOps adm…
- A SysOps administrator uses AWS CloudFormation to deploy a stack that includes an Amazon EC2 instance. The administrator…
Last reviewed: Jun 24, 2026
This SOA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SOA-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.