Pass Your LPI 102-500 Exam Easy!

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.

That observation checks A corporate client must send DNS queries to a new resolver persistently under NetworkManager. In this scenario it does not demonstrate Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate.; the relevant evidence must establish getent hosts resolves a test entry from /etc/hosts in preference to a conflicting DNS answer.

That observation checks A small host uses systemd-networkd, not NetworkManager, for its persistent wired network configuration. In this scenario it does not demonstrate Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate.; the relevant evidence must establish getent hosts resolves a test entry from /etc/hosts in preference to a conflicting DNS answer.

That observation checks A workstation Wi-Fi profile must join a secured SSID automatically after reboot. In this scenario it does not demonstrate Ensure the hosts line in /etc/nsswitch.conf orders files before dns as appropriate.; the relevant evidence must establish getent hosts resolves a test entry from /etc/hosts in preference to a conflicting DNS answer.

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 NSS is configured dns files and unexpectedly ignores the desired local override. The current requirement calls for a different check.

That symptom concerns A corporate client must send DNS queries to a new resolver persistently under NetworkManager. This concerns a separate requirement, not the one being tested. The relevant failure is NSS is configured dns files and unexpectedly ignores the desired local override. The current requirement calls for a different check.

That symptom concerns An operator needs to inspect all NetworkManager connection profiles and identify which one is active. This concerns a separate requirement, not the one being tested. The relevant failure is NSS is configured dns files and unexpectedly ignores the desired local override. The current requirement calls for a different check.

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 NSS is configured dns files and unexpectedly ignores the desired local override. and needs Set hosts: files dns in nsswitch.conf subject to system resolver policy.

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 NSS is configured dns files and unexpectedly ignores the desired local override. and needs Set hosts: files dns in nsswitch.conf subject to system resolver policy.

This fix is aimed at A temporary hostname command succeeds but the name reverts after reboot. and would be relevant if The system's static hostname must survive reboot and be reported consistently to utilities. The incident instead states NSS is configured dns files and unexpectedly ignores the desired local override. and needs Set hosts: files dns in nsswitch.conf subject to system resolver policy.

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: Run nmcli connection show --active and compare with nmcli connection show.

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: Run nmcli connection show --active and compare with nmcli connection show.

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: Run nmcli connection show --active and compare with nmcli connection show.

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 Run nmcli connection show --active and compare with nmcli connection show. 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 Run nmcli connection show --active and compare with nmcli connection show. satisfies the stated condition.

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 Run nmcli connection show --active and compare with nmcli connection show. satisfies the stated condition.

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 Run nmcli connection show --active and compare with nmcli connection show.; the relevant evidence must establish The intended profile appears active for the correct device; stale saved profiles are distinguishable.

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 Run nmcli connection show --active and compare with nmcli connection show.; the relevant evidence must establish The intended profile appears active for the correct device; stale saved profiles are distinguishable.

That observation checks A host must consult local files before DNS for resolving service hostnames. In this scenario it does not demonstrate Run nmcli connection show --active and compare with nmcli connection show.; the relevant evidence must establish The intended profile appears active for the correct device; stale saved profiles are distinguishable.

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 The operator edits an inactive duplicate profile while the active one retains wrong settings. The current requirement calls for a different check.

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 The operator edits an inactive duplicate profile while the active one retains wrong settings. The current requirement calls for a different check.

That symptom concerns A NetworkManager-managed Ethernet connection must retain its static IPv4 address after restart. This concerns a separate requirement, not the one being tested. The relevant failure is The operator edits an inactive duplicate profile while the active one retains wrong settings. 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 The operator edits an inactive duplicate profile while the active one retains wrong settings. and needs Identify the active connection profile and modify that specific entry.

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 The operator edits an inactive duplicate profile while the active one retains wrong settings. and needs Identify the active connection profile and modify that specific entry.

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 The operator edits an inactive duplicate profile while the active one retains wrong settings. and needs Identify the active connection profile and modify that specific entry.

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: Configure a matching .network file under /etc/systemd/network/ and reload/reconfigure systemd-networkd.

Configure a NetworkManager Wi-Fi connection with the correct SSID, security and autoconnect properties. That operation is designed for the different case: A workstation Wi-Fi profile must join a secured SSID automatically after reboot. It does not perform the specific action required here: Configure a matching .network file under /etc/systemd/network/ and reload/reconfigure systemd-networkd.

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: Configure a matching .network file under /etc/systemd/network/ and reload/reconfigure systemd-networkd.

This explains another Linux operation, namely Use hostnamectl set-hostname newname on a systemd host., where hostnamectl persists the configured static hostname while the hostname shell command can display or set transient state. It does not explain why Configure a matching .network file under /etc/systemd/network/ and reload/reconfigure systemd-networkd. 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 Configure a matching .network file under /etc/systemd/network/ and reload/reconfigure systemd-networkd. satisfies the stated condition.

This explains another Linux operation, namely Run nmcli connection show --active and compare with nmcli connection show., where The active-only view lists activated profiles, which can differ from saved profiles on the system. It does not explain why Configure a matching .network file under /etc/systemd/network/ and reload/reconfigure systemd-networkd. satisfies the stated condition.