LPIC-2 201-450 logo
Focused certification exam prep
Start practice

LPIC-2 201-450 Exam Domains 2026: Complete Guide to All 7 Content Areas

TL;DR
  • Exam 201 (version 4.5) has 60 multiple-choice and fill-in-the-blank questions in a 90-minute limit.
  • The seven content areas run from Capacity Planning through System Maintenance; LPI weights individual objectives, not whole domains.
  • Passing 201-450 alone does not award LPIC-2; you must also pass 202-450 and hold an active LPIC-1.
  • Fill-in-the-blank items reward exact command and option recall, so practice typing commands from memory.

How the Exam 201 Objectives Are Organized

LPIC-2 Exam 201 (Part 1 of 2), version 4.5, carries the exam code 201-450. It is one of two papers that together lead to the LPIC-2 credential issued by the Linux Professional Institute (LPI). The companion paper is 202-450, and both must be passed. An active LPIC-1 certification is also required before LPIC-2 is awarded, so passing 201-450 by itself does not earn you the credential. If you are still checking eligibility, the LPIC-2 201-450 requirements guide walks through prerequisites in detail.

The published objectives for this paper are grouped under seven headings: Capacity Planning, Linux Kernel, System Startup, Filesystem and Devices, Advanced Storage Device Administration, Networking Configuration, and System Maintenance. A detail worth understanding early: LPI does not publish aggregate percentage weights for these headings. Instead, weights are assigned to individual objectives within each area, which signals how much each topic can contribute to your score. That means you should not treat the seven areas as equal slices, and you should not trust any source that quotes a tidy percentage per domain.

The paper contains 60 questions, a mix of multiple-choice and fill-in-the-blank, with a 90-minute limit. That works out to roughly a minute and a half per question, which is comfortable for recall items but tight for questions that require you to reason through a configuration file or command pipeline. For the broader picture of how the pieces fit together, see our LPIC-2 201-450 study guide.

Why domain weights are not published: Because LPI weights objectives rather than domains, a single heavily weighted objective inside a small-looking area can matter more than an entire lightly weighted area. Study at the objective level, using the official objectives page on lpi.org as your checklist.

Domain 1: Capacity Planning

Capacity Planning is about knowing what your system is doing now and predicting what it will need next. This is the most "sysadmin-in-practice" area of the exam, and it rewards candidates who have actually watched a loaded server misbehave.

Capacity Planning: What You Must Be Able to Do

Measure resource usage, identify bottlenecks, and project future needs for CPU, memory, disk, and network.

  • Interpret output from tools such as top, vmstat, iostat, sar, free, and netstat or ss.
  • Distinguish CPU-bound, memory-bound, and I/O-bound symptoms from the numbers alone.
  • Understand load average, swap activity, and what sustained values imply.
  • Recognize the role of monitoring and trending tools used to forecast growth.

Expect questions that hand you a snippet of tool output and ask what is wrong, or ask which tool and option would reveal a specific metric. Fill-in-the-blank items here often ask for the exact command or flag. Knowing that a tool exists is not enough; you need to recall what its columns mean.

Domain 2: Linux Kernel

The Linux Kernel area covers working with the kernel as an administrator: inspecting it, configuring it at runtime, building it, and managing modules. It is highly procedural, which makes it ideal for hands-on practice in a virtual machine.

Linux Kernel: High-Value Topics

Kernel components, modules, compilation, and runtime parameters.

  • Loading, unloading, and inspecting modules with modprobe, insmod, rmmod, lsmod, and modinfo.
  • Module configuration under /etc/modprobe.d/ and dependency handling with depmod.
  • Runtime tuning through sysctl and /proc/sys, plus the persistent configuration files that survive reboot.
  • The kernel build workflow: obtaining source, configuring, compiling, installing, and patching.
  • Using dmesg and kernel logs to troubleshoot hardware and driver problems.

