Linux Professional Institute 101-500 LPIC-1 System Administrator Exam 101, Part 1 of 2, version 5.0 Free Practice Test - 10 Questions
This practice set exercises key skills for the LPIC-1 101-500 exam, focusing on boot troubleshooting, systemd targets, filesystem integrity checks, SUID behavior, Debian package dependency resolution, command pipelines, process management with pkill, virtual filesystems like /proc, text filtering with grep -v, and archive extraction with tar. By working through these scenarios, you reinforce conceptual understanding and practical command usage. The set emphasizes common administrative tasks and potential pitfalls, such as the ignored SUID bit on scripts and the role of the fstab pass field. Use this study guide to solidify your ability to recall exact commands and rationale.
What this 101-500 practice set measures
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Boot Troubleshooting and Runlevels
The practice bank covers critical boot and runlevel concepts. In GRUB2, pressing 'e' allows editing kernel parameters before booting, which is essential for fixing a misconfigured X server. On systemd-based distributions, runlevel 5 maps to graphical.target, starting the GUI. Understanding these mappings between traditional runlevels and systemd targets is vital for controlling the system state. Recognizing that runlevel 3 is multi-user without GUI and runlevel 1 is single-user helps in recovery scenarios.
- GRUB2 edit key: 'e' to modify boot parameters.
- Systemd target for GUI: runlevel 5 / graphical.target.
- Non-GUI multi-user: runlevel 3 / multi-user.target.
- Single-user mode: runlevel 1 / rescue.target.
Filesystem Integrity and Permissions
The fstab 'pass' field (sixth column) determines the fsck order: 1 for root, 2 for other filesystems, 0 to skip. This ensures filesystem checks happen in the correct sequence. The SUID bit on shell scripts is ignored for security reasons; only binary executables can leverage SUID. Understanding these nuances prevents common configuration errors. The practice set also implicitly tests knowledge of mount options and dump frequency fields.
- fstab pass field: fsck order, 1=root, 2=others, 0=no check.
- SUID on scripts: ignored by Linux kernel; only works on binaries.
- Sticky bit: affects directory deletion, not script execution.
- Permissions: -rwsr-xr-x indicates SUID set, but irrelevant for scripts.
Debian Package Management and Dependencies
When dpkg reports unmet dependencies, 'apt-get install -f' (or 'apt --fix-broken') corrects them by installing missing packages or removing conflicting ones. This is a common fix after manual dpkg operations. The practice bank distinguishes this from 'dpkg --configure -a' which reconfigures unpacked packages without resolving dependencies. Understanding the Debian package management toolchain is essential for maintaining system stability.
- Fix broken dependencies: apt-get install -f or apt --fix-broken.
- dpkg --configure -a: configures unpacked packages only.
- apt-cache check: validates cache, does not fix issues.
- Always use apt after dpkg to resolve dependency chains.
Command Line, Process Management, and Text Processing
The practice set reinforces constructing command pipelines (e.g., ls -l | grep file | wc -l) to count filtered lines. For process control, 'pkill -P 1234' kills all children of a parent process, which is more precise than kill or killall. The /proc filesystem provides real-time kernel and process data, while /sys exposes hardware info. Text filtering with 'grep -v' inverts matches, showing lines without a pattern. These fundamental tools are frequently tested.
- Pipeline counting: pipe through grep then wc -l for line counts.
- Kill process tree: pkill -P <parent_PID> to target children.
- Virtual filesystems: /proc for processes/kernel, /sys for devices.
- Invert grep: grep -v pattern to exclude matching lines.
- Archive extraction: tar -xzf for .tar.gz files; -c creates, -x extracts.
Practice Linux Professional Institute 101-500 LPIC-1 System Administrator Exam 101, Part 1 of 2, version 5.0 with real flashcards
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 10-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
A Linux system fails to boot because of a misconfigured X server. Which key is typically pressed during the GRUB2 menu to edit the kernel line before booting?
Show hint
101.2 Boot the system
Study workflow
Turn one 101-500 attempt into a study plan
- 1
Edit Kernel Parameters in GRUB2 at Boot
When the system fails to boot due to a misconfigured X server, restart and press Shift or Esc to reach the GRUB2 menu. Highlight the desired entry and press 'e' to edit boot parameters. Navigate to the line starting with 'linux' and add or modify parameters (e.g., 'single', 'nomodeset'). Press Ctrl+X or F10 to boot with the changes.
- 2
Fix Broken Dependencies with apt
After a dpkg installation fails with unmet dependencies, run 'sudo apt-get install -f' (or 'sudo apt --fix-broken'). This command attempts to correct broken dependencies by installing missing packages or downgrading conflicting ones. It will automatically mark packages and complete the configuration. Then, resume normal installs with 'sudo apt-get install <package>'.
- 3
Kill a Process and All Its Children
To terminate a parent process (PID 1234) and all its children, first use 'pkill -P 1234' to kill all child processes. Then kill the parent process with 'kill 1234' or 'kill -15 1234'. Alternatively, use 'kill -9 1234' for forceful termination, but this does not handle children automatically. The pkill approach ensures a clean termination tree.
- 4
Extract a .tar.gz Archive
To extract the contents of 'backup.tar.gz', use 'tar -xzf backup.tar.gz'. The options: -x for extract, -z to decompress gzip, -f to specify the file. If the archive is not compressed, omit -z. For .tar.bz2 files use -j instead. Extracted files will appear in the current directory unless a path is included in the archive.
- 5
Use grep -v to Exclude Lines Matching a Pattern
To display lines from a log file that do not contain 'INFO', run 'grep -v "INFO" logfile'. The -v option inverts the match, showing only lines that do not match the pattern. This is useful for filtering out noise. Combine with other commands: 'grep -v "INFO" logfile | grep "ERROR"' shows errors while excluding info lines.
FAQ
Questions about this 101-500 practice page
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
Why does the SUID bit not work on shell scripts?+
Linux ignores SUID and SGID bits on interpreted scripts (like bash, perl) for security reasons. The kernel would have to trust the script's interpreter, which can be subverted easily. SUID only works on binary executables compiled from C or similar languages.
What are the exact commands to check and repair a filesystem?+
First, unmount the filesystem if possible (e.g., 'umount /dev/sda1'). Then run 'fsck /dev/sda1' to check and interactively repair. Use 'fsck -y' to auto-answer yes. The pass field in /etc/fstab determines the order of checks at boot. For the root filesystem, use a live CD or recovery mode.
How do runlevels map to systemd targets?+
Runlevel 0 maps to poweroff.target, 1 to rescue.target, 2-4 are typically multi-user.target (no GUI), 5 to graphical.target, and 6 to reboot.target. Use 'systemctl isolate graphical.target' or 'systemctl isolate multi-user.target' to switch between them.
What is the difference between /proc and /sys?+
/proc primarily provides process information and kernel parameters (e.g., /proc/cpuinfo, /proc/meminfo). /sys exposes hardware and device driver information (e.g., /sys/class, /sys/devices). Both are virtual filesystems in memory, but /proc is more process-centric while /sys is hardware-centric.
Can 'pkill -P' kill the parent process itself?+
No, pkill -P kills all child processes of the given parent PID, but not the parent. You must still kill the parent separately. This allows you to first terminate children cleanly, then handle the parent. For a complete termination, use pkill -P followed by kill on the parent.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.