The answer is to add a configuration file in /etc/modules-load.d/. This is correct because systemd-based Linux distributions use the /etc/modules-load.d/ directory to specify kernel modules that should be loaded automatically at boot; placing a file like my_driver.conf containing just the module name 'my_driver' in this directory instructs the systemd-modules-load.service to load it during early boot. On the LPIC-2 exam, this question tests your understanding of modern module loading mechanisms versus legacy methods like /etc/modules or /etc/modprobe.d/, which are common traps—remember that /etc/modprobe.d/ sets module options, not load lists. The key distinction is that /etc/modules-load.d/ is the systemd-native, distribution-agnostic way to load kernel modules automatically at boot, while /etc/modules is the older sysvinit approach. A helpful memory tip: think "load" in the directory name—modules-load.d—directly tells you its purpose is to load modules at boot.
LPIC-2 Linux Kernel and System Startup Practice Question
This LPIC-2 practice question tests your understanding of linux kernel and system startup. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A system administrator needs to ensure that a custom kernel module loads automatically at boot. The module is named 'my_driver' and is built for the current kernel. Which configuration file should be modified to ensure the module loads automatically?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add a configuration file in /etc/modules-load.d/
Option C is correct because systemd-based Linux distributions use /etc/modules-load.d/ to specify kernel modules that should be loaded automatically at boot. Placing a configuration file (e.g., my_driver.conf) containing the module name 'my_driver' in this directory instructs systemd-modules-load.service to load the module during early boot. This is the modern, distribution-agnostic method for ensuring a custom kernel module loads automatically.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Add the insmod command in /etc/rc.local
Why it's wrong here
While possible, rc.local is not the recommended method for loading modules at boot.
✗
Add the module name to /etc/modules.conf
Why it's wrong here
/etc/modules.conf is not a standard file in modern Linux distributions.
✓
Add a configuration file in /etc/modules-load.d/
Why this is correct
/etc/modules-load.d/ is the standard location for specifying modules to load at boot.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add a configuration file in /etc/modprobe.d/
Why it's wrong here
/etc/modprobe.d/ is for modprobe options, not for auto-loading modules.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse /etc/modprobe.d/ (used for modprobe configuration) with /etc/modules-load.d/ (used for automatic loading), or they assume the legacy /etc/modules.conf is still valid on modern distributions.
Detailed technical explanation
How to think about this question
The /etc/modules-load.d/ directory is processed by systemd-modules-load.service, which reads all .conf files in lexicographic order and runs modprobe for each listed module. This mechanism ensures modules are loaded before filesystems and services that depend on them, and it respects module dependencies defined in /lib/modules/$(uname -r)/modules.dep. A real-world scenario is loading a custom hardware driver (e.g., for a proprietary NIC) that must be available before network configuration; placing it in /etc/modules-load.d/ guarantees it loads early in the boot sequence.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the LPIC-2 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Linux Kernel and System Startup — This question tests Linux Kernel and System Startup — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Add a configuration file in /etc/modules-load.d/ — Option C is correct because systemd-based Linux distributions use /etc/modules-load.d/ to specify kernel modules that should be loaded automatically at boot. Placing a configuration file (e.g., my_driver.conf) containing the module name 'my_driver' in this directory instructs systemd-modules-load.service to load the module during early boot. This is the modern, distribution-agnostic method for ensuring a custom kernel module loads automatically.
What should I do if I get this LPIC-2 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A system administrator needs to add a kernel module to the kernel at runtime without recompiling. Which command should be used?
easy
✓ A.insmod
B.rmmod
C.modprobe
D.depmod
Why A: The correct command is `insmod` because it inserts a kernel module into the running kernel without recompiling. It directly loads the specified module file (e.g., `.ko` file) into the kernel, making it available immediately. This is the standard low-level command for adding a single module at runtime.
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This LPIC-2 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-2 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.