Pass Your LPI 102-500 Exam Easy!

Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it. That operation is designed for the different case: A corporate client must send DNS queries to a new resolver persistently under NetworkManager. It does not perform the specific action required here: Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf.

Use hostnamectl set-hostname newname on a systemd host. That operation is designed for the different case: The system's static hostname must survive reboot and be reported consistently to utilities. It does not perform the specific action required here: Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf.

Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate. That operation is designed for the different case: A host must consult local files before DNS for resolving service hostnames. It does not perform the specific action required here: Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf.

This explains another Linux operation, namely Configure a matching .network file under /etc/systemd/network/ and reload/reconfigure systemd-networkd., where systemd-networkd reads .network units for interfaces it manages; NetworkManager profile changes may not affect such a host. It does not explain why Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf. satisfies the stated condition.

This explains another Linux operation, namely Set ipv4.dns-search for the correct connection profile and validate resolver behavior., where Resolver search domains append configured suffixes to eligible relative hostnames; they are separate from DNS server IPs. It does not explain why Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf. satisfies the stated condition.

This explains another Linux operation, namely Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it., where NetworkManager commonly manages resolver settings and may regenerate /etc/resolv.conf from profile data. It does not explain why Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf. satisfies the stated condition.

That observation checks A machine must use a stable DNS search domain for unqualified internal hostnames under NetworkManager. In this scenario it does not demonstrate Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf.; the relevant evidence must establish getent hosts testname returns the expected local IP even if DNS lacks the name.

That observation checks An operator needs to inspect all NetworkManager connection profiles and identify which one is active. In this scenario it does not demonstrate Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf.; the relevant evidence must establish getent hosts testname returns the expected local IP even if DNS lacks the name.

That observation checks A network interface has two saved profiles with different IPv4 settings; production uses the wrong profile on boot. In this scenario it does not demonstrate Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf.; the relevant evidence must establish getent hosts testname returns the expected local IP even if DNS lacks the name.

This fix is aimed at The configured DNS server is reachable but a short hostname fails without its expected search suffix. and would be relevant if A machine must use a stable DNS search domain for unqualified internal hostnames under NetworkManager. The incident instead states A resolv.conf nameserver was changed but the required local override is absent. and needs Maintain the /etc/hosts mapping and check hosts: source order.

This fix is aimed at Only a manual iw scan was performed; no saved connection was created. and would be relevant if A workstation Wi-Fi profile must join a secured SSID automatically after reboot. The incident instead states A resolv.conf nameserver was changed but the required local override is absent. and needs Maintain the /etc/hosts mapping and check hosts: source order.

This fix is aimed at Editing generated /etc/resolv.conf is overwritten when NetworkManager reactivates the connection. and would be relevant if A corporate client must send DNS queries to a new resolver persistently under NetworkManager. The incident instead states A resolv.conf nameserver was changed but the required local override is absent. and needs Maintain the /etc/hosts mapping and check hosts: source order.

Adjust the correct NetworkManager connection's autoconnect behavior and priority, then activate it. That operation is designed for the different case: A network interface has two saved profiles with different IPv4 settings; production uses the wrong profile on boot. It does not perform the specific action required here: Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it.

Run nmcli connection show --active and compare with nmcli connection show. That operation is designed for the different case: An operator needs to inspect all NetworkManager connection profiles and identify which one is active. It does not perform the specific action required here: Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it.

Set ipv4.dns-search for the correct connection profile and validate resolver behavior. That operation is designed for the different case: A machine must use a stable DNS search domain for unqualified internal hostnames under NetworkManager. It does not perform the specific action required here: Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it.

This explains another Linux operation, namely Adjust the correct NetworkManager connection's autoconnect behavior and priority, then activate it., where NetworkManager chooses among eligible profiles based on connection matching and autoconnect preferences. It does not explain why Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it. satisfies the stated condition.

This explains another Linux operation, namely Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate., where Name Service Switch controls source precedence independent of the contents of resolv.conf. It does not explain why Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it. satisfies the stated condition.

This explains another Linux operation, namely Configure a NetworkManager Wi-Fi connection with the correct SSID, security and autoconnect properties., where NetworkManager can persist wireless credentials and connection autostart separately from transient scans. It does not explain why Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it. satisfies the stated condition.

