- A
net.ifnames=0
Enables predictable naming based on firmware topology.
- B
ifrename=enable
Why wrong: Not a valid kernel parameter.
- C
net.ifnames=1
Why wrong: Disables predictable naming, using ethX style.
- D
biosdevname=0
Why wrong: biosdevname is an older tool; net.ifnames is the current method.
LFCS Networking Practice Question
This LFCS practice question tests your understanding of networking. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 wants to ensure that network interfaces receive predictable names based on firmware/BIOS topology rather than kernel enumeration. Which naming scheme should be enabled in GRUB?
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
net.ifnames=0
Option A is correct because setting `net.ifnames=0` in GRUB disables the predictable network interface naming scheme (based on firmware/BIOS topology) and reverts to the traditional kernel enumeration (e.g., eth0, eth1). This is the standard kernel parameter used to control systemd's udev naming policy, ensuring names like enp0s3 or ens33 are replaced with legacy names.
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.
- ✓
net.ifnames=0
Why this is correct
Enables predictable naming based on firmware topology.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
ifrename=enable
Why it's wrong here
Not a valid kernel parameter.
- ✗
net.ifnames=1
Why it's wrong here
Disables predictable naming, using ethX style.
- ✗
biosdevname=0
Why it's wrong here
biosdevname is an older tool; net.ifnames is the current method.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse `net.ifnames=0` with enabling predictable naming, when in fact it disables it, and they may also mistake `biosdevname=0` as the correct parameter for enabling topology-based names, whereas biosdevname is a separate, older scheme from Dell.
Detailed technical explanation
How to think about this question
The predictable naming scheme is implemented by systemd's udev via rules in `/usr/lib/udev/rules.d/80-net-setup-link.rules`, which uses information from ACPI (_DSM) or PCI slot firmware to generate names like enp0s3 (Ethernet, PCI bus 0, slot 3). The `net.ifnames` parameter controls whether udev applies these rules; when set to 0, udev falls back to kernel-generated names (ethX). In real-world scenarios, disabling predictable naming is often necessary for compatibility with legacy scripts or network configurations that hardcode eth0/eth1.
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 LFCS 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.
- →
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
Related LFCS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
User and Group Management practice questions
Practise LFCS questions linked to User and Group Management.
Operation of Running Systems practice questions
Practise LFCS questions linked to Operation of Running Systems.
Essential Commands practice questions
Practise LFCS questions linked to Essential Commands.
Networking practice questions
Practise LFCS questions linked to Networking.
Service Configuration practice questions
Practise LFCS questions linked to Service Configuration.
Storage Management practice questions
Practise LFCS questions linked to Storage Management.
LFCS fundamentals practice questions
Practise LFCS questions linked to LFCS fundamentals.
LFCS scenario practice questions
Practise LFCS questions linked to LFCS scenario.
LFCS troubleshooting practice questions
Practise LFCS questions linked to LFCS troubleshooting.
Practice this exam
Start a free LFCS practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this LFCS question test?
Networking — This question tests Networking — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: net.ifnames=0 — Option A is correct because setting `net.ifnames=0` in GRUB disables the predictable network interface naming scheme (based on firmware/BIOS topology) and reverts to the traditional kernel enumeration (e.g., eth0, eth1). This is the standard kernel parameter used to control systemd's udev naming policy, ensuring names like enp0s3 or ens33 are replaced with legacy names.
What should I do if I get this LFCS 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 →
Last reviewed: Jun 25, 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.