CV0-004 Operations and Support Practice Question
A cloud administrator notices that an auto-scaling group is frequently adding and removing instances due to brief spikes in CPU usage. What should be adjusted to stabilize the scaling activity?
⚠ Common exam trap
CV0-004 often tests whether candidates confuse cooldown with capacity limits — increasing max size or decreasing min size changes the bounds, but only the cooldown period controls how quickly the group reacts to metric fluctuations.
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
✓
Increase the cooldown period
Increasing the cooldown period prevents the auto-scaling group from launching or terminating additional instances immediately after a scaling activity, which smooths out reactions to brief CPU spikes. A longer cooldown gives metrics time to stabilize before another scaling decision is made, reducing thrashing. This directly addresses the frequent add/remove behavior described.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Increase the cooldown period
Why this is correct
The cooldown period enforces a waiting interval after each scaling activity before another can begin. Extending it prevents the auto-scaling group from reacting to brief CPU spikes, stabilising instance additions and removals as the stem requires.
- ✗
Increase the maximum instance count
Why it's wrong here
Raising the maximum instance count only caps how far the group can grow; it does not stop repeated add-and-remove cycles caused by brief CPU spikes breaching the scaling threshold. It is tempting when capacity is the concern, but the correct adjustment changes the alarm evaluation or cooldown timing.
- ✗
Decrease the minimum instance count
Why it's wrong here
Lowering the minimum instance count does not dampen reaction to CPU spikes; scaling policies still add and remove instances within the new floor and ceiling. It is tempting as a cost-control measure, but the correct fix targets the alarm threshold or cooldown so brief spikes do not trigger scaling actions.
- ✗
Decrease the cooldown period
Why it's wrong here
Shortening the cooldown period lets the group react to further alarms sooner, amplifying the flapping rather than stabilising it. It is tempting because cooldown sounds like the throttling control, but lengthening it, or adjusting the alarm threshold, is what prevents brief CPU spikes from triggering repeated scaling actions.
About these practice questions
Courseiva writes every CV0-004 question from scratch — 834 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This CV0-004 practice question is part of Courseiva's free CompTIA 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 CV0-004 exam.