CV0-004 Operations and Support Practice Question
A cloud engineer notices that an auto-scaling group is adding and removing instances too frequently, causing instability. Which configuration parameter should be adjusted to reduce this behavior?
⚠ Common exam trap
CV0-004 often tests the confusion between cooldown (dampening scaling frequency) and health check grace period (delaying health evaluation), causing candidates to pick the wrong stabilization control.
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 is the correct adjustment because cooldown is the waiting time after a scaling activity before the auto-scaling group can perform another scaling action. A longer cooldown lets newly launched instances stabilize and metrics to reflect the new capacity, preventing the rapid add/remove oscillation known as thrashing. This directly reduces the instability 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 health check grace period
Why it's wrong here
The grace period only delays health-check evaluation after launch; it does not stop repeated scale-out and scale-in decisions. It is tempting because it addresses instance stability, and it would be correct when new instances are wrongly marked unhealthy before they finish booting.
- ✗
Disable lifecycle hooks
Why it's wrong here
Lifecycle hooks pause instances during launch or termination for custom actions; they do not govern how often scaling policies trigger. Disabling them is tempting when instances terminate before draining connections, but the flapping stems from cooldown and threshold settings, not hook behaviour.
- ✓
Increase the cooldown period
Why this is correct
Increasing the cooldown period forces the auto-scaling group to wait after each scaling activity before triggering another, directly damping the rapid add-remove oscillation described. This satisfies the stability constraint by preventing consecutive scale-out and scale-in events from chasing transient metric spikes.
- ✗
Lower the scaling metric thresholds
Why it's wrong here
Lowering thresholds makes the group react to smaller metric deviations, increasing add-and-remove cycles rather than damping them. It is tempting because tightening thresholds feels like tuning sensitivity, and it would be right when scaling responds too slowly to genuine load changes.
Go deeper
Related to this question
About these practice questions
One of 834 original CV0-004 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.