Question 154 of 511
Network Client ManagementeasyMultiple ChoiceObjective-mapped

Quick Answer

The answer is `/etc/NetworkManager/system-connections/`. NetworkManager stores each connection profile as an individual keyfile with a `.nmconnection` extension in this directory, containing all parameters like SSID, security keys, and IP settings. This location is correct because NetworkManager reads and writes these plain-text files to persist configurations across reboots, making them the authoritative source for per-connection data. On the LPIC-2 exam, this tests your understanding of how NetworkManager manages network state versus traditional interface scripts; a common trap is confusing this directory with `/etc/sysconfig/network-scripts/` (used by legacy initscripts) or assuming profiles are stored in a single binary file. Remember the mnemonic: "NetworkManager keeps its connections in a system-connections folder, not a single file."

LPIC-2 Network Client Management Practice Question

This LPIC-2 practice question tests your understanding of network client management. 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.

Which file is used by the NetworkManager daemon to store connection profiles on a Linux system?

Question 1easymultiple 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

/etc/NetworkManager/system-connections/

NetworkManager stores per-connection profiles in the `/etc/NetworkManager/system-connections/` directory. Each profile is a keyfile (`.nmconnection` file) containing connection parameters such as SSID, security settings, and IP configuration. When NetworkManager starts or a connection is modified, it reads and writes these files to persist network configurations across reboots.

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.

  • /etc/NetworkManager/system-connections/

    Why this is correct

    NetworkManager stores connection profiles as individual files in this directory.

    Related concept

    Read the scenario before looking for a memorised answer.

  • /etc/sysconfig/network-scripts/

    Why it's wrong here

    This directory is used by the legacy network scripts (ifup/ifdown).

  • /etc/netctl/

    Why it's wrong here

    This directory is used by netctl, a different network configuration tool.

  • /etc/systemd/network/

    Why it's wrong here

    This directory is used by systemd-networkd.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse the NetworkManager connection profile directory with other network configuration directories like the legacy initscripts path (`/etc/sysconfig/network-scripts/`) or systemd-networkd's path (`/etc/systemd/network/`), leading them to pick a plausible but incorrect option based on their distribution's default tools.

Detailed technical explanation

How to think about this question

NetworkManager's connection profiles use the `.nmconnection` keyfile format, which is an INI-style file with sections like `[connection]`, `[wifi]`, `[ipv4]`, and `[ipv6]`. These files can be manually edited or managed via `nmcli` or `nmtui`. A subtle behavior: if a profile is set to `permissions=` (empty), it is available to all users; otherwise, it is restricted to specific users. In real-world scenarios, administrators often use `nmcli connection reload` to re-read these files after manual edits without restarting the daemon.

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-2 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-2 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-2 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-2 question test?

Network Client Management — This question tests Network Client Management — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: /etc/NetworkManager/system-connections/ — NetworkManager stores per-connection profiles in the `/etc/NetworkManager/system-connections/` directory. Each profile is a keyfile (`.nmconnection` file) containing connection parameters such as SSID, security settings, and IP configuration. When NetworkManager starts or a connection is modified, it reads and writes these files to persist network configurations across reboots.

What should I do if I get this LPIC-2 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 →

How Courseiva writes practice questions · Editorial policy

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-2 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-2 exam.