A classic trap is confusing a change that is applied immediately but lost at reboot with one that is persistent. Practice both halves of every kernel parameter change.

Domain 3: System Startup

System Startup tests whether you can follow a machine from power-on to a usable login prompt and repair it when the sequence breaks. This area spans the boot loader, init systems, and recovery procedures.

System Startup: What Candidates Must Master

Boot sequence, boot loader configuration, and service management.

  • GRUB configuration, installing the boot loader, and editing kernel parameters at boot.
  • Differences among SysV init, Upstart-style, and systemd approaches, including targets versus runlevels.
  • Managing units and services, enabling or disabling them, and checking status and logs.
  • Recovery techniques: single-user or rescue mode, repairing a broken boot loader, and working from rescue media.

Because the exam covers more than one init approach, do not study systemd in isolation. Candidates who learned only one init system often stumble when a question is framed around another. Our difficulty breakdown discusses which areas tend to catch people off guard.

Domain 4: Filesystem and Devices

This area concerns creating, mounting, maintaining, and securing filesystems, and understanding how devices appear and are managed by the system.

Filesystem and Devices: Core Skills

Operating Linux filesystems and managing device nodes.

  • Creating and tuning ext2/3/4 and XFS filesystems, and checking or repairing them with the matching tools.
  • Mount options, /etc/fstab, and mounting by label or UUID.
  • Automounting and on-demand filesystem mounting.
  • Quotas, swap space, and filesystem inspection utilities.
  • Device management with udev, including writing and reading rules.

Questions here are often option-heavy: which flag to pass to a filesystem creation or tuning command, or what a particular mount option does. Build a habit of running these commands in a lab and reading the manual page afterward to confirm what each option actually did.

Lab habit that pays off: Create a throwaway virtual disk, format it, mount it, break it on purpose, and repair it. The memory of having fixed a real corrupted filesystem is far stickier than reading about the repair tools.

Domain 5: Advanced Storage Device Administration

Where the previous area handles single filesystems, Advanced Storage Device Administration deals with the layers underneath and around them: RAID, logical volumes, encryption, and storage tuning.

Advanced Storage: Topics to Drill

Software RAID, LVM, disk encryption, and performance configuration.

  • Configuring and monitoring software RAID with mdadm, including failure and rebuild scenarios.
  • Logical volume management: physical volumes, volume groups, logical volumes, resizing, and snapshots.
  • Disk encryption with LUKS and the related tooling.
  • Adjusting disk access and performance with tools such as hdparm, plus awareness of SSD considerations.
  • Understanding how storage layers stack on one another.

This is typically where hands-on experience separates strong candidates from weak ones. The sequence of commands for extending a logical volume and then growing the filesystem on it, or for replacing a failed RAID member, is exactly the kind of multi-step knowledge that fill-in-the-blank items probe.

Domain 6: Networking Configuration

Networking Configuration focuses on bringing a Linux host onto a network, diagnosing connectivity, and handling more advanced interface setups.

Networking Configuration: What to Know

Interface setup, routing, and troubleshooting.

  • Configuring interfaces and routes with ip and understanding the older ifconfig and route equivalents.
  • Persistent network configuration files and how they differ by distribution family.
  • Advanced setups such as bonding, bridging, and VLANs.
  • Troubleshooting with tools like ping, traceroute, tcpdump, ss, and netcat.
  • Wireless basics and name resolution settings.

Because the exam is distribution-agnostic in spirit, be ready to recognize both the runtime command and the persistent configuration approach. A question may ask how to make a change survive a reboot rather than how to make it take effect right now.

Domain 7: System Maintenance

System Maintenance rounds out the paper with the routine duties of keeping a system current, documented, and recoverable.

System Maintenance: Key Responsibilities

Building from source, managing packages, backups, and notifying users.

  • Compiling and installing software from source, including the usual configure, make, and install steps.
  • Package management with both RPM-based and Debian-based tools, including querying, verifying, and installing packages.
  • Backup and restore strategies, and the tools used to implement them.
  • Notifying users of system events and maintenance activity.