That observation checks A machine must use a stable DNS search domain for unqualified internal hostnames under NetworkManager. In this scenario it does not demonstrate Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it.; the relevant evidence must establish After reconnect, the resolver query uses the intended DNS server and persists across restart.

That observation checks A local application must resolve a special test hostname to a fixed IP before public DNS lookup according to host resolution policy. In this scenario it does not demonstrate Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it.; the relevant evidence must establish After reconnect, the resolver query uses the intended DNS server and persists across restart.

That observation checks A NetworkManager-managed Ethernet connection must retain its static IPv4 address after restart. In this scenario it does not demonstrate Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it.; the relevant evidence must establish After reconnect, the resolver query uses the intended DNS server and persists across restart.

That symptom concerns A local application must resolve a special test hostname to a fixed IP before public DNS lookup according to host resolution policy. This concerns a separate requirement, not the one being tested. The relevant failure is Editing generated /etc/resolv.conf is overwritten when NetworkManager reactivates the connection. The current requirement calls for a different check.

That symptom concerns A workstation Wi-Fi profile must join a secured SSID automatically after reboot. This concerns a separate requirement, not the one being tested. The relevant failure is Editing generated /etc/resolv.conf is overwritten when NetworkManager reactivates the connection. The current requirement calls for a different check.

That symptom concerns The system's static hostname must survive reboot and be reported consistently to utilities. This concerns a separate requirement, not the one being tested. The relevant failure is Editing generated /etc/resolv.conf is overwritten when NetworkManager reactivates the connection. The current requirement calls for a different check.

This fix is aimed at NSS is configured dns files and unexpectedly ignores the desired local override. and would be relevant if A host must consult local files before DNS for resolving service hostnames. The incident instead states Editing generated /etc/resolv.conf is overwritten when NetworkManager reactivates the connection. and needs Change the managed connection DNS setting instead of an ephemeral generated resolver file.

This fix is aimed at An nmcli command edits a nonexistent or unmanaged profile, leaving the interface unchanged. and would be relevant if A small host uses systemd-networkd, not NetworkManager, for its persistent wired network configuration. The incident instead states Editing generated /etc/resolv.conf is overwritten when NetworkManager reactivates the connection. and needs Change the managed connection DNS setting instead of an ephemeral generated resolver file.

This fix is aimed at The operator edits an inactive duplicate profile while the active one retains wrong settings. and would be relevant if An operator needs to inspect all NetworkManager connection profiles and identify which one is active. The incident instead states Editing generated /etc/resolv.conf is overwritten when NetworkManager reactivates the connection. and needs Change the managed connection DNS setting instead of an ephemeral generated resolver file.

Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf. That operation is designed for the different case: A local application must resolve a special test hostname to a fixed IP before public DNS lookup according to host resolution policy. It does not perform the specific action required here: Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate.

Set ipv4.dns-search for the correct connection profile and validate resolver behavior. That operation is designed for the different case: A machine must use a stable DNS search domain for unqualified internal hostnames under NetworkManager. It does not perform the specific action required here: Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate.

Set ipv4.method manual with address/gateway using nmcli connection modify on the correct connection, then activate it. That operation is designed for the different case: A NetworkManager-managed Ethernet connection must retain its static IPv4 address after restart. It does not perform the specific action required here: Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate.

This explains another Linux operation, namely Add the entry in /etc/hosts and confirm the hosts source precedes DNS in nsswitch.conf., where The hosts database provides explicit local name-to-address mappings consulted by the resolver per NSS order. It does not explain why Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate. satisfies the stated condition.

This explains another Linux operation, namely Set ipv4.dns on the appropriate NetworkManager connection profile and reactivate it., where NetworkManager commonly manages resolver settings and may regenerate /etc/resolv.conf from profile data. It does not explain why Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate. satisfies the stated condition.

This explains another Linux operation, namely Configure a matching .network file under /etc/systemd/network/ and reload/reconfigure systemd-networkd., where systemd-networkd reads .network units for interfaces it manages; NetworkManager profile changes may not affect such a host. It does not explain why Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate. satisfies the stated condition.