LPIC-1 Exam 102 (102-500) Version 5.0: Practical Study and Scheduling Guide
LPIC-1 Exam 102, code 102-500, validates the second half of LPIC-1: shell use and scripting, desktop administration, routine system services, networking, and security. It is intended for candidates building practical Linux administration capability across distributions, not for memorizing isolated answers. This guide helps you decide whether your current Linux practice is broad enough for Exam 102, which objectives deserve the most lab time, and when to schedule the exam after checking LPI’s current delivery, language, pricing, and registration information.
What does LPIC-1 Exam 102 validate?
Exam 102 validates practical maintenance and administration skills that complement Exam 101. LPI describes LPIC-1 as covering command-line maintenance, Linux installation and configuration, and basic networking; Exam 102 concentrates on the administrative and operational tasks listed in Topics 105 through 110.
The exam is the second part of the LPIC-1 certification path. Passing Exam 102 alone does not grant LPIC-1: LPI requires candidates to pass both the 101 and 102 exams. LPI lists no prerequisites for the certification, so the relevant readiness question is not whether you hold another credential but whether you can work confidently with a Linux system and its configuration files.
The objectives are distribution-neutral in scope, but the command examples and configuration approaches can differ between Debian-family and RPM-based systems. Prepare by learning the underlying task first, then compare the relevant tools and file locations on at least one system from each family.
Who should take this exam, and what should they know first?
Exam 102 suits an administrator, support technician, junior engineer, or Linux learner who already has basic command-line familiarity and wants to demonstrate broader operational knowledge. It is also a sensible next step for someone who has completed Exam 101 preparation and needs to cover the second LPIC-1 objective set.
Prior experience is helpful but not an official prerequisite. A candidate starting from zero should first become comfortable navigating directories, reading manual pages, editing text files, using elevated privileges responsibly, and recovering from simple configuration errors. Without those foundations, the shell, networking, and security objectives become memorization exercises rather than connected skills.
Treat the exam as a skills-validation target rather than a substitute for production experience. The official objective pages describe knowledge areas and utilities; they do not promise that every listed command will appear in a particular form. Use the list to build capability, not to predict live questions.
What topics are measured in Exam 102?
The version 5.0 blueprint divides Exam 102 into six domains: Topic 105 Shells and Shell Scripting, Topic 106 User Interfaces and Desktops, Topic 107 Administrative Tasks, Topic 108 Essential System Services, Topic 109 Networking Fundamentals, and Topic 110 Security. Read the objective descriptions and key knowledge areas before choosing books, courses, or practice tests.
Topic 105 covers shell environment customization and simple Bash scripts. Topic 106 covers X11 installation and configuration, graphical desktops, and accessibility. Topic 107 covers user and group accounts, scheduled jobs, and localisation and internationalisation. Topic 108 covers system time, logging, MTA basics, and printing.
Topic 109 covers Internet protocol fundamentals, persistent network configuration, network troubleshooting, and client-side DNS. Topic 110 covers security administration, host security, and encryption. The official Learning Materials page follows this same structure and provides lessons for each objective, making it a useful study index rather than a replacement for hands-on practice.
How should objective weights change my study time?
Use objective weights to prioritise revision, not to ignore lower-weight domains. LPI states that higher-weighted objectives are covered by more exam questions, so a weight 5 objective should receive more deliberate practice than a weight 1 objective, while every objective still needs at least a basic review.
Topic 107, Administrative Tasks, gives 107.1 Manage user and group accounts and related system files Weight 5, making account administration a high-priority area. Topic 105 gives 105.1 Customize and use the shell environment Weight 4 and 105.2 Customize or write simple scripts Weight 4; both deserve repeated command-line practice.
Topic 109 assigns 109.1 Fundamentals of internet protocols Weight 4, 109.2 Persistent network configuration Weight 4, and 109.3 Basic network troubleshooting Weight 4. Topic 110 assigns 110.3 Securing data with encryption Weight 4. Topic 108 assigns 108.2 System logging Weight 4. These labels are more useful than comparing bare numbers because each weight belongs to a specific official domain.
A practical allocation is to spend the first pass across all domains, then devote extra lab cycles to the high-weight objectives where you make mistakes. Do not infer an exact question count for an individual objective from its weight; LPI only states the relative significance of the weights.
Which skills require real terminal practice?
The strongest preparation method is to turn every objective into a small administrative task, perform it in a disposable virtual machine, and record the command, configuration file, expected result, and recovery step. Reading a command list can establish recognition, but it does not prove that you understand permissions, environment inheritance, service state, or network troubleshooting.
For Topic 105, practise shell startup files, environment variables, aliases, functions, quoting, command lookup, and Bash control structures. Write short scripts that accept arguments, test conditions, loop over input, use exit status, and produce predictable output. Then deliberately introduce quoting or permission errors and diagnose them.
For Topic 107, create and modify users and groups, inspect the related account files, adjust password ageing, and test access without damaging the host. Practise cron, systemd timers, and at as different scheduling mechanisms. Keep a clear distinction between a recurring job, a one-time job, and a service-managed timer.
For Topic 108, configure and inspect time settings, generate and locate log entries, understand rsyslog and journal tools, and manage a print queue in a lab where possible. For Topic 109, configure a host, inspect interfaces and routes, test connectivity in layers, and separate name-resolution failure from transport failure. For Topic 110, review permissions and service exposure, use SSH-related tools, and practise public-key encryption concepts and operations covered by the objectives.
A command-and-file checklist worth building
Build the checklist from the official utility lists, but group commands by the problem they solve. For shell work, include source, env, export, set, unset, type, which, man, and history. For scheduled administration, include crontab, at, atq, atrm, systemctl, and systemd-run. For logging, include logger, logrotate, journalctl, and systemd-cat.
For networking, work with ip, hostname, ss, ping, traceroute or tracepath, netcat, nmcli, host, dig, and getent. Know the roles of /etc/hostname, /etc/hosts, /etc/nsswitch.conf, and /etc/resolv.conf. The objective list also includes common TCP and UDP ports; learn each port together with its service instead of memorizing an unlabelled sequence.
For security, review find, passwd, fuser, lsof, nmap, chage, sudo, su, usermod, ulimit, who, w, and last, then connect each tool to an administrative question. The official objectives also identify SSH client configuration and server host keys as knowledge areas.
How should you study the six Exam 102 domains?
Study in an order that builds dependencies: shell foundations first, account administration next, then services and networking, with desktops and security integrated into the lab. This sequence lets you automate routine work before you troubleshoot systems, while still returning regularly to the less familiar desktop and printing material.
Start with Topic 105. Environment variables, shell startup files, quoting, command substitution, pipelines, and exit status support later scripting and administration. Do not merely copy scripts. Explain what each expansion does, what happens in a different shell context, and how a failed command affects the script.
Move to Topic 107 and create a repeatable user-management exercise. Record the difference between changing an account, changing a group, locking access, and changing password ageing. Add a scheduled task that writes a timestamp to a log, then inspect the result. This links identities, scheduling, and logging in one controlled exercise.
Study Topic 108 by tracing information rather than memorizing daemon names. Set the system time zone, inspect time synchronisation configuration, send a test log message, identify where it is written, and review rotation concepts. Learn MTA basics as awareness and simple forwarding or alias work, because the objective does not require full mail-server administration. Practise CUPS and the LPD compatibility interface if you have access to a printer or a safe simulated queue.
Approach Topic 109 as a troubleshooting chain: interface and link, address, route, reachability, port, name resolution, and application protocol. Use the tools in that order when it makes sense. For Topic 110, connect account controls, permissions, exposed services, SSH, and encryption to the threat they address. The goal is to choose an appropriate control and understand its limits.
Give Topic 106 a focused review rather than allowing it to disappear behind command-line work. Know the purpose of X11 configuration, the broad characteristics of KDE, GNOME, and Xfce, remote desktop protocols listed in the objectives, and the role of accessibility technologies. These are awareness-heavy areas, but the objective wording still matters.
What is the most efficient preparation roadmap?
Use a four-stage roadmap: baseline, build, troubleshoot, and verify. The stages can be compressed or extended according to your experience, but do not skip the baseline. It tells you whether your weak areas are command recall, conceptual understanding, or the ability to diagnose a changing system.
Stage one is a blueprint audit. Download or print the official 102-500 objectives, mark each objective as confident, familiar, or weak, and note the distributions and tools in your lab. Check that your materials explicitly cover version 5.0 and Exam 102 rather than only LPIC-1 in general. The official Learning Materials page is a useful starting point because it lists lessons under Topics 105 through 110.
Stage two is structured construction. Complete shell and scripting exercises, then account and scheduling exercises. Follow with time, logging, networking, and security labs. Finish with X11, desktop, accessibility, MTA, and printing review. Keep a lab journal with four fields: task, command or file, observed result, and explanation. If you cannot explain a result, classify the objective as unfinished.
Stage three is fault isolation. Break one thing at a time: use an invalid DNS setting, stop a relevant service, create a permission mismatch, alter a scheduled job, or introduce a shell quoting error in a disposable environment. Practise identifying the symptom, selecting evidence, and restoring the known-good state. Avoid destructive experiments on a personal or production machine.
Stage four is verification. Revisit every objective, answer scenario questions without notes, and reproduce representative tasks from a blank terminal. Review mistakes by objective code, not by the order in which they occurred. Schedule only after you can explain why a command is appropriate and what evidence would show that it worked.
A final-week routine that exposes gaps
In the final week, stop collecting unrelated resources. Use the official objectives as the boundary, rotate through one high-weight objective and one neglected objective each study session, and practise writing exact command syntax from memory before checking documentation. Reserve time for language, delivery, and identification details on the official LPI pages.
Create a compact reference sheet for personal revision containing configuration-file purposes, command families, network troubleshooting layers, account-file relationships, and common service-management distinctions. Do not take unauthorised notes into the exam or rely on leaked questions. A reference sheet is valuable because creating it exposes ambiguity; it is not a substitute for knowing the material.
Use timed practice to improve decision-making, but treat third-party question banks as supplementary and potentially inaccurate. A practice score is not an official prediction unless LPI says it is. Analyse every guessed answer and every correct answer reached for the wrong reason.
What are the exam format and delivery options?
LPI states that each LPIC-1 exam lasts 90 minutes and contains 60 multiple-choice and fill-in-the-blank questions. Exam 102 is therefore a time-managed knowledge exam, not a lab exam. Practise reading the task precisely, identifying the requested command or concept, and moving on when a question is consuming disproportionate time.
LPI lists the current LPIC-1 version as 5.0, with exam codes 101-500 and 102-500. The official objectives page identifies Exam 102 as 102-500 and labels the objectives version 5.0. Confirm the code shown during registration so that your appointment matches the objective version you studied.
For VUE test-center delivery, 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. Delivery and language availability can change, so verify the current selection, technical requirements, appointment rules, and local pricing directly with LPI before purchasing or scheduling.
LPI directs candidates to country-specific exam pricing rather than publishing one universal price in the supplied facts. Check the official LPIC-1 overview and the scheduling route for your country. Do not base the decision on a reseller’s old price or an unofficial claim about availability.
How should you decide whether to schedule now?
Schedule when your evidence shows consistent performance across the blueprint, not when you have finished reading a book. A sensible readiness test is to start with a blank lab, complete representative shell, account, service, networking, and security tasks, and explain the related concepts without a command reference. Then confirm the appointment language and delivery option on LPI’s current pages.
You are probably not ready if you can recognise commands but cannot choose between them, if you confuse persistent and temporary network changes, or if a small configuration error leaves you without a recovery path. Other warning signs include knowing cron syntax but not permissions, knowing journalctl but not what evidence to search for, or memorising ports without understanding the service relationship.
Candidates who have passed Exam 101 should still audit Exam 102 independently. The exams cover different objective groups, and competence in GNU and Unix commands from Exam 101 does not automatically demonstrate scripting, user administration, DNS, logging, or encryption. If Exam 102 is your first LPIC-1 exam, plan the certification sequence around both exams rather than treating this exam as a standalone credential.
Common mistakes that waste preparation time
The most expensive mistake is studying a topic list without performing the associated task. Replace passive review with short, repeatable labs and keep the expected result visible. When a command fails, investigate the cause instead of silently copying a corrected version; the explanation is often the part that transfers to a new scenario.
Another mistake is over-specialising in one distribution. LPIC-1 objectives cover common Linux administration skills, while package, network, service, and configuration details can vary. Compare Debian package management with RPM, YUM, and Zypper objectives, and learn both the portable concept and the family-specific command pattern.
Do not treat every utility in an official partial list as an isolated flashcard. Ask what problem it solves, what input it expects, what privileges it needs, and how you would verify the result. For example, pair a DNS tool with the layer it tests, a logging tool with the destination it reads or writes, and an account command with the system files it changes.
Do not assume version 4.0 material is sufficient. LPI’s version 5.0 update increased systemd coverage, revised networking, and added Linux cloud and virtual-machine considerations. Use the version 5.0 objectives as the authority, especially where older study material still focuses on removed or reorganised content.
What should you do next?
Start with the official objective page and the English Exam 102 Learning Materials page, then create your confidence audit. Set up a disposable Linux lab, complete one task from each Topic 105 through 110, and record the gaps that appear. After that, allocate additional practice to the higher-weight objectives and revisit every weak objective before checking the official scheduling details.
Your immediate checklist is straightforward: confirm that you are preparing for 102-500; verify whether you need Exam 101 as well for LPIC-1; select a supported language and delivery route; check country-specific pricing; and schedule only after your lab and blueprint review support the decision. Keep the official objectives bookmarked because they are the appropriate reference when a training resource and the blueprint disagree.
Conclusion
LPIC-1 Exam 102 is best approached as a practical administration syllabus with a time-limited assessment at the end. Build working familiarity with shell scripting, accounts, scheduled jobs, logs, networking, and security; give lighter but deliberate attention to desktops, MTA basics, and printing; then verify every Topic 105–110 objective against version 5.0. Use LPI’s current pages to confirm registration details, and rely on demonstrated understanding rather than dumps or question memorization when deciding that you are ready.
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
