Which statement correctly distinguishes a container from a full virtual machine on Linux?
LPIC-1 Exam 101-500, objective 102. Linux installation and package management medium
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Not correct A container requires hardware virtualization support in the CPU, while a virtual machine does not
Wrong, and backwards. Containers need no CPU virtualization extensions at all, whereas full virtualization with KVM depends on Intel VT-x or AMD-V.
Not correct A container boots its own kernel, while a virtual machine shares the host's kernel
Wrong — this reverses the two. Sharing the host kernel is precisely what makes containers lightweight and fast to start.
Not correct A container can only run one process, while a virtual machine can run many
Wrong. A container commonly runs one main process by convention, but nothing prevents it from running several; that is a packaging practice, not a technical boundary.
Correct A container shares the host's running kernel, while a virtual machine boots its own kernel on virtualized hardware
Correct. Containers are isolated process groups on the host kernel, using kernel features such as namespaces and cgroups; a VM is presented with virtual hardware and runs a full operating system including its own kernel.
Why
The distinction is where the kernel boundary sits. A virtual machine is given emulated or paravirtualized hardware by a hypervisor and boots its own kernel, so it can run a different operating system than the host. A container is host processes isolated by kernel namespaces and limited by cgroups, so it must run on the host's kernel — which is why Linux containers on macOS or Windows are actually running inside a hidden Linux VM. Paravirtualized guests sit between the extremes: still their own kernel, but using virtio drivers that know they are virtualized rather than emulated hardware.
Where this comes from
- Cited
- LPI exam objective 102.6
- What it says
- Understand the general concept of virtual machines and containers.
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 102 and space the ones you get wrong.
More questions on this objective
- A mail server keeps filling its root filesystem because spooled mail and logs grow without bound, and when the disk fills the whole system becomes unusable. Which single change to the disk layout most directly contains that failure? machine-checked
- In LVM terminology, which object is created directly on a partition or whole disk so that its storage can be added to a pool? machine-checked
- You are laying out storage for a general-purpose Linux server. Which TWO of the following are genuine reasons to use LVM for the data filesystems rather than plain partitions? machine-checked
- Which file is the configuration file that GRUB 2 generates, and which administrators are told not to edit by hand on a typical Linux distribution? machine-checked
- You replaced the boot disk in a BIOS/MBR system and need to write the GRUB 2 boot loader into the master boot record of /dev/sda, installing the required GRUB modules under /boot. Which command does that? machine-checked
- On a GRUB 2 system whose configuration file is /boot/grub/grub.cfg, type the grub-mkconfig command — including the option and its argument — that regenerates that file. machine-checked