LPIC-3 Virtualization and Containerization study guide
LPIC-3 Virtualization and Containerization · Work through your exam, one topic at a time.
LPIC-3 Virtualization and Containerization is one of the four LPIC-3 specialty certifications offered by the Linux Professional Institute (LPI). LPI describes LPIC-3 as the culmination of its multi-level professional certification programme, aimed at enterprise-level Linux professionals; passing the exam for a specialty grants the LPIC-3 certification for that specialty. An active LPIC-2 certification is required to receive it. The specialty sits where two operational worlds meet: host-level virtualization - hypervisors, guest lifecycle, virtual networking and storage - and container platforms - image building, runtimes, registries, namespaces, cgroups and persistent data - plus the orchestration layer that schedules and keeps containerised workloads running across many nodes. Topics on this exam: Virtualization, Containerization, and Container Orchestration. The LPIC-3 Virtualization and Containerization study guide has 3 sections and about 1,341 words.
01Virtualization
Exam 306 separates virtualization from containerization because a hypervisor runs a full guest kernel on emulated or paravirtualized hardware, while containers share the host kernel. This domain tests how KVM, QEMU and libvirt divide the work, and how you define, boot, network and store virtual machines from the shell. KVM is the in-kernel hypervisor exposed as /dev/kvm: it virtualizes CPU and memory but emulates no devices. QEMU is the userspace device model (chipset, disk controllers, NICs).
450 words, about 2 min02Containerization
Containers are ordinary processes constrained by kernel features: namespaces for isolation, cgroups for accounting and limits. This domain tests the mechanics behind docker and podman - which namespace does what, how cgroup v2 limits are expressed, how images and layers are addressed, and where rootless operation changes behaviour. Namespaces: pid (own process tree), net (interfaces and routes), mnt (mount table), uts (hostname), ipc, user (UID mapping), cgroup and time. A container is a process with a set of these unshared.
454 words, about 2 min03Container Orchestration
Orchestration turns a pool of nodes into one scheduling surface. This domain tests Kubernetes primitives and the kubectl workflow: how control-plane components cooperate, how workloads are declared and rolled out, how Services find Pods, and how configuration and storage reach containers. kube-apiserver is the only component that talks to etcd; every other component watches the API. kube-scheduler binds unscheduled Pods to nodes based on requests and constraints.
437 words, about 2 min