CV0-004 Cloud Architecture and Design Practice Question
A cloud architect is evaluating a multi-cloud strategy to improve resilience. Which THREE factors should be considered when designing multi-cloud architecture? (Select THREE.)
⚠ Common exam trap
CV0-004 often tests multi-cloud design factors; candidates may incorrectly select vendor lock-in as a benefit or overlook the importance of data transfer costs and portability.
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
✓
Data transfer costs between clouds
Option B (Data transfer costs between clouds) is correct because multi-cloud designs frequently move data across provider boundaries, and egress charges plus inter-cloud transfer fees can significantly erode the cost benefits of a multi-cloud strategy, so they must be modeled during design. Option D (Application portability and interoperability) is correct because resilience in a multi-cloud architecture depends on workloads being able to run on more than one provider, which requires avoiding proprietary APIs and using portable formats such as containers, Kubernetes, and open standards. Option E (Consistent security and compliance policies across clouds) is correct because each provider implements identity, encryption, and logging differently, so a unified policy framework and controls such as federated IAM and centralized logging are needed to maintain a consistent security posture. Option A (Increased vendor lock-in) is not a valid factor because multi-cloud is generally adopted to reduce dependence on a single vendor, not to increase lock-in. Option C (Ability to manage all clouds with a single API) is not a required design factor because no single universal API natively manages AWS, Azure, and GCP; management is typically achieved through abstraction layers, IaC tools like Terraform, or multi-cloud platforms rather than one provider API.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increased vendor lock-in
Why it's wrong here
Multi-cloud reduces lock-in by distributing workloads across independent providers, so increased lock-in contradicts the stated resilience goal. It is tempting because single-provider commitment does deepen lock-in, but that describes a consolidation scenario, not the multi-cloud design being evaluated here.
- ✓
Data transfer costs between clouds
Why this is correct
Egress charges apply whenever data leaves a provider's network, so cross-cloud replication and failover traffic incur fees that single-cloud designs avoid. This directly addresses the resilience-versus-cost trade-off the architect must weigh, since continuous synchronisation between clouds multiplies billable egress volume.
- ✗
Ability to manage all clouds with a single API
Why it's wrong here
Each provider exposes its own proprietary API, so no single API manages all clouds; abstraction layers only partially mask this. It is tempting because unified tooling is a genuine multi-cloud design goal, but the stem asks for factors to consider, and API fragmentation is a constraint rather than a benefit.
- ✓
Application portability and interoperability
Why this is correct
Portability and interoperability let workloads move between providers without re-engineering, directly satisfying the resilience goal of avoiding dependence on any single cloud. Without common APIs and container standards, failover between clouds becomes impractical, so this factor underpins the multi-cloud design.
- ✓
Consistent security and compliance policies across clouds
Why this is correct
Multi-cloud spans providers with differing IAM models, encryption defaults and regional data-residency rules, so a unified policy framework is required to satisfy regulatory obligations and avoid per-cloud security gaps. This addresses the governance constraint inherent in distributing workloads across independent providers.
Go deeper
Related to this question
About these practice questions
One of 834 original CV0-004 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.