LPIC-1 System Architecture Practice Question
A junior admin is tasked with configuring network bonding on a Debian server with two Ethernet interfaces, eth0 and eth1. The goal is to provide link redundancy using active-backup mode. The admin edits /etc/network/interfaces and adds configuration for bond0 with slaves eth0 eth1, then runs 'ifup bond0'. However, the bond interface fails to come up and the error message indicates that the 'bond' kernel module is not loaded. The admin checks with 'lsmod | grep bonding' and finds no output. Which additional step is required to successfully bring up the bond interface? Options: A) Run 'modprobe bonding' before ifup, B) Use ifenslave directly after ifup, C) Reboot the system to load the module, D) Add 'auto bond0' in /etc/network/interfaces.
⚠ Common exam trap
Test-takers frequently think adding 'auto bond0' or rebooting will solve the module loading issue, but the kernel module must be explicitly loaded before the bonding interface can be created.
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
✓
Run 'modprobe bonding' before ifup
The 'bond' kernel module must be loaded before the bonding interface can be created. Running 'modprobe bonding' loads the module into the kernel, making the bonding functionality available. Without this step, 'ifup bond0' fails because the kernel does not recognize the bonding driver.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Run 'modprobe bonding' before ifup
Why this is correct
The bonding driver is built as a loadable module, and ifup does not auto-load it, so the bond0 interface cannot be created. Running modprobe bonding loads the module into the kernel before ifup, satisfying the missing-module constraint reported by lsmod.
- ✗
Use ifenslave directly after ifup
Why it's wrong here
ifenslave only attaches slave interfaces to an already-existing bond master; with the bonding module absent, bond0 cannot exist, so the command has nothing to enslave. It would be relevant only after the module is loaded and the master interface is present.
- ✗
Reboot the system to load the module
Why it's wrong here
Rebooting would eventually load bonding, but it is a disruptive workaround rather than the required step; the module can be inserted immediately with modprobe. Rebooting is tempting because it loads modules listed in /etc/modules, which is the correct persistent approach when you want bonding available automatically at every boot.
- ✗
Add 'auto bond0' in /etc/network/interfaces
Why it's wrong here
'auto bond0' merely makes ifup bring the interface up at boot; it does not load the bonding kernel module, so the same failure recurs. It would be correct when the bond must activate automatically during system startup rather than manually.
Go deeper
Related to this question
About these practice questions
One of 402 original LPIC-1 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.