LPIC-1 101-500 logo
Focused certification exam prep
Start practice

LPIC-1 101-500 Exam Domains 2026: Complete Guide to All 4 Content Areas

TL;DR
  • Exam 101 (101-500) has four content areas, and each paper contains 60 multiple-choice and fill-in-the-blank questions in 90 minutes.
  • LPI weights individual objectives rather than whole domains, so don't trust any blog's claimed domain percentages.
  • You must pass both 101-500 and 102-500 to earn LPIC-1; this paper alone awards no credential.
  • GNU and Unix Commands is the hands-on core: practice pipes, regular expressions, vi, and text tools at a real shell.

How LPIC-1 Exam 101 Is Built

LPIC-1 Exam 101 (LPIC-1: Linux Administrator, version 5.0), exam code 101-500, is the first of two papers issued by the Linux Professional Institute (LPI) on the path to the LPIC-1 certification. The objectives are published on LPI's official LPIC-1 objectives page, and they organize the paper into four content areas: System Architecture; Linux Installation and Package Management; GNU and Unix Commands; and Devices, Linux Filesystems, Filesystem Hierarchy Standard.

Each paper consists of 60 questions, a mix of multiple-choice and fill-in-the-blank, with a 90-minute time limit. That format matters more than most candidates expect. Multiple-choice items let you eliminate wrong answers, but fill-in-the-blank items ask you to type a command, an option, or a file path from memory. If you only ever read about tar flags or dpkg subcommands, you may recognize them on a list but fail to produce them cold.

No aggregate domain weights: LPI assigns weights to individual objectives inside each content area, not to the four areas as a whole. Any article quoting a tidy percentage split for "Domain 3" is guessing. Use the per-objective weights on LPI's published objectives page to decide where to spend your hours.

There are no LPIC-1 certification prerequisites, so you can sit this paper without holding another credential. For a fuller breakdown of eligibility, see LPIC-1 101-500 requirements and how to qualify. Current pricing and regional delivery options should be verified directly with LPI and Pearson VUE; our certification cost breakdown explains how to think about the budget without relying on stale numbers.

Domain 1: System Architecture

This content area covers what happens beneath the shell prompt: hardware configuration, how a Linux system starts, and how it shuts down. It is conceptual but also practical, because administrators diagnose boot failures and hardware problems for a living.

Determine and Configure Hardware Settings

Expect questions about how the kernel exposes hardware and how you inspect it.

  • The roles of /proc and /sys in presenting kernel and device information
  • Inspecting devices with lspci, lsusb, and related utilities
  • Kernel modules: lsmod, modprobe, modinfo, and where module configuration lives
  • How udev manages device nodes and responds to hardware events

Boot the System

You should be able to trace the boot sequence from firmware to a running system.

  • BIOS versus UEFI behavior and the bootloader's role
  • Reading kernel messages with dmesg and the system journal
  • Common boot parameters passed to the kernel
  • Where bootloader and init-related logs are found when something goes wrong

Change Runlevels / Boot Targets and Shutdown or Reboot

Version 5.0 expects familiarity with how modern init systems manage system state.

  • systemd targets versus traditional SysV runlevels and how they map to each other
  • Setting the default target and switching targets on a running system
  • Using systemctl, shutdown, and related commands to halt, reboot, and notify users
  • Rescue and emergency modes, and when you would use them

The trap here is treating this area as trivia. Candidates who skim it lose points on questions that ask which file or command applies in a specific scenario. Build a small lab, boot a virtual machine, break its default target on purpose, and recover it. That single exercise cements most of the objectives in this section.

Domain 2: Linux Installation and Package Management

This area covers laying out disks, choosing and managing boot loaders, handling shared libraries, and, most heavily in practice, working with both major package ecosystems. The exam is distribution-neutral in intent, so you need working knowledge of both the Debian and Red Hat families rather than loyalty to one.

Design Hard Disk Layout

  • Allocating filesystems and swap space to partitions or logical volumes
  • Mount points that are commonly split onto separate partitions, and the reasoning behind that
  • The basics of LVM and how it differs from fixed partitions

Install a Boot Manager

  • Providing boot options and locating GRUB configuration
  • Reinstalling or repairing a bootloader after a failure
  • The difference between GRUB Legacy and GRUB 2 concepts as they appear in the objectives

