- What LPIC-2 Exam 201 Actually Is
- Format, Rules and Logistics
- Capacity Planning: Measuring Before You Tune
- Linux Kernel: Build, Patch and Modules
- System Startup: From Firmware to Services
- Filesystem and Devices
- Advanced Storage Device Administration
- Networking Configuration
- System Maintenance
- A Domain-Ordered Study Sequence
- Who Hires for LPIC-2 Skills
- Frequently Asked Questions
- Exam 201 (201-450) has 60 multiple-choice and fill-in-the-blank questions in 90 minutes; fill-in answers require exact command or file names.
- Passing 201-450 alone does not award LPIC-2; you must also pass 202-450 and hold an active LPIC-1.
- The seven domains run from Capacity Planning through System Maintenance, with no published domain percentages to budget around.
- Hands-on repetition of kernel builds, GRUB repair, LVM and RAID operations matters more than memorizing prose.
What LPIC-2 Exam 201 Actually Is
LPIC-2 Exam 201 (Part 1 of 2), version 4.5 (exam code 201-450), is the first of two papers that make up the Linux Professional Institute's advanced-level administrator certification. The objectives are published by LPI at lpi.org as the LPIC-2 Exam 201 and 202 Objectives, version 4.5. If you want the big-picture definition before diving in, the explainer on what LPIC-2 201-450 is covers the basics, and the page on the LPIC-2 201-450 certification frames where it sits in the LPI ladder.
Two structural facts shape your whole plan. First, an active LPIC-1 certification is required to receive LPIC-2. Second, both 201-450 and 202-450 must be passed. Clearing this paper alone does not earn you the credential, so think of Exam 201 as the first half of a two-step campaign. The full eligibility picture is laid out in the LPIC-2 201-450 requirements guide.
Exam 201 is weighted toward the infrastructure underneath services: how a system measures its own load, how the kernel is built, how the machine boots, how storage is carved up, and how the network is configured. Exam 202 moves up the stack into services such as DNS, web, file sharing, email and security. That split tells you what this paper rewards: deep, command-line-level familiarity with the machine itself.
Format, Rules and Logistics
Each paper contains 60 questions, a mix of multiple-choice and fill-in-the-blank items, with a 90-minute limit. That works out to roughly a minute and a half per question, which sounds comfortable until you hit a fill-in item and have to type an exact command or path from memory.
| Item | What to Know |
|---|---|
| Exam | LPIC-2 Exam 201 (Part 1 of 2), version 4.5 (201-450) |
| Issuer | Linux Professional Institute (LPI) |
| Questions | 60, multiple-choice and fill-in-the-blank |
| Time limit | 90 minutes |
| Prerequisite | Active LPIC-1 certification required to receive LPIC-2 |
| Completing LPIC-2 | Both 201-450 and 202-450 must be passed |
| Validity | 5 years |
Delivery, scheduling and regional pricing run through LPI and Pearson VUE, and they change, so verify them at registration rather than trusting a blog post. For the money side, see the LPIC-2 201-450 certification cost breakdown, and for scheduling mechanics see exam dates and testing windows. A current official passing score was not verified for this article, so check the passing score page and LPI directly instead of relying on a number from a forum.
Capacity Planning: Measuring Before You Tune
The first domain, Capacity Planning, is about knowing what your system is doing under load and predicting when it will run out of room. Expect questions that hand you tool output and ask what it means, or ask which tool answers a particular question.
Domain 1: Capacity Planning
You should be able to measure and troubleshoot resource usage and forecast future needs.
- Read CPU, memory, I/O and swap statistics using tools such as
top,vmstat,iostat,sarandfree. - Distinguish a CPU-bound problem from a memory-pressure or disk-wait problem from the numbers alone.
- Understand load average and what it does and does not tell you.
- Know how historical data collection (for example
sararchives) supports trend analysis. - Be aware of monitoring and alerting approaches used to predict resource exhaustion.
The trap here is treating tools as interchangeable. Each one answers a different question, and exam items often hinge on picking the tool that shows per-device I/O versus the one that shows memory paging.
Linux Kernel: Build, Patch and Modules
The Linux Kernel domain is hands-on territory. Candidates are expected to understand the kernel as something you can configure, compile, patch and extend, not just a black box that ships with the distribution.
Domain 2: Linux Kernel
Know the lifecycle of a custom kernel and how modules are managed at runtime.
- Configure a kernel using the standard configuration interfaces, then compile and install it.
- Understand where the build output lands and how the boot loader is made aware of it.
- Apply patches to kernel source and know the purpose of a clean rebuild.
- Manage modules with
lsmod,modprobe,modinfoanddepmod, and know how module configuration files shape loading behavior. - Tune runtime parameters through
sysctland the/procand/sysinterfaces. - Use
dmesgand system logs to diagnose kernel-level problems.
If you have never compiled a kernel, do it once in a throwaway virtual machine. Seeing the configure, build, install and boot-loader steps happen in order makes the exam's sequencing questions far easier than any diagram would.
System Startup: From Firmware to Services
System Startup covers everything between power-on and a usable login prompt. Questions probe whether you understand each stage well enough to diagnose a machine that will not boot.
Domain 3: System Startup
Understand the boot chain, the boot loader and the service manager.
- Explain the sequence from firmware through the boot loader to the kernel and the init system.
- Customize and troubleshoot the boot loader (GRUB), including reinstalling it and editing boot parameters at boot time.
- Work with both the legacy SysV init model and systemd, including unit files, targets and the commands used to control services.
- Recover a system by booting to a minimal target or single-user mode.
- Understand the role of the initial RAM filesystem and when it must be regenerated.
Because the exam spans older and newer init approaches, do not skip the legacy material just because your daily driver is systemd. Questions can reference either world, and knowing the mapping between runlevels and targets saves points.
Key Takeaway
Rebuild a broken boot on purpose. Corrupt a boot entry in a test VM, then repair it from rescue media. The recovery workflow you rehearse is exactly what scenario-style questions describe in words.
Filesystem and Devices
This domain deals with how storage is formatted, mounted and kept healthy, plus how devices are recognized and named by the system.
Domain 4: Filesystem and Devices
Operate and maintain filesystems and understand device management.
- Create, check and repair filesystems with the relevant
mkfs,fsckand tuning utilities for common Linux filesystem types. - Control mounting through
/etc/fstab, including options, UUID and label usage, and automounting. - Manage swap space.
- Understand how
udevnames and configures devices, and how rules influence persistent naming. - Use tools to inspect and adjust filesystem attributes and quotas where applicable.
Know the differences between filesystem types at the level of features and tooling, not just names. Questions tend to ask which utility applies to which filesystem or which option achieves a particular mount behavior.
Advanced Storage Device Administration
Where the previous domain covers the basics, Advanced Storage Device Administration goes into the layers that sit between physical disks and filesystems: RAID, logical volumes and encryption, plus hardware-level tuning.
Domain 5: Advanced Storage Device Administration
Combine, abstract and protect storage.
- Configure and manage software RAID with
mdadm, including creating arrays, checking status and replacing failed members. - Use LVM to create and extend physical volumes, volume groups and logical volumes, and understand snapshots.
- Set up and unlock encrypted block devices with the standard disk-encryption tooling.
- Adjust and query disk parameters, including hardware-level settings and SMART-style health information.
- Understand how these layers stack so you can reason about which command acts at which level.
The layered-stack idea is the key to this domain. A question might describe a filesystem on a logical volume on a RAID array and ask where to apply an operation. Draw the stack on paper until you can place any command on the correct layer instantly.
Networking Configuration
Networking Configuration in Exam 201 concentrates on configuring and troubleshooting connectivity on the host itself, rather than running network services, which belongs to Exam 202.
Domain 6: Networking Configuration
Bring interfaces up, route traffic and diagnose faults.
- Configure interfaces and addresses, including persistent configuration through the distribution's mechanisms.
- Understand routing tables, static routes and basic routing decisions.
- Use diagnostic tools such as
ip,ss,ping,tracerouteand packet capture utilities to locate faults. - Work with advanced topics such as bonding, bridging, VLANs and VPN connectivity at the configuration level.
- Troubleshoot name resolution and general connectivity problems methodically.
Modern ip and ss syntax appears alongside older tools in many study resources. Learn the current commands first, then recognize the legacy equivalents so older phrasing in a question does not throw you.
System Maintenance
The final domain, System Maintenance, covers the practical housekeeping that keeps a system current and recoverable.
Domain 7: System Maintenance
Build, install, back up and notify.
- Compile software from source and understand the configure, make and install workflow.
- Use the RPM and Debian package toolchains to install, query, verify and remove software.
- Plan and perform backups and restores, and know the strengths of common archiving and synchronization tools.
- Notify users and manage system messages through the standard facilities.
- Understand how logs and system information support routine maintenance tasks.
Dual packaging knowledge is the common stumbling block. If you live on one distribution family, deliberately spend time on the other so package-query questions do not feel foreign.
A Domain-Ordered Study Sequence
Since LPI publishes no percentage weighting per domain here, avoid budgeting study time by guesswork about "heavy" areas. Instead, sequence your preparation by dependency: later domains assume skills from earlier ones. The order below follows that logic. For an overview of how the domains connect, see the complete guide to all seven content areas.
Measurement and the Kernel
- Capture baseline performance data with the monitoring tools.
- Compile, install and boot a custom kernel in a test VM.
Boot Chain and Filesystems
- Repair a deliberately broken boot loader and practice recovery targets.
- Build, mount, check and tune several filesystem types.
Layered Storage and Networking
- Create RAID, LVM and encrypted volumes, then extend and recover them.
- Configure interfaces, routes, bonding and bridging, and trace faults.
Maintenance and Full Review
- Practice both package systems, source builds and backup/restore.
- Take timed practice sets and revisit your weakest domain.
Adjust the pace to your experience. A seasoned administrator may compress this considerably, while someone moving up from LPIC-1 may want longer on storage and networking. To gauge where you stand, read how hard the exam is, and keep the one-page cheat sheet handy for last-week review. When you want timed, objective-mapped questions, use the LPIC-2 201-450 practice tests to find gaps, then return to the lab to fix them.
Who Hires for LPIC-2 Skills
The skills behind Exam 201 map to roles where someone owns the health of Linux servers: systems administrator, Linux engineer, infrastructure or operations engineer, and site reliability or DevOps roles that still require solid host-level knowledge. Hosting providers, managed-service companies, enterprises running large Linux estates and organizations with on-premises or hybrid infrastructure value people who can diagnose boot failures, resize storage safely and tune a loaded machine.
Employers rarely treat the paper itself as the point; it works as evidence that you have disciplined, vendor-neutral Linux depth. For realistic role titles see the LPIC-2 201-450 jobs overview, and for earnings context see the salary guide. If you are still weighing the investment, the ROI analysis walks through the trade-offs. Because no verified pass-rate figure is asserted here, the pass rate discussion is the place to see how to read whatever data is available.
Frequently Asked Questions
No. LPIC-2 requires passing both 201-450 and 202-450, and you must hold an active LPIC-1 certification to receive it. Exam 201 is one of two required papers.
The paper has 60 multiple-choice and fill-in-the-blank questions with a 90-minute time limit. Plan to type exact commands and file paths for the fill-in items.
Capacity Planning, Linux Kernel, System Startup, Filesystem and Devices, Advanced Storage Device Administration, Networking Configuration, and System Maintenance. LPI weights individual objectives, so no aggregate domain percentages are published here.
LPIC-2 certification is valid for 5 years. Renewal options and regional pricing can change, so confirm current terms with LPI and Pearson VUE before you plan.
Work in a real lab and type commands, options and paths from memory rather than recognizing them from a list. Rehearse kernel builds, GRUB repair, mdadm and LVM operations until the syntax is automatic.
Exam 201 rewards people who have actually broken and repaired Linux systems. Pair a lab habit with objective-mapped practice, work through the domains in dependency order, and you will walk in prepared for what the paper really asks. For a consolidated plan, return to the full LPIC-2 201-450 study guide whenever you need to re-orient.