LPIC-1 Exam 101 Version 5.0: Practical Preparation Guide
LPIC-1 Exam 101, code 101-500, validates the first half of LPI’s Linux administration certification: hardware and boot concepts, installation and package management, command-line work, and filesystems. It suits candidates building or demonstrating practical Linux maintenance skills, whether they are new administrators or experienced users formalizing their knowledge. This guide helps you decide whether Exam 101 is the right next step, which objectives deserve the most study time, how to practise safely, and whether a Pearson VUE test center or OnVUE delivery fits your situation.
What Exam 101 validates
Exam 101 tests the foundation needed to operate and maintain a Linux system. Its scope is practical rather than tied to one distribution: candidates work across system architecture, installation and package management, GNU and Unix commands, and devices, Linux filesystems, and the Filesystem Hierarchy Standard.
LPI describes LPIC-1 as validating command-line maintenance, Linux installation and configuration, and basic networking. Exam 101 covers the command-line and system foundations; networking, security, administrative tasks, shells and desktops are primarily represented in Exam 102. Treating 101 as the complete LPIC-1 syllabus is a common planning mistake.
LPIC-1 certification requires passing both Exam 101 and Exam 102. There are no prerequisites for the certification, so a candidate can begin with Exam 101 without holding another LPI credential. The certification’s listed validity period is 5 years, with LPI directing candidates to its renewal information for options beyond that period.
Who should take this part first
Exam 101 is a sensible first exam for someone who can use a Linux shell but needs a structured test of system internals, package tools, storage, permissions, and troubleshooting commands. It is also appropriate for an administrator who works mainly with one distribution and needs broader vendor-neutral coverage before attempting the second LPIC-1 exam.
Choose Exam 101 now if you can already create files, inspect processes, read manual pages, and work in a disposable Linux installation without relying on graphical tools. If those actions are unfamiliar, start with basic Linux practice first; reading objective names alone will not substitute for command-line fluency.
Experienced users should not skip the objective list. Daily work can hide gaps: a Debian administrator may rarely use RPM, a desktop user may not understand boot loaders, and a cloud user may have little experience with partitions or filesystem repair. Use the objectives as a gap analysis rather than assuming workplace familiarity equals exam coverage.
How the version 5.0 blueprint is organized
The official Exam 101 blueprint contains four topic areas: Topic 101 System Architecture, Topic 102 Linux Installation and Package Management, Topic 103 GNU and Unix Commands, and Topic 104 Devices, Linux Filesystems, Filesystem Hierarchy Standard. Study by objective number, not by a loosely selected list of Linux commands.
Topic 101 begins with 101.1 Determine and configure hardware settings, which has weight 2, then covers booting and changing runlevels or boot targets, shutting down, and rebooting. The learning materials identify tools and concepts including /sys/, /proc/, /dev, modprobe, lsmod, lspci, and lsusb.
Topic 102 includes disk layout, boot managers, shared libraries, Debian package management, RPM and YUM package management, and Linux as a virtualization guest. Objective 102.5 Use RPM and YUM package management has weight 3; objective 102.3 Manage shared libraries has weight 1; objective 102.6 Linux as a virtualization guest has weight 1.
Topic 103 is the command-line core. Objective 103.3 Perform basic file management has weight 4, objective 103.4 Use streams, pipes and redirects has weight 4, objective 103.5 Create, monitor and kill processes has weight 4, objective 103.7 Search text files using regular expressions has weight 3, and objective 103.8 Basic file editing has weight 3. Objective 103.2 Process text streams using filters has weight 2.
Topic 104 connects storage operations with file access. Objective 104.3 Control mounting and unmounting of filesystems has weight 3, while objective 104.5 Manage file permissions and ownership has weight 3. Objective 104.1 Create partitions and filesystems and objective 104.2 Maintain the integrity of filesystems each have weight 2; objective 104.6 Create and change hard and symbolic links has weight 2; objective 104.7 Find system files and place files in the correct location has weight 2.
LPI says that higher-weighted objectives receive more questions. That makes weights useful for allocating revision time, but they are not a reason to ignore a weight 1 objective. A short objective can still expose a terminology gap, and the official page remains the authority for the complete list and current wording.
What changed from version 4.0 to version 5.0
Version 5.0 adds or refocuses several areas that should influence your lab plan. The most important changes for Exam 101 include UEFI and journalctl in boot coverage, the EFI System Partition in disk layout, a new virtualization-guest objective, Zypper and awareness of dnf, expanded regular-expression knowledge, and modern filesystem identification with labels and UUIDs.
For 101.2 Boot the system, practise both BIOS and UEFI concepts and use journalctl when investigating boot events. For 102.1 Design hard disk layout, understand the purpose of the EFI System Partition rather than memorizing only legacy MBR arrangements. These are version-specific priorities, not optional extras for an older objective set.
For 102.4 Use Debian package management, the change summary notes removal of aptitude and added awareness of apt. For 102.5 Use RPM and YUM package management, Zypper was added with coverage comparable to YUM, and dnf awareness was added. Build a comparison table from the official objective terms and then verify each operation in a suitable distribution.
The version update also removed objective 104.4 Manage disk quotas. Do not spend study sessions treating that removed objective as part of Exam 101 version 5.0. Conversely, do not mistake removed command names for permission to ignore the surrounding topic: partitions, filesystems, mounting, permissions, links, and filesystem hierarchy remain in scope.
The LPI Wiki summary is a change aid, not a replacement for the current objectives. Begin with the current 101-500 objective page, then use the version comparison to identify areas where an old book or course may be incomplete.
Build a lab that supports the objectives
Use a disposable Linux virtual machine for command practice and keep a separate notes file recording the command, its purpose, expected output, and a safe reversal. A lab should let you inspect hardware abstractions, install packages, manipulate files, create filesystems, mount storage, and recover from mistakes without risking your main computer.
Keep one Debian-family environment and one RPM-family environment if possible. This makes package-management differences concrete and gives you a place to compare apt and dpkg with rpm, yum, dnf awareness, and Zypper concepts. The exact distribution versions are less important than practising the objective’s operation and terminology.
Use snapshots before destructive filesystem, boot-loader, partition, and permission exercises. Never experiment with fdisk, gdisk, parted, mkfs, mkswap, fsck, e2fsck, or boot configuration against a drive containing personal data. A successful lab is one you can reset and repeat, not one that depends on recovering an accidental outage.
Practise observing before changing. For a problem involving a device, package, process, mount, or boot event, first gather evidence with the relevant inspection tools, state what you expect to learn, then make the smallest change. This habit reinforces the practical administration mindset represented by the objectives.
Study Topic 101 through failure diagnosis
Study Topic 101 as a sequence: discover hardware, understand the boot path, then control system targets and shutdown actions. The useful outcome is not a memorized list of boot terms; it is the ability to explain where a failure occurs and which command, file, or log would provide the next evidence.
For 101.1, work with lspci and lsusb, inspect /sys/, /proc/, and /dev, and distinguish a kernel module from a device node. Explore lsmod and modprobe in the lab. Also learn the conceptual roles of udev, sysfs, and dbus instead of treating them as interchangeable commands.
For 101.2, map the stages from firmware through boot loader, kernel, initramfs, and init system. Compare BIOS and UEFI at a conceptual level, including the EFI System Partition as a disk-layout concern. Use dmesg and journalctl to connect boot messages with the system’s initialization process.
For 101.3, compare SysVinit runlevels with systemd boot targets and practise shutdown and reboot procedures. Know where init scripts and systemd unit information fit. Add awareness of acpid because it appears in the version 5.0 change summary. Ask yourself which action changes the current state and which action changes what happens at future boot.
A weak approach is to memorize systemctl subcommands without understanding targets or service state. A stronger exercise is to describe a scenario, inspect the current target, identify the relevant unit or log, and then return the virtual machine to its original state.
Study Topic 102 as an installation workflow
Topic 102 becomes easier when studied as one installation story: design storage, install a boot manager, resolve shared-library requirements, manage software packages, and understand how virtualization changes the guest’s view of hardware. This sequence prevents package commands and partition commands from becoming disconnected memorization topics.
For storage design, identify mount points such as /, /var, /home, and /boot, along with swap space and the EFI System Partition. Learn the difference between a partitioning scheme and a filesystem created inside a partition. Practise reading lsblk and blkid output before making any changes.
For boot managers, understand the roles of grub-install, grub-mkconfig, grub.cfg, grub.conf, menu.lst, the MBR, and UEFI-related storage. The objective is configuration knowledge, not a recipe copied blindly from one distribution. Confirm which file is generated, which command generates it, and which component actually starts the boot process.
For shared libraries, use ldd to see executable dependencies and understand ldconfig, /etc/ld.so.conf, and LD_LIBRARY_PATH. The practical question is why a program cannot find a library and which configuration mechanism should be investigated. Avoid treating LD_LIBRARY_PATH as a universal fix without understanding its scope and risks.
For Debian package management, practise obtaining package information such as version, contents, dependencies, integrity, and installation status. Use the objective’s named tools, including dpkg, dpkg-reconfigure, apt-get, apt-cache, and /etc/apt/sources.list. For RPM-based systems, perform the equivalent information checks with rpm and understand the roles of rpm, yum, /etc/yum.conf, and /etc/yum.repos.d/.
The objective specifically expects package information about version, content, dependencies, package integrity, and whether a package is installed. Make a matrix with those five information needs as rows and Debian and RPM-family tools as columns. Fill it from your own command output and the official objectives, rather than from an unverified command cheat sheet.
For 102.6, learn the implications of running Linux as a virtualization guest, including the distinction between a virtual machine and a container and the effects of on-premises or cloud placement. Focus on guest-specific concerns such as virtual hardware, resource presentation, and the boundary between guest and host. The objective has weight 1, but it is new in version 5.0.
Make GNU and Unix commands your daily practice
Topic 103 rewards repeated use more than passive reading. Work from a shell prompt every day and combine commands into small investigations: locate a file, inspect its content, filter the result, redirect output, identify a process, and edit a configuration copy. This builds the command relationships that isolated flashcards cannot provide.
For 103.1, practise command expansion, quoting, environment inspection, history, help through man and related tools, and the distinction among type, which, and path lookup. Write examples where quoting changes the result. Include bash, echo, env, export, pwd, set, unset, uname, and the EDITOR variable in your notes.
For 103.2 and 103.4, create text files with repeated, missing, and irregular data. Use filters such as cut, head, tail, sort, tr, uniq, paste, nl, od, and wc, then connect them with pipes and redirects. Test standard input, standard output, and standard error separately so that >, >>, 2>, and | have distinct meanings in your mind.
For 103.3, practise cp, find, mkdir, mv, ls, rm, rmdir, touch, tar, cpio, dd, file, and compression utilities. Include gzip, bzip2, xz, and their corresponding inspection or decompression tools. Before running a command, predict whether it changes content, metadata, location, or only the displayed information.
For 103.5, create background jobs and inspect them with ps, top, pgrep, or similar tools. Practise job control with &, bg, fg, jobs, and nohup, and understand how signals differ from simply closing a terminal. Use watch, screen, and tmux for awareness and controlled repetition rather than memorizing names without a use case.
For 103.6, compare nice and renice and observe process priorities in a controlled workload. Know that changing priority is a process-management decision with permission implications. Do not use a resource-intensive experiment on a machine that hosts important work.
For 103.7, separate basic and extended regular expressions. Practise character classes, quantifiers, anchors, special characters, and the use of grep, egrep, fgrep, sed, and regex(7). Include exercises that delete, change, or substitute text, because searching alone is narrower than the objective’s stated capability.
For 103.8, use vi in a lab until modes, navigation, insertion, saving, and quitting are deliberate actions rather than guesses. Also recognize nano, Emacs, and vim and understand how EDITOR influences tool behavior. A common mistake is learning one emergency vi sequence while failing to understand which mode receives a command.
Treat Topic 104 as safe storage administration
Topic 104 should be practised with extreme care because several commands can destroy data. Use loop-backed or virtual disks, verify device names before every operation, and keep a written record of the filesystem state. The goal is to understand the complete lifecycle: partition, format, check, mount, protect, link, and locate.
For 104.1, compare fdisk, gdisk, parted, mkfs, and mkswap and understand common partition-table and filesystem concepts. Include GPT, exFAT, and the basic features of Btrfs identified in the version 5.0 summary, including multi-device filesystems, compression, and subvolumes. Do not confuse filesystem creation with mounting.
For 104.2, practise the purpose and safe use of fsck, e2fsck, mke2fs, tune2fs, xfs_repair, xfs_fsr, and xfs_db. Learn when a filesystem must be unmounted before repair and how to identify the filesystem type first. The command is not the skill; selecting an appropriate diagnostic or repair tool is.
For 104.3, create and remove mounts using /etc/fstab, mount, and umount, then inspect devices with blkid and lsblk. Use labels and UUIDs rather than relying only on device names, and become aware of systemd mount units. Test what happens when an fstab entry is incorrect, but do so in a recoverable virtual machine.
For 104.5, practise chmod, umask, chown, and chgrp with separate owner, group, and other permissions. Test directory permissions independently from file permissions, and record the effect of symbolic and numeric modes. Include ownership changes and default permissions so that you can reason about access instead of translating isolated octal values.
For 104.6, create hard and symbolic links, inspect them with ls and related file information, and test what happens when the original name is removed. Understand inode sharing, filesystem boundaries, and dangling symbolic links. For 104.7, learn the Filesystem Hierarchy Standard through real paths: identify where configuration, executable, user, variable, temporary, and device-related files normally belong.
The official objective list marks 104.4 as removed. Do not allocate version 5.0 study time to disk quotas merely because an older course includes them. Keep a copy of the current objective list beside your lab checklist so legacy material does not silently control your preparation.
Use the official learning materials without outsourcing practice
LPI’s LPIC-1 Exam 101 learning materials follow the same objective structure as the 101-500 blueprint, from 101.1 through 104.7 with 104.4 omitted. Use each lesson as a reading and vocabulary checkpoint, then turn its key knowledge areas and utility list into a lab task or explanation you can perform without looking at the page.
Read the objective before the lesson and mark three things: concepts you can explain, commands you can execute, and files or terms you can locate. After the lesson, close the reference and reproduce the task in the lab. Finally, return to the objective and identify anything that the lesson did not make clear enough for you to demonstrate.
The English learning materials identify a partial utility list for each objective. Treat that list as a scope signal, not as a promise that every named command will appear in one predictable form. Learn what each utility is for, the kind of output it produces, and how it relates to the objective.
The version 5.0 change summary is particularly useful when your primary book or video was written for version 4.0. Compare its additions and removals with your notes, then verify the final wording on the current LPI objectives page. This avoids studying stale coverage while still preserving useful explanations from older resources.
A practical six-stage study roadmap
A staged plan works better than trying to cover every command in one pass. Start with an objective audit, build command fluency, add installation and storage labs, then use timed mixed review. The calendar length can vary with your background; the sequence should remain stable because each stage depends on the previous one.
Stage one: audit the blueprint. Read every Exam 101 objective and label it confident, familiar, or new. Record the official weights beside the objective, keeping each weight attached to its domain name. Do not schedule the exam yet if you cannot identify a safe way to practise the unfamiliar objectives.
Stage two: establish shell fluency. Work through command-line navigation, text processing, file management, streams, processes, priorities, regular expressions, and vi. Produce small outputs rather than merely copying examples: filter a log, extract fields, find a pattern, change a file, suspend a process, and explain the result.
Stage three: cover architecture and installation. Build a boot-path diagram, inspect virtual hardware, compare init systems, and practise package operations in Debian-family and RPM-family environments. Add shared-library diagnosis and virtualization concepts. At the end of this stage, explain what you would inspect when a system fails before reaching a usable login.
Stage four: run storage and filesystem labs. Use an extra virtual disk or loop-backed device to partition, create a filesystem, mount it by UUID or label, check it safely, apply permissions, and create links. Reset the environment and repeat the workflow from memory. Repetition matters because storage questions often combine several concepts.
Stage five: practise integrated incidents. Give yourself tasks such as identifying a missing command dependency, finding a configuration file, determining why a mount is unavailable, locating a process, or explaining a boot message. Require yourself to state the evidence, command, expected result, and safe corrective action before touching the system.
Stage six: perform readiness reviews. Use the official objectives as a checklist and explain every key knowledge area aloud or in writing. Mix topics rather than reviewing only one domain at a time. Schedule only after your weak areas have specific corrective exercises; a general feeling of familiarity is not a reliable readiness measure.
How to use weights and practice results
Allocate more revision time to high-weight objectives, but use performance evidence to adjust the allocation. For example, a candidate who knows file management but cannot reason about permissions should not blindly follow the weight table; the weak skill creates a larger practical risk than the label alone suggests.
Start with the official weight because LPI says higher-weighted objectives receive more questions. Then add two personal indicators: how often you miss the concept in review and whether you can perform it in a clean lab. A low-weight objective with repeated errors deserves immediate attention, while a high-weight objective you can demonstrate may need only maintenance review.
Keep an error log with the objective number, mistaken assumption, command or concept involved, corrected explanation, and a repeat date. Group errors by cause: syntax recall, output interpretation, permissions reasoning, distribution differences, or unsafe sequencing. This turns practice into a study plan instead of a succession of disconnected scores.
Do not infer a pass threshold, question distribution, or guaranteed outcome from objective weights. The official information supports relative emphasis, not a personal prediction. Use weights to decide where to start, and use demonstrations and objective-by-objective explanations to decide whether you are ready.
Common preparation mistakes to eliminate
The most damaging mistake is studying from memory aids that are detached from the current 101-500 objectives. Legacy material can include removed areas or omit version 5.0 additions. Anchor every resource to the official blueprint and change summary, and record the version it covers before investing study time.
Another mistake is treating commands as interchangeable across distributions. apt, dpkg, rpm, yum, Zypper, and dnf do not represent one identical interface. Compare their purposes and information queries, but learn the objective’s terminology rather than forcing every tool into a single command pattern.
Many candidates read about filesystems without performing a mount, permission, link, or repair exercise. That leaves them unable to interpret output or sequence a safe action. Use virtual disks, snapshots, and repeatable tasks. If an operation could destroy data, practise the observation and planning steps even when you do not execute the destructive version.
Regular expressions are often reduced to a few grep examples. Version 5.0 explicitly broadens the area to basic and extended expressions, special characters, classes, quantifiers, anchors, and text changes or substitutions. Write patterns against controlled sample data and explain why each metacharacter changes the match.
Do not overfocus on graphical administration. Exam 101’s command-line and system objectives require you to understand files, utilities, logs, processes, storage, and boot behavior. A desktop can host the lab, but it should not replace terminal work.
Finally, do not use exam dumps, leaked questions, or memorization claims as a preparation strategy. They cannot establish that you can administer a system, may reflect an obsolete objective version, and do not provide a legitimate substitute for official learning materials and hands-on practice.
What delivery options are evidenced
LPI offers LPIC-1 Exam 101 through Pearson VUE test centers and through Pearson VUE’s OnVUE online-testing system. The choice is practical: select a test center if your equipment or private workspace is unsuitable, and consider OnVUE only after checking the current system requirements, policies, and supported language for your booking.
Each LPIC-1 exam is listed as 90 minutes with 60 multiple-choice and fill-in-the-blank questions. Exam 101 is one of the two required exams, not a shortened practice component. Use the format to practise concise reading, careful entry of fill-in responses, and steady time management without treating practice timing as a prediction of your result.
For Pearson VUE test centers, LPI lists English, German, Japanese, Brazilian Portuguese, Simplified Chinese, Traditional Chinese, and Modern Spanish. For OnVUE delivery, LPI lists LPIC-1 in English, German, Japanese, Brazilian Portuguese, and Spanish. Confirm the available language in the scheduling system because delivery availability can vary by location and appointment.
Online-proctored candidates take the exam at home or in an office while monitored by a verified Pearson VUE proctor through a webcam. LPI says OnVUE candidates need a quiet, private location, a reliable computer with a camera, and a stable Internet connection. The platform currently supports Windows and macOS, not Linux.
If you study and work on Linux, do not assume that your Linux workstation can host OnVUE merely because the certification covers Linux. LPI states that Windows and macOS are currently supported and that it has been discussing Linux support with Pearson VUE. Check the official OnVUE requirements before choosing online delivery.
LPI states that exam prices and lengths remain the same on OnVUE as in test centers. The pricing page directs candidates to select their country or territory for current pricing, so check that page and the booking system rather than relying on a copied price or an old regional comparison.
Decide when and where to schedule
Schedule after you have checked the current objective version, confirmed your intended language and delivery method, and completed a mixed review with no unresolved high-impact gaps. Booking first can create avoidable pressure, especially when your computer, operating system, workspace, or preferred language does not meet online-testing conditions.
If you need OnVUE, verify the supported operating system, camera, network, private room, and Pearson VUE requirements before purchasing or booking. If any condition is uncertain, a test center may be the more predictable option. This is a delivery decision, not a measure of Linux ability.
Use the official pricing page for your country or territory and the official LPIC-1 overview for the certification structure. Keep the exact exam code visible when booking: version 5.0 uses 101-500 for Exam 101 and 102-500 for Exam 102.
Plan the second exam separately. Passing Exam 101 does not complete LPIC-1, and studying Exam 102 topics too early can dilute the time needed for the four Exam 101 domains. Once 101 is scheduled, maintain a short review cycle for it while preparing the second half from its own objective list.
Final readiness checklist
You are ready to make a scheduling decision when you can connect each objective to a practical task, explain the relevant files and utilities, and perform the task safely in a lab. Readiness is stronger when it survives mixed-topic review and when you can explain why an action is appropriate, not merely recall its syntax.
Confirm that you can:
- identify hardware and kernel-related information with the named tools and explain /sys/, /proc/, and /dev;
- trace BIOS or UEFI boot concepts through the boot loader, kernel, initramfs, and init system, including journalctl boot-event use;
- design a partition and filesystem layout including the EFI System Partition, mount points, and swap;
- explain GRUB-related files and commands and diagnose shared-library dependencies;
- compare Debian package management with RPM and YUM-family package management, including package information, integrity, dependencies, and installation status;
- work confidently with shell quoting, filters, pipes, redirects, file operations, processes, priorities, regular expressions, and vi;
- create, check, mount, and protect filesystems using a safe disposable device;
- reason about permissions, ownership, hard links, symbolic links, and standard filesystem locations;
- explain the version 5.0 addition covering Linux as a virtualization guest; and
- complete a mixed practice session within the official 90-minute exam duration without depending on unauthorized material.
If one item remains weak, turn it into a concrete lab task and repeat it after a short interval. Then recheck the official objectives page, verify the delivery requirements, and book through the appropriate Pearson VUE route. After Exam 101, use the Exam 102 objectives—not assumptions about the first exam—to plan the remainder of LPIC-1.
Conclusion
LPIC-1 Exam 101 is best approached as a system-maintenance assessment, not a command glossary. Follow the version 5.0 objectives, give extra attention to higher-weighted domains while correcting your own weak areas, and practise every risky operation in a resettable lab. Before booking, confirm the 101-500 code, country-specific pricing, language, and delivery requirements. Passing this exam establishes the first half of LPIC-1; the certification decision is complete only after Exam 102 is also passed.
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