Manage Shared Libraries

  • Identifying a binary's library dependencies with ldd
  • The purpose of ldconfig, /etc/ld.so.conf, and LD_LIBRARY_PATH

Debian and RPM Package Management

  • Debian side: dpkg, apt-get, apt-cache, and apt for installing, removing, querying, and upgrading
  • Red Hat side: rpm, yum, and dnf, plus how repositories are configured
  • Querying which package owns a file, listing a package's contents, and verifying installed packages
  • The practical difference between low-level tools (dpkg, rpm) and dependency-resolving front ends
Why fill-in-the-blank hurts here: Package management questions often ask for the exact command that lists files installed by a package or finds the owning package of a file. The Debian and RPM answers differ, and mixing them up is the most common error. Make a two-column sheet of equivalent operations and drill it until recall is automatic.

If you want a compact reference for these paired commands, the LPIC-1 101-500 cheat sheet is a useful companion once you have done the underlying lab work.

Domain 3: GNU and Unix Commands

This is the practical heart of Exam 101 and the area where daily shell fluency pays off most. It covers working on the command line, processing text, managing files, using streams and pipes, handling processes, and editing with vi. Candidates who spend real time in a terminal tend to find this section the most natural; those who have only used graphical tools find it the steepest.

Command Line Fundamentals

Know the shell environment: variables, export, env, PATH, quoting rules, command substitution, and shell history. Understand the difference between shell built-ins and external programs, and how to find documentation with man, info, and /usr/share/doc.

Text Processing and Streams

Expect heavy coverage of filters and redirection. You should be comfortable chaining small tools into pipelines.

  • Viewing and slicing: cat, head, tail, cut, sort, uniq, wc, tr, paste, join, split
  • Stream redirection: standard input, output, and error, plus tee and xargs
  • Searching: grep with basic and extended regular expressions, and sed for substitution

File and Directory Management

You must handle copying, moving, and deleting with cp, mv, and rm; recursive operations; wildcards and globbing; and archiving with tar, gzip, bzip2, and xz. Questions frequently test the precise flags for creating versus extracting archives and how compression options interact.

Processes, Priorities, and Job Control

  • Foreground and background jobs: &, jobs, fg, bg, and nohup
  • Monitoring with ps, top, and free; signaling with kill and killall
  • Process priority using nice and renice
  • Keeping sessions alive with a terminal multiplexer such as screen or tmux

Regular Expressions and vi

The objectives expect you to build and read regular expressions and to perform basic editing in vi. Know the modes, how to navigate, delete, copy, paste, search, and save or quit. Questions here are unforgiving: knowing that :wq saves and quits matters, but so does recognizing what dd, yy, p, and /pattern do.

Key Takeaway

Practice Domain 3 at a live shell, not in a flashcard app. Build pipelines such as grep | sort | uniq -c | sort -nr until you can write them without hesitation, because the fill-in-the-blank items reward typed recall.

Domain 4: Devices, Linux Filesystems, Filesystem Hierarchy Standard

The final content area ties storage, permissions, and the layout of the directory tree together. It is where system administration thinking meets exam detail, and permission questions in particular reward careful reading.

Create Partitions and Filesystems

  • Partitioning with fdisk, gdisk, and parted, including MBR versus GPT considerations
  • Creating filesystems with mkfs variants and configuring swap with mkswap and swapon
  • Awareness of ext, XFS, and Btrfs characteristics at the level the objectives describe

Maintain the Integrity of Filesystems

  • Checking and repairing with fsck, e2fsck, and xfs_repair
  • Inspecting space and inode usage with df, du, and tune utilities such as tune2fs

Control Mounting and Unmounting

  • The structure of /etc/fstab, including UUID and label-based entries
  • Mounting and unmounting manually with mount and umount
  • Understanding mount options and systemd mount units at an introductory level

Manage File Permissions and Ownership

  • Reading and setting permissions in symbolic and octal notation with chmod
  • Changing ownership with chown and chgrp, and controlling defaults with umask
  • Special bits: SUID, SGID, and the sticky bit, and what each does on files versus directories

Links, Searching, and the Filesystem Hierarchy Standard

  • Hard links versus symbolic links and how each behaves when the target is removed
  • Locating files with find, locate, which, whereis, and type
  • The purpose of top-level directories defined by the FHS, such as /etc, /var, /usr, /opt, /tmp, and /srv
