The correct design principle is to refactor the application into microservices deployed across multiple instances. This approach is essential for cloud-native scalability and resilience because microservices allow each component to scale independently based on demand, rather than forcing the entire monolithic application to scale as a single unit. By breaking the application into loosely coupled services, you also achieve fault isolation—if one service fails, it does not bring down the entire system, which directly addresses the single-point-of-failure risk of the legacy design. On the CompTIA Cloud+ CV0-004 exam, this scenario tests your understanding of how cloud-native design patterns like containerization and orchestration (e.g., Kubernetes) enable horizontal scaling and elasticity, a core objective in the “Cloud Architecture and Design” domain. A common trap is assuming that simply moving the monolithic app to a cloud VM is sufficient, but that ignores the need for distributed, stateless services that leverage cloud storage instead of a local file system. Memory tip: think “M for Microservices, M for Multiple instances, M for Maximum resilience.”
CV0-004 Cloud Architecture and Design Practice Question
This CV0-004 practice question tests your understanding of cloud architecture and design. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company is migrating a legacy on-premises application to a public cloud. The application currently uses a single monolithic architecture and relies on a local file system for storage. The cloud architect needs to redesign the application to take advantage of cloud-native features. Which design principle should the architect prioritize to ensure scalability and resilience?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Refactor the application into microservices deployed across multiple instances
Option C is correct because refactoring the monolithic application into microservices enables independent scaling of components, improves fault isolation, and aligns with cloud-native patterns like containerization and orchestration (e.g., Kubernetes). This approach leverages horizontal scaling across multiple instances, which is essential for achieving elasticity and resilience in a public cloud environment, unlike the legacy single-point-of-failure monolithic design.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Maintain the monolithic architecture and connect via VPN to on-premises storage
Use vertical scaling by increasing vCPU and RAM on a single large VM
Why it's wrong here
Vertical scaling has limits and does not provide resilience.
✓
Refactor the application into microservices deployed across multiple instances
Why this is correct
Microservices enable independent scaling and fault isolation.
Related concept
Read the scenario before looking for a memorised answer.
✗
Deploy the entire application in a single availability zone to reduce latency
Why it's wrong here
Single availability zone lacks high availability.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse vertical scaling (Option B) as a valid cloud-native approach, but the exam emphasizes horizontal scaling and decoupled architectures as the correct principles for scalability and resilience in cloud design.
Detailed technical explanation
How to think about this question
Microservices communicate via lightweight protocols like HTTP/REST or gRPC, and each service can be independently deployed, scaled, and monitored using container orchestration platforms such as Kubernetes, which provides auto-scaling based on CPU/memory metrics and self-healing through liveness probes. In a real-world scenario, a monolithic application with a local file system would be refactored to use a distributed object store (e.g., Amazon S3) for persistence, and stateful services would leverage managed databases (e.g., Amazon RDS) to ensure data durability and availability across zones.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Cloud Architecture and Design — This question tests Cloud Architecture and Design — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Refactor the application into microservices deployed across multiple instances — Option C is correct because refactoring the monolithic application into microservices enables independent scaling of components, improves fault isolation, and aligns with cloud-native patterns like containerization and orchestration (e.g., Kubernetes). This approach leverages horizontal scaling across multiple instances, which is essential for achieving elasticity and resilience in a public cloud environment, unlike the legacy single-point-of-failure monolithic design.
What should I do if I get this CV0-004 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.