48 real Containers vs VMs questions from the Virtualization bank, as asked in Indian campus drives and tech interviews. Every question has a verified answer and an AI-tutor explanation on placd — free to start.
1. What is container vs VM?
Junior
A.A Windows container mode that runs each container inside a lightweight utility VM for kernel isolation, versus process-isolation sharing the host kernel
B.Linux control groups that limit and account for a container's CPU, memory, I/O and other resource usage
C.a container shares the host kernel (lightweight); a VM virtualizes hardware (strong isolation)
D.Stacked read-only filesystem layers that compose a container image, with a thin writable layer added at runtime via a union filesystem
A.container vs VM — A container runtime conforming to the Open Container Initiative spec (runc, crun, kata-runtime) that creates and runs containers from a bundle
B.container vs VM — VMs virtualize hardware with a full guest OS; containers share the host kernel and isolate via namespaces and cgroups.
C.container vs VM — a container shares the host kernel (lightweight); a VM virtualizes hardware (strong isolation)
D.container vs VM — A runtime that wraps each container or pod in a lightweight VM, combining container workflow with hypervisor-grade isolation
5. Which term means: "Kernel isolation primitives (pid, net, mnt, uts, ipc, user) that give a container its own view of process, network and filesystem resources"?
A.Linux namespaces — Stacked read-only filesystem layers that compose a container image, with a thin writable layer added at runtime via a union filesystem
B.Linux namespaces — Kernel isolation primitives (pid, net, mnt, uts, ipc, user) that give a container its own view of process, network and filesystem resources
C.Linux namespaces — a container shares the host kernel (lightweight); a VM virtualizes hardware (strong isolation)
D.Linux namespaces — Linux kernel feature limiting and accounting CPU, memory, and I/O for container processes.
A.cgroups — Lightweight VMs presenting an OCI container interface, adding hardware isolation to untrusted workloads.
B.cgroups — A minimal virtual machine with a stripped device model and fast boot (Firecracker, Cloud Hypervisor) used to isolate serverless and container workloads
C.cgroups — Linux control groups that limit and account for a container's CPU, memory, I/O and other resource usage
D.cgroups — A Windows container mode that runs each container inside a lightweight utility VM for kernel isolation, versus process-isolation sharing the host kernel
A.a container shares the host kernel (lightweight); a VM virtualizes hardware (strong isolation)
B.Kernel isolation primitives (pid, net, mnt, uts, ipc, user) that give a container its own view of process, network and filesystem resources
C.Running pods inside microVMs (Kata) or user-space kernels (gVisor) to give container orchestration the security boundary of a hypervisor
D.A minimal virtual machine with a stripped device model and fast boot (Firecracker, Cloud Hypervisor) used to isolate serverless and container workloads
14. Which term means: "A minimal virtual machine with a stripped device model and fast boot (Firecracker, Cloud Hypervisor) used to isolate serverless and container workloads"?
A.microVM — A user-space application kernel that intercepts syscalls to sandbox containers without a full VM.
B.microVM — A minimal virtual machine with a stripped device model and fast boot (Firecracker, Cloud Hypervisor) used to isolate serverless and container workloads
C.microVM — a container shares the host kernel (lightweight); a VM virtualizes hardware (strong isolation)
D.microVM — Kernel isolation primitives (pid, net, mnt, uts, ipc, user) that give a container its own view of process, network and filesystem resources
A.A minimal virtual machine with a stripped device model and fast boot (Firecracker, Cloud Hypervisor) used to isolate serverless and container workloads
B.A Windows container mode that runs each container inside a lightweight utility VM for kernel isolation, versus process-isolation sharing the host kernel
C.Lightweight VMs presenting an OCI container interface, adding hardware isolation to untrusted workloads.
D.Minimal KVM-based VMs booting in milliseconds, used by serverless platforms for strong isolation at scale.
17. Which term means: "A Windows container mode that runs each container inside a lightweight utility VM for kernel isolation, versus process-isolation sharing the host kernel"?
A.Windows Hyper-V isolation mode — Kernel isolation primitives (pid, net, mnt, uts, ipc, user) that give a container its own view of process, network and filesystem resources
B.Windows Hyper-V isolation mode — A Windows container mode that runs each container inside a lightweight utility VM for kernel isolation, versus process-isolation sharing the host kernel
C.Windows Hyper-V isolation mode — Linux kernel feature limiting and accounting CPU, memory, and I/O for container processes.
D.Windows Hyper-V isolation mode — A user-space application kernel that intercepts syscalls to sandbox containers without a full VM.
20. Which term means: "Stacked read-only filesystem layers that compose a container image, with a thin writable layer added at runtime via a union filesystem"?
A.Container image layers — Containers run inside confidential VMs (SEV-SNP/TDX) so workload memory is shielded from the host and platform operator
B.Container image layers — A Windows container mode that runs each container inside a lightweight utility VM for kernel isolation, versus process-isolation sharing the host kernel
C.Container image layers — Stacked read-only filesystem layers that compose a container image, with a thin writable layer added at runtime via a union filesystem
D.Container image layers — Lightweight VMs presenting an OCI container interface, adding hardware isolation to untrusted workloads.
A.A Windows container mode that runs each container inside a lightweight utility VM for kernel isolation, versus process-isolation sharing the host kernel
B.Linux kernel feature limiting and accounting CPU, memory, and I/O for container processes.
C.Containers run inside confidential VMs (SEV-SNP/TDX) so workload memory is shielded from the host and platform operator
D.Running pods inside microVMs (Kata) or user-space kernels (gVisor) to give container orchestration the security boundary of a hypervisor
A.Confidential containers — Containers run inside confidential VMs (SEV-SNP/TDX) so workload memory is shielded from the host and platform operator
B.Confidential containers — Lightweight VMs presenting an OCI container interface, adding hardware isolation to untrusted workloads.
C.Confidential containers — Stacked read-only filesystem layers that compose a container image, with a thin writable layer added at runtime via a union filesystem
D.Confidential containers — Running pods inside microVMs (Kata) or user-space kernels (gVisor) to give container orchestration the security boundary of a hypervisor
26. Which term means: "A container runtime conforming to the Open Container Initiative spec (runc, crun, kata-runtime) that creates and runs containers from a bundle"?
A.OCI runtime — Kernel isolation of PID, network, mount, UTS, IPC, and user views giving each container its own world.
B.OCI runtime — Stacked read-only filesystem layers that compose a container image, with a thin writable layer added at runtime via a union filesystem
C.OCI runtime — A container runtime conforming to the Open Container Initiative spec (runc, crun, kata-runtime) that creates and runs containers from a bundle
D.OCI runtime — a container shares the host kernel (lightweight); a VM virtualizes hardware (strong isolation)
29. Which term means: "Running pods inside microVMs (Kata) or user-space kernels (gVisor) to give container orchestration the security boundary of a hypervisor"?
A.Pod sandbox isolation — Lightweight VMs presenting an OCI container interface, adding hardware isolation to untrusted workloads.
B.Pod sandbox isolation — Stacked read-only filesystem layers that compose a container image, with a thin writable layer added at runtime via a union filesystem
C.Pod sandbox isolation — a container shares the host kernel (lightweight); a VM virtualizes hardware (strong isolation)
D.Pod sandbox isolation — Running pods inside microVMs (Kata) or user-space kernels (gVisor) to give container orchestration the security boundary of a hypervisor
Showing 30 of 48 Containers vs VMs questions — the full set, with answers, explanations and an AI tutor on every question, is inside.
Free to start
Answers, AI explanations, and a scored voice mock interview
Sign up free to check your answers with explanations, ask the AI tutor anything on any question, and take one full AI mock interview — scored like a real panel.