Permission math is a points trap: Questions often give a mode like 2755 or 1777 and ask what it means, or ask for the mode that produces a described behavior. Practice converting both directions until octal and symbolic forms feel interchangeable, and remember that the leading digit encodes the special bits.

Comparing the Four Content Areas

The table below summarizes the character of each area. It deliberately avoids percentage splits, since LPI weights objectives individually rather than assigning domain totals.

Content AreaDominant SkillTypical Question FeelBest Practice Method
System ArchitectureConceptual understanding of boot and hardwareWhich file, target, or command fits this scenarioBreak and recover a VM's boot target
Linux Installation and Package ManagementCommand recall across two package ecosystemsExact tool and option for a query or install taskPaired Debian and RPM command drills
GNU and Unix CommandsShell fluency and pipelinesTyped commands and short pipeline completionDaily terminal practice with text filters and vi
Devices, Linux Filesystems, FHSStorage, permissions, and layout reasoningInterpret a mode, fstab line, or directory purposeCreate, mount, and permission a scratch disk image

Sequencing the Domains in Your Study Plan

You do not need an elaborate method here, just a sensible order. Domain 3 deserves the most hands-on hours because its skills transfer to everything else, so start it early and keep touching it throughout. A four-week arrangement built around the domains themselves works well for most candidates with some Linux exposure.

Week 1

GNU and Unix Commands, part one

  • Shell environment, streams, redirection, and text filters
  • Start a daily terminal habit you will keep for the whole plan
Week 2

GNU and Unix Commands, part two plus Package Management

  • Regular expressions, sed, process control, and vi
  • Debian and RPM tooling, paired side by side
Week 3

Devices, Filesystems, and FHS

  • Partition, format, mount, and permission a loopback disk image
  • Drill octal modes, special bits, and the FHS directory roles
Week 4

System Architecture and full review

  • Boot sequence, targets, kernel modules, and hardware inspection
  • Timed mixed practice under the 90-minute limit

For a longer treatment of pacing and resources, the LPIC-1 101-500 study guide expands on this approach, and the difficulty guide helps you judge how much preparation time your background calls for. When you are ready to test recall under pressure, our LPIC-1 101-500 practice tests let you rehearse the question styles described above. Note that independently authored practice material is not actual LPI exam content and should not be treated as an official simulation.

What Passing This Paper Does and Does Not Give You

Passing 101-500 does not award the LPIC-1 certification by itself. You must also pass the companion 102-500 paper, and only the pair earns the credential. Certification validity is five years, though you should confirm LPI's current renewal or extension policy before planning around it. Because a current official passing score and pass rate were not verified for this article, treat any specific figure you see elsewhere with caution and check LPI directly; the passing score article and pass rate analysis explain how to evaluate such claims.

The skills in these four areas are the daily vocabulary of Linux support, junior system administration, and operations roles, which is why employers who run Linux fleets recognize the credential. If you are weighing the investment, the worth-it analysis and the jobs overview are good next reads. You can also explore the broader LPIC-1 101-500 Exam Prep home page for practice resources organized around these same four content areas.

Frequently Asked Questions

How many content areas are on LPIC-1 Exam 101 (101-500)?

There are four: System Architecture; Linux Installation and Package Management; GNU and Unix Commands; and Devices, Linux Filesystems, Filesystem Hierarchy Standard. Each contains several individually weighted objectives published by LPI.

Does each domain have a fixed percentage of the exam?

No aggregate domain percentages are published. LPI assigns weights to individual objectives rather than to whole domains, so check the per-objective weights on LPI's official objectives page when prioritizing your study time.

What is the format and length of the 101-500 paper?

The paper has 60 questions, a mix of multiple-choice and fill-in-the-blank, with a 90-minute time limit. Fill-in-the-blank items require you to type exact commands, options, or paths from memory.

Does passing 101-500 earn me the LPIC-1 certification?

No. You must pass both the 101-500 and 102-500 papers to earn LPIC-1. Passing this single paper alone does not award the credential, though there are no prerequisites to sit either exam.

Which domain should I spend the most time on?

Most candidates benefit from heavy hands-on time in GNU and Unix Commands because shell fluency supports every other area. Still, use LPI's per-objective weights and your own weak spots to decide, rather than a fixed domain ratio.

Ready to pass your LPIC-1 101-500 exam?

Put this into practice with free LPIC-1 101-500 questions across every exam domain.