Quick Answer
The answer is the file /etc/sysconfig/network-scripts/ifcfg-eth0. This is correct because CentOS 7, like its RHEL lineage, stores permanent network interface configurations in individual scripts under the /etc/sysconfig/network-scripts/ directory, named ifcfg- followed by the interface name, such as eth0. Within this file, you set BOOTPROTO=static and define the IPADDR, NETMASK, and GATEWAY parameters to establish a static IP that persists across reboots, bypassing the dynamic assignment from DHCP. On the Linux Foundation Certified System Administrator LFCS exam, this question tests your knowledge of legacy network configuration methods, as CentOS 7 still relies on these scripts by default even though NetworkManager is present. A common trap is confusing this with the newer /etc/NetworkManager/system-connections/ directory used by NetworkManager’s keyfile format, but the exam expects the traditional ifcfg path for permanent static configuration. Memory tip: think of “ifcfg” as “interface config” and remember that the file name always matches the interface name you see in ip link.
This LFCS practice question tests your understanding of networking. 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.
An administrator wants to permanently configure a static IP address on a CentOS 7 system. Which file should be edited?
/etc/sysconfig/network-scripts/ifcfg-eth0
This is the standard network interface configuration file for CentOS/RHEL 7.
/etc/sysconfig/network
Why wrong: This file sets global network parameters, not per-interface IP.
/etc/hostname
Why wrong: This sets the hostname, not IP address.
/etc/network/interfaces
Why wrong: This is used by Debian/Ubuntu systems.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
/etc/sysconfig/network-scripts/ifcfg-eth0
On CentOS 7, network interface configuration is stored in individual files under /etc/sysconfig/network-scripts/, named ifcfg-<interface>. The ifcfg-eth0 file contains parameters like BOOTPROTO, IPADDR, NETMASK, and GATEWAY, and setting BOOTPROTO=static along with the IP address values permanently configures a static IP. This is the standard method for RHEL/CentOS 7 systems using the legacy network scripts (not NetworkManager's keyfile format).
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
/etc/sysconfig/network-scripts/ifcfg-eth0
Why this is correct
This is the standard network interface configuration file for CentOS/RHEL 7.
Related concept
Read the scenario before looking for a memorised answer.
/etc/sysconfig/network
Why it's wrong here
This file sets global network parameters, not per-interface IP.
/etc/hostname
Why it's wrong here
This sets the hostname, not IP address.
/etc/network/interfaces
Why it's wrong here
This is used by Debian/Ubuntu systems.
Common exam traps
The trap here is that candidates familiar with Debian-based systems may choose /etc/network/interfaces (Option D), while those who confuse global network settings with per-interface settings may pick /etc/sysconfig/network (Option B), both of which are incorrect for CentOS 7's static IP configuration.
Detailed technical explanation
The ifcfg-eth0 file is parsed by the /etc/init.d/network script (or the network service) which sources the file to set kernel parameters via ip and ifconfig commands. For a static IP, BOOTPROTO must be set to 'static' or 'none', and IPADDR, NETMASK (or PREFIX), and GATEWAY are specified. A common subtlety is that if NetworkManager is enabled, it may override these settings unless NM_CONTROLLED=no is added to the ifcfg file, ensuring the legacy network service manages the interface.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A network engineer segments a warehouse floor into three subnets: 20 scanners, 5 printers, and 2 management hosts. Picking the wrong mask wastes addresses or leaves too few usable hosts. Exam questions test whether you can apply CIDR notation, calculate block size, and identify the correct usable-host range for a given prefix.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Networking — study guide chapter
Learn the concepts, then practise the questions
Networking practice questions
Targeted practice on this topic area only
All LFCS questions
513 questions across all exam domains
Linux Foundation Certified System Administrator LFCS study guide
Full concept coverage aligned to exam objectives
LFCS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise LFCS questions linked to User and Group Management.
Practise LFCS questions linked to Operation of Running Systems.
Practise LFCS questions linked to Essential Commands.
Practise LFCS questions linked to Networking.
Practise LFCS questions linked to Service Configuration.
Practise LFCS questions linked to Storage Management.
Practise LFCS questions linked to LFCS fundamentals.
Practise LFCS questions linked to LFCS scenario.
Practise LFCS questions linked to LFCS troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Networking — This question tests Networking — Read the scenario before looking for a memorised answer..
The correct answer is: /etc/sysconfig/network-scripts/ifcfg-eth0 — On CentOS 7, network interface configuration is stored in individual files under /etc/sysconfig/network-scripts/, named ifcfg-<interface>. The ifcfg-eth0 file contains parameters like BOOTPROTO, IPADDR, NETMASK, and GATEWAY, and setting BOOTPROTO=static along with the IP address values permanently configures a static IP. This is the standard method for RHEL/CentOS 7 systems using the legacy network scripts (not NetworkManager's keyfile format).
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Same concept, more angles
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. Order the steps to configure a static IP address on a CentOS/RHEL 7 system using ifcfg files.
mediumWhy : Static IP configuration requires editing the ifcfg file, restarting network, and verification.
Last reviewed: Jun 11, 2026
This LFCS practice question is part of Courseiva's free Linux Foundation 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 LFCS 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.