Containerization vs Virtualization for OS Reduction
A company is decommissioning its physical servers and replacing them with an architecture that will reduce the number of individual operating systems. Which of the following strategies should the company use to achieve this security requirement?
Community Votes
64% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests your ability to distinguish between hardware-level isolation (virtualization) and OS-level isolation (containerization) when the specific goal is minimizing the count of individual operating systems.
This question tests the distinction between containerization and virtualization, specifically how each technology impacts the number of operating systems required to host applications. The page establishes that containerization is the correct strategy because it allows multiple applications to run on a single shared host OS kernel.
Most learners choose Virtualization (C) because they associate server consolidation with VMs; however, virtualization still requires a distinct guest OS for every virtual machine, failing to reduce the total number of OS instances as effectively as containers.
Community Discussion (17 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Containerization (B) is the correct answer because it utilizes OS-level virtualization where multiple isolated user-space instances (containers) run on a single host operating system kernel. By sharing the underlying OS, you drastically reduce the number of individual operating systems compared to running separate physical servers or even separate virtual machines. This aligns perfectly with the requirement to "reduce the number of individual operating systems" while maintaining application isolation.Why the Other Options Are Wrong
Virtualization (C) creates hypervisors that allow multiple virtual machines to run on one physical server, but each VM must have its own full guest operating system installed. Therefore, if you replace 5 physical servers with 5 VMs, you still have 5 operating systems. Microservices (A) is an architectural style, not an infrastructure deployment technology, so it doesn't inherently reduce OS counts. Infrastructure as Code (D) is a management practice for provisioning resources, not a runtime environment technology that affects OS overhead.Community Comment Notes
Many users correctly identified B by focusing on the phrase "reduce the number of individual operating systems." As one commenter noted, "Containerization allows fewer Operating Systems," highlighting the key differentiator from virtualization. Another user explained that while virtualization consolidates hardware, it still requires multiple OS instances (one per VM), whereas containerization shares the host OS kernel. Some learners initially chose C, confusing server consolidation with OS reduction, but the consensus clarified that containers are lighter because they don't need a separate guest OS.Exam Strategy
Always read the specific constraint in the question stem carefully. If the goal is reducing physical hardware, think Virtualization. If the goal is reducing Operating System instances or overhead, think Containerization. These two concepts are often paired in SY0-701 questions to test precise terminology.
Frequently Asked Questions
Why isn't Virtualization the answer if it also reduces physical servers?
Virtualization reduces physical servers but still requires a full guest OS for each VM. Containerization shares the host OS, resulting in fewer total OS instances.
Does Microservices architecture reduce the number of OSs?
No. Microservices is a design pattern. You can deploy microservices using containers or VMs. It doesn't inherently dictate the OS footprint.
Related Analysis
Practice All SY0-701 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SY0-701 Practice Test →