Question 222 of 522
System ArchitecturemediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the network interface's MAC address is not unique or changes. This is the most likely cause because udev persistent network interface names rely on rules that match hardware attributes, and the MAC address is the primary identifier used to bind a specific name to a specific interface. If the MAC address is duplicated—common in virtual machines or cloned network interface cards—or if it changes after a hardware replacement or driver update, the udev rule cannot consistently identify the interface, leading to unpredictable naming. On the LPIC-1 exam, this tests your understanding of how udev manages device persistence in /etc/udev/rules.d, and a common trap is assuming the rule syntax is wrong when the real issue is a non-unique MAC. Remember the mnemonic: "MAC must be unique, or the name will leak."

LPIC-1 System Architecture Practice Question

This LPIC-1 practice question tests your understanding of system architecture. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 server with a udev rule fails to consistently assign a persistent network interface name. What is the most likely cause?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

Question 1mediummultiple choice
Full 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

The network interface's MAC address is not unique or changes.

Persistent network interface names in Linux rely on udev rules that match attributes like MAC address. If the MAC address is not unique (e.g., due to a virtual machine or cloned NIC) or changes (e.g., after hardware replacement or driver update), the rule will fail to consistently identify the interface, causing the name assignment to be unpredictable.

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.

  • The rule uses an incorrect operator.

    Why it's wrong here

    Syntax errors would cause the rule to be ignored, not inconsistent naming.

  • The BIOS device name is configured incorrectly.

    Why it's wrong here

    BIOS naming is separate from udev rules.

  • The kernel module for the NIC is not loaded.

    Why it's wrong here

    If the module is not loaded, the interface wouldn't appear at all.

  • The network interface's MAC address is not unique or changes.

    Why this is correct

    If the MAC address changes, a rule matching by MAC will fail.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume udev rules always work if the syntax is correct, overlooking that dynamic or non-unique MAC addresses undermine the stability of the matching attribute.

Detailed technical explanation

How to think about this question

Udev rules for persistent naming often use the `ATTR{address}` key to match the MAC address. However, MAC addresses can be spoofed or changed by virtualization layers (e.g., VMware, KVM) or by using `macchanger`. In such cases, the rule may match a different interface or fail to match, causing the kernel to fall back to unpredictable names like `eth0` or `enp0s3`. The `udevadm test` command can be used to debug rule matching.

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-1 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.

Related practice questions

Related LPIC-1 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free LPIC-1 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 LPIC-1 question test?

System Architecture — This question tests System Architecture — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The network interface's MAC address is not unique or changes. — Persistent network interface names in Linux rely on udev rules that match attributes like MAC address. If the MAC address is not unique (e.g., due to a virtual machine or cloned NIC) or changes (e.g., after hardware replacement or driver update), the rule will fail to consistently identify the interface, causing the name assignment to be unpredictable.

What should I do if I get this LPIC-1 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More LPIC-1 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.