| 🏠 Back to Exam Syllabus | 📺 RooCloud on YouTube | 🎯 Free CISSP Practice Test |
CISSP 9.17 - Containerization
This episode of the ISC2 Certified Information Systems Security Professional (CISSP) exam prep series unpacks containerization within Domain 3. It explains how containers differ from traditional virtual machines, what a container shares versus isolates, and why this model underpins how modern software actually ships from a developer’s laptop to the production cloud.
What this episode covers
- Containers vs virtual machines — each app carries only what it needs instead of duplicating a full guest operating system.
- Operating-system virtualization — shared operating-system parts live once in a common container engine.
- Dropping the hypervisor — some setups let containers call on a shared set of binaries and libraries.
- Application density — sharing components lets a server host ten to a hundred times more apps than hypervisor virtualization.
- Application cells — apps wrapped so the same package runs on almost any operating system, built once and run anywhere.
- Configurability — some solutions allow several apps per container, and many let you tune how much containers interact.
Watch the full episode above for the worked examples and detailed explanations of each concept.
Frequently Asked Questions
What is containerization, and how does it differ from virtual machines?
A traditional virtual machine runs a full guest operating system on top of a hypervisor and usually carries just one main application, so the same operating system gets duplicated over and over, which wastes resources. Containerization, sometimes called operating-system virtualization, strips out that duplication. Each application goes into a container holding only what that specific app needs, while the shared operating-system parts live once in a common container engine, like apartments in one building sharing the plumbing and foundation.
Why does containerization pack so much more onto a single server?
Because you are no longer paying the overhead of a full operating system for every workload. By sharing common components instead of copying them, a single physical server can host far more applications than classic hypervisor virtualization allows, on the order of ten to a hundred times the density. Picture a parking garage: give every car its own private lot and you fit a handful, but stack them efficiently in shared levels and you fit hundreds in the same footprint.
What makes containers so portable and flexible?
Applications get wrapped in application cells, also called application containers, so the same packaged software can run on almost any operating system, and a container built once behaves the same wherever it lands. The technologies grouped under containerization vary in the details. Some allow several applications to share one container while others keep it to one app each, and many let you tune exactly how much containers are allowed to interact with one another.
Do containers still use a hypervisor?
Not always. Some container setups drop the hypervisor entirely and let containers call on a shared set of binaries and libraries instead of each running a full guest operating system. The shared operating-system parts live once in a common container engine, which is what removes the wasteful duplication and delivers the dramatically higher application density that containerization is known for compared with classic virtual machines.
📚 Master the ISC2 CISSP Exam!
Reinforce this lesson with real practice. The RooCloud CISSP Practice Pack gives you 6,000+ exam-style questions, 366 section-wise practice tests and 40 full-length adaptive (CAT) tests across all 8 CISSP domains, with full explanations. Start with a FREE full-length adaptive CISSP test →
Reference: This article is based on concepts discussed in CISSP 9.17 - Containerization.