“"The practice exams helped me strengthen my Linux administration skills and improve my confidence before taking the certification exam."”
Raghav D
Linux System Administrator
Exam 101-500 gives you 90 minutes for 60 questions, a mix of standard multiple-choice and fill-in-the-blank items. The fill-in-the-blank questions are the part people underestimate: there’s no answer list to recognize a command from, you have to type the exact command, path, or flag from memory — /etc/fstab, chmod, -R, that kind of precision. Partial credit doesn’t exist here; a misspelled command or a missing flag counts as wrong.
LPI scores the exam on a scaled 200–800 range, with 500 needed to pass — so your result isn’t a raw percentage, and a “500” doesn’t mean you got exactly 62.5% of questions right. The scaling accounts for slight difficulty differences between question pools, which is also why two people who feel equally prepared can walk away with noticeably different scores.
Questions lean scenario-based rather than pure definition recall, especially in the command-line and filesystem topics. Instead of “What does chmod do?” expect something closer to “A script needs to run with the owner’s privileges regardless of who executes it — which permission bit and command accomplish this?” That framing rewards people who’ve actually typed the commands, not just read about them.
Objectives Version 5.0 splits Exam 101 into four topics, each weighted by how many questions it generates. Total weight across the exam is 60.
Topic | Weight | % of Exam | Focus |
|---|---|---|---|
101 — System Architecture | 8 | ~13% | Hardware detection, boot sequence, runlevels/boot targets |
102 — Linux Installation & Package Management | 12 | ~20% | Disk layout, GRUB, shared libraries, dpkg/apt, rpm/yum/zypper, virtualization awareness |
103 — GNU and Unix Commands | 26 | ~43% | Command line, text filters, file management, pipes/redirects, process control, regex, vi |
104 — Devices, Filesystems, FHS | 14 | ~23% | Partitioning, filesystem integrity, mounting, permissions, links, FHS |
Topic 103 alone accounts for nearly half the exam — four of its eight sub-objectives (103.1 command line, 103.3 file management, 103.4 streams/pipes/redirects, 103.5 process management) carry the exam’s single highest weight of 4 points each. If your command-line fluency is shaky, that’s where it costs you most.
vi, not a GUI editor. Objective 103.8 expects you to navigate, insert, delete, copy, and find text in vi from modes — i, o, a to enter insert mode, dd/yy/p to cut and paste, :w!/:q! to force-write or quit. People who’ve only ever used nano or a GUI editor lose easy points here because they’ve never built the muscle memory.
systemd alongside SysVinit, not instead of it. The objectives still test SysVinit concepts (runlevels, /etc/inittab, telinit) right next to systemd targets and systemctl. Candidates who learned exclusively on a modern systemd-only distro often blank on runlevel numbering or SysVinit terminology that still appears in questions.
Package management across three systems. You need working knowledge of Debian tooling (dpkg, apt-get, apt-cache) and RPM-family tooling (rpm, yum, zypper, with awareness of dnf) — not just whichever distro you personally use. If you’ve only ever run Ubuntu, the RPM/YUM objective (102.5) is where unfamiliarity shows.
Regular expressions as their own skill, separate from the commands that use them. Objective 103.7 tests understanding of basic vs. extended regex, character classes, anchors, and quantifiers independently of grep or sed syntax. Knowing how to run grep isn’t the same as being able to reason about why a pattern matches or doesn’t.
Filesystem Hierarchy Standard as memorized fact, not inferred logic. Objective 104.7 expects you to know specific FHS locations — where logs live, where temporary files go, where system binaries versus user binaries are installed — and this is tested as direct recall, not something you can reason your way to on exam day.
Given how command-heavy this exam is, practice questions that only test recognition (“which of these is the correct syntax?”) undersell what you need. Push yourself to answer fill-in-the-blank style questions without an option list in front of you — that’s the actual exam format for a meaningful chunk of the test, and it’s the format most practice resources skip because it’s harder to grade automatically.
When you get a question wrong, don’t just note the right answer — open a terminal and run the command. The exam rewards people who’ve built working muscle memory with find, tar, xargs, and the text-processing filters (cut, sort, sed), not people who’ve memorized flag definitions in isolation.
Because Topic 103 carries almost half the exam’s weight, weight your practice time accordingly rather than spreading it evenly across all four topics. A candidate who’s rock-solid on command-line and file management but a little shaky on virtualization awareness (102.6, weight 1) will pass more comfortably than the reverse.
Treating this as a multiple-choice-only exam and never rehearsing typed answers, then freezing on the first fill-in-the-blank question
Studying one package manager family deeply and skipping the other, assuming the exam will “favor” the distro they use day-to-day
Skipping vi practice because a GUI editor feels more natural, then losing points on an objective (103.8) worth weight
Under-preparing on FHS specifics (104.7) because it feels like “just memorization” compared to hands-on topics — it’s tested directly and often skipped in last-minute review
Confusing SysVinit and systemd terminology under time pressure because study materials only covered one init system in depth
New to Linux administration: Budget 8–10 weeks of consistent practice, ideally with daily terminal time rather than passive reading. Build comfort with the shell first (Topic 103) before layering in package management and filesystem topics — the command-line fluency carries over into every other section.
Has related experience (e.g., works with Linux day-to-day but hasn’t studied formally): 3–4 weeks is usually enough to fill gaps, but don’t skip the objectives outside your daily routine — most working admins have blind spots in whichever package manager family they don’t use, and in FHS specifics they’ve never had to recite.
Retaking after a fail: Go back to your score report’s weak areas first rather than re-studying everything. A narrow retake gap (2–3 weeks) focused specifically on what tripped you up the first time is usually more effective than a full restart.
Objectives Version 5.0 is the current release; LPI has flagged a handful of likely future changes, including eventual removal of ifup/ifdown and legacy net-tools commands and TCP wrappers references from the objectives, plus wording adjustments to the package management objective. None of these have landed yet as of this writing, so they’re still in scope — but they signal where the exam is trending toward newer tooling (iproute2 over net-tools, for instance) if you’re choosing which command variants to prioritize memorizing Put your knowledge to the test with our PECB Certified ISO/IEC 27001 Lead Auditor mock test.
Last updated on Oct, 31 2026