305-300
LPIC-3: Virtualization and Containerization
305-300 Exam Guide: LPIC-3 Virtualization and Containerization
Exam 305-300 validates enterprise-level Linux administration focused on full virtualization, container virtualization, and repeatable virtual-machine deployment. It is intended for Linux professionals who already hold an active LPIC-2 certification and need to demonstrate practical knowledge across Xen, QEMU, libvirt, LXC, Docker, orchestration concepts, cloud tools, Packer, cloud-init, and Vagrant. This guide helps you decide whether your background is ready, which objectives deserve the most study time, how to build useful practice work, and when to schedule the exam.
What does 305-300 certify?
305-300 is the LPIC-3 Virtualization and Containerization exam, version 3.0. It tests the administration of Linux systems across an enterprise environment, with particular emphasis on virtualization and containerization rather than general Linux administration alone.
LPI describes LPIC-3 as an enterprise-level, distribution-neutral extension of the LPIC program. The expected professional should be able to understand, plan roll-outs, install, configure, maintain, and troubleshoot the technologies covered by the relevant exam. For 305-300, that means connecting architecture and terminology with operational decisions.
The exam resulted from the split of version 2.0 of exam 304. Do not use older exam 304 material as your primary study plan without checking it against the version 3.0 objectives. The current official objective page identifies the code as 305-300 and separates the content into Full Virtualization, Container Virtualization, and VM Deployment and Provisioning.
Who should consider this exam?
The strongest candidate is an experienced Linux administrator, virtualization engineer, platform engineer, or systems professional who can investigate a host, guest, container, network, or storage problem rather than merely recognize product names. Familiarity with Linux administration is necessary because the exam assumes that virtualization and container tasks are performed on Linux systems.
LPI’s minimally qualified candidate description refers to experience installing and maintaining Linux on multiple computers, integrating diverse technologies and operating systems, and handling advanced administration, troubleshooting, security, and maintenance. Those are useful readiness indicators, although practical experience does not replace a review of every listed objective.
This is a poor first Linux certification target if you have only used virtual machines as an end user. Build a foundation first if terms such as hypervisor, virtual machine monitor, guest agent, container image, bridge, snapshot, or resource limit are still unfamiliar.
What must be true before you register?
To receive the LPIC-3 Virtualization and Containerization certification, you must have an active LPIC-2 certification and pass exam 305. Passing the exam alone does not satisfy the certification prerequisite if LPIC-2 is not active.
Treat the LPIC-2 requirement as a scheduling checkpoint, not an administrative detail. Verify your certification status before purchasing a voucher or selecting an exam appointment. If your LPIC-2 status needs attention, resolve that issue first so that passing 305 can be applied to the intended LPIC-3 certification.
The 305-300 exam and certification have a stated validity period of 5 years, and LPI provides options for extending active status beyond that period. Check the official certification page for the current extension process rather than relying on an older renewal explanation.
Which delivery and language details are published?
LPI lists English and Japanese as available languages at VUE test centers and through OnVUE online delivery. Confirm the current options and appointment conditions on LPI’s certification page before scheduling, because delivery availability can depend on the selected channel and location.
The published exam format is 60 multiple-choice and fill-in-the-blank questions in a 90-minute exam. This makes precise terminology and efficient reading important: you need to identify the requested concept, command, configuration element, or operational result without spending excessive time on one uncertain item.
LPI’s page directs candidates to country-specific pricing rather than stating one universal price. Use the official page for the price in your country and for the current voucher and scheduling links.
How is the blueprint organized?
Study the four objective groups in the order that matches your weaknesses, but use the official weights to decide where a gap is expensive. The weights indicate relative importance and higher-weight objectives are expected to receive more questions; they are not a published pass-score formula.
Topic 351, Full Virtualization, contains virtualization concepts and theory, Xen, QEMU, libvirt virtual machine management, and virtual machine disk image management. Its listed objective weights are 6 for Virtualization Concepts and Theory, 3 for Xen, 4 for QEMU, 9 for Libvirt Virtual Machine Management, and 3 for Virtual Machine Disk Image Management.
Topic 352, Container Virtualization, contains container concepts, LXC, Docker, and container orchestration platforms. Its listed objective weights are 7 for Container Virtualization Concepts, 6 for LXC, 9 for Docker, and 3 for Container Orchestration Platforms.
Topic 353, VM Deployment and Provisioning, covers cloud management tools, Packer, cloud-init, and Vagrant. Its listed objective weights are 2 for Cloud Management Tools, 2 for Packer, 3 for cloud-init, and 3 for Vagrant.
A useful first allocation is to give the largest practical blocks to Libvirt Virtual Machine Management and Docker, then cover virtualization and container concepts, LXC, QEMU, and the deployment tools. That is a preparation recommendation based on the official weights, not a prediction of the exact question mix.
What does the weight tell you?
A high weight should change your revision behavior. For Libvirt, you should be able to perform and explain management tasks, inspect domains and connections, reason about virtual networks and storage, and troubleshoot common configuration failures. For Docker, you should understand node and container management, images, networking, storage, and the surrounding lifecycle concepts identified in the objectives.
A low weight is not permission to skip a topic. Cloud management tools, Packer, cloud-init, and Vagrant still appear in the blueprint, and a narrow study plan can leave avoidable gaps. Cover every objective once, then spend additional lab and review time where the weight and your diagnostic results intersect.
What should you learn about full virtualization?
Full virtualization preparation should move from architecture to administration. Learn how hypervisors, virtual machine monitors, hardware support, emulation, paravirtualization, guest drivers, networking, storage, migration, snapshots, cloning, pausing, and resource limits relate to one another before memorizing individual commands.
The objectives include Xen, QEMU, and libvirt terminology, the advantages and disadvantages of virtualization, hypervisor variations, physical-to-virtual migration, virtual-machine migration between hosts, and the implications of adjusting resources. You should be able to explain why a design choice affects performance, portability, availability, or operational complexity.
Do not treat Xen and QEMU as interchangeable labels. The objective list expects separate understanding of Xen architecture and management, QEMU architecture and operation, and libvirt as a management layer for virtual machines and hosts. Create a comparison sheet that records each component’s role, configuration location, management tools, networking model, storage model, and troubleshooting evidence.
The Xen objective focuses on version 4.x. Review Dom0 and DomU, PV-DomU and HVM-DomU, node and domain management, networking and storage, configuration through relevant Xen files, and the listed utilities such as xl and xentop. Include basic troubleshooting rather than limiting study to installation.
For QEMU, practise starting instances from the command line, understanding KVM and the relevant kernel modules, using the QEMU monitor for snapshots, installing the QEMU Guest Agent and VirtIO device drivers, and investigating networking and storage problems. Know the purpose of /dev/kvm and the listed networking utilities.
Libvirt is the largest single Full Virtualization objective by weight. Study its architecture and related tools, domain lifecycle operations, host and guest configuration, virtual networks, storage pools and volumes, connection choices, and troubleshooting workflow. Your notes should map a symptom to the layer you would inspect rather than presenting an unconnected command list.
Virtual machine disk image management deserves its own lab. Practise identifying image formats and backing relationships, handling snapshots and conversion concerns, and distinguishing guest filesystem capacity from virtual disk capacity. The objective material also emphasizes adjusting virtual machines to match available hardware resources, including disk space and volumes.
A practical full-virtualization lab
Use a disposable Linux host or nested lab only when your environment supports it safely. Create one or more guests, connect them to a controlled virtual network, attach storage, change a resource allocation, and record what changed in the host and guest. Then deliberately introduce a networking or storage mistake and document the evidence that isolates the fault.
The goal is not to reproduce a proprietary production environment. It is to make the relationships visible: host capability affects guest configuration; a guest driver affects device behavior; a virtual network affects reachability; and an image or volume operation affects storage availability. Keep a lab journal with the command, expected result, observed result, and explanation.
How should you prepare for container virtualization?
Start container study with the boundary between a container and a fully virtualized guest. Containers share a host kernel and isolate processes and resources, while a virtual machine presents a guest operating system environment through virtualization. The exam expects terminology, architecture, management, networking, storage, resource limits, and orchestration awareness—not just the ability to launch a sample container.
The Container Virtualization Concepts objective has a listed weight of 7. Learn namespaces, control groups, images, layers, registries, isolation, persistence, networking, and security implications well enough to compare a design and identify its operational trade-offs. Pay attention to what belongs to the host, what belongs to the image, and what is created at runtime.
The LXC objective has a listed weight of 6 and includes LXC and LXD architecture, managing containers from existing images, networking and storage, container properties, resource limits, profiles, images, and awareness of traditional LXC tools. Practise the LXD workflow as a sequence: obtain or inspect an image, launch a container, configure resources and networking, apply a profile, inspect state, and remove or preserve data intentionally.
Docker has a listed weight of 9 and should receive serious hands-on time. Learn how Docker nodes and containers are managed, how images and containers differ, how commands affect lifecycle state, and how networking, storage, logging, and resource settings affect an operational deployment. The objective list also requires understanding container orchestration relevance, Docker Compose, Docker Swarm, Kubernetes, and Helm, with awareness of OpenShift, Rancher, and Mesosphere DC/OS.
Do not study orchestration as a collection of brand names. Build a comparison table: what is being orchestrated, how desired state is represented, how services are exposed, how configuration and secrets are handled, and how scaling or scheduling is approached. The objectives distinguish key concepts from awareness, so reserve deep implementation practice for the areas explicitly described as management or key knowledge.
Container exercises that expose weak understanding
Build a small service image, run it with a deliberate port mapping, attach persistent storage, inspect its logs, stop and restart it, and verify what persists. Then create a network or permission error and trace it from the host to the container. Repeat the same reasoning with LXC so that you can distinguish tool-specific syntax from general container behavior.
When reviewing an answer, ask what state is durable and where it lives. A container’s writable layer, an image, a named volume, a bind mount, and a host filesystem are not interchangeable. Confusing them is a common preparation mistake because a command may appear to work while losing data when the container is recreated.
What belongs in VM deployment and provisioning?
Topic 353 tests how standardized virtual machines are described, built, initialized, and managed. Study it as a pipeline rather than four isolated products: a cloud or infrastructure platform provides resources, Packer creates an image, cloud-init configures a new instance, and Vagrant can define and control a repeatable development environment.
Cloud management tools have a listed weight of 2. The objectives require understanding common public-cloud offerings, basic feature knowledge of OpenStack and Terraform, and awareness of CloudStack, Eucalyptus, and OpenNebula. Learn the service categories and the role of infrastructure-as-code and cloud management, but do not spend most of your time memorizing provider-specific screens.
Packer has a listed weight of 2 and focuses on creating system images. Review its functionality, template files, builders, and the process of building images from templates. A useful exercise is to annotate a template by identifying variables, source or builder settings, provisioners, output artifacts, and the point at which a reusable image is produced.
cloud-init has a listed weight of 3 and concerns configuring virtual machines created from standardized images. Practise separating image customization from first-boot initialization. Review common configuration structure, user creation, packages, files, commands, networking assumptions, and how you would determine whether initialization completed or failed.
Vagrant has a listed weight of 3. Learn how it defines and controls virtual machine environments, how a configuration selects a provider and base image, and how networking, synced folders, provisioning, and lifecycle commands fit together. The important preparation decision is to understand what Vagrant manages and what the underlying provider still controls.
The deployment objectives are especially useful for candidates who know one tool deeply but have not connected image creation, instance initialization, and environment management. Draw the lifecycle on paper and label the hand-off between each stage. Then explain what could go wrong if an image contains environment-specific settings that should have been supplied at initialization time.
A repeatable provisioning exercise
Create a small disposable workflow in which an image is built from a template, a new machine receives first-boot configuration, and a declarative environment tool starts or manages that machine. Record which settings belong in the image and which belong in initialization. If you cannot run every tool locally, use the official objectives to build a conceptual runbook and verify each term with authoritative documentation.
Do not turn this exercise into a production deployment. Its purpose is to test sequencing, configuration ownership, and troubleshooting. A failed build, missing initialization log, or incorrect provider setting should lead you to inspect the relevant stage rather than randomly changing commands.
How should you sequence your study time?
Use a diagnostic-first plan: read the objectives, rate every subobjective, perform a small lab or explanation task, and then revisit only the weak areas. A staged plan prevents the common error of spending all preparation time on Docker because it is familiar while neglecting libvirt, Xen, QEMU, or provisioning tools.
Begin with the official 305-300 objectives and make a checklist for all thirteen objectives across Topics 351, 352, and 353. For each item, record four things: terms you can define, tasks you can perform, failures you can diagnose, and commands or configuration artifacts you can recognize. Mark a topic incomplete if you can only recite vocabulary.
Next, establish the architecture. Compare a hypervisor-based virtual machine with LXC and Docker containers. Map host, guest, container, image, volume, virtual network, bridge, registry, management layer, and initialization service. This prevents later confusion when several products use similar words for different layers.
Then work through the high-value administration areas. Spend a substantial block on libvirt and Docker, followed by virtualization concepts, container concepts, LXC, QEMU, and the remaining objectives. The exact schedule should reflect your baseline: an administrator who manages KVM daily may need more Xen and LXC work, while a container specialist may need a deeper full-virtualization block.
After the first pass, use scenario drills rather than passive rereading. Examples include a guest that cannot reach the network, a container that loses data after recreation, an image that boots with the wrong initialization state, or a host whose available resources do not match the guest configuration. For each scenario, state the layer, evidence, likely cause, and corrective action.
Finish with a compact review of terms, files, utilities, lifecycle states, and configuration relationships. Avoid learning new material at the last moment. Use the final study period to close checklist gaps and practise choosing the most direct answer to a precisely worded question.
A four-stage roadmap
Stage one is scope and baseline. Read every objective, mark confidence, and verify that your LPIC-2 certification is active. Do not schedule yet if you cannot identify a realistic lab or study source for several major areas.
Stage two is construction. Build or use a safe lab, starting with virtualization concepts and a simple guest, then adding libvirt, QEMU or Xen concepts, container workflows, and provisioning tools. Keep notes organized by objective number so that a review session can target one gap.
Stage three is diagnosis. Break working configurations on purpose, inspect logs and state, and explain why the fix works. Mix topics so that you practise selecting the right technology or layer instead of recognizing an isolated command from a familiar chapter.
Stage four is readiness and scheduling. Revisit every objective, test recall without notes, confirm the published delivery and language option you need, and check current scheduling information on LPI’s page. Schedule when your preparation evidence shows consistent coverage, not merely when you finish a video or book.
Which mistakes waste preparation time?
The most damaging mistake is treating the exam as a product-name quiz. The objectives describe installation, configuration, maintenance, migration, management, and troubleshooting. Learn what each tool does, how it interacts with adjacent layers, and what evidence confirms a successful operation.
Another mistake is using the wrong blueprint. Version 3.0 is exam code 305-300, while the preceding version is identified as exam 304-200. Older material may explain useful foundations, but it can omit or misrepresent the current split between virtualization, containers, and VM deployment. Always reconcile notes with the current objective page.
Do not equate a high-weight topic with a guaranteed question count or a passing threshold. LPI publishes relative objective weights, not a promise that every candidate will see a fixed number of questions from each item or that a particular total guarantees success.
Do not skip low-weight objectives. Cloud management tools and Packer may appear less prominent than libvirt or Docker, but the blueprint includes them. A short, accurate review is better than leaving an entire objective unstudied.
Avoid memorizing commands without understanding scope and side effects. A command that manages a host, a domain, an image, a container, a volume, or a network can produce very different consequences. Write the object and expected state beside each command in your notes.
Finally, do not rely on exam dumps, leaked questions, or memorization claims. They do not establish competence, may be inaccurate or unauthorized, and leave you unprepared for a question framed around a different symptom or configuration. Use the objectives and legitimate technical documentation to build transferable understanding.
How can you tell whether a topic is ready?
For each objective, use a three-part test. First, define the important terms without copying a sentence. Second, complete a representative task or walk through it accurately from a clean starting point. Third, diagnose a plausible failure and identify the evidence you would inspect. If one part fails, keep that objective in the active study queue.
A strong final review also checks distinctions: image versus container, guest versus host, snapshot versus backup, virtualization management versus provisioning, and orchestration awareness versus platform administration. These distinctions are more useful than a long unstructured list of commands.
What should you do in the final week?
Use the final week to consolidate, not to expand endlessly. Re-read the objective wording, revisit the highest-weight gaps, run short scenario drills, and confirm your appointment, language, delivery channel, and identification requirements from the current official source. Keep your notes concise enough to review without creating a second textbook.
A practical final checklist is: confirm active LPIC-2 status; verify that your study checklist covers Topics 351, 352, and 353; review libvirt and Docker administration; refresh Xen, QEMU, LXC, and orchestration distinctions; review Packer, cloud-init, Vagrant, and cloud management concepts; and practise answering both recognition and fill-in-the-blank prompts precisely.
During the exam, read the requested object and outcome before choosing an answer. Eliminate options that belong to another layer or lifecycle stage. For a fill-in-the-blank item, use the terminology expected by the objective and avoid adding unnecessary text. If an item consumes too much time, record your best answer, move forward, and return if the exam interface permits.
Do not schedule solely because a preparation provider says you are ready. Schedule after your own evidence shows that you can explain and troubleshoot the objectives, and after the official LPI page confirms the current administrative details relevant to you.
Your next actions
Open the official 305-300 objectives and create a thirteen-item checklist. Mark each item as definition-ready, task-ready, and troubleshooting-ready. Then verify your LPIC-2 status and choose a safe practice environment.
Give your first focused lab block to the weakest major area, not the tool you already use every day. After that block, update the checklist with specific gaps, such as virtual networking, image management, container persistence, orchestration roles, or cloud-init sequencing.
When every objective has evidence behind it, review the official certification page for delivery, language, validity, voucher, and scheduling information. Use that page—not an undated third-party summary—as the final authority for registration decisions.
Official sources to keep open
Use LPI’s certification overview for the prerequisite, format, validity, language, delivery, pricing direction, and official scheduling links. Use the exam objectives page and its LPI Wiki counterpart for the version 3.0 scope, weights, key knowledge areas, and listed tools. The LPI program page provides context for the enterprise-level minimally qualified candidate.
The LPI articles on Full Virtualization and VM Deployment and Provisioning can supplement the objective checklist with introductory learning discussions. They should support—not replace—the current objectives, which remain the clearest source for deciding whether a topic is covered.
Conclusion
305-300 is best approached as an enterprise administration exam, not as a memorization exercise for virtualization and container commands. Confirm the LPIC-2 prerequisite, use the version 3.0 objectives as your checklist, prioritize libvirt and Docker while covering every domain, and build troubleshooting practice around hosts, guests, containers, images, networks, storage, and provisioning stages. Schedule only after your own lab work and objective-by-objective review show that you can explain both the technology and the operational decision behind it.