easyMultiple Choice
Auto-Scaling for Unpredictable Traffic Spikes
An architect is designing a cloud application that must handle unpredictable spikes in traffic. The application should automatically add resources during peak demand and remove them when demand decreases to minimize costs. Which scaling strategy should be used?
Quick Answer
The correct answer is horizontal auto-scaling based on CPU utilization. This strategy is the right choice because it directly implements cloud elasticity, allowing the application to dynamically add new instances (scale out) when CPU load spikes unpredictably and remove them (scale in) when demand drops, thereby handling unpredictable traffic spikes while minimizing costs. On the CompTIA Cloud+ CV0-004 exam, this question tests your understanding of scaling policies and the distinction between horizontal and vertical scaling; a common trap is selecting vertical scaling, which adds power to a single instance and fails to handle distributed spikes efficiently. Remember the memory tip: “Horizontal handles the herd” — think of adding more servers (horizontal) rather than a bigger server (vertical) when traffic is unpredictable.
⚠ Common exam trap
Candidates often confuse vertical scaling (scaling up) with horizontal scaling (scaling out), assuming resizing existing instances is more cost-effective, but vertical scaling has hard limits and cannot match the elasticity required for unpredictable spikes.
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 auto-scaling based on CPU utilization
Horizontal auto-scaling based on CPU utilization is the correct strategy because it dynamically adds or removes instances in response to real-time demand, ensuring the application can handle unpredictable traffic spikes while minimizing costs. This approach aligns with cloud elasticity principles, where resources scale out (add instances) during high CPU load and scale in (remove instances) when load decreases, without manual intervention.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Scheduled scaling based on historical patterns
Why it's wrong here
Scheduled scaling provisions capacity at predetermined times from historical patterns, so it cannot react to unpredictable spikes occurring outside those windows. It is tempting because schedule-based rules suit workloads with known, repeating peaks, such as a payroll batch run every Friday evening.
- ✗
Vertical scaling of existing instances
Why it's wrong here
Vertical scaling adds CPU or memory to existing instances, which cannot absorb unpredictable spikes quickly and leaves capacity idle once demand falls, so costs are not minimised. It is tempting because resizing a single instance suits steady growth on a monolithic database that cannot be distributed across nodes.
- ✗
Manual scaling by operations team
Why it's wrong here
Manual scaling requires an operator to detect demand and resize capacity, which is too slow for unpredictable spikes and cannot remove resources promptly to minimise cost. It is tempting because hands-on scaling suits rare, planned events where an engineer deliberately controls capacity changes.
- ✓
Horizontal auto-scaling based on CPU utilization
Why this is correct
Horizontal auto-scaling adds or removes instances, and CPU utilisation is the trigger metric that reflects load. This matches unpredictable spikes by scaling out at peak and in during lulls, minimising cost, whereas vertical scaling requires restarts and has fixed ceilings.
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 →
Same concept, more angles
1 more way this is tested on CV0-004
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A startup is deploying a web application on a public cloud and expects variable traffic throughout the day. The team wants to minimize costs while ensuring that the application can handle sudden spikes in demand. Which scaling strategy best meets these requirements?
easy- ✓ A.Auto scaling based on CPU utilization thresholds
- B.Horizontal scaling using a fixed schedule
- C.Vertical scaling during off-peak hours
- D.Manual scaling based on historical data
Why A: Auto scaling based on CPU utilization thresholds is the correct strategy because it dynamically adjusts the number of compute instances in response to real-time demand, ensuring the application can handle sudden spikes while minimizing costs during low-traffic periods. This approach aligns with the startup's requirement for variable traffic and cost efficiency, as it only provisions resources when needed, unlike fixed schedules or manual interventions that cannot react to unpredictable spikes.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.