LPIC-1 Essential System Services and Networking Practice Question
On a Debian-based system using ifupdown, which file should be edited to configure a static IP address for an interface?
⚠ Common exam trap
It's easy for candidates to confuse the default network configuration file for Debian-based systems with those used by other distributions (Red Hat) or newer abstraction layers (Netplan, systemd-networkd), leading them to pick a file that is technically valid but not used by the ifupdown tool specified in the question.
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
✓
/etc/network/interfaces
On Debian-based systems using the traditional ifupdown suite, the file `/etc/network/interfaces` is the central configuration file for defining network interfaces, including static IP addresses. This file is parsed by the `ifup` and `ifdown` commands to bring interfaces up or down with the specified settings, such as `address`, `netmask`, and `gateway`.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
/etc/systemd/network/50-static.network
Why it's wrong here
/etc/systemd/network/50-static.network is consumed by systemd-networkd, not ifupdown, so editing it leaves the Debian interfaces file untouched and the static address unapplied. It is tempting because systemd-networkd is the native network manager on many modern distributions, and this path would be correct where systemd-networkd, rather than ifupdown, manages the interface.
- ✓
/etc/network/interfaces
Why this is correct
On Debian systems using ifupdown, /etc/network/interfaces is the canonical configuration file where interface stanzas define addressing. Editing it to add an iface entry with static address, netmask and gateway satisfies the requirement for persistent static IP configuration applied by ifup at boot.
- ✗
/etc/netplan/01-netcfg.yaml
Why it's wrong here
Netplan is the default renderer on Ubuntu Server, not on a Debian system running ifupdown; Debian's ifupdown reads /etc/network/interfaces. Netplan would be the right file where netplan.io manages the interface and renders to systemd-networkd or NetworkManager.
- ✗
/etc/sysconfig/network-scripts/ifcfg-eth0
Why it's wrong here
/etc/sysconfig/network-scripts/ifcfg-eth0 belongs to Red Hat's NetworkManager/network-scripts convention, so ifupdown on Debian never reads it. It is tempting because that path is genuinely correct on RHEL-family systems, where per-interface ifcfg files define static addressing; Debian instead uses /etc/network/interfaces.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every LPIC-1 question from scratch — 402 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.