CCSP Cloud Concepts, Architecture, and Design Practice Question
Which of the following is a key benefit of using containers, such as Docker, in a cloud environment to achieve portability?
⚠ Common exam trap
The trap here is conflating containers with virtual machines — candidates who remember 'virtualization' from VM study material may pick hardware-level virtualization (D) or hypervisor dependency (C), missing that containers virtualize at the OS layer and are defined by packaging dependencies for consistency.
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
✓
Containers package applications with dependencies to run consistently across environments
Containers bundle the application code together with its libraries, runtime, and configuration into a single immutable image, so the same image runs identically on a developer laptop, on-premises servers, or any cloud VM/container service. This decoupling from the underlying host OS and infrastructure is precisely what delivers portability across cloud environments.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Containers package applications with dependencies to run consistently across environments
Why this is correct
Containers bundle the application with its libraries and dependencies into a single image, so the same artefact runs identically on any container host. This dependency packaging, rather than hypervisor abstraction, delivers the portability across cloud environments.
- ✗
Containers are always stateless
Why it's wrong here
Containers can hold persistent volumes and writable layers, so statelessness is a design choice rather than an inherent property, and it is not what delivers portability. It tempts because twelve-factor guidance favours stateless services; that suits horizontally scalable microservices, not the portability benefit itself.
- ✗
Containers require a specific hypervisor to run
Why it's wrong here
Containers share the host operating system kernel and run via a container runtime such as containerd, requiring no hypervisor at all. It tempts because virtual machines do depend on hypervisors, and containers are often deployed inside them; that fits VM-based isolation, not container portability across cloud platforms.
- ✗
Containers provide hardware-level virtualization
Why it's wrong here
Containers share the host kernel and virtualise at the operating-system layer, so they deliver no hardware-level isolation; that is the hypervisor's role. The temptation is real: containers do package dependencies for portability across clouds, but the benefit stems from image immutability and namespace isolation, not hardware virtualisation.
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.