On a workstation whose interfaces are managed by NetworkManager, which two approaches make an address change survive a reboot? (Choose two.)
LPIC-1 Exam 102-500, objective 109. Networking fundamentals medium
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Choose 2.
Correct Run `nmcli connection modify` against the profile, then reactivate it
Correct. `nmcli connection modify` writes the change into the stored profile immediately, so it is reapplied at every subsequent activation, including at boot.
Correct Edit the keyfile under /etc/NetworkManager/system-connections/ and run `nmcli connection reload`
Correct. The keyfile is the on-disk form of the profile. After editing it, `nmcli connection reload` makes NetworkManager re-read the directory; NetworkManager itself writes these files root-owned and mode 600 because they can hold secrets.
Not correct Run `ip addr add 10.1.1.5/24 dev enp0s3`
Wrong. iproute2 changes only the running kernel configuration. Nothing is written to disk, and the address is gone after a reboot or after NetworkManager reactivates the device.
Not correct Run `nmcli device modify enp0s3 ipv4.addresses 10.1.1.5/24`
Wrong. Device-level modifications are explicitly temporary: they apply to the active device and are discarded when it is deactivated.
Not correct Run `ifconfig enp0s3 10.1.1.5 netmask 255.255.255.0`
Wrong on two counts. net-tools is deprecated, and like iproute2 it writes only to the live kernel state with nothing persisted.
Why
Persistence under NetworkManager comes from the profile on disk, not from anything applied to the interface. Profiles live as keyfiles in /etc/NetworkManager/system-connections/ with the .nmconnection suffix, and they can be edited either through nmcli or with a text editor followed by `nmcli connection reload`. Any command that talks to the kernel directly, whether iproute2 or net-tools, configures only the current boot.
Where this comes from
- Cited
- manual page nm-settings-keyfile(5)
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 109 and space the ones you get wrong.
More questions on this objective
- A subnet is defined as 192.168.10.0/26. How many addresses in it can actually be assigned to hosts? machine-checked
- A host is configured with the address 172.20.35.77/20. What is the network address of its subnet? machine-checked
- In IPv6, which address is the loopback address, equivalent in role to 127.0.0.1 in IPv4? machine-checked
- Which is the correct fully compressed form of the IPv6 address 2001:0db8:0000:0000:0000:ff00:0042:8329? machine-checked
- Which pairing of a service with its default port number is correct? machine-checked
- DNS normally uses UDP port 53. In which situation does a DNS client or server fall back to TCP on port 53? machine-checked