CV0-004 Cloud Architecture and Design Practice Question
A company is running a stateless web application on a public cloud. They expect traffic to spike during certain hours. Which scaling strategy would be most cost-effective and efficient?
⚠ Common exam trap
CV0-004 often tests the misconception that vertical scaling is more efficient for spiky traffic, but the exam expects you to recognize that horizontal scaling with auto-scaling groups is the most cost-effective and efficient for stateless applications.
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
✓
Horizontal scaling using auto-scaling groups based on CPU utilization
Horizontal scaling with auto-scaling groups based on CPU utilization is the most cost-effective and efficient strategy for a stateless web application with variable traffic. Auto-scaling groups automatically adjust the number of instances in response to real-time demand, ensuring you only pay for the capacity you need. Because the application is stateless, any instance can handle any request, making horizontal scaling seamless and highly available. This approach eliminates manual intervention and optimizes costs by scaling in during low-traffic periods.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Using a larger instance type and scheduling scaling actions
Why it's wrong here
Resizing to a larger instance and scheduling actions keeps capacity fixed between spikes, so the application still cannot absorb unexpected load and pays for idle headroom. It tempts for predictable diurnal patterns, but horizontal auto-scaling matching instance count to demand handles variable spikes cost-effectively.
- ✗
Pre-provisioning double capacity permanently
Why it's wrong here
Permanently doubling capacity provisions for peak continuously, so the company pays for idle instances during every off-peak hour. It tempts when spikes are guaranteed and latency-critical, but horizontal auto-scaling that adds instances on demand and removes them afterwards matches the stateless workload's variable traffic.
- ✓
Horizontal scaling using auto-scaling groups based on CPU utilization
Why this is correct
Auto-scaling groups add or remove identical stateless instances horizontally as CPU utilisation rises and falls, matching capacity to demand. This satisfies the cost-effectiveness constraint because instances are billed only while running, unlike vertical scaling, which requires permanently larger, pricier instances.
- ✗
Vertical scaling with manual adjustments before anticipated spikes
Why it's wrong here
Vertical scaling resizes a single instance, so capacity is capped by the largest available instance type and manual pre-spike adjustments cannot track unpredictable hourly demand. It suits steady growth in a stateful workload where horizontal distribution is impractical, not a stateless web tier that can scale out automatically.
Go deeper
Related to this question
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.