easyMultiple Choice
CV0-004 Practice Question: Needs to deploy a stateless application across…
A cloud engineer needs to deploy a stateless application across multiple availability zones. The application must scale horizontally based on CPU utilization. Which of the following is the BEST configuration?
⚠ Common exam trap
A common trap is choosing vertical scaling (Option A) because it seems simpler, but it does not meet the requirement for multi-AZ distribution and automated horizontal scaling.
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
✓
Create an auto-scaling group spanning multiple zones with a load balancer
An auto-scaling group spanning multiple availability zones ensures high availability and fault tolerance by distributing instances across zones, while the load balancer distributes traffic and the scaling policy adjusts capacity based on CPU utilization. This configuration meets the requirements for a stateless, horizontally scalable application 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.
- ✗
Deploy a single large instance and increase its size as needed
Why it's wrong here
Vertical scaling enlarges one instance in a single zone, so it neither spans availability zones nor adds instances in response to CPU load. It is tempting because resizing is a legitimate capacity tactic for monolithic workloads that cannot be distributed, and it would be correct where the application is stateful and cannot run as multiple replicas.
- ✓
Create an auto-scaling group spanning multiple zones with a load balancer
Why this is correct
An auto-scaling group spanning multiple availability zones with a load balancer directly satisfies both constraints: horizontal scaling driven by CPU utilisation and resilience across zones. The load balancer distributes traffic to healthy instances, while the scaling group adds or removes capacity as demand changes.
- ✗
Use a managed container service and manually add containers
Why it's wrong here
Manual container addition provides no CPU-driven autoscaling and no automatic replacement across zones, so capacity changes require operator action. It is tempting because managed container services host stateless workloads well, and the approach would be correct if scaling were event-driven or scheduled rather than metric-based on CPU utilisation.
- ✗
Deploy instances in one zone using spot instances to reduce cost
Why it's wrong here
Spot instances can be reclaimed with little notice, and confining them to one zone removes the multi-zone resilience the application requires. It is tempting because spot capacity cuts compute cost substantially, and it would be correct for interruption-tolerant batch or fault-tolerant workloads that do not need zone redundancy.
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 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.