LPIC-2 Exam 201-400 Study Guide: Verify the Version Before You Schedule
The label 201-400 refers to an older LPIC-2 exam version, while LPI’s current overview identifies LPIC-2 version 4.5 with exam code 201-450. LPIC-2 validates advanced Linux administration across capacity planning, kernels, startup, storage, networking, maintenance, and related services. It serves administrators who already hold LPIC-1 and need to manage small to medium-sized mixed networks. This guide helps you decide whether your voucher or study material matches 201-400, whether you should prepare for 201-450 instead, and how to sequence practical study without relying on memorized question collections.
Is 201-400 the current LPIC-2 exam?
Do not schedule from the 201-400 label until you confirm the exam code and objective version with LPI or the delivery provider. LPI’s current LPIC-2 overview lists version 4.5 and exam codes 201-450 and 202-450, while the objectives page identifies version 4.5. The official material therefore supports treating 201-400 as an older or catalogue label rather than assuming it is the current selectable exam.
The distinction matters because the version-4.5 update changed the technology coverage. The update increased coverage of systemd and added or expanded IPv6, TLS, SSSD, DKMS, Btrfs, UEFI, NVMe, xz, iotop, htop, ss, iptraf, and Sieve filters. A preparation product labelled 201-400 may omit subjects that appear in the current 201-450 objectives.
Before buying a voucher or setting a date, check three items: the exact code shown in the scheduling system, the objective version attached to that code, and the language and delivery channel available to you. If those details do not align, use the current LPI objectives page as the controlling study document and ask LPI or the exam provider to resolve the discrepancy.
Who should take exam 201?
Exam 201 is intended for an experienced Linux administrator moving beyond routine command-line maintenance into advanced system administration. It is the first of the two exams required for LPIC-2, but passing 201 alone does not produce the LPIC-2 certification. An active LPIC-1 certification is required to receive LPIC-2, and both exams 201 and 202 must be passed.
The target operating context is a small to medium-sized mixed network. That means preparation should extend beyond one distribution’s desktop tools. You should be comfortable reasoning about Linux services, storage, network interfaces, boot processes, filesystems, and operational recovery even when configuration details vary between environments.
Exam 201 is a sensible priority when your work or intended role includes server maintenance, infrastructure support, systems administration, or networked Linux services. It is not a substitute for a specialist security, cloud, or distribution-specific certification. Its value comes from testing a broad administrator’s ability to diagnose, configure, maintain, and explain Linux systems.
Check the prerequisite before investing in preparation
The formal prerequisite is an active LPIC-1 certification. LPI also states that LPIC-2 certification requires passing both 201 and 202. If LPIC-1 is not active, you can still study the exam objectives, but you should confirm your certification path before purchasing or scheduling an LPIC-2 exam.
Do not confuse the exam prerequisite with a recommended learning background. LPI’s requirement is the active LPIC-1 status; practical readiness additionally means that command-line administration, basic networking, permissions, processes, and filesystem work are familiar enough that they do not consume all your study time.
What skills does exam 201 measure?
Exam 201 measures advanced administration in seven areas: capacity planning, the Linux kernel, system startup, filesystems and devices, advanced storage device administration, networking configuration, and system maintenance. The objectives describe tasks and knowledge areas rather than a single product or distribution, so preparation should connect commands with the operational problem they solve.
The official objective weights indicate relative importance: capacity planning is divided between measuring and troubleshooting resource usage with weight 6 and predicting future resource needs with weight 2; Linux kernel objectives carry weights 2, 3, and 4; system startup carries weights 3, 4, and 2; and filesystem and device objectives carry weights 4, 3, and 2.
Advanced storage covers RAID with weight 3, storage device access with weight 2, and LVM with weight 3. Networking configuration covers basic networking with weight 3, advanced network configuration with weight 4, and network troubleshooting with weight 4. System maintenance covers building software from source with weight 2, backup operations with weight 3, and user notification with weight 1.
A weight is not a guaranteed percentage of the exam and does not identify an exact question count. It is a prioritization signal: higher-weighted objectives are covered with more questions. Use the weights to allocate revision time, but do not abandon weight-2 or weight-1 objectives because a question can still expose a narrow knowledge gap.
Capacity planning requires interpretation, not just command recall
The capacity-planning section begins with measuring and troubleshooting resource usage, the highest-weighted individual objective in exam 201. The objective names hardware resources and network bandwidth and expects candidates to identify and troubleshoot resource problems. The related tools include iostat, iotop, vmstat, netstat, ss, iptraf, pstree, ps, lsof, top, htop, uptime, and sar.
Study each tool by asking what it measures, what a suspicious result might mean, and what command or configuration you would inspect next. For example, distinguish CPU saturation from blocked I/O, memory pressure from swap activity, and a network symptom from a local process holding a socket. The second capacity-planning objective is about monitoring usage to predict future needs, with awareness of monitoring solutions such as Icinga2, Nagios, collectd, MRTG, and Cacti.
Kernel preparation should follow the lifecycle of a change
The kernel objectives cover components, compiling a kernel, and runtime management and troubleshooting. The official list includes kernel configuration, make targets, module tools, initramfs creation, DKMS, /usr/src/linux/.config, /lib/modules/kernel-version/, depmod, and awareness of dracut. Kernel runtime management and troubleshooting has weight 4, while kernel components has weight 2 and compiling a Linux kernel has weight 3.
Build a disposable laboratory system and record the sequence: identify the running kernel, inspect loaded modules, locate configuration, change a controlled option, build or install only when safe, update the module dependency information, and verify the result after reboot. Learn the purpose of targets such as menuconfig, oldconfig, modules, modules_install, and the image targets named in the objectives. The goal is to understand dependencies and recovery, not to compile a production kernel casually.
System startup and recovery need a decision tree
System startup includes customizing startup, system recovery, and alternate bootloaders. The objectives cover systemd, SysV init, systemctl, systemd-delta, /etc/inittab, init scripts, GRUB 2, GRUB Legacy, BIOS, UEFI, NVMe booting, initrd or initramfs, the EFI System Partition, efibootmgr, PXE-related loaders, systemd-boot, and U-Boot.
Practice troubleshooting in layers: firmware and boot mode, bootloader configuration, kernel loading, initramfs, filesystem mounting, service initialization, and the final login environment. Create notes that map an observed failure to the layer you would inspect. Include recovery-mode tasks and understand how a system can be repaired when normal service startup is unavailable.
Do not study systemd as an isolated command list. Compare service status, enablement, dependencies, logs, and generated configuration with the older SysV model. The version-4.5 update specifically increased systemd coverage and added UEFI and NVMe booting, so older material can leave a significant gap.
Filesystems and devices combine administration with safety
The filesystem objectives cover operating, maintaining, and creating or configuring filesystem options. Required knowledge includes /etc/fstab, /etc/mtab, /proc/mounts, mount, umount, blkid, swapon, swapoff, fsck, automount units, ISO9660 and UDF tools, dm-crypt, and LUKS. The version-4.5 summary also adds basic Btrfs operations and awareness of ZFS.
Build a reference table for persistent mounts: device or UUID, mount point, filesystem type, options, dump field, and filesystem-check field. Then test how you identify a device, mount it temporarily, make a persistent entry, and diagnose a bad entry without making the system unbootable. Keep filesystem creation, checking, resizing, encryption, and automounting as separate study tasks; confusing their utilities is a common avoidable error.
For Btrfs and encryption, learn the scope stated by the objectives rather than expanding into an unrelated specialist course. You need to recognize the basic administration concepts and tools named by LPI, while still understanding when a filesystem or encrypted block device changes the normal mount and recovery workflow.
RAID and LVM should be practiced as change procedures
Advanced storage administration covers software RAID, adjusting storage device access, and LVM. The RAID objective includes RAID 0, 1, and 5, together with mdadm, mdadm.conf, /proc/mdstat, and related partition information. Storage access includes kernel support for drives and version-4.5 additions such as SSD and NVMe configuration and awareness of SAN. LVM includes physical volumes, volume groups, logical volumes, snapshots, activation, resizing, and lvm.conf.
Use a lab with disposable virtual disks. For RAID, practice assembling an array, checking its state, understanding degraded operation, and identifying the configuration needed for persistence. For LVM, follow the complete path from physical volume to volume group to logical volume, then mount the result and test a snapshot or controlled size change. Write down which operation affects the block device, which affects the filesystem, and which affects the mount configuration.
A frequent mistake is treating RAID and LVM as interchangeable forms of backup. They address storage layout and availability characteristics; they do not remove the need for backup operations. Another mistake is resizing a filesystem without confirming whether the underlying logical volume or partition has been changed safely.
Networking preparation should move from configuration to diagnosis
Networking configuration is split into basic configuration, advanced network configuration, and troubleshooting. The objectives name ip, ifconfig, route, arp, ss, netstat, lsof, ping, ping6, nc, tcpdump, nmap, iw, iwconfig, iwlist, traceroute6, and mtr. Advanced configuration includes network authentication schemes, while troubleshooting requires locating configuration files and correcting common setup issues.
Practice from the bottom upward: interface state, address and prefix, route, name resolution, local listening socket, firewall path, and remote service. For every failure, write the smallest test that separates two possible causes. A failed ping does not by itself prove that an application is down, and a listening socket does not prove that a remote client can reach it.
Include IPv6 deliberately. The version-4.5 update added IPv6-related coverage, including ping6, IPv6 troubleshooting tools, and IPv6 concepts elsewhere in LPIC-2. Do not reduce the topic to memorizing syntax differences; understand addresses, routes, link-local behavior, and the evidence each diagnostic command provides.
System maintenance rewards repeatable procedures
System maintenance covers making and installing programs from source, backup operations, and notifying users about system-related issues. The objectives name configure, make, install, patch, tar, compression tools including xz, dd, rsync, tape-device paths, mt, system notices, wall, shutdown, systemctl, /etc/issue, /etc/issue.net, and /etc/motd. Backup operations carry weight 3, while user notification carries weight 1.
Create a source-build checklist that records prerequisites, configuration choices, installation locations, verification, and rollback considerations. For backups, compare archive-based copies, block-level approaches, synchronization, and tape-oriented utilities at the level required by the objectives. A backup is not demonstrated merely because a command completed: you should know what was included, where it was stored, how it would be restored, and how you would verify it.
Practice communicating maintenance without relying on an invented operational scenario. Know the difference between a message shown at login, a message sent to logged-in users, and a service or shutdown action. The small weight of notification does not justify ignoring it; it is a short topic that can be closed efficiently with a clear command-and-purpose table.
How should you study the 201 objectives?
Use the official objective list as a checklist, then turn every objective into a lab action, a diagnostic question, and a short explanation. Read broadly enough to recognize all named tools, but spend the most lab time on high-weight areas and tasks where one change affects boot, storage, networking, or service availability.
A productive sequence is foundations first, dependency-heavy subjects next, and timed review last. This prevents you from memorizing isolated options before you understand the system relationships that make the options meaningful.
Phase one: audit your LPIC-1 foundation
Start by testing the skills that exam 201 assumes: shell use, processes, permissions, package and file handling, basic network configuration, mounts, logs, and service control. Mark each item as reliable, slow, or unfamiliar. If basic commands still require constant lookup, repair that gap before beginning kernel and storage troubleshooting.
Your output from this phase should be a gap list, not a collection of notes. For each gap, write the command or concept, the symptom it addresses, and one lab exercise. This makes later revision measurable and prevents rereading from becoming a substitute for practice.
Phase two: work through the current objective version
Download or consult the official 4.5 objectives and keep the version visible while studying. Create one row for every exam-201 objective, including its weight, key knowledge areas, commands, and lab status. Add a separate column for version-4.5 additions such as systemd, UEFI, NVMe, Btrfs, DKMS, xz, and the newer diagnostic tools.
Do not let an older 201-400 book define the syllabus by itself. Use it for explanation only when its contents match the current objective list. When a source uses old terminology, compare it against LPI’s version-4.0-to-4.5 change summary and update your notes rather than silently carrying forward obsolete emphasis.
Phase three: build a fault-oriented laboratory
A useful lab contains at least one Linux installation and disposable virtual disks, plus a way to observe services, logs, interfaces, mounts, and resource usage. Keep a recovery path before experimenting with bootloaders, filesystems, RAID, LVM, or kernel changes. The lab’s purpose is controlled learning, not production simulation.
For each exercise, record the initial state, the change, the expected evidence, the verification command, and the recovery step. Repeat the exercise from a clean state later. This develops the procedural memory needed for fill-in-the-blank questions while preserving the reasoning needed for multiple-choice troubleshooting questions.
Phase four: convert notes into retrieval practice
Close your notes and answer prompts such as: Which layer would you inspect first? Which file persists this setting? What evidence distinguishes a route problem from a service problem? What must be updated after installing a module? Which component is changed by this command? Retrieval practice exposes confusion more effectively than highlighting.
Use short comparison sheets for pairs that are easy to mix up: systemd and SysV init, RAID and LVM, /proc/mounts and /etc/fstab, IPv4 and IPv6 diagnostics, service state and service enablement, archive backup and synchronization. Keep the explanation beside the command so you learn purpose and effect together.
Phase five: add timed mixed review
The official LPIC-2 overview states that each exam is 90 minutes and contains 60 multiple-choice and fill-in-the-blank questions. Use that format for final practice only after the objective audit and lab work are complete. The aim is to manage reading, recall, and uncertainty without sacrificing accuracy.
Review every missed or guessed item by objective, not merely by topic title. If several errors belong to one objective, return to the lab or documentation. If errors are scattered, improve command recognition and question reading. Practice questions can assess readiness, but they cannot replace the official objectives or guarantee a pass.
What study mistakes most often waste preparation time?
The costliest mistakes are version confusion, command memorization without system context, and overconfidence after recognizing familiar terminology. Correct these by verifying the exam code, performing controlled tasks, and explaining why an answer is correct. Avoid any resource that claims leaked questions or promises that memorization alone guarantees success.
A sound preparation plan also protects time for less familiar areas. Administrators often over-study the services they use at work and under-study boot recovery, kernel modules, storage maintenance, or IPv6. The objective weights help correct that bias, but complete coverage still matters.
Mistake: preparing for 201-400 without checking the code
An old code in a catalogue, book, or practice platform is not proof that the same code is available for scheduling. The official current overview lists 201-450 and 202-450, and the objective page identifies version 4.5. Resolve the mismatch before you build a study calendar or pay for an exam attempt.
Save a copy or note of the objective version you used. Recheck it close to scheduling because LPI’s exam overview is the appropriate place to confirm current versions and language availability.
Mistake: treating objective weights as a pass formula
Weights show relative coverage, not a guaranteed pass threshold or an exact proportion of questions. A weight-6 objective deserves more time than a weight-1 objective, but every listed objective remains examinable. Use weighted time allocation alongside a completion check for all topics.
Never convert a weight into an invented percentage. Instead, state the objective name with its weight and track whether you can perform or explain the required task.
Mistake: learning commands without observing results
A command list is weak preparation if you cannot interpret its output. After running a diagnostic or configuration command, say what changed, what stayed unchanged, and what evidence would disprove your first hypothesis. This is especially important for resource monitoring, networking, startup, filesystems, RAID, and LVM.
If a laboratory command is unsafe on a live system, use a disposable virtual machine or study the documented behavior without applying it. Do not experiment on production infrastructure merely to gain exam practice.
Mistake: confusing certification scope with job scope
LPIC-2 validates a broad administrator skill set, not mastery of every enterprise platform. Prepare to the objective boundaries. The exam includes awareness-level technologies as well as hands-on configuration areas, so do not spend all your time pursuing deep specialist implementation that is not reflected in the objectives.
Conversely, do not dismiss an awareness item because you would delegate it at work. You still need to identify its purpose, vocabulary, and relationship to the surrounding administration task.
What are the delivery and language details?
LPI states that LPIC-2 exams are available through Pearson VUE OnVUE online testing, and its online-testing page describes remote-proctored delivery. The online LPIC-2 exam language identified there is English. LPI’s broader exam information also lists test-center language availability and warns that language availability can depend on the delivery channel.
Delivery requirements are practical scheduling constraints, not study topics. Confirm them before selecting a remote appointment or test center, especially if your preferred language is not English or if you plan to use a Linux computer for online delivery.
Online testing checklist
For OnVUE delivery, LPI states that candidates need a quiet, private location, a reliable computer with a camera, and a stable Internet connection. The page states that the OnVUE platform is available in English only and that Windows and MacOS are currently supported. A Linux study machine therefore may not satisfy the online delivery requirement.
Run the provider’s system checks before scheduling and review the full Pearson VUE policies and procedures linked from LPI’s online-testing information. If your equipment or room does not meet the requirements, compare an authorized test-center option instead of assuming that remote delivery will work.
Confirm the language at the channel you will use
The LPI exam overview lists LPIC-2 version 4.5 languages as German, English, Japanese, French, and Portuguese (Brazilian), while the online-testing page identifies LPIC-2 online delivery in English. Some languages may be available only through particular channels. Confirm the exact language during scheduling rather than relying on a general certification summary.
If you study in a language different from the delivered exam, build a glossary for commands, configuration files, and objective terms. The English objectives are canonical when a discrepancy exists between English and a translation, according to LPI’s published information.
Understand the exam structure without inventing a score target
Each LPIC-2 exam is 90 minutes with 60 multiple-choice and fill-in-the-blank questions according to LPI’s current overview. The supplied official information does not establish a passing score in this guide, so do not use an unofficial percentage as a scheduling rule. Prepare for both recognition and exact recall.
In final practice, read the whole question, identify the objective, eliminate answers that alter the stated scope, and mark uncertain items for later review when the delivery interface permits it. The exact navigation behavior should be confirmed in the current provider instructions rather than assumed from a practice platform.
How long should the study roadmap be?
Choose the roadmap length from your gap audit, not from a generic promise. A candidate with strong LPIC-1 skills and regular Linux administration may need a focused review; someone unfamiliar with boot recovery, storage, or network diagnosis should extend the lab phase. The four-stage roadmap below is sequential, but each stage can occupy more or less calendar time.
Schedule only when you can explain every objective, complete the core lab procedures safely, and finish timed mixed practice without leaving entire domains unreviewed. That readiness decision is more reliable than counting study days.
Stage one: establish the map
Read the current exam-201 objectives from start to finish. Record every domain, objective weight, key knowledge area, and unfamiliar command. Verify that your notes say 201-450 when preparing for the current version, even if the page or product that brought you here uses 201-400.
At the end of this stage, decide whether exam 201 is the immediate target or whether LPIC-1 fundamentals need attention first. Also decide whether you will use online delivery or a test center, because language and operating-system constraints can affect that choice.
Stage two: learn in dependency order
Study capacity and diagnostics first, then kernel and startup, followed by filesystems, RAID and LVM, networking, and maintenance. This order moves from observing system state to changing core components and then to maintaining and troubleshooting the resulting environment.
Do not postpone the high-risk subjects until the final week. Boot, kernel, storage, and networking require time to set up safely and to repeat after a mistake. Keep a short awareness list for technologies that do not justify a full laboratory build.
Stage three: test procedures under pressure
Run mixed drills that begin with a symptom rather than a topic name. For example, start with a failed mount, missing route, unavailable module, degraded array, unexpected service state, or resource alert, then identify the evidence and next action. Keep the exercises within the published objectives and do not use live exam content.
Time the complete 60-question, 90-minute format only when your review system is ready. After each session, classify errors as knowledge, interpretation, command syntax, or time management. Apply the classification to the next lab session.
Stage four: schedule and close gaps
Once the objective checklist is complete, confirm the current code, version, language, delivery channel, and prerequisite status. Revisit only the gaps shown by your review record. Avoid replacing structured revision with a last-minute search for question dumps or claims about repeated live items.
Prepare a compact final sheet containing diagnostic sequences, configuration-file locations, storage relationships, boot layers, and command purposes. The sheet should prompt recall, not reproduce a large reference manual. Stop adding new topics when doing so would weaken your ability to retrieve the core procedures.
What should you do after reading this guide?
First, open LPI’s current LPIC-2 overview and verify whether your intended exam is 201-450 rather than 201-400. Next, confirm that your LPIC-1 certification is active and decide whether your delivery channel supports your preferred language and computer. Then download the official objectives, mark your weak domains, and begin with a lab-based audit rather than a question-dump search.
Your immediate study deliverables should be a version-checked objective matrix, a disposable Linux laboratory, a procedure log, and a timed-review plan. When those four items are in place, you can make a defensible scheduling decision and adjust preparation based on evidence instead of catalogue labels or unsupported pass claims.
Conclusion
The central decision is not whether a page carries the label 201-400; it is which LPIC-2 objective version and exam code your provider will actually deliver. LPI’s current information points to version 4.5 and code 201-450, with LPIC-2 requiring both exams 201 and 202 plus an active LPIC-1 certification. Verify that foundation first, study the official domains by weight and dependency, practise recovery and diagnosis in a safe lab, and confirm delivery details directly before scheduling.
