Page 1 of 99
LINUX PROFESSIONAL INSTITUTE LPIC‑1: 150 HIGH‑FIDELITY PRACTICE
QUESTIONS – EXAM 101‑500 & 102‑500 READINESS ASSESSMENT EXAM
QUESTIONS WITH DETAILED- VERIFIED ANSWERS- ALREADY GRADED
A+ || NEWEST EXAM
Information Technology / Systems Administration / Network
Administration
• Practical, Scenario‑Based Questions: Over 70% of questions
present real‑world administrative tasks (troubleshooting boot
failures, configuring firewalls, managing user accounts, debugging
network issues) rather than rote memorization.
• Command‑Centric Focus: Heavy emphasis on standard Linux
utilities (find, grep, sed, awk, systemctl, ip, ss, iptables, lsof, tar,
cron) – mirroring the hands‑on nature of the LPI exams.
• Modern Tooling: Questions reflect current best practices using
systemd, journalctl, dnf/apt, iproute2, and timedatectl, avoiding
deprecated tools unless contrasted with modern equivalents.
• Security and Hardening: Includes SSH key management, SELinux
contexts, sudo configuration, password policies, and log
monitoring – essential for production environments.
• Troubleshooting Mindset: Many questions require diagnosing errors
from given outputs (e.g., kernel panics, DNS failures, mount errors),
cultivating analytical problem‑solving skills.
TOPIC 101: SYSTEM ARCHITECTURE
Q1. A system administrator is troubleshooting a USB device that is not
being recognized after hot-plugging. The administrator needs to examine
, Page 2 of 99
the kernel's dynamic device management system and the user-space
component that handles device events, permissions, and persistent
device naming. Which combination of subsystems and utilities would
provide the most comprehensive diagnostic information for this
scenario?
A. /etc/fstab, mount, and blkid – these handle static file system mounting
and block device identification, but do not manage dynamic device
events or permissions.
B. /proc/cpuinfo, lscpu, and dmidecode – these provide CPU and
hardware inventory information but are unrelated to USB device hot-plug
events.
C. /sys/, udev, and dbus ✔️ – sysfs (/sys/) exports kernel device
information; udev manages device nodes, permissions, and persistent
naming in user space; dbus facilitates communication between system
services and applications about device events.
D. /var/log/messages, syslog, and dmesg – these provide kernel ring
buffer and system log messages but do not manage device permissions
or persistent naming.
Rationale: The Linux device management architecture relies on sysfs
(/sys/) for kernel device representation, udev for dynamic device node
management and permission setting in user space, and dbus for event
notification to applications. Together, these provide comprehensive
diagnostic capability for USB hot-plug issues. The other options address
only logging or hardware inventory, not the complete device
management chain.
, Page 3 of 99
Q2. An administrator needs to identify all PCI devices connected to a
Linux system, including their vendor and device identification numbers,
to verify that a newly installed network interface card is properly
detected by the kernel. Which command provides the most detailed and
structured output for this purpose?
A. lsusb – this command lists USB devices, not PCI devices, and would
not show the network interface card if it is connected via PCI.
B. lscpi – this is a misspelling of the correct command and would not
execute.
C. lspci -v ✔️ – the lspci command with the verbose (-v) option displays
detailed information about all PCI buses and devices, including vendor
IDs, device IDs, IRQ settings, and I/O port addresses.
D. dmidecode – this retrieves hardware information from the DMI
(Desktop Management Interface) table, which includes system-wide
hardware data but does not provide the structured PCI device tree
output of lspci.
Rationale: lspci is the standard utility for listing PCI devices. The verbose
option (-v) provides comprehensive details including vendor and device
IDs, which are essential for verifying hardware detection. This is explicitly
listed as a key tool in the LPIC-1 objectives.
Q3. A Linux system has multiple storage devices attached, including
SATA hard drives, NVMe solid-state drives, and a USB external drive. The
, Page 4 of 99
administrator needs to understand the fundamental differences
between these mass storage device types to make appropriate
partitioning and mounting decisions. Which statement correctly
describes the device naming convention and the kernel driver interface
for these storage types in a modern Linux kernel?
A. SATA drives appear as /dev/hd* and use the ide driver, while NVMe
drives appear as /dev/sd* and use the nvme driver – this is incorrect
because SATA drives use /dev/sd* and the libata driver; IDE/PATA drives
use /dev/hd*.
B. SATA and USB drives appear as /dev/sd* and use the scsi subsystem
via libata or usb-storage, while NVMe drives appear as /dev/nvme*n* and
use the nvme driver directly. ✔️
C. All mass storage devices, regardless of interface, appear as /dev/sd*
and use the same unified block driver – this is false because NVMe has a
distinct naming scheme and driver.
D. SATA drives appear as /dev/sata*, NVMe as /dev/nvme*, and USB as
/dev/usb* – Linux does not use /dev/sata* or /dev/usb* as primary block
device names.
Rationale: Linux device naming follows the driver model: SATA, USB, and
SCSI drives are managed by the SCSI subsystem (sd driver), resulting in
/dev/sda, /dev/sdb, etc. NVMe drives are managed by the native NVMe
driver, yielding /dev/nvme0n1, /dev/nvme0n2, etc. This distinction is
crucial for administrators writing fstab entries or troubleshooting disk
detection.
LINUX PROFESSIONAL INSTITUTE LPIC‑1: 150 HIGH‑FIDELITY PRACTICE
QUESTIONS – EXAM 101‑500 & 102‑500 READINESS ASSESSMENT EXAM
QUESTIONS WITH DETAILED- VERIFIED ANSWERS- ALREADY GRADED
A+ || NEWEST EXAM
Information Technology / Systems Administration / Network
Administration
• Practical, Scenario‑Based Questions: Over 70% of questions
present real‑world administrative tasks (troubleshooting boot
failures, configuring firewalls, managing user accounts, debugging
network issues) rather than rote memorization.
• Command‑Centric Focus: Heavy emphasis on standard Linux
utilities (find, grep, sed, awk, systemctl, ip, ss, iptables, lsof, tar,
cron) – mirroring the hands‑on nature of the LPI exams.
• Modern Tooling: Questions reflect current best practices using
systemd, journalctl, dnf/apt, iproute2, and timedatectl, avoiding
deprecated tools unless contrasted with modern equivalents.
• Security and Hardening: Includes SSH key management, SELinux
contexts, sudo configuration, password policies, and log
monitoring – essential for production environments.
• Troubleshooting Mindset: Many questions require diagnosing errors
from given outputs (e.g., kernel panics, DNS failures, mount errors),
cultivating analytical problem‑solving skills.
TOPIC 101: SYSTEM ARCHITECTURE
Q1. A system administrator is troubleshooting a USB device that is not
being recognized after hot-plugging. The administrator needs to examine
, Page 2 of 99
the kernel's dynamic device management system and the user-space
component that handles device events, permissions, and persistent
device naming. Which combination of subsystems and utilities would
provide the most comprehensive diagnostic information for this
scenario?
A. /etc/fstab, mount, and blkid – these handle static file system mounting
and block device identification, but do not manage dynamic device
events or permissions.
B. /proc/cpuinfo, lscpu, and dmidecode – these provide CPU and
hardware inventory information but are unrelated to USB device hot-plug
events.
C. /sys/, udev, and dbus ✔️ – sysfs (/sys/) exports kernel device
information; udev manages device nodes, permissions, and persistent
naming in user space; dbus facilitates communication between system
services and applications about device events.
D. /var/log/messages, syslog, and dmesg – these provide kernel ring
buffer and system log messages but do not manage device permissions
or persistent naming.
Rationale: The Linux device management architecture relies on sysfs
(/sys/) for kernel device representation, udev for dynamic device node
management and permission setting in user space, and dbus for event
notification to applications. Together, these provide comprehensive
diagnostic capability for USB hot-plug issues. The other options address
only logging or hardware inventory, not the complete device
management chain.
, Page 3 of 99
Q2. An administrator needs to identify all PCI devices connected to a
Linux system, including their vendor and device identification numbers,
to verify that a newly installed network interface card is properly
detected by the kernel. Which command provides the most detailed and
structured output for this purpose?
A. lsusb – this command lists USB devices, not PCI devices, and would
not show the network interface card if it is connected via PCI.
B. lscpi – this is a misspelling of the correct command and would not
execute.
C. lspci -v ✔️ – the lspci command with the verbose (-v) option displays
detailed information about all PCI buses and devices, including vendor
IDs, device IDs, IRQ settings, and I/O port addresses.
D. dmidecode – this retrieves hardware information from the DMI
(Desktop Management Interface) table, which includes system-wide
hardware data but does not provide the structured PCI device tree
output of lspci.
Rationale: lspci is the standard utility for listing PCI devices. The verbose
option (-v) provides comprehensive details including vendor and device
IDs, which are essential for verifying hardware detection. This is explicitly
listed as a key tool in the LPIC-1 objectives.
Q3. A Linux system has multiple storage devices attached, including
SATA hard drives, NVMe solid-state drives, and a USB external drive. The
, Page 4 of 99
administrator needs to understand the fundamental differences
between these mass storage device types to make appropriate
partitioning and mounting decisions. Which statement correctly
describes the device naming convention and the kernel driver interface
for these storage types in a modern Linux kernel?
A. SATA drives appear as /dev/hd* and use the ide driver, while NVMe
drives appear as /dev/sd* and use the nvme driver – this is incorrect
because SATA drives use /dev/sd* and the libata driver; IDE/PATA drives
use /dev/hd*.
B. SATA and USB drives appear as /dev/sd* and use the scsi subsystem
via libata or usb-storage, while NVMe drives appear as /dev/nvme*n* and
use the nvme driver directly. ✔️
C. All mass storage devices, regardless of interface, appear as /dev/sd*
and use the same unified block driver – this is false because NVMe has a
distinct naming scheme and driver.
D. SATA drives appear as /dev/sata*, NVMe as /dev/nvme*, and USB as
/dev/usb* – Linux does not use /dev/sata* or /dev/usb* as primary block
device names.
Rationale: Linux device naming follows the driver model: SATA, USB, and
SCSI drives are managed by the SCSI subsystem (sd driver), resulting in
/dev/sda, /dev/sdb, etc. NVMe drives are managed by the native NVMe
driver, yielding /dev/nvme0n1, /dev/nvme0n2, etc. This distinction is
crucial for administrators writing fstab entries or troubleshooting disk
detection.
