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

LPIC-1 101-500 Cheat Sheet 2026: One-Page Review of Must-Know Facts

TL;DR
  • Exam 101-500 has 60 multiple-choice and fill-in-the-blank questions in a 90-minute limit.
  • Passing 101-500 alone does not award LPIC-1; you must also pass 102-500.
  • The four Exam 101 content areas are System Architecture, Installation and Package Management, GNU and Unix Commands, and Devices/Filesystems/FHS.
  • Fill-in-the-blank items mean you must recall exact command names and options, not just recognize them.

The Exam at a Glance

This page condenses what you need to have loaded in your head on exam day for LPIC-1 Exam 101 (LPIC-1: Linux Administrator, version 5.0), exam code 101-500, issued by the Linux Professional Institute (LPI). It is a review sheet, not a replacement for hands-on practice. If you are still building your plan, start with the LPIC-1 101-500 study guide and come back here for the final pass.

ItemWhat to remember
IssuerLinux Professional Institute (LPI)
ExamLPIC-1 Exam 101, version 5.0, code 101-500
Format60 questions, multiple-choice and fill-in-the-blank
Time limit90 minutes
PrerequisitesNone for LPIC-1 certification
Credential rulePass both 101-500 and 102-500 to earn LPIC-1
Validity5 years (check LPI's current renewal/extension policy)
Fees, delivery, passing scoreVerify with LPI/Pearson VUE; not asserted here

Ninety minutes for 60 questions works out to roughly 90 seconds each. That is generous for single-fact recall and tight for items that ask you to parse a command pipeline or a config excerpt, so bank time on the easy ones.

Domain 1: System Architecture Essentials

This domain tests whether you understand what happens between power-on and a login prompt, and how Linux sees hardware. For a deeper breakdown of all four areas, see the complete guide to the LPIC-1 101-500 content areas.

Hardware and Kernel Visibility

Know where Linux exposes hardware information and how to inspect it.

  • /proc holds runtime kernel and process data (for example /proc/cpuinfo, /proc/interrupts, /proc/ioports, /proc/dma).
  • /sys exposes the device model; /dev holds device nodes.
  • lspci, lsusb, and lsmod list PCI devices, USB devices, and loaded modules.
  • udev creates device nodes dynamically; know that udevadm is the management tool.
  • Kernel modules: modprobe resolves dependencies, insmod and rmmod do not.

Boot Process and Init Systems

Expect questions on the sequence firmware, bootloader, kernel, init.

  • BIOS versus UEFI, and the role of the EFI system partition.
  • Bootloader (GRUB) loads the kernel and an initial RAM filesystem.
  • dmesg and journalctl are where you inspect boot messages.
  • systemd targets replace classic runlevels; know systemctl get-default, systemctl set-default, and systemctl isolate.
  • Be able to map legacy SysV runlevels to systemd targets (poweroff, rescue, multi-user, graphical, reboot).

Shutdown and Runlevel Control

Know the commands that change system state and their effect.

  • shutdown, halt, poweroff, and reboot, plus systemctl equivalents.
  • Sending warning messages to logged-in users with shutdown.
  • Switching to rescue or emergency targets for repair.

Domain 2: Installation and Package Management Essentials

This domain rewards candidates who have actually installed software on both Debian-family and Red Hat-family systems. The exam expects you to be bilingual across package managers.

Disk layout and boot loader

  • Design a partitioning scheme: / (root), /boot, /home, /var, swap, and the EFI system partition on UEFI systems.
  • Understand LVM at a conceptual level: physical volumes, volume groups, logical volumes.
  • Know that swap can be a partition or a file, and that it needs initializing and activating.
  • Know how GRUB is installed and configured, and how to reach a GRUB prompt to boot manually.

Shared libraries

  • ldd shows a binary's shared library dependencies.
  • ldconfig rebuilds the library cache.
  • Library search locations are controlled by /etc/ld.so.conf and the LD_LIBRARY_PATH variable.

Debian package tools

  • dpkg works on individual .deb files (-i install, -r remove, -P purge, -l list, -L list files, -S find owning package).
  • apt-get, apt, and apt-cache handle repositories and dependencies; know update versus upgrade.
  • Repository sources live in /etc/apt/sources.list and /etc/apt/sources.list.d/.

RPM tools

  • rpm works on individual packages (-i, -U, -F, -e, -q, -qa, -qi, -ql, -qf, -V).
  • yum, dnf, and zypper resolve dependencies from repositories.
  • Know how to extract files from an RPM without installing it using rpm2cpio piped to cpio.
Query direction matters: "Which package owns this file?" is dpkg -S on Debian and rpm -qf on RPM systems. "Which files does this package contain?" is dpkg -L and rpm -ql. Candidates routinely swap these under time pressure.

Virtualization concepts

Know the difference between a virtual machine and a container at a conceptual level, and recognize terms such as hypervisor, guest, and cloud-init style provisioning. This is recognition-level material rather than deep configuration.

Domain 3: GNU and Unix Commands Essentials

This is the practical heart of Exam 101 and the area where hands-on shell time pays off most. Because some items are fill-in-the-blank, you need command names and flags available from memory.

Shell Basics and Environment

  • Variables: export, env, set, unset, and the difference between shell and environment variables.
  • Command lookup: type, which, whereis, and how PATH is searched.
  • Quoting rules: single quotes preserve literally, double quotes allow variable expansion, backslash escapes one character.
  • Command history, aliases, and startup files (/etc/profile, ~/.bash_profile, ~/.bashrc, ~/.profile) with login versus non-login behavior.

Text Processing

  • cat, head, tail (including -f), less, wc, nl, od.
  • cut, paste, join, sort, uniq, tr, split, fmt, pr.
  • sed for stream substitution and grep/egrep for pattern matching.
  • Checksums and hashes: md5sum, sha256sum, sha512sum.
  • Compression viewers: zcat, bzcat, xzcat.

Streams, Pipes, and Redirection

  • File descriptors: 0 stdin, 1 stdout, 2 stderr.
  • > overwrites, >> appends, 2> redirects errors, 2>&1 merges them.
  • tee writes to a file and passes data along the pipe; xargs builds command lines from input.
  • Command substitution with $( ) and backticks.

Files, Archives, and Searching

  • ls, cp, mv, rm, mkdir, touch, file, plus globbing with *, ?, and [ ].
  • tar create/extract/list flags with gzip, bzip2, and xz options; cpio and dd for archiving and raw copies.
  • find with -name, -type, -size, -mtime, -perm, -user, and -exec; know that locate uses a prebuilt database refreshed by updatedb.

Processes and the vi Editor

  • Jobs: &, jobs, fg, bg, nohup; monitoring with ps, top, free, uptime.
  • Signals with kill, killall, and pkill; priority with nice and renice; screen or tmux for persistent sessions.
  • vi navigation, insert, delete, yank, put, search, and save/quit commands.

Key Takeaway

For every command above, be able to write it from a blank answer field, not just choose it from a list. Practice typing find-with-exec, tar extraction, and sed substitution commands until the flag order is automatic.

Domain 4: Devices, Filesystems, and the FHS

This domain blends storage administration with security-relevant permission handling and the Filesystem Hierarchy Standard.

Creating and maintaining filesystems

  • Partition tools: fdisk (MBR), gdisk (GPT), and parted.
  • Create filesystems with mkfs, mkfs.ext4, mkfs.xfs, mkfs.vfat; create swap with mkswap and activate it with swapon.
  • Check and repair: fsck and e2fsck for ext, xfs_repair for XFS; inspect with tune2fs, dumpe2fs, xfs_info.
  • Report usage with df and du; know the difference between them.

Mounting

  • Manual mount and umount, with options such as ro, rw, noexec, nosuid, and remount.
  • /etc/fstab fields in order: device, mount point, type, options, dump, fsck pass.
  • Identify devices by UUID or label using blkid and lsblk.
  • Systemd mount units exist alongside fstab; recognize them.

Permissions and ownership

  • Symbolic and octal chmod; chown and chgrp; default permissions via umask (subtract the mask from 666 for files and 777 for directories).
  • Special bits: setuid (4), setgid (2), sticky (1) and how they display in ls -l output.
  • Directory permissions differ from file permissions: execute on a directory means you can traverse it.

Links and file location

  • Hard links share an inode and cannot cross filesystems; symbolic links are separate files pointing at a path.
  • Create both with ln (add -s for symbolic).
  • FHS purpose of key directories: /bin, /sbin, /usr, /usr/local, /etc, /var, /tmp, /opt, /home, /boot, /dev, /proc, /sys, /run, /media, and /mnt.
  • Searching tools: find, locate, which, whereis, type.
FHS shortcut: Variable data (logs, spools, caches) belongs in /var, static configuration in /etc, locally installed software in /usr/local or /opt, and temporary files in /tmp. When a question asks "where should this live," ask first whether it changes at runtime.

How the Questions Behave

Exam 101 mixes multiple-choice items with fill-in-the-blank items, which is a meaningful difference from purely recognition-based exams. A few patterns to expect:

  • Multiple-choice with one correct answer: distractors are usually real commands with the wrong flag or the wrong tool for the job.
  • Multiple-choice with several correct answers: read the instruction carefully for how many to select.
  • Fill-in-the-blank: you type a command, option, path, or filename. Spelling and exact syntax matter, so practice writing rather than reading.
  • Scenario fragments: a short config excerpt or command output followed by "what does this do" or "what is wrong."

For a candid look at where candidates struggle, read how hard the LPIC-1 101-500 exam really is. Independently authored practice material, including what you will find on our practice test site, is study support and should never be treated as actual issuer questions or an official exam simulation.

A Domain-Ordered Revision Plan

Generic scheduling advice is everywhere; what matters here is ordering by dependency. Commands underpin almost everything else, so give them the most hands-on time.

Week 1

System Architecture

  • Read hardware via /proc, /sys, lspci, lsusb, lsmod.
  • Trace a boot from firmware to systemd target and practice systemctl target commands.
Week 2

Installation and Package Management

  • Install, query, and remove software with both dpkg/apt and rpm/dnf.
  • Drill the "which package owns this file" query on both families.
Weeks 3-4

GNU and Unix Commands

  • Build pipelines daily using cut, sort, uniq, tr, sed, and grep.
  • Practice find with -exec, tar archives, redirection, and vi until fluent.
Week 5

Devices, Filesystems, FHS

  • Partition and format a scratch disk image, mount it, and edit fstab.
  • Work through permission and umask arithmetic by hand.

Finish with timed mixed sets to rehearse the 90-minute pace. The training options overview can help if you prefer a structured course alongside self-study.

High-Frequency Confusion Pairs

PairDistinction
modprobe vs insmodmodprobe resolves dependencies; insmod loads a single module file
dpkg vs aptdpkg handles local .deb files; apt resolves repositories and dependencies
rpm vs dnf/yumrpm works on local packages; dnf/yum fetch and resolve dependencies
> vs >>Overwrite versus append
df vs duFilesystem free space versus space used by files and directories
hard link vs symlinkSame inode, same filesystem only, versus path pointer that can cross filesystems
locate vs findDatabase lookup (needs updatedb) versus live filesystem walk
kill vs killall vs pkillBy PID, by exact process name, by pattern
fdisk vs gdiskMBR-oriented versus GPT-oriented partitioning

Credential Mechanics You Should Not Guess

A few facts are deliberately left for you to verify at the source, because they change and guessing wrong costs money or time:

  • Fees and delivery: confirm current pricing and regional delivery options with LPI and Pearson VUE. Our certification cost breakdown explains what to budget for, but the official figure is the one that counts.
  • Passing score: a current official value was not verified for this sheet, so check LPI directly. See the passing score article for context on how to interpret it.
  • Scheduling: testing windows and availability are covered in the exam dates guide.
  • Prerequisites: there are none for LPIC-1, as detailed in the requirements overview.
  • Renewal: certification is valid for 5 years; check LPI's current renewal or extension policy.
Two exams, one credential: Passing 101-500 is a milestone, not the finish line. LPIC-1 is awarded only after you also pass 102-500. Plan your second attempt window before the first exam result changes your motivation.

If you are weighing whether the effort pays off, the ROI analysis and the jobs overview cover who values a Linux administrator credential.

Frequently Asked Questions

How many questions are on LPIC-1 Exam 101-500, and how long do I have?

The paper has 60 multiple-choice and fill-in-the-blank questions with a 90-minute time limit.

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

No. You must pass both 101-500 and 102-500 to earn LPIC-1. Passing this paper alone does not award the credential.

What are the four areas covered by Exam 101-500?

System Architecture; Linux Installation and Package Management; GNU and Unix Commands; and Devices, Linux Filesystems, and the Filesystem Hierarchy Standard. LPI weights individual objectives rather than publishing aggregate domain percentages.

Are there prerequisites for taking the exam?

There are no LPIC-1 certification prerequisites. Practical Linux command-line experience is still the best preparation for the command and filesystem material.

How long is the certification valid?

Validity is 5 years. Because renewal and extension rules can change, check LPI's current policy before planning your recertification.

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

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