Package management questions frequently test whether you can pick the right query or verification option, such as listing files owned by a package or finding which package owns a file. Know both package ecosystems rather than favoring the one you use at work.

Sequencing the Seven Domains Over Your Prep Weeks

Rather than a generic schedule, order your study by how the topics build on each other. Storage and filesystems depend on understanding devices, and troubleshooting anything depends on the ability to read system output. The timeline below is one reasonable ordering for a roughly six-week effort; adjust the pace to your experience.

Week 1

Capacity Planning and Linux Kernel

  • Learn to read monitoring output first; it sharpens every later troubleshooting skill.
  • Practice module and sysctl changes, both temporary and persistent.
Week 2

System Startup

  • Walk the full boot path and rehearse GRUB and rescue-mode repairs.
  • Compare init systems side by side.
Weeks 3-4

Filesystem and Devices, then Advanced Storage

  • Cover single filesystems and udev before layering RAID, LVM, and LUKS on top.
  • Spend the most lab time here; this is the densest procedural material.
Week 5

Networking Configuration and System Maintenance

  • Configure bonding or bridging in a VM and troubleshoot with packet tools.
  • Drill both RPM and Debian package queries.
Week 6

Review and Practice

  • Re-test weak objectives and run timed question sets against the official objectives list.

For a compact reference to keep beside you while reviewing, the LPIC-2 201-450 cheat sheet condenses the commands and options worth memorizing.

Question Style and Format

The paper mixes multiple-choice and fill-in-the-blank items across 60 questions in 90 minutes. The fill-in-the-blank format is what distinguishes this exam from many entry-level certifications: you may need to type a command, an option, or a file path exactly, with no answer choices to jog your memory. That makes recognition-based studying risky. If you only ever read commands, you may recognize them yet fail to produce them.

Item TypeWhat It TestsHow to Prepare
Multiple-choiceSelecting the correct command, option, or interpretation of outputPractice eliminating near-miss distractors that differ by one flag
Fill-in-the-blankExact recall of a command, option, file, or valueType commands from memory in a lab, then verify against manual pages

Pacing matters. Do a first pass that answers the questions you know immediately, flag the ones needing configuration-file reasoning, and return to them. Questions about the scoring threshold and how results are reported are covered in our passing score article; we do not quote a figure here because a current official value has not been verified.

Key Takeaway

Study at the objective level, drill exact command syntax for the fill-in-the-blank items, and spend your heaviest lab hours on Filesystem and Devices plus Advanced Storage. Use the practice test site for objective-mapped practice, which is independently authored and is not a copy of real issuer questions or an official exam simulation.

Frequently Asked Questions

How many content areas does LPIC-2 Exam 201 cover?

Seven: Capacity Planning, Linux Kernel, System Startup, Filesystem and Devices, Advanced Storage Device Administration, Networking Configuration, and System Maintenance. These are the published objective headings for version 4.5 (201-450).

Does passing 201-450 earn me the LPIC-2 certification?

No. You must pass both 201-450 and 202-450 and hold an active LPIC-1 certification to receive LPIC-2. See the requirements guide for the full path.

What is the exam format and time limit?

The paper has 60 questions, a mix of multiple-choice and fill-in-the-blank, with a 90-minute time limit. Verify current delivery details and regional pricing with LPI and Pearson VUE; fee information is broken down in the cost guide.

Are there official percentage weights for each domain?

No aggregate domain percentages are published. LPI assigns weights to individual objectives instead, so use the official objectives page to see how heavily each specific topic is weighted.

How long is the certification valid?

LPIC-2 certification validity is 5 years. Confirm current renewal options directly with LPI, since renewal rules and pricing can change over time.

Ready to pass your LPIC-2 201-450 exam?

Put this into practice with free LPIC-2 201-450 questions across every exam domain.