CV0-004 Operations and Support Practice Question
A cloud administrator is configuring an auto-scaling group for a web application. The application experiences predictable traffic spikes every weekday at 9 AM. Which scaling policy is most appropriate?
⚠ Common exam trap
CV0-004 often tests the misconception that target tracking or step scaling is 'best' for all workloads — the discriminator is whether the load pattern is predictable (scheduled) or variable (dynamic), and candidates who default to CPU-based target tracking miss the 'predictable spike' keyword.
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
✓
Scheduled scaling to add instances before 9 AM
The traffic spike is predictable (every weekday at 9 AM), and scheduled scaling pre-provisions capacity before the spike begins, avoiding the lag inherent in reactive policies. This is the canonical use case for scheduled scaling in AWS Auto Scaling, Azure VMSS, and GCP MIG.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Step scaling with a cool-down period
Why it's wrong here
Step scaling reacts to breached CloudWatch thresholds, so weekday 9 AM spikes still incur detection and alarm latency rather than pre-empting them. It is tempting because it handles unpredictable load, and would be correct for variable traffic where thresholds must trigger graduated capacity additions.
- ✗
Simple scaling with a 300-second cooldown
Why it's wrong here
Simple scaling triggers on a single alarm and enforces a 300-second cooldown, delaying capacity during the predictable 9 AM spike. It is tempting as the default policy, and would be correct for infrequent, non-urgent adjustments where a single step suffices.
- ✗
Target tracking scaling based on average CPU utilization
Why it's wrong here
Target tracking responds to observed CPU breaches, so capacity arrives after the 9 AM spike begins rather than before it. It is tempting because it self-tunes without manual thresholds, and would be correct for steady, unpredictable demand where CPU correlates with load.
- ✓
Scheduled scaling to add instances before 9 AM
Why this is correct
Scheduled scaling adds instances ahead of the known 9 AM weekday spike, matching the predictable, time-based demand pattern. Unlike dynamic or reactive policies, it provisions capacity before traffic arrives, avoiding the lag inherent in metric-triggered responses and ensuring sufficient resources are ready when the surge begins.
About these practice questions
This CV0-004 question is part of Courseiva's 834-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.