101-500
LPIC-1 Exam 101, Part 1 of 2, version 5.0
LPIC-1 Exam 101 Guide: Part 1 of 2, Version 5.0
LPIC-1 Exam 101, identified by LPI as exam code 101-500, validates the command-line, installation, package-management, system-architecture, and filesystem knowledge expected of a junior Linux administrator. It is the first of two exams required for LPIC-1 certification and has no prerequisite. This guide helps you decide whether your current experience is ready for 101-500, which objectives deserve the most study time, whether online or test-center delivery fits your situation, and how to turn the official blueprint into a practical preparation plan.
What LPIC-1 Exam 101 validates
Exam 101 tests whether you can understand a Linux system, install and maintain core components, use GNU and Unix commands, and manage devices and filesystems. LPI describes LPIC-1 as a certification for command-line maintenance, Linux installation and configuration, and basic networking, although the networking objectives themselves belong mainly to Exam 102.
The certification is designed around real-world system-administration job skills. That does not mean the exam is a live administration exercise; it means your preparation should connect commands with the system state they change. Learn why a command is used, what evidence confirms success, and what failure looks like.
Exam 101 is Part 1 of 2, not the complete LPIC-1 credential. LPI requires passing both Exam 101 and Exam 102. There are no prerequisites for the LPIC-1 certification, so a candidate may begin with 101-500 without holding another LPI certification or a stated prior qualification.
The current LPIC-1 version is 5.0, with exam codes 101-500 and 102-500. Confirm the code when selecting study material or purchasing a voucher; resources labelled only for an earlier objectives version may omit or overemphasize topics that changed.
Who should choose Exam 101 first
Exam 101 is a sensible starting point for candidates who routinely use a Linux shell and want to formalize foundational administration skills. It also suits learners building toward LPIC-1 from general IT experience, provided they are prepared to practise commands rather than rely on desktop-only Linux familiarity.
You are closer to readiness if you can work in a terminal without copying every command, explain the difference between a process and a shell job, inspect hardware and boot information, install packages from more than one package family, and mount a filesystem while preserving the system’s configuration.
Candidates coming from Debian-based systems should deliberately add RPM, YUM, Zypper, and related package concepts. Candidates coming from Red Hat-based systems should do the reverse with Debian package tools. Exam 101 is distribution-neutral in its objectives, so comfort with only one package ecosystem leaves a specific gap.
Do not treat the absence of prerequisites as evidence that the exam is introductory in every area. The objectives span booting, shared libraries, regular expressions, filesystem repair, permissions, links, and partitioning. If these subjects are unfamiliar, schedule lab time before choosing an exam appointment.
How the Exam 101 blueprint is organized
Use the four official domains as your study map: System Architecture; Linux Installation and Package Management; GNU and Unix Commands; and Devices, Linux Filesystems, and the Filesystem Hierarchy Standard. The objectives page lists each topic and objective, its weight, description, and a partial list of relevant files, terms, and utilities.
The System Architecture domain covers objective 101.1, determining and configuring hardware settings, with weight 2; objective 101.2, booting the system, with weight 3; and objective 101.3, changing runlevels or boot targets and shutting down or rebooting, with weight 3. Study the relationship between hardware discovery, boot stages, and service targets rather than memorizing isolated utilities.
The Linux Installation and Package Management domain includes disk layout, boot managers, shared libraries, Debian package management, RPM and YUM package management, and Linux as a virtualization guest. The stated weights are 2 for 102.1, 2 for 102.2, 1 for 102.3, 3 for 102.4, 3 for 102.5, and 1 for 102.6.
The GNU and Unix Commands domain contains command-line work, filters, file management, streams and redirection, process management, process priorities, regular expressions, and basic file editing. Its objective weights are 2 for 103.1, 2 for 103.2, 4 for 103.3, 4 for 103.4, 4 for 103.5, 2 for 103.6, 3 for 103.7, and 3 for 103.8.
The Devices, Linux Filesystems, and the Filesystem Hierarchy Standard domain covers partitions and filesystems, filesystem integrity, mounting, permissions and ownership, hard and symbolic links, and file locations. The listed weights are 2 for 104.1, 2 for 104.2, 3 for 104.3, 3 for 104.5, 2 for 104.6, and 2 for 104.7. Objective 104.4 was removed in version 5.0.
LPI says higher-weighted objectives receive more questions. Use weights to allocate revision time, but do not skip a lower-weighted objective: a weight of 1 still identifies examinable knowledge. Keep each weight attached to its domain and objective in your notes so that you do not turn the blueprint into unsupported percentage estimates.
What changed in version 5.0
Version 5.0 added or revised several Exam 101 areas, so an older study plan needs an explicit gap check. The most consequential updates include UEFI and journalctl coverage in booting, the EFI System Partition in disk layout, Zypper and awareness of dnf in package management, and a new objective for Linux as a virtualization guest.
The version-change summary also identifies changes in command-line coverage. Quoting, type, and which were added to 103.1; compressed-stream and checksum utilities were added to 103.2; and watch and tmux were added to 103.5. Regular-expression coverage expanded, while its objective weight increased from 2 to 3.
Filesystem preparation also changed. Version 5.0 added GPT partition tables and exFAT, clarified basic Btrfs features, and added labels and UUIDs, blkid, lsblk, and systemd mount-unit awareness to mounting. Disk quotas were removed as objective 104.4.
Start your version check by opening LPI’s current objectives and then its version 4.0-to-5.0 summary. Mark every added, removed, and changed item in your notes. This is more reliable than assuming that a book’s title or publication date proves full alignment with 101-500.
Which commands and concepts deserve hands-on practice
A small Linux lab is more useful than passive reading for Exam 101. Use a disposable virtual machine or another system you can safely modify, and record the command, expected result, and recovery step for each exercise. The objective lists are the authority for scope; the lab is the method for turning that scope into recall and judgment.
For hardware and boot work, practise identifying information under /sys, /proc, and /dev; use lsmod, modprobe, lspci, and lsusb; and inspect boot messages with dmesg and journalctl. Learn the distinction between BIOS and UEFI, including the role of the EFI System Partition, and connect systemd targets with shutdown and reboot operations.
For package management, create a comparison sheet rather than one long command list. Include package search, installation, removal, upgrade, file ownership, dependency information, integrity, and installation status. The objectives cover Debian tools such as dpkg, dpkg-reconfigure, apt-get, and apt-cache, as well as rpm, YUM, and Zypper tools.
For commands, build short tasks that combine operations: locate files, transform text, archive data, redirect output, filter results, and inspect processes. Practise cp, find, mkdir, mv, ls, rm, tar, cpio, dd, file, gzip, bzip2, and xz. Then add tee, xargs, ps, top, pgrep, pkill, killall, watch, and tmux where appropriate.
For filesystems, practise partition inspection, filesystem creation in a disposable device, integrity checks, mounting by device, label, and UUID, and safe unmounting. Use fdisk, gdisk, parted, mkfs, mkswap, blkid, lsblk, mount, and umount only when you understand which device is being changed. Never experiment with a production disk.
For permissions and links, create files owned by different users, vary read, write, and execute permissions, apply umask, and compare hard and symbolic links after moving or deleting the target. For file placement, map common locations to the Filesystem Hierarchy Standard instead of memorizing directory names without purpose.
How to study the GNU and Unix command objectives
Treat command-line fluency as a connected skill: interpret the shell, select a command, control its input and output, and verify the result. Exam questions can test distinctions that disappear when you memorise a single successful example, so practise explaining what happens to standard input, standard output, standard error, exit status, quoting, globbing, and expansion.
Begin with 103.1 and 103.4 because shell interpretation and redirection support the rest of the command work. Use man, info, help, history, type, which, and uname to investigate a command. Then deliberately test quoted and unquoted variables, wildcard expansion, command substitution, and pipelines in a safe directory.
Next, work through file management and text processing. Combine head, tail, cut, paste, sort, uniq, tr, wc, sed, and the compression readers listed in the objectives. Do not just copy a pipeline: write down the input format, the transformation performed by each stage, and the final stream.
Give regular expressions a separate revision pass. Know the difference between basic and extended regular expressions, along with special characters, character classes, quantifiers, and anchors. Practise searching and changing text with grep, egrep, fgrep, and sed. A common mistake is confusing a shell wildcard with a regular-expression pattern.
Process questions require both observation and control. Use ps, top, free, uptime, pgrep, jobs, bg, fg, kill, nohup, and the relevant process-control tools. Then practise nice and renice for priorities. Keep foreground jobs, background jobs, process IDs, signals, and priority values as separate concepts in your notes.
For editing, become comfortable with vi modes and the basic editing actions within the objective scope. Also recognise the role of Emacs, nano, and vim and understand how the EDITOR environment variable affects a default editor. Reading about vi is not enough; make small edits repeatedly until mode changes are deliberate.
How to prepare for installation, packages, and storage
Study installation topics as a sequence: choose a disk layout, install a boot manager, understand libraries, install and inspect packages, then account for virtualization. This sequence gives each tool a system context. It also exposes the boundary between package management, shared-library resolution, boot configuration, and filesystem administration.
For disk layout, explain the purpose of root, /var, /home, and /boot filesystems, swap space, mount points, partitions, and the EFI System Partition. Compare partition-table concepts without assuming that every Linux installation uses the same firmware mode. The objective asks for design knowledge, not a memorized partition recipe.
For boot managers, learn what grub-install and grub-mkconfig do and how grub.cfg, grub.conf, menu.lst, the MBR, and UEFI-related components fit into the boot process. Practise recovery reasoning in a disposable machine: identify whether the problem is firmware selection, boot-manager configuration, kernel loading, or userspace startup.
For shared libraries, use ldd and ldconfig, and understand /etc/ld.so.conf and LD_LIBRARY_PATH. Your goal is to determine what an executable depends on and how a missing library can be made available. Do not treat LD_LIBRARY_PATH as a universal repair; first establish which library is missing and why.
Compare Debian package management with RPM-based management by asking the same questions in each ecosystem: What package provides this file? What version is installed? What are its dependencies? Is the package installed and intact? The official objectives specifically include package version, content, dependencies, integrity, installation status, and RPM signatures.
The virtualization-guest objective has weight 1 in the Linux Installation and Package Management domain. Learn the implications of running Linux in virtual machines and containers on premise or in the cloud, including the difference between the guest’s operating environment and the underlying host. Do not spend disproportionate time on product-specific administration that the objective does not require.
How to prepare for filesystems and permissions
Filesystem questions become easier when you follow the lifecycle of data: partition a device, create a filesystem, check or repair it, mount it, expose it at the right location, and protect access. Practise this lifecycle with disposable storage and keep a written recovery procedure; a destructive command remembered without context is a preparation liability.
Learn the purpose and broad characteristics of standard filesystems in the objective scope, including ext-family filesystems, XFS, Btrfs, and exFAT. Know the tools named by LPI, including fsck, e2fsck, mke2fs, tune2fs, xfs_repair, xfs_fsr, and xfs_db. The required skill is selecting an appropriate tool and interpreting its role.
Mounting requires more than knowing mount and umount. Use /etc/fstab, mount points, labels, UUIDs, blkid, and lsblk to reason about persistent configuration. Include awareness of systemd mount units. Before changing fstab, validate the device identity and keep a recovery path; a typo can prevent a system from reaching its normal boot state.
For permissions, translate symbolic modes into owner, group, and other access, then account for directory execute permission, ownership changes, and umask. Practise chmod, chown, and chgrp with multiple users. Test access as the affected user rather than assuming that the mode string alone proves the outcome.
Hard and symbolic links answer different administration needs. Create both with ln and ln -s, inspect them with ls, and test what happens when the target is renamed or removed. Then connect links to inode and pathname concepts. This prevents the common mistake of describing a symbolic link as a second directory entry for the same inode.
Build a filesystem-hierarchy reference from actual files on your lab system. Include the root filesystem and common locations such as /etc, /var, /home, /boot, /dev, /proc, /sys, and /usr. The point is to place configuration, variable data, user data, device interfaces, and kernel interfaces correctly, not to memorise arbitrary paths.
A practical study roadmap for 101-500
A staged roadmap works better than reading every objective once. First establish command-line and filesystem safety, then add system architecture and packages, and finally test integrated troubleshooting. Adjust the pace to your experience; the sequence is a practical recommendation, not an LPI requirement or a prediction of your exam result.
Stage one is a baseline assessment. Read every 101-500 objective and mark each as confident, familiar, or unknown. For each unknown item, write one task you cannot yet perform. Check the version number and remove notes for Exam 102 topics that do not belong in this first exam.
Stage two builds command-line control. Work through shell interpretation, filters, file management, pipes, redirection, processes, priorities, regular expressions, and vi. After each lab, close your notes and reproduce the task from a short scenario. Record errors and their causes; error analysis is more valuable than simply repeating a successful command.
Stage three covers storage and boot. In a disposable environment, inspect hardware, trace the boot process, compare BIOS and UEFI concepts, examine targets, design a disk layout, and use GRUB-related tools conceptually. Practise mounting and unmounting, filesystem checks, permissions, links, and FHS placement without touching production data.
Stage four compares package ecosystems and libraries. Use the official objective lists to create a Debian versus RPM/YUM/Zypper matrix. Add shared-library discovery and the virtualization-guest concepts. The decision to spend extra time here should come from your baseline: a Debian-only administrator should not assume package-management transfer is automatic.
Stage five is integration and review. Start with a symptom such as a missing command, unavailable device, failed mount, incorrect permission, missing library, or process consuming resources. State the evidence you would collect, the least risky command to run, and how you would verify the fix. Keep the exercise within the published objective scope.
Stage six is readiness review. Revisit every objective marked unknown, explain each high-weight objective without notes, and use practice questions only to identify gaps. Avoid materials that claim to reproduce live exam questions. Memorisation of leaked or copied content is not a substitute for understanding and may expose you to unreliable or improper material.
How to decide between test center and online delivery
LPI offers LPIC-1 Exam 101 through Pearson VUE test centers and through the OnVUE online-testing system. Choose based on your equipment, language, privacy, and environment rather than convenience alone. Confirm current appointment rules and system requirements with LPI and Pearson VUE before scheduling because delivery conditions can change.
LPI lists each LPIC-1 exam as 90 minutes with 60 multiple-choice and fill-in-the-blank questions. Use that information to practise concise reading and answer review, but do not turn it into an unsupported timing formula for individual questions. Build familiarity with both selected-response and fill-in responses during revision.
At Pearson VUE test centers, LPI lists English, German, Japanese, Brazilian Portuguese, Simplified Chinese, Traditional Chinese, and Modern Spanish for LPIC-1 exams. For OnVUE delivery, LPI lists English, German, Japanese, Brazilian Portuguese, and Spanish. Check the booking interface for the option actually available to you.
Online OnVUE delivery uses webcam monitoring by a verified Pearson VUE proctor, and LPI says candidates take the exam at home or in an office. Candidates are expected to have a quiet, private location, a reliable computer with a camera, and a stable Internet connection.
LPI states that the OnVUE proctoring platform is available in English language only and currently supports Windows and macOS. That platform limitation is separate from the language options listed for LPIC-1 online exams. If your intended workstation runs Linux, do not assume it is supported; verify the current Pearson VUE requirements before paying or scheduling.
LPI says exam prices and lengths remain the same on OnVUE as in test centers, while its pricing page directs candidates to select their country or territory for pricing. Treat the country-specific pricing page as the authority for your location rather than relying on an old voucher listing or a third-party estimate.
What to verify before booking
Book only after the exam code, objectives version, delivery method, language, and local price are confirmed on official pages. Exam 101 version 5.0 is 101-500. The LPIC-1 credential additionally requires Exam 102, so make sure a booking for 101 is not being mistaken for completion of the certification.
Check the official objectives page against your study notes one final time. Confirm that your plan includes UEFI, journalctl boot events, the EFI System Partition, Zypper, dnf awareness, virtualization guests, GPT, exFAT, Btrfs features, labels and UUIDs, and the revised regular-expression coverage.
If you choose online delivery, run the official system check on the intended Windows or macOS computer, confirm camera and network reliability, and reserve a private space. If those conditions are uncertain, compare them with the requirements of a Pearson VUE test center before selecting an appointment.
Do not schedule solely because you have completed a book or a video course. Schedule when you can explain the objective areas, perform the core lab tasks safely, and distinguish similar tools and concepts. If one domain remains weak, postpone and use the blueprint weight to prioritize targeted practice rather than restarting the entire course.
Common preparation mistakes to avoid
The most damaging mistake is studying a broad Linux curriculum without mapping it to 101-500. Keep the official objective list beside your notes, label material as Exam 101 or Exam 102, and stop expanding into unrelated administration topics until every listed Exam 101 objective has evidence of practice.
Another mistake is learning commands as synonyms. apt-get, dpkg, rpm, YUM, and Zypper do not form one interchangeable command set; mount and fstab have different roles; hard and symbolic links behave differently; and a shell job is not the same thing as a process. Compare tools by purpose, input, output, and side effects.
Avoid lab work that is unsafe by design. Never test partitioning, filesystem creation, repair, boot-manager installation, or fstab changes on a production system. Use a disposable virtual machine or storage device, take appropriate snapshots or backups, and document how to undo the change.
Do not ignore low-weight objectives or over-focus on the command names shown in a partial utility list. The description and key knowledge areas define the skill, while the utility list helps identify vocabulary. Be ready to interpret a scenario and select an approach, not just recognise a command spelling.
Finally, do not use exam dumps or leaked questions. They are unreliable, do not establish command-line competence, and cannot guarantee a pass. Use legitimate objectives, official learning materials, controlled labs, and practice questions that test your understanding without claiming access to live exam content.
Your next actions
Start with the official 101-500 objectives, create a four-domain checklist, and mark your current confidence for every objective. Then open the LPI Learning Materials for Exam 101 and begin with the first weak objective rather than following an unexamined generic course sequence.
Within your first study session, create a safe lab, practise hardware inspection, and capture the output of lsusb, lspci, lsmod, and relevant system-information tools. In the next sessions, connect command-line work to file and process tasks, then build toward package, boot, mounting, permissions, and filesystem exercises.
After the first pass, use the version-change summary as an audit document. Add missing version-5.0 subjects to your checklist, remove obsolete 104.4 disk-quota study, and revisit 103.7 regular expressions because its coverage expanded and its weight changed.
When your checklist shows repeatable performance rather than recognition, verify the official delivery, language, system, and country-specific pricing information and choose the appointment format that you can support reliably. Keep Exam 102 as a separate planning decision; first make the 101-500 scope precise and manageable.
Conclusion
LPIC-1 Exam 101 is best approached as a command-line and Linux-foundations assessment with four clearly defined domains. The official objectives should control what you study, while a disposable lab should control how you learn it. Confirm version 5.0 coverage, prioritise higher-weight objectives without dropping smaller ones, and verify delivery conditions before booking. Passing 101-500 is an important step toward LPIC-1, but the full certification still requires Exam 102.
Related exams
- 102-500 exam — LPIC-1 Exam 102, Part 2 of 2, version 5.0
- 010-160 exam — Linux Essentials Certificate Exam - version 1.6