LPIC-1 Exam 101 Version 5.0: Part 1 of 2 Study Guide
LPIC-1 Exam 101 validates practical Linux administration foundations: command-line maintenance, Linux installation and configuration, basic networking within the wider certification, and the system architecture and filesystem skills covered by this first exam. It is intended for candidates building vendor-neutral Linux administration capability, with no prerequisites for the LPIC-1 certification. This guide helps you decide whether your preparation should begin with command-line practice, installation and storage labs, objective-by-objective review, or an immediate delivery and scheduling check. Passing Exam 101 alone does not earn LPIC-1; you must also pass Exam 102.
What Exam 101 is and what it is not
Exam 101 is the first component of LPIC-1 version 5.0, identified by LPI as exam code 101-500. It measures four areas: System Architecture; Linux Installation and Package Management; GNU and Unix Commands; and Devices, Linux Filesystems, and the Filesystem Hierarchy Standard. It is not the complete LPIC-1 certification.
The certification decision
LPI states that LPIC-1 candidates must pass both Exam 101 and Exam 102. There are no prerequisites for the certification, so a newcomer can pursue it without holding another LPI credential. The certification validity period is 5 years, and LPI provides options for extending beyond 5 years on its overview page.
Treat Exam 101 as a standalone preparation milestone, not as permission to ignore Exam 102. Exam 101 concentrates on the system beneath and around the command line: hardware, boot, packages, processes, filesystems, permissions, and standard Unix tools. Exam 102 covers different areas, including shells and shell scripting, user administration, networking fundamentals, essential services, and security.
Who benefits from this exam
The exam suits people who administer Linux workstations or servers, support users from a shell, or need a vendor-neutral way to organize foundational Linux knowledge. It is especially useful for candidates who can already navigate a Linux system but need disciplined coverage of package management, boot behavior, storage, permissions, and troubleshooting.
The official LPIC-1 description emphasizes real-world system administration and job-task analysis during exam development. That makes a lab-based approach more appropriate than learning isolated command definitions. You should be able to explain what a command changes, identify the relevant file or subsystem, and choose a safe next diagnostic step.
What the version 5.0 blueprint measures
Use the official objectives as the controlling checklist. LPI assigns every objective a weighting value, and higher-weighted objectives receive more questions, so your study time should follow both the breadth of the blueprint and the weight attached to each objective rather than the order in a textbook.
System Architecture: boot and hardware foundations
Topic 101 covers determining and configuring hardware settings, booting the system, and changing runlevels or boot targets while shutting down or rebooting. Objective 101.1, “Determine and configure hardware settings,” has weight 2 and includes hardware-resource discovery plus tools such as lsusb and lspci.
For 101.1, connect the conceptual pieces: /sys, /proc, and /dev expose different views of the system; lsusb and lspci identify hardware; lsmod and modprobe relate to kernel modules. Do not reduce this objective to memorizing output. Practise tracing a device from discovery to the module or interface that supports it.
Version 5.0 added UEFI coverage equal to BIOS coverage in objective 101.2 and added journalctl in relation to boot events. Objective 101.3 also added awareness of acpid. If your older notes discuss only BIOS, SysVinit, or traditional log files, mark them for revision rather than assuming the version 4.0 material is sufficient.
Linux Installation and Package Management: storage, libraries, and packages
Topic 102 covers disk layout, boot managers, shared libraries, Debian package management, RPM and YUM package management, and Linux as a virtualization guest. The version 5.0 blueprint introduced objective 102.6, “Linux as a virtualization guest,” with weight 1, including the characteristics of Linux in virtual machines and containers on premise and in the cloud.
Package work requires more than installing software. The objectives require obtaining package information such as version, content, dependencies, package integrity, installation status, and, for RPM packages, signatures. Build comparison notes for dpkg and apt tools on Debian-family systems, then rpm, yum, and zypper on RPM-oriented systems. Include dnf awareness because version 5.0 added it.
For shared libraries, learn the relationship among an executable, its dependencies, the dynamic linker configuration, ldd, ldconfig, /etc/ld.so.conf, and LD_LIBRARY_PATH. For storage, practise designing partitions and identifying the EFI System Partition, root, /var, /home, /boot, swap, and mount points without treating one layout as universally correct.
GNU and Unix Commands: the largest practice area
Topic 103 tests command-line work, filters, file management, streams and redirection, process control, priorities, regular expressions, and basic file editing. The practical objective is fluent problem solving: read a command’s documentation, combine tools, preserve or redirect output correctly, and select a process or text operation from the evidence in front of you.
Objective 103.3, “Perform basic file management,” has weight 4 and includes commands such as cp, find, mkdir, mv, ls, rm, rmdir, touch, tar, cpio, dd, file, gzip, gunzip, bzip2, bunzip2, xz, unxz, and globbing. Create a lab directory and deliberately practise copying, moving, archiving, compressing, inspecting, and deleting files while checking paths before destructive operations.
Objective 103.4, “Use streams, pipes and redirects,” has weight 4. Work with standard input, standard output, and standard error separately; then combine commands with pipes and redirects. Test what happens when output overwrites a file, appends to it, or is redirected while an error remains on the terminal. These distinctions are more useful than a flat list of symbols.
Objective 103.5, “Create, monitor and kill processes,” has weight 4. Use ps, top, pgrep, pkill, kill, killall, jobs, fg, bg, nohup, watch, screen, and tmux in controlled sessions. Learn the difference between a shell job and a system process, and identify a process before sending a signal.
Objective 103.7, “Search text files using regular expressions,” has weight 3. Version 5.0 increased this objective from weight 2 to 3 and added explicit understanding of basic versus extended regular expressions, special characters, character classes, quantifiers, anchors, and substitution or deletion operations. Practise with grep, egrep, fgrep, sed, and regex(7), using small files whose expected matches you can verify.
Objective 103.2, “Process text streams using filters,” has weight 2. Version 5.0 decreased its weight from 3 to 2 and removed several utilities while adding bzcat, md5sum, sha256sum, sha512sum, xzcat, and zcat. Use the current objective page and version-change summary to prevent an old study sheet from directing too much time to removed coverage.
Basic editing remains part of the exam through objective 103.8. Understand vi modes and common editing operations, while also recognizing other common editors such as Emacs, nano, and vim and the role of the EDITOR environment variable. A useful test is whether you can open, modify, save, exit, and recover from an accidental mode change without relying on a graphical editor.
Devices, Linux Filesystems, and FHS: make storage decisions safely
Topic 104 covers creating partitions and filesystems, filesystem integrity, mounting and unmounting, permissions and ownership, links, and locating files according to the Filesystem Hierarchy Standard. It rewards candidates who can distinguish a block device, partition, filesystem, mount point, pathname, owner, and permission set.
Objective 104.3, “Control mounting and unmounting of filesystems,” has weight 3. Practise /etc/fstab, mount, umount, blkid, and lsblk, and understand labels and UUIDs as filesystem identifiers. Version 5.0 added awareness of systemd mount units. In a lab, inspect before changing /etc/fstab and use a reversible test rather than risking an unbootable configuration.
Objective 104.5, “Manage file permissions and ownership,” has weight 3. Work through symbolic and numeric modes, user/group/other permissions, umask, chown, and chgrp. Include directory behavior: read, write, and execute have different effects on listing, creating, deleting, and entering a directory. Check results as the affected user, not only as root.
Objective 104.2, “Maintain the integrity of filesystems,” has weight 2 and includes tools such as fsck, e2fsck, mke2fs, tune2fs, xfs_repair, xfs_fsr, and xfs_db. Learn when a filesystem must be unmounted or otherwise made safe before repair, and distinguish filesystem repair from merely checking available space with df or du.
Objective 104.1, “Create partitions and filesystems,” has weight 2. The version 5.0 material includes GPT partition tables and exFAT, while Btrfs coverage includes basic knowledge of multi-device filesystems, compression, and subvolumes. Practise identifying the operation you are performing before choosing fdisk, gdisk, parted, mkfs, or mkswap.
Objective 104.6, “Create and change hard and symbolic links,” has weight 2. Create both link types, inspect them with ls -l and the relevant inode information, then test what happens when the target is moved or removed. The point is to understand pathname references and inode relationships, not to memorize a single ln syntax.
Objective 104.7, “Find system files and place files in the correct location,” has weight 2. Learn the purpose of major FHS locations and use find, locate, updatedb, whereis, which, and type appropriately. Record both what a tool searches and what its result means; confusing command lookup with content search is a common avoidable error.
How to turn objectives into hands-on competence
Build one disposable Linux environment and use it repeatedly. Each session should begin with a task, continue with observation and a controlled change, and end with a short record of the command, expected result, alternative tool, and recovery step. This method exposes gaps that passive reading hides while keeping practice within the published objectives.
A low-risk lab design
Use a virtual machine or another non-production installation for partitioning, boot configuration, package removal, filesystem checks, and permission experiments. Take notes about the distribution and package family you are using, because a Debian package command is not automatically interchangeable with an RPM command. The objective is transferable reasoning, not loyalty to one distribution.
Keep a small directory of test files containing plain text, compressed text, checksums, symbolic links, hard links, and deliberately varied permissions. Create a second user and group for access tests. Run commands first without elevated privileges, then explain why administrative access is necessary before using it.
For boot and filesystem work, write down the original state before changing anything. Identify the device, partition table, filesystem type, mount point, and boot mode. This habit is a practical recommendation, not an LPI examination requirement, but it reduces the chance that a study exercise becomes a data-loss event.
A repeatable command-learning method
For every command family, answer five questions: What problem does it solve? What input does it read? Where does its output go? Which privilege or configuration does it depend on? How would you verify success? Apply that sequence to package queries, process signals, mount operations, regular-expression searches, and permission changes.
Use man pages and objective terminology together. If the blueprint names a utility, practise a small task with it; if it names a concept such as udev, sysfs, UEFI, journaling, or shared libraries, explain how the concept changes the interpretation of command output. Avoid collecting commands without understanding their object, scope, and side effects.
A practical study roadmap for Exam 101
A sensible roadmap moves from observation to manipulation, then from isolated commands to diagnosis. Start with a baseline check against every 101-500 objective, study the high-weight command and filesystem tasks early, and reserve the final stage for mixed scenarios and delivery readiness. Adjust the calendar to your experience rather than forcing a fixed timetable.
Stage 1: establish the gap
Print or copy the current 101-500 objective list into a tracker. For each objective, label yourself unfamiliar, familiar, or demonstrable. “Demonstrable” should mean you can perform the task in a clean lab and explain the result, not that you recognize the term in a multiple-choice question.
Begin with a short diagnostic: identify hardware, inspect boot and log information, query installed packages, locate libraries, manipulate files, create a pipeline, manage a process, mount a test filesystem, and change permissions. Record where you needed a reference. Those notes become the first study queue.
Stage 2: secure command-line fluency
Study topics 103 and 104 together because commands become more useful when attached to filesystems and permissions. Practise navigation, quoting, globbing, filters, pipes, redirects, archives, searches, vi, processes, signals, priorities, links, and ownership. After each exercise, change one condition—for example, a missing file, a different owner, or redirected error output—and diagnose the new result.
Give additional attention to 103.4, 103.5, and 103.3, each listed with weight 4, while still completing the lower-weight objectives. Treat the weight as a prioritization signal, not as permission to skip topics; LPI says higher-weighted objectives receive more questions, but the published weight does not tell you the exact wording or distribution of questions.
Stage 3: practise installation and recovery reasoning
Move to Topic 101 and Topic 102 after your command foundation is stable. Inspect modules and hardware, compare BIOS and UEFI concepts, read boot-related journal information, reason about runlevels and boot targets, design a storage layout, install or inspect a boot manager, and query packages from both major package-management families.
Then add failure drills. What evidence would you collect if a device is absent, a shared library cannot be found, a package dependency is unresolved, a filesystem will not mount, or a service fails during boot? Write the diagnostic order before looking up the answer. This develops the maintenance judgment the objectives describe without depending on undisclosed exam questions.
Stage 4: close version 5.0 gaps
Compare your notes with the official version-change summary. Specifically check UEFI, journalctl boot events, acpid awareness, the EFI System Partition, apt awareness, zypper, dnf awareness, virtualization guests, quoting, type and which, the revised filter coverage, regular-expression concepts, GPT, exFAT, Btrfs features, labels and UUIDs, and systemd mount units.
If you prepared from version 4.0 material, do not simply append a few new commands. Rebuild the affected practice tasks. For example, a storage exercise should include GPT and an EFI System Partition where appropriate, and a boot exercise should include both firmware models and journal evidence. This is a practical recommendation based on the documented changes.
Stage 5: readiness review
In the final review, work from scenarios rather than rereading every page. Give yourself a broken command pipeline, an inaccessible file, a package question, a process problem, a failed mount, and a boot-information task. For each, state the likely subsystem, the first observation command, the change you would avoid making prematurely, and the verification step.
Use the official learning materials for structured lessons, then return to the objective page to confirm coverage. LPI’s Exam 101 learning-materials page lists lessons for the Topic 101 through Topic 104 objectives, including the current 104.1, 104.2, 104.3, 104.5, 104.6, and 104.7 entries.
Which delivery option fits your situation
LPI offers LPIC-1 exams through Pearson VUE test centers and through the OnVUE online-testing system. Choose only after checking the current official rules, supported language, computer, and location requirements; delivery details can affect scheduling even when the exam content is the same.
Test center or OnVUE
At Pearson VUE test centers, LPI lists LPIC-1 exam languages as English, German, Japanese, Brazilian Portuguese, Simplified Chinese, Traditional Chinese, and Modern Spanish. For online OnVUE delivery, LPI lists English, German, Japanese, Brazilian Portuguese, and Spanish.
For OnVUE, LPI says candidates need a quiet, private location, a reliable computer with a camera, and a stable Internet connection. The platform is available in English language only, and LPI states that only Windows and macOS operating systems are currently supported. A Linux study machine therefore cannot be assumed to be an eligible online-testing computer.
LPI says online-proctored candidates take the exam at home or in an office while monitored by a verified Pearson VUE proctor through a webcam. Check Pearson VUE’s full system requirements, policies, and procedures before booking. If your preferred language, operating system, room, or network does not fit the online conditions, a test center may be the simpler decision.
Timing and question format
LPI states that each LPIC-1 exam is 90 minutes long and contains 60 multiple-choice and fill-in-the-blank questions. That means your preparation should include concise recall and careful reading, not only long laboratory sessions.
A useful practice routine is to solve objective-based prompts without pausing for documentation, mark uncertain answers, and review the reasoning afterward. Do not turn that routine into memorization of unauthorized or leaked material. No collection of purported exam dumps can guarantee a pass, and relying on them leaves practical gaps in the exact skills the certification is designed to validate.
Pricing and booking checks
LPI’s pricing page asks you to select your country or territory to view the applicable exam pricing, and the LPIC-1 overview directs candidates to country-specific pricing. Confirm the current voucher price, taxes or regional terms, appointment availability, identification rules, rescheduling policy, and delivery choice directly with the official booking flow before paying.
The supplied official pricing research lists a USD 200 voucher price for LPIC-1 Exam 101 while also showing regional pricing tiers. Because regional pricing can differ and can change, treat the country-specific pricing page as the controlling reference rather than using one figure as a universal cost.
Mistakes that waste preparation time
Most weak preparation plans fail through misalignment: they study a familiar distribution instead of the objective, memorize command names without testing effects, or use old version material without checking changes. Correct those errors by keeping the 101-500 blueprint visible and making every study block produce an observable lab result or a documented explanation.
Treating Exam 101 as all of LPIC-1
Passing 101-500 is not the LPIC-1 credential by itself. LPI requires both Exam 101 and Exam 102. Plan the sequence deliberately: complete 101 when its system, command, package, and filesystem skills are reliable, then use the separate 102 objectives to plan the second exam rather than assuming the domains overlap completely.
Studying obsolete or incomplete material
Version 5.0 removed or changed several areas from version 4.0 and introduced new ones. A particularly damaging approach is to study an old list of commands without checking the current objectives. Use the official change summary as a reconciliation document, and make a separate “added, removed, changed” list before selecting books, courses, or practice environments.
Using one package manager as a universal model
Debian package management and RPM/YUM package management are distinct objective areas. Compare their query, installation, removal, dependency, integrity, and repository concepts in your notes. Include zypper and awareness of dnf from the version 5.0 coverage. A lab that uses only one package family cannot demonstrate the full package-management objective.
Ignoring explanation and verification
A command that appears to work can still change the wrong file, target the wrong device, or hide an error in a pipeline. Make verification part of every exercise: inspect the resulting process, package state, mount table, permissions, link target, checksum, or log entry. Also practise recognizing when a command should not be run until a filesystem is safely unmounted or a path is confirmed.
Booking online delivery without checking the computer
Do not assume that a Linux laptop qualifies simply because the exam is a Linux certification. LPI’s current online-testing information states that OnVUE supports Windows and macOS only, requires a camera and stable connection, and uses an English-language platform. Verify the current Pearson VUE requirements before choosing online delivery.
A final self-check before scheduling
Schedule when you can demonstrate the objectives under light time pressure and can explain unfamiliar output methodically. You do not need to know every command from memory before beginning a booking decision, but you should not schedule merely because a course has been completed or a glossary looks familiar.
Technical readiness checklist
You should be able to identify hardware and modules; explain BIOS and UEFI boot concepts; interpret boot-related journal information; change boot targets safely; design a basic disk layout; distinguish GPT, partitions, filesystems, mount points, and the EFI System Partition; and reason about virtualized Linux guests.
You should also be able to query and manage Debian and RPM-family packages; investigate shared-library dependencies; use shell quoting and common GNU and Unix commands; combine filters, pipes, and redirects; manage and reprioritize processes; use regular expressions; edit with vi; create and check filesystems; mount by labels or UUIDs; manage permissions and ownership; create links; and locate files according to the FHS.
Booking readiness checklist
Confirm that you are preparing for 101-500 rather than a version 4.0 exam, that you understand LPIC-1 still requires Exam 102, and that your selected delivery method is supported in your location and language. For OnVUE, verify the Windows or macOS computer, camera, private room, and network conditions. Check current pricing and appointment rules on the official pages before purchasing a voucher.
The next three actions
First, open the current 101-500 objectives and mark each objective as unfamiliar, familiar, or demonstrable. Second, build or refresh a disposable lab and complete one command-line, package, boot, and filesystem task while recording verification evidence. Third, compare your weakest areas with the version 5.0 change summary, then choose test-center or OnVUE delivery only after checking the official requirements.
Conclusion
LPIC-1 Exam 101 is best approached as a practical systems examination with a precise blueprint. Use the weights to prioritize, but cover every objective; use the official learning materials to structure study, but verify each skill in a lab; and use the version 5.0 change summary to remove obsolete assumptions. Once your diagnostic gaps are closed and your delivery conditions are confirmed, schedule the exam as the first step toward LPIC-1—not as a substitute for 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
