The answer is to verify that the CloudWatch alarm associated with the scaling policy is in ALARM state when CPU is high. This is the first step because a dynamic scaling policy relies entirely on the CloudWatch alarm to trigger the scaling action; if the alarm never enters ALARM state due to a misconfigured threshold, insufficient data points, or a broken metric, the Auto Scaling group will not scale regardless of actual CPU load. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this question tests your understanding of the dependency chain between CloudWatch alarms and Auto Scaling policies, often hiding traps like cooldown periods or incorrect metric names that prevent the alarm from firing. A common mistake is jumping to check the scaling policy itself before confirming the alarm state, so always start with the alarm. Memory tip: think “Alarm first, scaling second”—if the alarm isn’t red, the policy won’t act.
SOA-C02 Monitoring, Logging, and Remediation Practice Question
This SOA-C02 practice question tests your understanding of monitoring, logging, and remediation. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 company is using an Auto Scaling group with a dynamic scaling policy based on average CPU utilization. The SysOps administrator notices that the scaling is not triggering as expected. Which THREE steps should the administrator take to troubleshoot the issue?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Check the scaling activity history in the Auto Scaling group for any errors or cooldown periods.
Option A is correct because the scaling activity history provides a log of all scaling actions, including errors, cooldown periods, and why a scaling event was or was not triggered. By reviewing this history, the administrator can identify if the scaling policy was blocked by a cooldown period, if the alarm state was not reached, or if there were any configuration errors that prevented the scaling action 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.
✓
Check the scaling activity history in the Auto Scaling group for any errors or cooldown periods.
Why this is correct
Activity history shows why scaling did not occur.
Related concept
Read the scenario before looking for a memorised answer.
✗
Ensure that the EC2 instances are passing the ELB health checks.
Review the scaling policy's cooldown period and threshold settings.
Why this is correct
Incorrect cooldown or thresholds can prevent scaling.
Related concept
Read the scenario before looking for a memorised answer.
✓
Verify that the CloudWatch alarm associated with the scaling policy is in ALARM state when CPU is high.
Why this is correct
The alarm must trigger the scaling policy.
Related concept
Read the scenario before looking for a memorised answer.
✗
Manually increase the desired capacity to see if the scaling policy takes effect.
Why it's wrong here
Manual changes do not test the policy.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse ELB health checks with the metric-based alarm that drives scaling, or think that manually adjusting capacity is a valid diagnostic step, when in fact it bypasses the automated policy logic and does not reveal why the policy failed to trigger.
Detailed technical explanation
How to think about this question
Dynamic scaling policies in AWS Auto Scaling rely on CloudWatch alarms that monitor metrics like average CPU utilization. When the alarm transitions to ALARM state, it triggers the scaling policy, which then evaluates the cooldown period and threshold settings before executing a scaling action. The scaling activity history records each step, including the alarm state change, the policy evaluation, and any cooldown delays, allowing administrators to pinpoint where the process failed.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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 — 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: Check the scaling activity history in the Auto Scaling group for any errors or cooldown periods. — Option A is correct because the scaling activity history provides a log of all scaling actions, including errors, cooldown periods, and why a scaling event was or was not triggered. By reviewing this history, the administrator can identify if the scaling policy was blocked by a cooldown period, if the alarm state was not reached, or if there were any configuration errors that prevented the scaling action 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.
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 →
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.
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.