LPIC-1 System Architecture Practice Question
Which TWO of the following are valid methods to list currently loaded kernel modules?
⚠ Common exam trap
Watch out — candidates often confuse commands that list available modules (like modprobe -l or find /lib/modules) with commands that list currently loaded modules, or they assume dmesg is a valid module listing tool because it shows kernel messages related to module loading.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
lsmod
Lsmod reads /proc/modules and prints the currently loaded kernel modules along with their size and usage count, making it the standard tool for this task. Option D (cat /proc/modules) is also correct because /proc/modules is the kernel-provided virtual file that lists all loaded modules, so displaying it directly shows the same information lsmod parses. Option A (dmesg | grep module) only filters kernel ring-buffer log messages and does not enumerate loaded modules. Option C (modprobe -l) lists available module files on disk rather than loaded modules, and the -l option is deprecated/removed in modern kmod. Option E (modinfo) displays metadata about a specific module file or name, not a list of currently loaded modules.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
dmesg | grep module
Why it's wrong here
dmesg prints kernel ring-buffer messages, which may mention modules during boot but never enumerate currently loaded ones. It is tempting because module-loading messages appear there, yet lsmod or /proc/modules is what actually lists loaded modules.
- ✓
lsmod
Why this is correct
lsmod reads /proc/modules and prints currently loaded kernel modules in a formatted table with size and usage counts. It satisfies the requirement to list loaded modules without loading or unloading anything, unlike modprobe or insmod.
- ✗
modprobe -l
Why it's wrong here
modprobe -l was removed in kmod; it listed available module files on disk, not loaded ones, and now errors out. It is tempting because modprobe manages modules, but listing loaded modules requires lsmod or reading /proc/modules, which reflect current kernel state.
- ✓
cat /proc/modules
Why this is correct
/proc/modules is the kernel-generated file listing every loaded module with its size, reference count and dependencies. Reading it with cat lists loaded modules directly, matching the requirement, and it is the same source lsmod parses.
- ✗
modinfo
Why it's wrong here
modinfo only displays metadata about a single module (author, licence, parameters, dependencies); it does not enumerate loaded modules. It is tempting because it inspects kernel modules, but it answers "what is this module?" rather than "what is loaded?", which lsmod or /proc/modules provide.
Go deeper
Related to this question
About these practice questions
This LPIC-1 question is part of Courseiva's 402-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This LPIC-1 practice question is part of Courseiva's free LPI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LPIC-1 exam.