Failed Linux Professional Institute LPIC-1? Here's Your Recovery Plan

Pro tip: Contact the exam provider directly for their specific retake policy.

• Studying only one package manager. LPIC-1 devotes a weight of 3 to Debian package management and another 3 to RPM, YUM, and Zypper, so ignoring half of topic 102 costs six questions on exam 101.
  Run one Debian-based and one RPM-based virtual machine side by side and perform the same task in both, including finding which package owns a specific file.
• Preparing for multiple choice only. LPI exams include fill-in-the-blank items where you type a command, path, or option and spelling counts.
  Practise by writing answers on paper rather than in a shell with tab completion. Learn the exact spelling of file paths such as /etc/nsswitch.conf and /etc/logrotate.d.
• Skipping topic 106 because you are a server administrator and never touch X11. It is worth 4 points including an accessibility objective that most candidates never open.
  Spend one focused session on xorg.conf and its .d directory, xhost, xauth, DISPLAY, Wayland awareness, and the accessibility list covering screen readers, magnifiers, Braille displays, and sticky or bounce keys.
• Learning only iproute2 and dismissing the legacy net-tools commands. Objective 109.3 explicitly requires awareness of ifconfig, netstat, and route.
  Learn ip and ss properly, then build a translation table to the legacy equivalents. LPI lists removing the legacy commands as a future change consideration, so they are still in version 5.0.
• Ignoring the port numbers in objective 109.1 on the assumption that nobody asks for them directly.
  Memorise the exact list LPI publishes, which runs from 20 and 21 through 995 and includes 123, 161, 162, 389, 465, 514, and 636. These are exactly the kind of item that appears as a fill-in-the-blank.
• Treating systemd as the whole answer. Version 5.0 objectives still require understanding SysVinit and awareness of Upstart, plus /etc/inittab and /etc/init.d.
  Learn both init systems for the boot and runlevel objectives, and pay particular attention to the systemd journal work in objective 108.2, which includes persistent storage, size limits, and recovering journal data from a rescue system.
• Booking the second exam too soon after a failed first attempt. LPI requires a seven-day wait after a first failure and fourteen days after a second or subsequent failure.
  Use the score report you receive immediately after the exam to identify weak sections, and plan the retake for after the waiting period rather than assuming you can rebook the next day.
• Assuming you can re-sit a passed exam to improve a score or refresh a certification early. LPI states that anyone who passes an exam may not retake it for at least two years.
  Plan recertification around the five-year ACTIVE window, and note that different versions of an exam count as the same exam for both the retake and the two-year rules.
• Planning an OnVUE session on a Linux laptop. LPI states plainly that the Pearson VUE OnVUE testing system requires a Mac or Windows operating system, and apologises for it.
  Arrange a Mac or Windows machine for an online sitting, or book a test centre. Also check the language list, because OnVUE covers five languages against seven at test centres.

• Two exams: 101 and 102
• Master command line and file management
• Study boot process and runlevels
• Understand package management (apt, yum, dnf)
• Practice on multiple Linux distributions