A server currently gets its address by DHCP through the NetworkManager profile office. It must instead keep the fixed address 192.0.2.50/24 with gateway 192.0.2.1 across reboots. Which command line configures the profile correctly?
LPIC-1 Exam 102-500, objective 109. Networking fundamentals hard
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
Correct nmcli connection modify office ipv4.addresses 192.0.2.50/24 ipv4.gateway 192.0.2.1 ipv4.method manual
Correct. The address and gateway properties are stored, and setting ipv4.method to manual is what stops the profile from asking DHCP for an address on the next activation.
Not correct nmcli connection modify office ipv4.addresses 192.0.2.50/24 ipv4.gateway 192.0.2.1
Wrong. The properties are recorded, but ipv4.method is left at auto, so on activation DHCP still supplies an address and the static one is treated as a supplementary address at best.
Not correct nmcli device modify enp0s3 ipv4.addresses 192.0.2.50/24 ipv4.method manual
Wrong. `nmcli device modify` exists, but its changes are temporary: they are not written to the profile and are lost when the device is deactivated or the machine reboots.
Not correct ip addr add 192.0.2.50/24 dev enp0s3 && ip route add default via 192.0.2.1
Wrong. iproute2 writes only to the running kernel. Nothing is stored on disk, so the configuration disappears at the next reboot and NetworkManager may overwrite it sooner than that.
Why
In NetworkManager, ipv4.method is the switch that decides where an address comes from: auto means DHCP, manual means use the addresses stored in ipv4.addresses, and disabled means no IPv4 at all. Setting ipv4.addresses without also setting the method is the classic half-configuration, because the profile keeps requesting DHCP. Changes made with `nmcli connection modify` are persistent, whereas `nmcli device modify` and iproute2 commands only touch the live state.
Where this comes from
- Cited
- manual page nmcli(1)
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