Containerization vs Virtualization for Resource Efficiency
Short answer
C The technician should suggest using containerization because it shares the host OS kernel and libraries, minimizing resource usage compared to full virtualization options like VDI or Type 2 hypervisors.
Question
Key Takeaways
The trap lies in confusing lightweight application-level isolation (containers) with heavy OS-level isolation (hypervisors); the key differentiator is sharing the host kernel and libraries rather than booting separate guest OSes.
This question addresses virtualization concepts by comparing containerization against full virtualization methods like VDI and Type 2 hypervisors. The correct approach for running multiple app instances with minimal resources is containerization.
Common mistake: Choosing B (Type 2 Hypervisor) is common because users associate virtualization with running multiple environments, but they overlook that hypervisors require a full guest OS per instance, leading to high resource consumption that contradicts the 'fewest resources' constraint.
Expert Analysis
The scenario requires running multiple application instances with minimal resource overhead on a host that already possesses the necessary libraries. This specific constraint—sharing existing libraries and avoiding full OS duplication—is the defining characteristic of containerization. Unlike virtual machines, containers share the host kernel and do not require a guest operating system for each instance.
Option A (VDI) and Option B (Type 2 Hypervisor) involve full virtualization. Both approaches require provisioning separate guest operating systems for each instance, which consumes significant CPU, RAM, and storage resources, violating the "fewest resources possible" requirement. Option D (Virtual Switch) is a networking component and does not address application isolation or resource efficiency.
As noted in community comments, containerization allows instances to share the host's OS kernel and available libraries. This results in significantly lower overhead compared to hypervisors, enabling higher density of application instances on the same hardware. Therefore, C is the only solution that meets the efficiency criteria.
Official Reference
https://docs.docker.com/get-started/overview/
This link opens the official vendor documentation in a new tab.
Exam Strategy
When troubleshooting or configuring systems, always evaluate the 'overhead cost' of your solution. If the prompt emphasizes 'lightweight', 'fast startup', or 'sharing libraries', think Containers. If it emphasizes 'complete isolation', 'different OSs', or 'security boundaries', think Hypervisors/VMs.
Frequently Asked Questions
Why is a Type 2 hypervisor not the best choice?
What is the main advantage of containerization over VDI?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
Afie 👍 1 Answered CThe question states: The developer needs to run multiple instances of an application. Use the fewest resources possible. The machine already has the necessary libraries available. Containerization is the best choice because containers: ✅ Share the host operating system kernel. ✅ Require much less CPU, RAM, and storage than virtual machines. ✅ Start quickly. ✅ Allow many application instances to run on the same host efficiently. Examples: Docker Podman Kubernetes containers
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All 220-1201 Questions
Access 105 questions with complete answers and detailed explanations.
View Full 220-1201 Practice Test →