Implementing Containers for Application Isolation
Short answer
A The developer should implement a container to test the new application in an isolated environment that restricts access to the host OS.
Question
Key Takeaways
The question tests the difference between application-level isolation (containers) and full OS-level isolation (hypervisors), with the trap being the selection of heavier virtualization methods when lighter options suffice.
Learn why containers are the best choice for software developers needing to test applications in an environment that limits OS access compared to hypervisors or VDI.
Common mistake: Selecting Type 2 hypervisor (B) because it also provides isolation; however, hypervisors are overkill for simple application testing and lack the agility of containers.
Expert Analysis
The developer requires an environment that isolates the application from the underlying operating system while limiting direct OS access. This is a classic virtualization and cloud computing scenario focused on lightweight isolation.
Containers (A) are the correct solution. They package code and dependencies together, running in isolated user-space instances called containers. Crucially, containers share the host OS kernel but have restricted file-system and resource access. This provides the necessary security boundary without the heavy overhead of a full hypervisor, aligning perfectly with modern software development practices for testing.
Type 2 Hypervisors (B) run inside a host OS to create virtual machines. While they do isolate the OS, they require significant resources and time to boot. For testing a new application specifically, containers are the preferred industry standard due to their speed and efficiency.
VDI (C) involves remote desktop protocols to access a centralized desktop image. It is designed for end-user productivity, not application-level isolation for developers.
Quarantined PCs (D) refer to physical or logical network segmentation for malware containment. They are too coarse-grained for software testing.
Comments suggest A because containers provide "application isolation while sharing the host operating system's kernel." This confirms that the key distinction is the granular level of isolation: containers limit access at the process/application level, whereas hypervisors limit it at the hardware/VM level.
Exam Strategy
When a question mentions 'testing', 'development', or 'lightweight' environments, prioritize containers over hypervisors. Look for keywords like 'kernel sharing' or 'rapid deployment'. If the question explicitly asks for full OS isolation or hardware emulation, choose a hypervisor instead.
Frequently Asked Questions
What is the main difference between a container and a VM?
Why not use a Quarantined PC for app testing?
Community Votes
100% of anonymous learners picked answer A. 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 A"an environment that limits access to the OS" A container provides application isolation while sharing the host operating system's kernel. Applications run in their own containerized environment with restricted access to the host OS. 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 →