101-500
LPIC-1 Exam 101, Part 1 of 2, version 5.0
LPIC-1 Exam 101 (101-500): Part 1 of 2 Version 5.0 Exam Guide
LPIC-1 Exam 101 validates practical Linux administration foundations: hardware and boot concepts, installation and package management, command-line work, processes, filesystems, permissions, and the Filesystem Hierarchy Standard. It serves candidates building a vendor-neutral Linux foundation, including administrators, support technicians, and experienced users formalizing their skills. This guide helps you decide whether Exam 101 is your next target, what to practise first, how to use the version 5.0 objectives, and whether Pearson VUE test-center or OnVUE delivery fits your circumstances.
What Exam 101 actually validates
Exam 101 is the first half of LPIC-1, not the complete certification. It tests whether you can maintain a Linux system from the command line, understand installation and startup, work with files and processes, and handle basic storage and permissions. To earn LPIC-1, you must pass both Exam 101 and Exam 102.
LPI describes LPIC-1 as a certification based on real-world system administration skills. The broader certification expects candidates to understand Linux architecture, install and maintain a Linux workstation, use common GNU and Unix commands, manage files and access permissions, and perform straightforward maintenance tasks. Exam 101 supplies the architecture, installation, command, and filesystem portion of that foundation.
The practical decision is scope. Choose Exam 101 first if you want to establish command-line and system fundamentals before studying shells and scripting, administrative tasks, essential services, networking fundamentals, and security in Exam 102. Do not treat a general Linux familiarity checklist as sufficient: the official objectives are the controlling study list for version 5.0.
Who should choose this exam first
Exam 101 is a sensible first target for a Linux user who can work in a terminal but wants a structured benchmark covering more than one distribution family. It also suits support staff and junior administrators who need to explain how Linux starts, stores files, installs software, and manages running programs.
There are no prerequisites for LPIC-1. That removes a formal entry barrier, but it does not remove the need for hands-on practice. A candidate who has only used graphical administration tools should first build terminal fluency. A candidate who already administers Linux should use the objective list as a gap analysis rather than automatically reviewing every topic at the same depth.
Passing Exam 101 does not by itself make you LPIC-1 certified. Plan the two exams as related but separate study projects. Exam 102 covers the remaining LPIC-1 domains, so record unresolved subjects rather than allowing Exam 101 preparation to expand into every Linux administration topic.
How the version 5.0 blueprint is organized
Exam 101 version 5.0 has four official topic areas: System Architecture; Linux Installation and Package Management; GNU and Unix Commands; and Devices, Linux Filesystems, and the Filesystem Hierarchy Standard. The objectives page assigns each objective a weight; LPI says higher-weighted objectives receive more questions, so weights are useful for ordering revision but do not reveal an exact question allocation.
Topic 101, System Architecture, covers hardware settings, booting, and runlevels or boot targets, including shutdown and reboot. Objective 101.1, Determine and configure hardware settings, has weight 2 and includes hardware-resource discovery plus tools such as lsusb and lspci. Objective 101.2, Boot the system, has weight 3. Objective 101.3, Change runlevels / boot targets and shutdown or reboot system, has weight 3.
Topic 102, Linux Installation and Package Management, covers disk layout, boot managers, shared libraries, Debian package management, RPM and YUM package management, and Linux as a virtualization guest. Objective 102.1, Design hard disk layout, has weight 2; objective 102.3, Manage shared libraries, has weight 1; objective 102.4, Use Debian package management, has weight 3; objective 102.5, Use RPM and YUM package management, has weight 3; and objective 102.6, Linux as a virtualization guest, has weight 1.
Topic 103, GNU and Unix Commands, is the broad command-line core. Objective 103.2, Process text streams using filters, has weight 2; 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.6, Modify process execution priorities, has weight 2; objective 103.7, Search text files using regular expressions, has weight 3; and objective 103.8, Basic file editing, has weight 3.
Topic 104, Devices, Linux Filesystems, Filesystem Hierarchy Standard, covers partitions, filesystem integrity, mounting, permissions and ownership, links, and file locations. Objective 104.1, Create partitions and filesystems, has weight 2; objective 104.2, Maintain the integrity of filesystems, has weight 2; objective 104.3, Control mounting and unmounting of filesystems, has weight 3; objective 104.5, Manage file permissions and ownership, has weight 3; objective 104.6, Create and change hard and symbolic links, has weight 2; and objective 104.7, Find system files and place files in the correct location, has weight 2. Objective 104.4, Manage disk quotas, was removed in the version 5.0 update.
Use the labels and weights together in your notes. For example, write “103.4 Use streams, pipes and redirects — weight 4,” not an isolated “weight 4.” That keeps the study priority attached to the skill being measured and prevents a bare number from being mistaken for a percentage or a prediction of the exact exam content.
What changed from version 4.0 to version 5.0
Version 5.0 is not simply a new code printed on an old outline. The update adds, removes, and refocuses several areas in Exam 101, so candidates moving from older books or notes should compare them with the current objectives and the official change summary.
For System Architecture, version 5.0 adds UEFI coverage equal to BIOS coverage in 101.2, adds journalctl in relation to boot events, and adds awareness of acpid to 101.3. For installation, 102.1 adds the EFI System Partition, 102.4 removes aptitude and adds awareness of apt, and 102.5 removes yumdownloader, adds Zypper alongside YUM, and adds awareness of dnf.
The update introduces 102.6, Linux as a virtualization guest, with weight 1. Its focus is the implications of running Linux in virtual machines and containers on premises and in the cloud. This is an awareness objective, so learn the operational distinctions and effects rather than turning it into an unrelated specialist virtualization course.
The command section changes the emphasis as well. Version 5.0 adds quoting and the type and which commands to 103.1; adds watch and tmux to 103.5; increases the weight of 103.7, Search text files using regular expressions, from 2 to 3; and adds basic versus extended regular-expression concepts, character classes, quantifiers, anchors, and text substitution concepts.
Filesystem changes include GPT partition tables and exFAT in 104.1, updated Btrfs feature awareness, revised XFS tool coverage in 104.2, and labels, UUIDs, systemd mount units, blkid, and lsblk in 104.3. Candidates using version 4.0 materials should mark removed content, then deliberately add these new areas rather than relying on memory of the older syllabus.
How to turn the objectives into a study plan
Start with the objectives page, not a random command list. Copy each Exam 101 objective into a study tracker, attach its topic and weight, and add three columns: explain, perform, and troubleshoot. A subject is not ready when you recognize its name; it is ready when you can describe its purpose, use the relevant tool safely, and interpret the result.
Read the official Learning Materials in objective order, beginning with 101.1 and continuing through Topic 104. The learning site provides lessons for hardware, booting, installation and package management, commands, filesystems, permissions, links, and file locations. Use the lessons to establish vocabulary, then move quickly into a disposable Linux environment for command practice.
Build a small command notebook with four entries for every difficult utility: what problem it solves, its important options or operands, the files it reads or changes, and one output pattern you can recognize. This is more useful than collecting long command definitions. Include commands named in the objectives, such as lsusb, lspci, journalctl, dpkg, apt-get, rpm, zypper, find, grep, sed, ps, mount, blkid, chmod, chown, and ln.
Use retrieval practice at the end of each session. Close your notes and explain why a command would be selected in a short scenario. Then verify the result in the lab. Questions that ask for a command, file, option, or consequence reward precise recall, while labs expose misunderstandings about paths, quoting, permissions, process identifiers, and filesystem state.
Allocate additional review to high-weight objectives, but do not abandon weight 1 objectives. LPI describes weights as relative importance and says higher-weighted objectives receive more questions; it does not provide a guarantee that every session or practice set will mirror that distribution. A low-weight objective can still be the difference between knowing and guessing.
A practical lab setup for Exam 101
A disposable Linux installation is the most efficient practice tool for this exam. Use a virtual machine or another noncritical system so you can inspect boot files, create filesystems, change permissions, install packages, and terminate test processes without risking personal data or a production host.
Keep the lab deliberately small. Create one Debian-family environment for dpkg and apt work and one RPM-family environment for rpm and YUM-related concepts if you have access to them. The objective also includes Zypper and awareness of dnf, so supplement the lab with the official objectives and documentation rather than assuming one distribution exposes every tool.
Practise observation before modification. Inspect /sys, /proc, and /dev; identify hardware with lspci and lsusb; examine loaded modules with lsmod; and use modprobe only when you understand the effect. For boot work, review BIOS and UEFI distinctions, the EFI System Partition, bootloader configuration, and journalctl output related to boot events.
For storage practice, use a throwaway virtual disk. Work through partition identification, filesystem creation, mount points, /etc/fstab entries, labels, UUIDs, and unmounting. Keep a recovery path. Never run filesystem or partition commands against a disk you have not positively identified.
For command work, generate your own text files and logs. Combine filters with pipes, redirect standard output and standard error separately, search with basic and extended regular expressions, edit with vi or another covered editor, and create processes that you can observe and stop. The goal is controlled repetition, not exposure to live exam questions.
The command-line skills that deserve repeated practice
The command section is easiest to retain when studied as a set of workflows rather than isolated utilities. Practise starting with a file or process, selecting the right inspection command, transforming or filtering output, and checking the result. This mirrors the operational relationships among the objectives without assuming that the exam will present any particular scenario.
For shell use, practise command lookup and environment inspection with type, which, env, export, set, unset, pwd, history, and uname. Include quoting: test how unquoted, single-quoted, and double-quoted text behaves when variables, spaces, or metacharacters are present. Be able to distinguish a shell builtin, an alias, a function, and an executable when the question gives you command-resolution clues.
For filters and streams, combine cat, cut, head, tail, sort, uniq, wc, tr, paste, tee, and xargs with grep and sed. Understand standard input, standard output, standard error, pipes, append redirection, and the difference between replacing and appending a file. Practise compressed-input tools such as bzcat, xzcat, and zcat, together with checksum utilities including md5sum, sha256sum, and sha512sum.
For file management, create and inspect directory trees using cp, find, mkdir, mv, rm, rmdir, touch, tar, cpio, dd, file, gzip, gunzip, bzip2, bunzip2, xz, and unxz. Focus on operand order, recursive behavior, archive contents, wildcard expansion, and the difference between a file’s name and its type. Use find predicates deliberately instead of relying on a remembered one-line recipe.
For processes, use ps, top, pgrep, jobs, bg, fg, kill, pkill, killall, nohup, watch, screen, and tmux. Know the distinction between a shell job and a system process, how signals affect termination, and how to identify the correct process before acting. Practise nice and renice separately so process control and process priority do not blur together.
For editing, learn vi modes and the core movement, insertion, deletion, search, save, and quit operations included by the objective. Version 5.0 also expects awareness of Emacs, nano, and vim, plus setting the default editor through the EDITOR environment variable. Do not spend all your time memorizing obscure editor commands when the larger risk is failing to understand modes or file changes.
Storage, filesystems, permissions, and file locations
Treat Topic 104 as one connected administration task: identify storage, create or check a filesystem, mount it predictably, protect its contents, and place files where the system expects them. This sequence makes the individual objectives easier to remember and gives you a repeatable troubleshooting method.
For partitioning and filesystems, distinguish partition tables from filesystems and know the roles of fdisk, gdisk, parted, mkfs, and mkswap. Review MBR and GPT concepts, the EFI System Partition, swap space, root, /var, /home, and /boot. Version 5.0 includes exFAT and basic Btrfs feature knowledge, including multi-device filesystems, compression, and subvolumes.
For integrity, practise the purpose and safe use of fsck, e2fsck, mke2fs, tune2fs, xfs_repair, xfs_fsr, and xfs_db at the level described by the objectives. The important decision is whether you are creating, checking, tuning, repairing, or inspecting. Do not confuse a repair utility with a general disk-information command, and do not experiment on a mounted filesystem without understanding the risk.
For mounting, compare temporary mounts with persistent configuration in /etc/fstab. Use mount, umount, blkid, and lsblk to connect devices, labels, UUIDs, filesystems, and mount points. Review systemd mount-unit awareness and verify a configuration in the lab before rebooting. A common mistake is remembering a device path while overlooking that device names can change; labels and UUIDs are part of the version 5.0 emphasis.
For permissions, practise symbolic and numeric modes, ownership, groups, chmod, chown, chgrp, and umask. Create test users and directories, then verify access as the relevant user instead of judging from the owner’s shell. Include set-user-ID, set-group-ID, and sticky-bit behavior if your objective materials cover them, and keep special permissions tied to the reason they are used.
For links and hierarchy, compare hard and symbolic links by inode relationship, filesystem limitations, directory behavior, and failure when a symbolic-link target disappears. Use ln and ls to inspect them. Then map common locations according to the Filesystem Hierarchy Standard, including where system configuration, user data, executables, variable data, devices, and temporary files normally belong.
Hardware, boot, packages, and virtualization: study the boundaries
Several Exam 101 subjects look similar because they all involve system changes, but their boundaries matter. Hardware discovery is not boot troubleshooting; package metadata is not package installation; and a Linux guest’s virtualization implications are not a complete hypervisor administration syllabus. Study each task by its question, tool, and expected result.
For hardware, connect /sys, /proc, and /dev to their different roles, then practise lspci and lsusb. Review modules with lsmod and modprobe, and understand the concepts of udev and dbus. The official Learning Materials begin with 101.1 and identify hardware-resource discovery, integrated peripherals, mass-storage types, and these inspection tools as key knowledge areas.
For booting, trace the path from firmware through bootloader, kernel, initramfs, and initialization system. Compare BIOS and UEFI, including the EFI System Partition, and recognize the relevance of dmesg and journalctl for evidence. For runlevels and boot targets, relate legacy SysVinit terms to systemd terminology and practise safe shutdown and reboot actions.
For packages, separate Debian operations from RPM-family operations. The objectives include obtaining package information such as version, content, dependencies, package integrity, and installation status. Practise dpkg, dpkg-reconfigure, apt-get, and apt-cache, then rpm, rpm2cpio, yum, and zypper. Review /etc/apt/sources.list, /etc/yum.conf, and /etc/yum.repos.d/ as configuration locations named by the objectives.
For shared libraries, use ldd and ldconfig and understand /etc/ld.so.conf and LD_LIBRARY_PATH. The task is to determine which libraries an executable depends on and understand how a missing library can be made available. Avoid memorizing a package command without learning how to inspect the dependency relationship first.
For virtualization, review what changes when Linux runs as a guest in a virtual machine or container, whether on premises or in the cloud. Consider hardware visibility, resource presentation, storage and network abstractions, and the operational difference between a guest and a container. Keep this preparation aligned with the weight 1 objective 102.6 rather than allowing it to displace command and filesystem practice.
A six-stage study roadmap
A staged roadmap prevents the broad syllabus from becoming a collection of disconnected facts. Move from orientation to command fluency, then storage and recovery concepts, followed by integrated labs and timed review. Advance only when you can demonstrate the current stage without depending on a copied command sequence.
Stage one is an objective audit. Read the official Exam 101 objectives and the version 4.0-to-5.0 change summary. Mark every objective as new, familiar, or operationally practised. Highlight UEFI, journalctl, apt, Zypper, dnf awareness, virtualization guests, quoting, regular expressions, GPT, exFAT, Btrfs features, UUIDs, labels, and systemd mount units if your prior study used version 4.0 materials.
Stage two is command-line foundation. Work through shell behavior, filters, files, streams, pipes, redirects, processes, priorities, regular expressions, and editing. End each lab with a short task such as extracting selected fields from a file, finding matching paths, redirecting errors, changing a process priority, or editing a configuration-like text file. Record the reasoning, not only the final command.
Stage three is system architecture and packages. Trace startup, compare BIOS and UEFI, inspect boot evidence, practise target and shutdown concepts, and review hardware tools. Then perform package queries and installations in separate distribution-family environments. Verify package status, dependencies, content, integrity, and configuration rather than stopping after a successful installation.
Stage four is filesystems and permissions. Use a throwaway disk or virtual disk to create and inspect partitions and filesystems, mount by UUID or label, and test /etc/fstab behavior. Practise permission and ownership changes with multiple users, create hard and symbolic links, and map files to the appropriate hierarchy locations.
Stage five is integration. Start from a symptom rather than a topic: a device is not visible, a system does not reach its normal target, an executable lacks a library, a package appears installed but a command is missing, a mount is absent, or a user receives an access error. Identify evidence, choose the least invasive command, make a change, and verify it.
Stage six is readiness review. Revisit every weak objective, especially those you know only by recognition. Use timed mixed practice that includes multiple-choice and fill-in-the-blank styles, but write your own questions from the objectives or use reputable study material. Review every wrong answer by objective label and cause of error. Schedule only after you can explain why the correct answer works and why the alternatives do not.
Common preparation mistakes to avoid
The most damaging mistake is studying commands without studying conditions. A command may be familiar yet still be the wrong answer because the task concerns package metadata, a persistent mount, a boot event, a shell expansion, or a process signal. Always ask what state is being inspected or changed before selecting a utility.
Do not use version 4.0 notes unchanged. The official change summary identifies both removed material and new emphasis, including the removal of disk quotas as objective 104.4, the new virtualization-guest objective, and the changes to boot, package, regular-expression, partition, and mounting coverage. Use older material only after reconciling it with version 5.0.
Do not overfit to one distribution. Debian package tools and RPM-family tools appear together because LPIC-1 is vendor-neutral. Learn the purpose and vocabulary of each family, and label distribution-specific behavior in your notes. A lab that exposes only one package ecosystem can create false confidence.
Do not confuse memorization with troubleshooting ability. Memorize important paths, utilities, options, and terminology, but verify them by building small failures in a lab. Remove a test permission, break a harmless mount entry, inspect a missing-library message, or create a process you can identify and stop. Restore the lab after each experiment.
Do not infer exact exam content from objective weights. A weight indicates relative importance and higher-weight objectives receive more questions, but it is not a published question count or a promise about the next form. Prepare every objective and use weighting to decide where to spend scarce revision time.
Do not rely on exam dumps, leaked questions, or memorized answer patterns. They do not establish command understanding, can be inaccurate, and do not guarantee a pass. Work from the official objectives and learning materials, then use legitimate practice to expose gaps without seeking live exam content.
Exam format, language, and delivery choices
LPI states that each LPIC-1 exam is 90 minutes and contains 60 multiple-choice and fill-in-the-blank questions. That format makes concise reading and exact command or path recall important, but preparation should still emphasize understanding because the objectives cover relationships among tools, files, system states, and administrative decisions.
Exam 101 version 5.0 is identified by exam code 101-500. The LPIC-1 certification uses exam codes 101-500 and 102-500, and both exams are required for certification. The certification validity period is five years, with LPI pointing candidates to options for extending beyond that period.
At Pearson VUE test centers, LPI lists LPIC-1 exams in English, German, Japanese, Brazilian Portuguese, Simplified Chinese, Traditional Chinese, and Modern Spanish. For online OnVUE delivery, LPI’s overview lists English, German, Japanese, Brazilian Portuguese, and Spanish, while the online-testing page lists LPIC-1 in English, Japanese, Brazilian Portuguese, and Spanish. Because the official pages present different online language lists, confirm the current choice during scheduling rather than assuming availability.
LPI offers LPIC-1 Exam 101 and Exam 102 through Pearson VUE’s OnVUE online-testing system. Online candidates take the exam at home or in an office while monitored by a verified Pearson VUE proctor through a webcam. The online-testing guidance says candidates need a quiet, private location, a reliable computer with a camera, and a stable Internet connection.
The OnVUE platform is available in English only as a platform, and LPI states that only Windows and macOS are currently supported. Linux is not listed as a supported operating system in that guidance. Run the official system check and review Pearson VUE’s current requirements and procedures before buying or scheduling if you are considering online delivery.
LPI says 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 pricing, and regional pricing can differ. Treat the official pricing page and scheduling flow as authoritative rather than relying on an old voucher price or a third-party listing.
How to decide when to schedule
Schedule when your readiness evidence is behavioral, not when you have merely finished reading. You should be able to work through the objective tracker, perform representative lab tasks without step-by-step notes, and explain mistakes in terms of an objective. If several high-weight command or filesystem objectives remain guesswork, postpone and close those gaps first.
Use a final readiness checklist with four tests. First, can you identify the relevant objective from a short administration scenario? Second, can you name the appropriate file or utility? Third, can you predict the effect before running the command? Fourth, can you verify the result and recover safely? Failure at any one of these points identifies the next study task.
Choose the delivery method after checking practical constraints, not as an afterthought. A test center may be preferable if your computer, operating system, room, camera, or Internet connection does not meet OnVUE requirements. Online delivery may reduce travel, but it still requires a private environment and technical preparation. Confirm language, country pricing, appointment availability, and current policies on the official pages before purchase.
Schedule Exam 102 only after reviewing what Exam 101 revealed about your study habits. The two exams share a Linux administration foundation, but Exam 102 has different domains. Keep separate objective trackers so you do not mistake progress in commands and filesystems for readiness in shells, networking, services, or security.
Your next actions after reading this guide
The next useful action is to open the official version 5.0 objectives and create a four-topic tracker for Exam 101. Add every objective, its weight, the named utilities and files, and a short lab task. Then compare your tracker with the official Learning Materials so your study sequence follows the current outline rather than an older course or book.
Set up a disposable Linux environment and complete one small task from each major area: inspect hardware, interpret a boot-related log, query a package, process a text stream, inspect a process, create a filesystem, mount it by UUID or label, change test permissions, and compare a hard link with a symbolic link. Write down what you observed and what you would verify next.
Finally, use the official version-change summary to audit older notes and check delivery details before scheduling. Confirm whether your chosen test center or OnVUE option supports your language and system, review the current country-specific price, and remember that Exam 101 is Part 1 of 2. Your immediate goal is not to collect more resources; it is to turn each objective into a demonstrated skill.
Conclusion
LPIC-1 Exam 101 is best approached as a practical foundation exam with a precise version 5.0 boundary. Use the official objectives to prioritize, the Learning Materials to structure explanations, and a disposable Linux lab to convert recognition into reliable action. Reconcile older notes with the version-change summary, verify current delivery details before scheduling, and keep the second LPIC-1 exam as a separate preparation decision.
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