202-450
LPIC-2 - Exam 202 (part 2 of 2), version 4.5
LPIC-1 Exam Guide: Objectives, Preparation Strategy, and Scheduling Decisions
LPIC-1 validates practical Linux administration across the command line, installation and configuration, filesystems, users, services, networking, and security. It is aimed at candidates building a professional Linux foundation, whether they are entering system administration or formalizing hands-on experience. This guide helps you decide whether LPIC-1 is the right starting point, how to split preparation between exams 101 and 102, which skills deserve laboratory practice, and when your preparation is strong enough to schedule.
What LPIC-1 validates
LPIC-1 validates the ability to perform command-line maintenance, install and configure a Linux computer, and configure basic networking. LPI describes the certification as a real-world system administration assessment, with objectives tied to job tasks identified through job task analysis during exam development.
The certification is vendor-neutral. That means your preparation should focus on transferable Linux concepts and utilities rather than memorizing the layout or preferred tools of one distribution. The published objectives include Debian package management as well as RPM, YUM, and Zypper, alongside systemd, SysVinit, filesystem tools, networking commands, and standard configuration files.
The practical implication is important: reading command descriptions is not enough. You should be able to explain what a command changes, identify the relevant configuration file, recognize a failure pattern, and select a safe next diagnostic step. The exam objectives are a checklist of knowledge, but your study method should build operational judgment.
Who should choose LPIC-1 instead of Linux Essentials or LPIC-2
Choose LPIC-1 when you want a professional-level foundation in Linux administration and are ready to work across system setup, command-line operations, account management, services, networking, and security. Linux Essentials is a gentler entry point; LPIC-2 is the next decision after you have completed LPIC-1 and can handle broader network administration.
Linux Essentials has no prerequisites and requires passing the Linux Essentials 010 exam. Its published scope covers Linux and open source concepts, common applications, command-line proficiency, and basic administration and security. The certificate has lifetime validity. It is a sensible option if you are still learning navigation, permissions, users, and basic shell work.
LPIC-1 has no certification prerequisite, but it requires passing both the 101 and 102 exams. It is better suited to a candidate who can already use a terminal comfortably and wants a more systematic administration credential. LPI lists LPIC-1 as the first certification in its multi-level Linux Professional program.
LPIC-2 is not simply a harder version of the same study plan. It validates administration of small to medium-sized mixed networks and requires an active LPIC-1 certification, in addition to passing exams 201 and 202. Its topics include advanced storage, kernel and startup administration, networking, authentication, security, DNS, web services, file sharing, and email services. Treat LPIC-2 as a later progression, not as a reason to skip the LPIC-1 objectives.
What you must pass and how the two exams fit together
LPIC-1 certification requires passing both exam 101 and exam 102. Each exam is 90 minutes and contains 60 multiple-choice and fill-in-the-blank questions. The current LPIC-1 version is 5.0, using exam codes 101-500 and 102-500, so confirm that every book, course, practice exercise, and objective list you use matches that version.
Exam 101 concentrates on the system’s foundation: architecture, installation and package management, GNU and Unix commands, and devices, Linux filesystems, and the Filesystem Hierarchy Standard. Exam 102 moves into shell scripting, interfaces and desktops, administrative tasks, essential system services, networking fundamentals, and security.
Study them in sequence unless your work experience gives you a strong reason not to. Exam 101 supplies the command, filesystem, package, and boot knowledge that makes many exam 102 tasks easier to understand. For example, networking troubleshooting is more manageable when you already understand processes, logs, configuration files, permissions, and text-processing commands.
The five-year validity period applies to LPIC-1. LPI also publishes options for extending beyond five years, so check the certification page when planning a renewal rather than relying on an older training provider’s policy.
Which LPIC-1 objectives deserve the most study time
Use the official objective weight as a prioritization signal, not as a substitute for full coverage. LPI states that higher-weight objectives are covered by more questions. Begin with high-weight objectives that combine frequently used commands with troubleshooting decisions, then cover lower-weight areas so that small topics do not become avoidable gaps.
For exam 101, the published objectives include GNU and Unix Commands, Devices and Linux Filesystems, Linux Installation and Package Management, and System Architecture. Within those domains, 103.3 Perform basic file management has Weight 4, 103.4 Use streams, pipes and redirects has Weight 4, and 103.5 Create, monitor and kill processes has Weight 4. These are practical command-line skills and should be exercised repeatedly rather than learned as isolated definitions.
For exam 102, 107.1 Manage user and group accounts and related system files has Weight 5, while 105.1 Customize and use the shell environment has Weight 4, 105.2 Customize or write simple scripts has Weight 4, 107.2 Automate system administration tasks by scheduling jobs has Weight 4, 108.2 System logging has Weight 4, 109.1 Fundamentals of internet protocols has Weight 4, 109.2 Persistent network configuration has Weight 4, and 109.3 Basic network troubleshooting has Weight 4.
Do not interpret a lower weight as permission to ignore an objective. For example, 102.6 Linux as a virtualization guest has Weight 1, but the topic can still expose whether you understand how a guest system differs from a physical host. Similarly, 106.2 Graphical Desktops has Weight 1, yet the objective expects awareness of major Linux desktops and remote desktop access protocols.
Make a study table with four columns: objective number, commands and files, your confidence, and the laboratory task that proves competence. A topic remains unfinished if you can define it but cannot complete the corresponding task without copying a solution.
Exam 101: build the system and control it
Start exam 101 with system architecture, boot, storage, and package management because these subjects explain how Linux becomes a functioning system. Practice identifying hardware through /proc, /sys, lspci, and lsusb; tracing the boot process; distinguishing BIOS and UEFI concepts; and relating the bootloader, kernel, initramfs, and init system.
Build a disposable virtual machine and deliberately inspect its partitions, filesystems, mount points, swap, and boot configuration. Practice both creating and checking filesystems and maintaining their integrity. Know the role of /etc/fstab, mount, umount, blkid, and lsblk, and be able to reason about what happens when a mount entry is wrong.
Package management should be comparative. Use a Debian-family environment to inspect and install packages with dpkg, apt-get, and apt-cache. In another suitable environment, inspect RPM packages and use the RPM, YUM, or Zypper concepts named by the objectives. Record the difference between package content, installation status, dependencies, integrity, and repository metadata.
The command domain is where passive study fails most visibly. Build short tasks around quoting, environment variables, command substitution, globbing, standard input and output, pipes, redirection, filters, regular expressions, file operations, process control, and vi. Keep a notebook of errors: the cause, the diagnostic command, the corrective command, and the result.
Exam 102: administer users, services, networks, and security
Exam 102 rewards a connected view of administration. A user account affects files and permissions; a scheduled task produces logs; a network service depends on name resolution and ports; and a security decision often requires checking processes, ownership, access rights, and configuration files together.
For account work, practice with /etc/passwd, /etc/shadow, /etc/group, and /etc/skel, along with useradd, usermod, userdel, groupadd, passwd, chage, and getent. Create test users, change account state, set group membership, inspect password-aging information, and verify the result. Never perform these exercises on a production machine.
Shell scripting should be small and purposeful. Write scripts that accept arguments, test conditions, use loops, return meaningful exit statuses, and safely process filenames. Then schedule harmless versions with cron, systemd timers, and at. Check both the schedule and the execution evidence; a job that exists but never runs is not a completed administration task.
Networking preparation should follow a diagnostic chain: confirm the interface and address, inspect routes, test local reachability, test name resolution, and then investigate the remote service. The objectives name tools including ip, hostname, ss, ping, ping6, traceroute, tracepath, netcat, nmcli, host, dig, and getent. Learn what question each tool answers instead of memorizing an undifferentiated command list.
Security topics should be practiced through review. Inspect permissions and ownership, account access, listening sockets, sudo configuration, login history, host restrictions, and encryption-related tools. The objective 110.1 Perform security administration tasks has Weight 3, 110.2 Setup host security has Weight 3, and 110.3 Securing data with encryption has Weight 4. Keep your notes focused on purpose, risk, and verification.
How to turn the objectives into a working laboratory
A small disposable Linux laboratory is more useful than a large collection of disconnected notes. Use virtual machines or another isolated environment that lets you reset changes, and maintain at least one Debian-family system plus an RPM-family system if possible. The objective is not to reproduce a particular enterprise; it is to make configuration changes, break them safely, and observe the evidence.
Create a baseline checklist before changing anything: hostname, addresses, routes, mounted filesystems, available packages, running services, users, groups, permissions, logs, and scheduled jobs. Save command output where appropriate. After every change, verify the intended state and record what would reveal failure.
Use scenario-based exercises rather than command drills alone. Examples include a user who cannot access a shared directory, a service that is listening on the wrong address, a DNS client that resolves some names but not others, a scheduled backup that runs manually but not automatically, or a full filesystem that causes a service to fail. These scenarios use multiple objectives in the way real troubleshooting does.
Keep the laboratory ethical and reversible. Do not scan systems you do not own, alter workplace accounts, test destructive filesystem operations on important storage, or copy private configuration data into study notes. Use synthetic users, local services, and disposable files.
A repeatable practice record
For each objective, write the task in operational language: “identify the process using the port,” “configure persistent name resolution,” or “restore access to a file without giving excessive permissions.” Then list the expected evidence, the commands you would use, and the mistake you are likely to make.
After completing the task, close the terminal and reproduce it from memory. Explain why each command was chosen, which alternative would also work, and what result would indicate that the diagnosis is wrong. This exposes memorized sequences that are not yet understanding.
Return to failed tasks after a gap. A task that succeeds only while the answer is open should remain in your review queue. Your progress measure should be independent reconstruction and verification, not the number of pages read.
A practical LPIC-1 study roadmap
Plan around the two exam boundaries, not around a single giant list. Finish a first pass of the relevant objectives, build and troubleshoot the lab, then use targeted review to remove weak areas. Do not schedule an exam solely because you have completed a textbook; schedule when you can demonstrate the skills and explain the underlying choices.
In the first phase, establish command-line fluency. Cover navigation, help, files, permissions, text streams, filters, regular expressions, processes, and vi. Create a one-page command map, but attach each command to a task and expected output. If basic shell work is slow, delay exam scheduling and repair that foundation first.
In the second phase, complete exam 101. Work through architecture, boot, partitioning, filesystems, mounting, package tools, shared libraries, virtualization guests, and the Filesystem Hierarchy Standard. Mix reading with lab sessions. At the end of the phase, perform a clean build or configuration exercise without following a step-by-step guide, then troubleshoot one deliberately introduced fault.
In the third phase, complete exam 102. Study shell environment and scripting before administrative automation. Then connect users and groups with permissions, system time and localization with services, logging with troubleshooting, and network fundamentals with persistent configuration and DNS. Finish with security review rather than leaving it as a final memorization block.
In the final phase, use the objective list as an audit. Mark each objective as demonstrated, understood but unpracticed, or unclear. Revisit every unclear item using the official learning materials and the relevant objective page. Use practice questions only to identify gaps; do not treat recalled questions, dumps, or memorized answer patterns as proof of readiness.
A useful weekly rhythm is one reading session, two laboratory sessions, one troubleshooting session, and one recall session. Adjust the rhythm to your schedule. The important decision is to reserve time for hands-on verification and spaced review instead of allowing all preparation time to become passive reading.
How to decide whether to schedule exam 101
Schedule exam 101 only after you can move from symptom to diagnosis across the core system domains. You should be able to inspect a machine, explain its boot and storage layout, manage packages in the environments you studied, manipulate text and files, and control processes without depending on a copied command sequence.
Before scheduling, conduct a closed-book review of all exam 101 objectives. For every weak objective, complete one lab task and one explanation task. The explanation should cover the relevant files, utilities, expected state, and a safe recovery path. If your weakness is concentrated in high-weight command topics, prioritize those before polishing minor terminology.
How to decide whether to schedule exam 102
Schedule exam 102 when you can administer a small practice system as a connected set of users, services, logs, and network settings. In particular, verify that you can create and modify accounts, write basic shell scripts, schedule jobs, inspect logs, configure networking persistently, troubleshoot DNS and connectivity, and review basic host security.
Use the same objective audit after exam 101 rather than assuming that passing the first exam proves readiness for the second. Exam 102 introduces its own command vocabulary and configuration relationships. A candidate who is strong at file operations but has never configured or diagnosed a network client should treat that gap as a scheduling issue, not as a minor review item.
Official learning materials and how to use them
LPI’s Learning Materials are free teaching resources for teachers and students, and LPI says they are designed to prepare candidates for its exams. They are continuously expanded and updated, and the material addresses the objectives in their current version. Use them as the central reading source, then verify that your copy and objective list correspond to the exam version you intend to take.
The materials separate explanations, exercises, and solutions. Use that structure actively: read only enough to understand the concept, attempt the exercise without looking at the solution, and compare not only the final answer but also the reasoning and verification step. A lesson is designed for 1-2 class hours, which can help you divide study into manageable units without treating that design as a promised personal completion time.
The official objective page is the authority for your coverage map. Read the description and the listed commands, files, terms, and utilities for each objective. Some objectives contain partial lists, so do not assume that the visible utility list is a complete set of possible knowledge. Use it to define the subject boundary and then practice the underlying task.
Training is optional. A course or training partner can provide structure, instructor feedback, and a laboratory, but it does not replace reading the current objectives. Ask any provider which LPIC-1 version it covers and how it handles both exam 101 and exam 102 before paying or committing to a schedule.
Delivery, languages, and scheduling checks
LPI offers LPIC-1 through Pearson VUE test centers and through the OnVUE online-proctoring system. The current official LPIC-1 page lists test-center languages as English, German, Japanese, Portuguese (Brazilian), Chinese (Simplified), Chinese (Traditional), and Spanish; it lists online languages as English, German, Japanese, Portuguese (Brazilian), and Spanish. Confirm availability for your location before booking.
OnVUE is not merely a different website for the same preparation decision. LPI states that the platform is available in English and that candidates need a quiet, private location, a reliable computer with a camera, and a stable Internet connection. The online-testing page states that Windows and MacOS are currently supported, so a Linux study machine cannot be assumed to be an eligible online testing device.
LPI states that exam prices and lengths remain the same on OnVUE as in test centers, but the actual price is country-specific. Use LPI’s official certification page and the Pearson VUE scheduling information for current fees, appointment availability, system requirements, identification rules, and policies. Do not rely on an old voucher page or a forum post for these details.
For a non-English exam, separate the exam language from the proctoring language. The language availability of the test and the language used by the online-proctoring platform are distinct practical considerations. If your preferred language is not shown for your selected delivery method, check a test center rather than assuming that OnVUE offers it.
Common preparation mistakes that waste time
The most damaging mistake is studying the command list without studying the administrative decision behind it. LPIC-1 does not become easier because you can recite utilities. For each command, ask what state it inspects or changes, what permissions it needs, and how you would verify success.
Do not study only one Linux distribution. Distribution-specific practice is useful, but LPIC-1 includes both Debian and RPM-family package management and covers concepts that appear across installations. Compare names, configuration locations, and package workflows while keeping the underlying administrative purpose in view.
Do not postpone networking and security because they seem less familiar. Networking fundamentals, persistent configuration, DNS, logs, accounts, permissions, and host security are easier when practiced in short recurring sessions. Leaving them until the final week creates a vocabulary problem and removes time for troubleshooting.
Do not confuse a successful demonstration with a safe administration method. A command that works as root may hide a permission mistake; a broad permission change may solve access while weakening security; and a manual service restart may conceal a broken persistent configuration. Include least-privilege reasoning and verification in your lab notes.
Do not use exam dumps or leaked-question collections. They are not a substitute for the published objectives or operational understanding, and memorizing unauthorized material cannot guarantee a pass. Use legitimate exercises and practice questions to locate weak concepts, then return to the objective and perform the task in your own laboratory.
Finally, do not let scheduling pressure determine readiness. A voucher purchase, a target date, or a completed video playlist is not evidence that you can troubleshoot. If your objective audit shows several unclear topics, change the study plan before changing the appointment.
What to do in the final review
The final review should reduce uncertainty, not introduce a new curriculum. Re-read the current objectives, rehearse your weak laboratory tasks, and review compact notes on files, utilities, option meanings, service relationships, and diagnostic order. Keep the last review focused on retrieval and correction rather than all-night coverage.
Separate recognition from production. Multiple-choice options may make a concept look familiar, while fill-in-the-blank prompts require you to retrieve the exact command, file, term, or value. Practice both explaining a solution and writing the essential command or configuration element without a prompt.
Review confusing pairs deliberately: hard and symbolic links, absolute and relative paths, standard output and standard error, package installation and package querying, a route failure and a DNS failure, authentication and authorization, a running process and a listening service, and temporary versus persistent network configuration.
Prepare a short exam-time method without claiming that it will predict the result. Read each prompt carefully, identify the objective area, eliminate answers that change the wrong layer of the system, and return to uncertain items if the interface permits. Do not spend preparation time trying to reconstruct live questions.
Next actions for an LPIC-1 candidate
Start with the official LPIC-1 overview and the current exam 101 and 102 objectives. Confirm that your intended codes are 101-500 and 102-500, choose whether you need both exams now, and create an objective-by-objective gap list before selecting a course, book, or appointment.
Then set up a reversible laboratory and begin with the weakest prerequisite rather than the most interesting advanced topic. Work through the official Learning Materials, complete exercises without copying solutions, and keep evidence of what you can reproduce. When every objective has a demonstrated task or a deliberate review plan, check the delivery language, computer requirements, local price, and appointment options through the official scheduling route.
If your current skills are limited to basic navigation and command-line exploration, begin with Linux Essentials and use it as a foundation. If you already perform routine Linux maintenance and want a professional, vendor-neutral validation, proceed with LPIC-1. If you are considering LPIC-2, first confirm the LPIC-1 requirement and finish the two LPIC-1 exams rather than mixing advanced topics into an unfinished foundation.
Conclusion
LPIC-1 preparation is strongest when the published objectives become a sequence of observable administration tasks. Select the certification level that matches your current command-line experience, study exam 101 and exam 102 as related but separate targets, prioritize higher-weight objectives without skipping the rest, and use a disposable laboratory to verify every important claim. Before scheduling, confirm the current version, delivery method, language, and technical requirements through LPI and Pearson VUE. That process gives you a defensible readiness decision instead of a guess based on study hours or recalled questions.