Question 90
A Linux administrator evaluates: An appliance image has two NetworkManager profiles and the wrong one automatically activates at startup. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: An appliance image has two NetworkManager profiles and the wrong one automatically activates at startup. The recommended direct administrative response is: Use NetworkManager nmcli connection profiles to set the intended IPv4 address, gateway and DNS, then activate and verify the profile safely. The relevant failure or security risk is: Changing an ephemeral interface address without saving its connection profile can remove remote access at restart. Validate success with: nmcli and ip address/ip route show the intended persistent configuration before and after reactivation.
For the specific observation (An appliance image has two NetworkManager profiles and the wrong one automatically activates at startup), the acceptance evidence is: nmcli and ip address/ip route show the intended persistent configuration before and after reactivation. This verifies the action (Use NetworkManager nmcli connection profiles to set the intended IPv4 address, gateway and DNS, then activate and verify the profile safely.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Changing an ephemeral interface address without saving its connection profile can remove remote access at restart.
Incorrect Answers
Hardware and device discovery (1.2) addresses another technical failure: Guessing a driver without confirming the kernel-visible hardware can mask a disconnected device or wrong bus identity. The case states: An appliance image has two NetworkManager profiles and the wrong one automatically activates at startup. The most direct paired action and test is: Use NetworkManager nmcli connection profiles to set the intended IPv4 address, gateway and DNS, then activate and verify the profile safely.
Rsync incremental backup and restoration verification (1.6) would demonstrate or implement: A restore rehearsal recovers the expected files, ownership and permissions to an isolated path with matching checksums. This choice can be useful for that problem, but it does not establish the Persistent network configuration with nmcli control being assessed here.
Persistent filesystem mounting by UUID (1.3) would demonstrate or implement: Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode. This case instead tests Persistent network configuration with nmcli; the choice measures or changes another part of the system.