102-500
LPIC-1 Exam 102, Part 2 of 2, version 5.0
LPIC-1 Exam 102 Version 5.0: Practical Study Guide for Part 2 of 2
LPIC-1 Exam 102 validates the second half of the Linux administrator foundation: shell use and scripting, desktop interfaces, account administration, essential services, networking fundamentals, and security. It serves candidates pursuing the LPIC-1 certification, which requires passing both Exam 101 and Exam 102, with no certification prerequisites listed by LPI. This guide helps you decide whether your current skills are ready for 102-500, which objectives deserve the most study time, how to practise safely, and when to schedule the exam through an available delivery route.
What LPIC-1 Exam 102 validates
Exam 102 tests whether you can maintain and configure a Linux system beyond basic command use. LPI describes LPIC-1 as validating command-line maintenance, Linux installation and configuration, and basic networking; Exam 102 concentrates on the operational tasks that turn those foundations into routine administration. It is not a test of one vendor’s distribution alone.
The certification relationship
Exam 102 is Part 2 of 2 for LPIC-1. Passing this exam alone does not complete the certification: LPI requires both the 101 and 102 exams. LPI lists no prerequisites for the certification. If you have not passed Exam 101, treat 102 preparation as a parallel part of the certification plan rather than as a standalone credential decision.
Who should use this guide
This guide is most useful for Linux users who already understand basic shell navigation and want to measure themselves against the version 5.0 objectives. It also suits administrators moving between distributions, because the objectives emphasize common Linux skills while including Debian, RPM-based, systemd, networking, desktop, and security concepts.
What the version 5.0 label means
LPI identifies the current version in the supplied exam information as 5.0, with exam code 102-500. The version update increased systemd coverage, redesigned networking around concepts, configuration, and troubleshooting, and added an objective concerning Linux as a virtualization guest. Use the version 5.0 objectives as your study boundary instead of older 4.x material.
How the Exam 102 blueprint is organized
The blueprint contains six domains: Shells and Shell Scripting, User Interfaces and Desktops, Administrative Tasks, Essential System Services, Networking Fundamentals, and Security. LPI assigns each objective a weight; higher-weighted objectives are covered by more exam questions, so your revision time should follow the objective weights rather than the apparent familiarity of a topic.
Topic 105: Shells and Shell Scripting
Topic 105 covers 105.1, customizing and using the shell environment, and 105.2, customizing or writing simple scripts. Both objectives have Weight 4. Practise the relationship between startup files, variables, aliases, functions, quoting, positional parameters, tests, loops, and command exit status rather than memorizing isolated command definitions.
Topic 106: User Interfaces and Desktops
Topic 106 covers installing and configuring X11, graphical desktops, and accessibility. Objective 106.1, Install and configure X11, has Weight 2; 106.2, Graphical Desktops, has Weight 1; and 106.3, Accessibility, has Weight 1. This domain is smaller by objective weight, but it remains a defined part of the exam and should not be skipped.
Topic 107: Administrative Tasks
Topic 107 covers user and group accounts, scheduled administration jobs, and localisation and internationalisation. Objective 107.1, Manage user and group accounts and related system files, has Weight 5; 107.2, Automate system administration tasks by scheduling jobs, has Weight 4; and 107.3, Localisation and internationalisation, has Weight 3. This is a high-priority study area.
Topic 108: Essential System Services
Topic 108 covers system time, logging, MTA basics, and printing. Objective 108.1, Maintain system time, has Weight 3; 108.2, System logging, has Weight 4; 108.3, Mail Transfer Agent basics, has Weight 3; and 108.4, Manage printers and printing, has Weight 2. Give logging and time configuration hands-on attention.
Topic 109: Networking Fundamentals
Topic 109 covers internet protocols, persistent network configuration, basic network troubleshooting, and client-side DNS. Objective 109.1, Fundamentals of internet protocols, has Weight 4; 109.2, Persistent network configuration, has Weight 4; 109.3, Basic network troubleshooting, has Weight 4; and 109.4, Configure client-side DNS, has Weight 2. Study this domain as a troubleshooting sequence, not as a port-number list.
Topic 110: Security
Topic 110 covers security administration, host security, and encryption. 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. The highest-weight objective requires public-key techniques for securing data and communication, so include SSH and key-management practice in your lab work.
What to practise in the shell first
Start with shell behavior before writing scripts. You should be able to explain where an environment variable comes from, how quoting changes expansion, how a command is located, and which startup file affects a shell. Then combine those ideas in short scripts that read input, test conditions, loop over values, and return a meaningful status.
Shell environment decisions
Work through env, export, set, unset, type, which, pwd, history, and the relevant Bash startup files. Compare a variable that exists only in the current shell with an exported variable visible to a child process. Test aliases and functions separately, and use source when you need to apply a changed file in the current shell.
Filters, redirection, and pipelines
Although text filters and streams are introduced in the broader LPIC-1 command objectives, Exam 102 scripting depends on using them accurately. Build commands with standard input, standard output, standard error, pipes, tee, and xargs. Check what happens when a filename contains whitespace, when a command produces no output, and when output is appended rather than replaced.
Simple Bash scripts
Write small scripts rather than copying large automation projects. Include a shebang, quoted variables, an if statement, a for or while loop, read, test expressions, command substitution, and the logical operators || and &&. Use positional parameters and check whether required arguments were supplied. The goal is to predict execution and repair a short script under pressure.
Common shell mistakes
Candidates often confuse shell variables with environment variables, treat a string as an integer without testing it, omit quotes around expansions, or assume that a command’s output is the same as its exit status. Keep a mistake log containing the command, the observed result, the reason, and a corrected version. Review that log instead of rereading every chapter.
How to prepare for administrative tasks
Make account administration the first major lab because it has the highest listed objective weight in Exam 102. Create disposable users and groups, change account properties, suspend and restore access, inspect the associated files, and schedule jobs under controlled conditions. Perform each task first manually, then explain which file or service records the result.
Users, groups, and account files
Study /etc/passwd, /etc/shadow, /etc/group, and /etc/skel together with getent, useradd, userdel, usermod, groupadd, groupdel, groupmod, passwd, and chage. Practise distinguishing identity data, password-aging data, group membership, and the files copied into a new home directory. Avoid changing important accounts in your main workstation.
Scheduled administration
Use crontab and at in a disposable environment, and compare recurring jobs with one-time jobs. Learn the purpose of /etc/crontab, the cron allow and deny files, the cron directories, and the user spool. Include systemd timers and systemd-run in your study because version 5.0 expanded systemd-related coverage. Verify a job’s command, environment, output destination, and permissions rather than assuming it ran.
Locale, language, and time-zone behavior
Practise reading locale output and identifying the roles of LANG, LC_*, LC_ALL, and TZ. Relate these settings to date formatting, character encoding, and command output. Review timedatectl and the locations associated with time zones, but keep time-zone selection separate from clock synchronization. This distinction prevents a correct clock from being mistaken for a correctly localized system.
How to study essential system services
Study essential services through evidence: identify the configuration file, generate or locate an event, inspect the service’s state, and explain the expected result. This method connects commands with administration decisions. Prioritize system logging and system time, then cover mail-transfer and printing basics without spending time on configuration that the objective explicitly does not require.
Time maintenance
The objective includes maintaining system time and synchronizing the clock through NTP. Practise date, hwclock, timedatectl, and the concepts represented by ntpd, ntpdate, chronyd, and chronyc. Review /etc/timezone, /etc/localtime, /etc/ntp.conf, and /etc/chrony.conf. Be able to distinguish the hardware clock, system clock, time zone, and synchronization service.
Logging and rotation
Learn the relationship among rsyslog, /etc/rsyslog.conf, /var/log, logger, logrotate, /etc/logrotate.conf, and files under /etc/logrotate.d/. Also practise reading the journal with journalctl and sending messages with systemd-cat. A useful lab exercise is to create a test message, locate it, identify its source, and explain how rotation affects retained logs.
MTA and printing scope
For MTA basics, know the commonly available programs postfix, sendmail, and exim, together with forwarding, aliases, mail, mailq, newaliases, and the sendmail emulation layer commands. The objective does not require MTA configuration. For printing, practise CUPS queue and job concepts plus the LPD compatibility commands lpr, lprm, and lpq, using the listed CUPS configuration locations as reference points.
How to build networking troubleshooting skill
Use a layered diagnostic order: identify the interface and address, check local reachability, test routing, test name resolution, and then test the application or service. This sequence keeps a DNS symptom from being confused with a link failure. The objectives cover both persistent configuration and troubleshooting, so practise restoring a working configuration after reboot rather than making only temporary changes.
Protocol fundamentals
Review IPv4 and IPv6 addressing, subnetting, TCP, UDP, and ICMP. Learn the common TCP and UDP ports and services named by LPI, including 22 for SSH, 53 for DNS, 80 and 443 for web services, and 123 for network time. Keep each port attached to its protocol and service; do not memorize an unlabeled number list.
Persistent host configuration
Practise hostname and host-file behavior with /etc/hostname, /etc/hosts, /etc/nsswitch.conf, and /etc/resolv.conf. Learn the role of hostnamectl, nmcli, ifup, and ifdown, and understand the objective’s requirement to configure Ethernet and Wi-Fi using NetworkManager. Review awareness of systemd-networkd without assuming that every distribution uses the same network manager.
Troubleshooting tools
Use ip, hostname, ss, ping, ping6, traceroute, traceroute6, tracepath, tracepath6, and netcat in a deliberate sequence. Include the older tools named in the objectives, such as ifconfig, netstat, and route, so you can recognize their output and purpose. Record what each test proves and what it cannot prove.
Client-side DNS
Practise host, dig, and getent while examining /etc/hosts, /etc/resolv.conf, and /etc/nsswitch.conf. Test a local hosts entry, a resolver query, and name-service lookup through the configured resolution order. Include awareness of systemd-resolved. The practical decision is to identify whether the failure concerns local name data, resolver configuration, or network reachability.
What security preparation should include
Security preparation should focus on inspection and controlled configuration, not on memorizing slogans. Review account and service exposure, permissions, running processes, listening sockets, login history, and restricted access files. Then practise public-key encryption concepts and OpenSSH client use. Never experiment with access-control changes on a system whose recovery you cannot control.
Security administration and host controls
Use find, passwd, fuser, lsof, nmap, chage, netstat, sudo, su, usermod, ulimit, who, w, and last to investigate different aspects of a host. Review /etc/sudoers, /etc/nologin, /etc/passwd, /etc/shadow, service configuration, and the legacy access-control files named in the objectives. Tie each tool to a question: who can log in, what is listening, or which process holds a resource?
Encryption and OpenSSH
The encryption objective requires public-key techniques for securing data and communication. Practise the distinction between a private key, a public key, a remote host key, and an authenticated user key. Review basic OpenSSH client configuration and usage, and understand the role of OpenSSH server host keys. Use a local virtual machine or two disposable hosts so you can observe authentication without risking real credentials.
Security pitfalls
Do not treat a successful connection as proof that a host is secure, and do not confuse encryption with authorization. Avoid copying private keys into notes or repositories. When practising sudo, permissions, or login restrictions, keep a second administrative session available and record how to undo each change. The objective is basic host security awareness and administration, not a promise of complete system hardening.
How much attention to give X11 and desktops
Treat the desktop domain as a focused review rather than as a reason to build a full graphical workstation. You need to understand X11 installation and configuration, recognize major desktop environments, know remote-desktop access protocols, and demonstrate awareness of accessibility technologies. Short comparison notes and one controlled display-configuration exercise are more useful than broad desktop customization.
X11 and display concepts
Review /etc/X11/xorg.conf, /etc/X11/xorg.conf.d/, ~/.xsession-errors, xhost, xauth, DISPLAY, and X. Be able to describe how a display is selected, how authorization affects access, and where session errors may be investigated. Do not rely on one distribution’s graphical settings panel as a substitute for understanding the underlying concepts.
Desktop and accessibility coverage
Know the major desktop environments listed by LPI: KDE, GNOME, and Xfce. Review the purpose of XDMCP, VNC, SPICE, and RDP as remote-desktop or display-access technologies. For accessibility, learn the kinds of technologies that assist users with visual, auditory, motor, or cognitive needs. The objective calls for knowledge and awareness, so distinguish recognition from configuration depth.
A practical study roadmap
Use the roadmap as a sequence of evidence-producing study blocks. Begin with a baseline against every 102 objective, then spend most practice time on shell scripting, accounts, scheduling, logging, networking, and encryption. Finish with mixed troubleshooting and timed review. Schedule only after you can explain results from a clean lab rather than merely recognize familiar commands.
Phase one: establish the baseline
Read the official 102-500 objective list and mark each objective as known, partly known, or untested. For every partly known or untested item, write one task you should be able to perform or explain. Use the official Learning Materials page as your lesson index; it organizes Exam 102 under Topics 105 through 110 and links lessons for each objective.
Phase two: build the administration core
Work through shell environment and simple scripting first, followed by users and groups, scheduled jobs, time, logging, and networking. For each topic, use a repeatable cycle: read the objective, perform a small lab, deliberately introduce a harmless fault, diagnose it, and write a one-page command-and-file summary. This produces revision material tied to tasks rather than isolated definitions.
Phase three: cover the smaller domains
Review X11, graphical desktops, accessibility, MTA basics, printing, localization, and DNS after the core is stable. Smaller objective weights do not make these areas optional. Use comparison tables in your own notes: command versus purpose, configuration file versus service, temporary change versus persistent change, and symptom versus diagnostic test.
Phase four: integrate and test
Create mixed scenarios such as a user whose scheduled job fails because of environment differences, a host that reaches an address but cannot resolve a name, or a service whose evidence appears in a journal rather than a traditional log file. Explain your diagnosis aloud or in writing. Then use practice questions only to locate gaps, not as a replacement for reading objectives and performing tasks.
How to use a Linux lab safely
A disposable virtual machine is the most practical study environment for Exam 102 because it lets you change users, services, network settings, logs, and SSH keys without endangering a production system. Keep a snapshot or rebuild path, record the distribution and configuration assumptions, and compare behavior across systems only when the objective requires it.
Build task cards
Create one card for each objective with four fields: the administration goal, the relevant commands, the configuration files or output to inspect, and the recovery action. For example, a DNS card can separate /etc/hosts, /etc/resolv.conf, /etc/nsswitch.conf, host, dig, and getent. The card is complete only when you can explain why each item belongs there.
Test persistence
After changing a network setting, locale, scheduled job, service state, or mount-related configuration in your lab, reboot or restart the relevant service and verify the result. Many preparation errors come from practising a command that works for the current session while ignoring persistence. Label notes explicitly as temporary, session-based, user-based, or system-wide.
Keep the lab reversible
Use test accounts, test files, noncritical network interfaces, and local SSH endpoints. Before editing a configuration file, copy it or use version control inside the lab. Avoid disabling authentication, deleting system accounts, or changing boot settings on your daily machine. A lab that can be rebuilt quickly encourages more useful experimentation and fewer unsafe shortcuts.
Delivery, language, and scheduling decisions
LPI states that each LPIC-1 exam is 90 minutes and contains 60 multiple-choice and fill-in-the-blank questions. The overview lists test-center delivery through VUE and online delivery through OnVUE, with different language lists. Check the official overview when scheduling because availability, pricing, and local appointment details are not fixed by this guide.
Choosing a delivery route
For VUE test centers, LPI lists English, German, Japanese, Brazilian Portuguese, Simplified Chinese, Traditional Chinese, and Modern Spanish for LPIC-1. For OnVUE, LPI lists English, German, Japanese, Brazilian Portuguese, and Modern Spanish. Select the route and language that you can use accurately, then verify the current booking conditions directly with LPI before purchasing or scheduling.
Planning around the exam format
The stated 90-minute limit and 60-question format make concise reading and disciplined pacing important. Practise answering a question, identifying the exact objective it tests, and moving on when the wording is uncertain. Do not spend preparation time trying to predict live questions. Instead, train the ability to distinguish commands, files, outputs, and administrative outcomes.
Checking cost and validity
LPI directs candidates to check exam pricing in their country rather than publishing one universal price in the supplied facts. LPI lists the LPIC-1 validity period as 5 years and provides options for extending beyond 5 years. Confirm the current policy, voucher terms, and certification status on the official overview before making a purchase decision.
Mistakes that waste preparation time
The most expensive preparation mistakes are scope mistakes: studying an obsolete objective set, ignoring lower-weight topics, memorizing commands without testing their output, and treating practice questions as a substitute for administration skill. Correct these by anchoring every study session to the version 5.0 objectives and by requiring a lab result or written explanation for each topic.
Using old version material without checking it
Version 5.0 changed the emphasis on systemd, networking, graphical interfaces, and Linux in cloud or virtual-machine environments. LPI also states that deprecated topics were removed during the update process, with examples including SQL and disk quotas. Older books can still explain fundamentals, but compare their contents with the current objectives before assigning them study time.
Memorizing port numbers in isolation
A bare port list does not demonstrate network understanding. Attach each port to its protocol and service, then test the related troubleshooting question: is the service listening, is the route available, can the name resolve, and is the client using the expected protocol? This produces usable recall instead of fragile number matching.
Confusing distribution habits with objective knowledge
A command may be common on one distribution while another uses a different service manager or network tool. Learn the objective’s concepts, named utilities, and configuration locations, then note distribution-specific differences separately. Do not conclude that an item is irrelevant because your current workstation hides it behind a graphical tool.
Skipping explanation because a command worked
A successful lab command is only the beginning. Ask what changed, where the change is stored, which user or service reads it, how you would verify it after restart, and how you would reverse it. These questions expose shallow memorization and connect the listed utilities to real administrative decisions.
Final readiness check before scheduling
Schedule when your preparation evidence shows consistent coverage, not when you have finished a particular book. You should be able to map every Exam 102 objective to a task, explanation, or recognition exercise; complete mixed scenarios without a command reference; and identify the topics that still need targeted review. Verify delivery details with LPI immediately before booking.
Use an objective-by-objective checklist
For Topic 105, demonstrate shell customization and a simple script. For Topic 106, explain X11, desktops, remote access, and accessibility. For Topic 107, manage accounts and jobs and explain localization. For Topic 108, inspect time, logs, mail, and printing. For Topic 109, configure and troubleshoot networking and DNS. For Topic 110, review host security and use public-key concepts safely.
Run a last mixed session
Combine tasks from different domains so that you must choose the next diagnostic step rather than follow a chapter order. Include one account task, one scheduled task, one log investigation, one network failure, one DNS check, and one SSH or encryption exercise. Review mistakes by objective code and return to the official lesson only for the gaps you actually found.
Take the next administrative steps
Confirm that you are preparing for exam code 102-500 and that your LPIC-1 plan includes Exam 101 as well. Review LPI’s current overview for delivery languages, pricing, validity information, and scheduling links. Keep your final study session focused on weak objectives and sleep, equipment, or appointment arrangements rather than beginning an entirely new resource.
Conclusion
LPIC-1 Exam 102 is best approached as a task-and-evidence exam. Prioritize the higher-weight objectives in shell scripting, account administration, scheduling, logging, networking, and encryption, but retain coverage of every Topic 105–110 objective. Use the official version 5.0 objectives and Learning Materials as your source of truth, practise in a reversible lab, and verify current delivery details with LPI before scheduling. That process gives you a defensible readiness decision without relying on leaked questions or unsupported exam predictions.
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