LPIC-1 helps structure the foundations of Linux administration: understanding the system, working in the terminal, and investigating problems without depending on a graphical interface. Good preparation requires more than memorizing options. You need to connect each command to a task, predict its effect, and check the outcome. This guide brings together the exam format, a study plan, and exercises you can safely repeat.
Reviewed on 12 September 2026. Check the objectives version before buying materials or booking. The plan and exercises below are LinuxPro editorial suggestions, not actual exam questions or a promise of passing.
How LPIC-1 works
The current version listed by LPI is 5.0: exams 101-500 and 102-500. You must pass both. Each exam has 60 multiple-choice and fill-in-the-blank questions and lasts 90 minutes. It is not a hands-on assessment in which you administer a machine during the exam.
There is no formal prerequisite: Linux Essentials can help build the foundations, but it is not mandatory. Certification validity is 5 years. The official page lists Brazilian Portuguese for both VUE test centers and OnVUE; confirm availability in your booking.
Budget for two exams and any possible retake. Check the price applicable to your country and the voucher conditions; a dollar conversion or an old blog price is not a definitive quote.
What to study for each exam
101-500: system, packages, and terminal
The syllabus combines architecture and boot, installation, packages, GNU/Unix commands, devices, filesystems, and the directory hierarchy. It includes the Debian and RPM families, libraries, processes, text filters, redirections, permissions, links, and editing with vi.
102-500: administration and services
The syllabus covers shells and scripts, interfaces and desktops, users, scheduling, localization, essential services, networking, and security. Do not skip X11/accessibility, printing, and email fundamentals just because your main lab is a server without a graphical interface.
Objectives have relative weights: higher values indicate greater exam importance, not permission to ignore smaller ones. Turn each subobjective into a verifiable task and also check the listed terms and utilities. This summary does not replace the full syllabus.
Build a lab where mistakes are safe
My suggestion is to use disposable virtual machines: one running Debian or Ubuntu and another running an RPM-based distribution. You do not need to keep both running at once. The aim is to compare behavior, package names, and tools without confusing one distribution with the entire Linux ecosystem.
Take snapshots before changing boot settings, disks, users, or networking. To practice partitioning, use an additional empty virtual disk; never copy formatting commands onto your work machine. Ensure you have access to the VM console before changing networking or SSH.
A terminal environment is sufficient for the file exercises below. Boot and disk practice needs an environment where you can observe startup and devices: do not treat a container as a complete VM replacement for those tasks.
A study plan in 6 stages
Use small deliverables as your progress criteria. The schedule depends on your experience; repeating a task and explaining the result is more valuable than merely marking lessons as watched.
- 1. Terminal and files: navigate without a graphical interface, read help, handle filenames containing spaces, and combine filters. Deliverable: produce a report from a test file and explain each stage.
- 2. System and packages: observe startup, inspect processes, and compare Debian and RPM tools. Deliverable: identify a package version and list its files without accidentally installing or removing anything.
- 3. Storage and access: practice mounting a training virtual disk, ownership, groups, and permissions. Deliverable: demonstrate who can read, write, and traverse a directory without granting everyone unrestricted permissions.
- 4. Shell and administration: write small scripts, examine exit statuses, and schedule a harmless task in a VM. Deliverable: a task that works outside the interactive terminal and records a verifiable result.
- 5. Networking, services, and security: distinguish addresses, routes, name resolution, and listening services. Deliverable: locate the layer responsible for a controlled failure while preserving console access and existing protections.
- 6. Review both exams: check less familiar topics, repeat exercises, and use legitimate practice tests. Deliverable: a short list of real gaps, with an action to address each one.
Starter lab: files, filters, links, and backup
Run this in Bash as a regular user on Linux with the usual GNU tools, tar, and diff installed. The steps create a new directory under your home directory and do not require sudo. Keep the same terminal and run the blocks in order.
1. Generate data and filter the result
LAB_DIR=$(mktemp -d "$HOME/lpic1-lab.XXXXXX") || exit 1
cd "$LAB_DIR" || exit 1
printf '%s\n' "$PWD"
cat > services.txt <<'EOF'
web:active
backup:inactive
ssh:active
web:active
EOF
grep ':active$' services.txt | cut -d: -f1 | sort | uniq -c
grep -c ':active$' services.txt
The first output should count one occurrence of ssh and two of web. The second should show 3 active lines. The pattern looks for the colon before active and the end of the line: searching only for active would also match inactive. Change the pattern and observe the difference.
2. Compare links and permissions
mkdir data
printf '%s\n' 'original' > data/note.txt
chmod 640 data/note.txt
ln data/note.txt data/hard.txt
ln -s note.txt data/symbolic.txt
ls -li data/
printf '%s\n' 'updated' >> data/hard.txt
cat data/note.txt
readlink data/symbolic.txt
The original file and the hard link share an inode on this filesystem; writing through one name changes the content seen through the other. The symbolic link stores a path. Permission 640 grants the owner read and write access, the group read access, and everyone else no access. Inspect the listing fields, not just the terminal colors.
The temporary directory created at the start also restricts access. This example therefore shows the file permission bits but does not demonstrate access by another user. For that test, use practice accounts in a VM and also check permissions on the directories along the path.
3. Back up and test restoration
tar -czf data.tar.gz data/
tar -tzf data.tar.gz
mkdir restored
tar -xzf data.tar.gz -C restored
diff -r data restored/data
The listing should show the archive members. The final comparison should produce no differences and exit with zero status. This checks the restored content but does not by itself validate every backup property, such as ownership, ACLs, or recovery of an entire system. Extract only the practice archive you created, inside the empty directory.
4. Write a script with a verifiable result
cat > check.sh <<'EOF'
#!/usr/bin/env bash
file=$1
if [ -f "$file" ]; then
printf 'OK: %s\n' "$file"
exit 0
fi
printf 'MISSING: %s\n' "$file" >&2
exit 1
EOF
chmod 700 check.sh
bash -n check.sh
./check.sh data/note.txt
if ./check.sh absent.txt >result.txt 2>error.txt; then
printf '%s\n' 'Unexpected success'
else
printf '%s\n' 'Expected failure'
fi
cat error.txt
The syntax check does not execute the script. The first run should print OK. The second should take the failure branch and write the message to error.txt; result.txt remains empty. This contrast helps explain the difference between standard output, standard error, and exit status. As a challenge, add a usage message when no argument is supplied.
Keep the path printed at the start so you can review the lab. All files remain in that directory; you do not need to run recursive cleanup to complete the exercise. To repeat from scratch, start again with the first block, which creates another directory.
Packages: compare queries, not just command names
In the respective VMs, query a known package without changing the system. On Debian or Ubuntu:
dpkg-query -W bash
dpkg-query -L bash
On the RPM-based VM with Bash installed:
rpm -q bash
rpm -ql bash
Compare the version and the files supplied by the package. Do not automatically treat the line count of package-manager output as the number of packages: headers and formats vary. Then, in a VM with a snapshot, practice installing and removing a nonessential package through the distribution’s package manager.
How to review without relying on rote memorization
- Practice active recall: close the material and explain which command you would use, which file you would change, and how you would validate it. Only then open the documentation to check the details.
- Create contrast flashcards: absolute and relative paths; hard and symbolic links; processes and services; installed packages and files available in a repository. The goal is to distinguish related concepts.
- Record actual lab errors with the symptom, cause, fix, and evidence. Repeat the task a few days later without copying the solution.
- Practice syntax and paths, including typing without autocomplete. Use man and command help to understand options; do not assume exam questions are literal copies of manuals.
- Use legitimate practice tests to find gaps and practice timing. Review why each alternative is wrong; avoid dumps, miracle targets, and promises of passing within a fixed period.
Study resources and preparation for exam day
Start with LPI’s own materials, organized by objective, and supplement them with manual pages from your lab distribution. Before choosing a course, check the version covered, the available exercises, and whether the syllabus includes both exams.
- LPI learning materials in Portuguese for exam 101-500
- LPI learning materials in Portuguese for exam 102-500
- LPI: official preparation guidance
When booking, check your name and identification, language, delivery format, rescheduling rules, and provider instructions. If you choose the remote option, complete the required compatibility tests in advance and prepare the environment according to current rules. Do not leave this until exam time.
After LPIC-1: choose your next direction
The best next step depends on the work you want to do. Compare the administration path with the DevOps tools path and deepen the topics you encounter in your routine. The credential can structure learning, but it does not replace practice, documentation, or care when operating real systems.