102-500
LPIC-1 Exam 102, Part 2 of 2, version 5.0
LPIC-1 Exam 102 Version 5.0: Practical Guide to Exam 102-500
LPIC-1 Exam 102, code 102-500, tests the second half of the LPIC-1 Linux Administrator certification: shell use and scripting, desktop systems, administration, essential services, networking, and security. It is intended for candidates who already understand the Exam 101 scope or are completing the two-exam certification requirement. This guide helps you decide whether your preparation should focus on command practice, objective-by-objective review, or scheduling logistics before you book the exam.
What Exam 102 validates
Exam 102 validates practical Linux administration across the command line, user and system administration, basic networking, services, and host security. LPI describes LPIC-1 more broadly as validating command-line maintenance, Linux installation and configuration, and basic networking configuration; Exam 102 concentrates on the second group of objectives in that certification.
The official objective set identifies this as version 5.0 and exam code 102-500. Exam 102 is not a replacement for Exam 101: candidates must pass both exams to obtain LPIC-1. LPI lists no prerequisites for the certification itself.
The version 5.0 update increased attention to systemd and related services, revised networking around concepts, configuration, and troubleshooting, and added an objective concerning Linux as a virtualization guest. Those changes matter when selecting study material: a resource built only around older objectives may omit material that belongs to this version.
Who should take it
This exam suits a Linux user moving toward administration, a support technician who needs distribution-neutral fundamentals, or an administrator completing LPIC-1 after Exam 101. It is also relevant to candidates who want a structured check of skills that span Debian-family and RPM-based systems rather than one vendor’s distribution.
There is no stated prerequisite, but that does not mean the exam is beginner-free. You will get more value from preparation if you can already navigate a Linux shell, read configuration files, and understand the basic filesystem and package concepts covered by Exam 101.
What you must know by topic
Use the official objectives as the controlling checklist. Exam 102 has six topic areas: Shells and Shell Scripting, User Interfaces and Desktops, Administrative Tasks, Essential System Services, Networking Fundamentals, and Security. The LPI Learning Materials page organizes its lessons under these same topics, making it a useful study sequence rather than just a reference list.
Topic 105: Shells and Shell Scripting
Topic 105 covers customizing and using the shell environment and customizing or writing simple scripts. Prepare to explain how shell startup files, variables, aliases, functions, and exported values affect a session. Practice reading a short Bash script line by line instead of memorizing isolated syntax.
A useful lab is to create a test account, compare an interactive shell with a login shell, and inspect the effect of files such as /etc/profile, /etc/bash.bashrc, ~/.profile, and ~/.bashrc. Then write small scripts using conditions, loops, positional parameters, command substitution, and exit status. Keep the lab disposable so that mistakes do not alter your everyday account.
Topic 106: User Interfaces and Desktops
Topic 106 covers installing and configuring X11, awareness of major graphical desktops, remote desktop access protocols, and accessibility. The objective is broader than naming a preferred desktop: you should understand the role of X11 configuration, display-related variables, authentication tools, and the distinction between desktop environments and remote-session protocols.
Review the listed environments and protocols, including KDE, GNOME, Xfce, XDMCP, VNC, Spice, and RDP. For X11, connect concepts such as DISPLAY, xhost, and xauth to the problem of allowing or refusing access to an X server. For accessibility, focus on awareness of the technologies and the administration purpose they serve rather than trying to turn this topic into a product-specific tutorial.
Topic 107: Administrative Tasks
Topic 107 covers user and group accounts, scheduled jobs, and localisation and internationalisation. User and group management is assigned Weight 5, while scheduling jobs is assigned Weight 4 and localisation and internationalisation Weight 3. LPI states that higher-weighted objectives receive more questions, so these are sensible candidates for early, hands-on study.
Build one administration exercise around /etc/passwd, /etc/shadow, /etc/group, and /etc/skel. Add, modify, suspend, and remove test accounts; inspect group membership with appropriate commands; and change password-aging settings. Separately, schedule a recurring task with cron, a one-time task with at, and a systemd timer. Record where each configuration is stored and how you verify that the job was accepted.
For localisation, change and inspect LANG, LC_* and LC_ALL values, then connect those settings to locale output, character encoding, dates, and time zones. Do not assume that changing a graphical desktop language is the same as configuring a process environment.
Topic 108: Essential System Services
Topic 108 covers system time, system logging, MTA basics, and printing. System logging is assigned Weight 4; system time is Weight 3, MTA basics Weight 3, and printing Weight 2. Treat this as an operations topic: learn where information is configured, which command inspects it, and what a sensible first diagnostic step would be.
For time, compare the purpose of the hardware clock, system clock, time-zone data, and NTP configuration. Practice identifying the role of date, hwclock, timedatectl, chronyc, and related configuration files listed in the objectives. The version 5.0 material specifically includes timedatectl and additional systemd-related coverage.
For logging, learn the relationship among rsyslog configuration, /var/log, logger, logrotate, and journalctl. A good exercise is to generate a test message, find it, and explain whether the message is being handled by a traditional log file, the systemd journal, or both. Review facility, priority, filtering, and rotation concepts without treating a single distribution’s defaults as universal.
MTA coverage is intentionally basic. Know the commonly available postfix, sendmail, and exim programs, the purpose of ~/.forward and aliases, and the basic mail and queue commands named by the objectives. Printing focuses on CUPS and the LPD compatibility interface, including queue and job management with commands such as lpq, lpr, and lprm.
Topic 109: Networking Fundamentals
Topic 109 covers Internet protocols, persistent network configuration, basic troubleshooting, and client-side DNS. Fundamentals of Internet protocols is assigned Weight 4, persistent network configuration Weight 4, basic network troubleshooting Weight 4, and client-side DNS Weight 2. This is the largest cluster of equally weighted operational objectives, so study it as a connected troubleshooting workflow rather than four unrelated chapters.
Review IPv4, IPv6, subnetting, TCP, UDP, and ICMP, along with the common ports and services named in the objectives. You should be able to reason from a symptom to a layer or dependency: a missing link, incorrect address, absent route, failed name lookup, or service that is not listening are different problems.
For persistent configuration, practice both the concepts and the tools listed by LPI. These include /etc/hostname, /etc/hosts, /etc/nsswitch.conf, /etc/resolv.conf, nmcli, hostnamectl, ifup, and ifdown. NetworkManager is explicitly included, while systemd-networkd is an awareness area. Use a virtual machine or isolated test network so that changing an address does not disconnect an important system.
Create a repeatable diagnostic order: inspect the local address and interface, check routes, test reachability by address, inspect listening sockets, test the path when appropriate, and only then investigate DNS if the symptom involves names. Practice with ip, ss, ping or ping6, traceroute or tracepath, and netcat. The commands are not interchangeable; your notes should state what evidence each one provides.
For client-side DNS, understand how /etc/hosts, /etc/resolv.conf, and /etc/nsswitch.conf interact, and practice host, dig, and getent. A frequent mistake is to treat a successful ping by address as proof that DNS works. It proves reachability to that address, not successful name resolution.
Topic 110: Security
Topic 110 covers security administration, host security, and encryption. Security administration and host security are assigned Weight 3 each, while securing data with encryption is assigned Weight 4. Prepare to explain how a configuration decision reduces exposure, limits access, or protects communication; merely recalling command names is less useful than understanding the condition each command investigates.
For security administration, review account status, open files and processes, network exposure, privilege delegation, and login history using the utilities listed in the objectives, including find, passwd, fuser, lsof, nmap, chage, sudo, su, ulimit, who, w, and last. Tie each tool to a question: who is logged in, what is using this file, which service is exposed, or which account policy applies.
Host security includes controls such as /etc/nologin, account files, service activation, systemd sockets, and the older hosts.allow and hosts.deny mechanisms named in the objective list. Learn the difference between awareness of a mechanism and a requirement to deploy it everywhere. In a real environment, the local security policy determines which controls are appropriate.
Encryption focuses on public-key techniques for securing data and communication. Review the purpose of key pairs, host keys, authentication, confidentiality, integrity, and trust. Include basic OpenSSH client configuration and usage, and understand the role of OpenSSH server host keys. Do not reduce this area to copying command recipes: be able to identify which key or trust relationship is involved in a scenario.
How to use objective weights without neglecting smaller areas
Weights should determine study emphasis, not define a pass strategy by themselves. LPI assigns each objective a weighting value and says that higher-weighted objectives are covered by more questions. Start with the highest-weighted objectives, but reserve review time for every listed objective because lower-weighted areas remain part of the blueprint.
A practical priority order
Begin with 107.1 Manage user and group accounts and related system files, assigned Weight 5. Next work through the Weight 4 objectives: 105.1 shell environment, 105.2 simple scripts, 108.2 system logging, 109.1 Internet protocols, 109.2 persistent network configuration, 109.3 network troubleshooting, and 110.3 encryption. This order is a recommendation based on the supplied objective weights, not an LPI promise about the exact distribution of questions.
Then cover Weight 3 objectives such as 107.3 localisation and internationalisation, 108.1 system time, 108.3 MTA basics, 110.1 security administration, and 110.2 host security. Finish the pass with Weight 2 and Weight 1 areas, including desktops, accessibility, printing, client-side DNS, and Linux as a virtualization guest. Keep a separate list of objectives that are knowledge-only or awareness-focused so you do not spend all your time building elaborate labs for them.
What not to infer from the weights
A weight is not a percentage, a pass mark, or permission to ignore another topic. The supplied official material does not provide a guaranteed question count for each individual objective. Avoid websites that convert objective weights into invented predictions about the exact exam. Use the weight only to allocate preparation time and to decide which weak areas deserve immediate practice.
A study method that produces usable recall
Study each objective in three passes: understand the concept, perform a controlled task, and explain the result without notes. This is more reliable than collecting command lists because Exam 102 connects configuration files, utilities, permissions, services, and troubleshooting decisions.
Build a two-system lab
Use at least one Debian-family environment and one RPM-based environment if you can do so safely. Exam 102 includes package and administration concepts that cross distributions, while the objective list names tools and files whose defaults may differ. A virtual machine is a practical recommendation, not an LPI delivery requirement; snapshot it before experiments involving users, services, networking, or boot configuration.
Keep a lab journal with four columns: task, command or file, expected evidence, and recovery step. For example, a logging task should record where the message should appear and how to inspect it; a DNS task should record whether the failure is name resolution or network reachability. This format turns mistakes into revision material.
Create explanation cards, not trivia cards
For every command, write the question it answers and one limitation. “What process owns this socket?” is better than memorizing ss as an isolated word. “Which startup file affects this kind of shell?” is better than memorizing a file path without context. Include pairs that are commonly confused, such as environment variables versus shell variables, cron versus at, and reachability versus name resolution.
Use the official partial lists of files, terms, and utilities as a boundary for command practice. The lists are not a substitute for the descriptions and key knowledge areas: a command may appear because you need to recognize its purpose, not because you must reproduce a long operational procedure.
Use retrieval and timed review
After studying a topic, close the reference and reconstruct the workflow from memory. Test yourself by asking what you would inspect first, what evidence would confirm the diagnosis, and what change would persist after reboot or a new login. Add short timed sets only after you understand the material; speed practice cannot repair a conceptual gap.
When reviewing practice questions, classify each error as a knowledge gap, a command-selection error, a reading error, or a time-management error. The remedy differs: revisit the objective for a knowledge gap, repeat the lab for command selection, annotate the wording for reading errors, and use shorter timed sets for pacing.
A staged roadmap to exam readiness
A useful roadmap moves from shell fluency to administration, then services and networking, and finally integrated security review. The exact calendar is your decision; LPI supplies the objectives and learning materials, not a universal preparation duration. Set a target date only after an initial diagnostic reveals how much of the six-topic scope you can already perform.
Stage one: establish the baseline
Read the version 5.0 objective list once without trying to memorize it. Mark each item as known, partly known, or unfamiliar. Run a small diagnostic: inspect a process, create a test user, read a log, examine an interface and route, resolve a name, and explain an SSH key’s role. Record what you could do unaided and what required a manual page.
If you have not passed Exam 101, stop and confirm the certification sequence before scheduling Exam 102. Exam 102 is the second exam, but its networking, filesystem, command-line, and installation concepts build naturally on the foundation represented by Exam 101.
Stage two: master the shell and administration core
Study Topics 105 and 107 together. Shell variables and startup files become more useful when you apply them to scheduled administration, user-specific environments, and small scripts. Write a script that validates input, reports errors, and performs a harmless file or account-related check in the lab. Then schedule it using more than one mechanism and compare the execution environment.
Spend extra time on user and group operations because 107.1 carries Weight 5. Verify every change by inspecting the relevant account or group data and by testing the resulting login or permission behavior. Never run destructive account or permission experiments on a production host.
Stage three: work through services and networking
Study Topics 108 and 109 as an incident sequence. Configure or inspect time, generate and query logs, then troubleshoot a deliberately misconfigured network in the lab. Follow the path from interface and address to route, socket, service, and DNS. This approach helps separate configuration knowledge from diagnostic reasoning.
Add the smaller service areas after the main workflow: MTA concepts, CUPS queue operations, desktop awareness, and accessibility. These topics are easy to postpone indefinitely because they may not be central to your current job, but the official blueprint includes them.
Stage four: integrate security and close gaps
Finish with Topic 110 and a second pass through every marked objective. Review how account management, permissions, services, logs, network exposure, SSH, and encryption interact. For each scenario, state the least invasive inspection step before proposing a change. This habit reduces the risk of confusing a symptom with a cause.
At this point, use a blank copy of the objective list as a readiness audit. You should be able to define the key term, identify the relevant file or utility, and describe a safe lab action for each objective. If one of those three is missing, schedule targeted review rather than booking solely because your general Linux confidence feels high.
Stage five: rehearse the session
LPI states that each LPIC-1 exam is 90 minutes and contains 60 multiple-choice and fill-in-the-blank questions. Use that official format for a final rehearsal: answer in a controlled sitting, flag uncertain items, and return to them after completing the questions you can solve confidently. Do not treat a practice score from an unofficial source as an official pass prediction.
Make your final revision compact. Review your error log, command distinctions, configuration-file purposes, and the objectives you repeatedly miss. Avoid learning an entirely new topic on the last study session unless it is a clear blueprint omission; consolidate first, then sleep and prepare for the appointment according to the delivery provider’s instructions.
Scheduling and delivery decisions
Verify delivery, language, price, and appointment information on LPI’s current certification page before purchase because these details can change. The supplied LPI overview identifies the current version as 5.0, exam codes 101-500 and 102-500, and states that certification requires passing both exams.
Exam format and language options
Each exam is listed as 90 minutes with 60 multiple-choice and fill-in-the-blank questions. For test-center delivery through VUE, LPI lists English, German, Japanese, Brazilian Portuguese, Simplified Chinese, Traditional Chinese, and Modern Spanish. For online OnVUE delivery, LPI lists English, German, Japanese, Brazilian Portuguese, and Modern Spanish.
Choose the language in which technical wording is clearest for you, not simply the language used by your study material. Confirm the available language and delivery option at the time you schedule. The official page is the authority for current availability.
Prerequisites, certification, and validity
LPI lists no prerequisites for LPIC-1, but the certification requirement is passing both Exam 101 and Exam 102. LPI lists the certification validity period as 5 years and provides options for extending beyond 5 years. These are certification-level details; passing Exam 102 alone does not confer LPIC-1.
Use the LPI page to check the current exam price in your country rather than relying on a third-party listing. The supplied official information directs candidates to country-specific pricing and does not establish a universal price.
Choosing a delivery route
A test center may suit candidates who want a dedicated examination location, while online delivery may suit candidates who meet the provider’s current technical and environmental requirements. The choice is practical, not a difference in blueprint scope. Check the official scheduling instructions, available language, identification requirements, and rescheduling rules before committing.
Do not schedule until your readiness audit covers all six Exam 102 topics. Conversely, do not postpone indefinitely while trying to make every command feel automatic. A sensible trigger is consistent performance on objective-based practice, the ability to complete the official time-and-question format in rehearsal, and no unresolved weakness in a high-weight objective.
Mistakes that waste preparation time
The most expensive preparation mistakes are usually organizational rather than technical: studying an obsolete objective set, confusing command recognition with administration ability, and spending all available time on familiar Linux tasks. Correct them by tying every study session to a version 5.0 objective and by requiring observable evidence from a lab.
Relying on an old blueprint
Version 5.0 changed the emphasis on systemd, revised networking, and added Linux-as-virtualization-guest coverage. It also introduced or expanded areas such as systemd mount units, timers, and timedatectl, while some older topics were removed. Check the version information on every book, course, and practice resource before using it as your primary guide.
Memorizing utilities without context
A list containing nmcli, journalctl, chage, dig, or ssh is not proof that you can administer a system. For each utility, know the administrative question, the relevant configuration, the expected output, and the risk of changing the system. Manual pages and controlled experiments are more valuable than copying commands into a notebook without running them.
Ignoring distribution differences
Do not assume that a command’s presence, service manager, configuration path, or default behavior is identical everywhere. Practice the cross-distribution concept and note implementation differences explicitly. This is especially important for package management, networking, logging, time synchronization, and service control. The exam objectives name both concepts and selected tools; your preparation should do both.
Treating practice questions as leaked content
Practice questions can reveal weak objectives, but they cannot guarantee the real exam’s wording or coverage. Avoid exam dumps, leaked questions, and memorization-based promises. Use legitimate practice only to test reasoning, then return to the official objective and reproduce the underlying task in your lab.
Your final readiness checklist
Before scheduling or sitting Exam 102, confirm that you can map each question type to an objective, perform the important operations safely, and explain why a selected command or file is relevant. This checklist is a practical recommendation; LPI does not publish it as a pass guarantee.
Knowledge and lab checks
You should be able to customize a shell environment and read or write a simple script; manage test users, groups, and password aging; schedule recurring and one-time tasks; inspect time and logs; explain MTA and printing basics; troubleshoot a network in a logical order; configure or diagnose client DNS; and distinguish host-security controls from encryption mechanisms.
Repeat the checks on a clean virtual machine or freshly reset snapshot. If your solution works only because of undocumented changes from earlier experiments, reset and document the required configuration. This exposes fragile understanding before the exam.
Source and appointment checks
Confirm that your materials identify LPIC-1 Exam 102 version 5.0 and code 102-500. Recheck the official LPI objectives and the Learning Materials page, then verify the current delivery language, location or online option, price, and appointment rules. Keep Exam 101 status and the two-exam certification requirement visible in your planning notes.
On the day before the appointment, stop expanding the scope. Review your error log and objective checklist, confirm the appointment details, and prepare the identification or technical setup required by the provider’s current instructions.
Where to continue after Exam 102
After completing Exam 102, use the same objective-based method to decide whether to consolidate LPIC-1 skills or move toward a higher-level Linux path. LPI describes LPIC-2 and LPIC-3 as higher-level certifications that can support progression toward senior IT administration, but the appropriate next step depends on your work responsibilities and gaps rather than on collecting credentials without practice.
Keep your lab available. The strongest follow-up is to turn the six Exam 102 areas into repeatable administration tasks: onboard and retire users, automate maintenance, diagnose network failures, review logs, secure remote access, and document changes. That work reinforces the exact command-line and system-configuration capabilities the certification is intended to validate.
Conclusion
LPIC-1 Exam 102 is best approached as an operations exam organized by a precise version 5.0 blueprint. Prioritize the high-weight administration, shell, logging, networking, and security objectives; use a disposable lab to verify behavior; and reserve time for the smaller desktop, printing, MTA, DNS, accessibility, and virtualization areas. Before booking, confirm the current LPI delivery details and audit every objective. The practical goal is not to recite commands, but to recognize a Linux administration problem, inspect the right evidence, and choose an appropriate action.
Related exams
- 101-500 exam — LPIC-1 Exam 101, Part 1 of 2, version 5.0
- 010-160 exam — Linux Essentials Certificate Exam - version 1.6