CCSP Cloud Concepts, Architecture, and Design Practice Question
Which design principle is most directly aimed at avoiding vendor lock-in and ensuring that workloads can be moved between cloud providers with minimal effort?
⚠ Common exam trap
Many exam-takers confuse portability with reversibility — both relate to avoiding lock-in, but portability is about moving workloads to another provider, while reversibility is about exiting and recovering data from the current provider.
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
✓
Portability
Portability is the design principle specifically concerned with avoiding vendor lock-in by ensuring workloads, data, and configurations can be moved between cloud providers with minimal rework. It drives the use of open standards, containerization, and abstraction layers so that an application is not tied to proprietary APIs or services. Reversibility is related but focuses on the ability to exit a provider and bring data back, whereas portability is about the ability to move and run elsewhere.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Portability
Why this is correct
Portability is the design principle that keeps workloads free of provider-specific dependencies, allowing migration between clouds with minimal rework. It directly addresses vendor lock-in by requiring portable formats, APIs and configurations, so the stem's movement requirement is met.
- ✗
Reversibility
Why it's wrong here
Reversibility concerns rolling back a deployment or state change, not portability between providers; it addresses recovering from failed releases. Avoiding lock-in requires abstraction layers, open standards and portable data formats. Reversibility would be the right principle when the requirement is undoing a bad change quickly.
- ✗
Elasticity
Why it's wrong here
Elasticity governs automatic scaling of resources to match demand, not portability between providers; it does nothing to reduce lock-in. It is tempting because it is a headline cloud design principle, and would be correct when the requirement is matching capacity to fluctuating load rather than enabling migration.
- ✗
Multitenancy isolation
Why it's wrong here
Multitenancy isolation addresses separating tenants' data and workloads within shared infrastructure, which is a security and compliance concern, not provider portability. It is tempting because it is a recognised cloud design principle, and would be correct when the requirement is preventing cross-tenant data leakage rather than avoiding lock-in.
Go deeper
Related to this question
About these practice questions
One of 934 original CCSP 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 ISC2 exam blueprint
This CCSP practice question is part of Courseiva's free ISC2 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 CCSP exam.