You save $69.98
102-500 Premium Bundle
- Premium File 120 Questions & Answers
- Last Update: Nov 10, 2026
- Training Course 126 Lectures
- Study Guide 962 Pages
You save $69.98
A Linux troubleshooter is gathering specific evidence for this situation: A server's static address survives reboot but its manually added default route disappears because the connection profile lacks a gateway. Which check MOST directly diagnoses or confirms the technical condition described?
Compare ip route default with nmcli connection ipv4.gateway properties. This check targets the relevant state for persisting an ipv4 default gateway and directly assesses the observed behavior. The result should be evaluated against: The default route reappears after connection reactivation without manual commands.
Inspect ip route default, ARP neighbor state and gateway reachability. This check is relevant to testing the local gateway before remote hosts but not the most targeted diagnosis of persisting an ipv4 default gateway. The specific check is: Compare ip route default with nmcli connection ipv4.gateway properties.
Check nmcli device show DNS information and the effective resolv.conf ownership. This check is relevant to persisting dns settings through networkmanager but not the most targeted diagnosis of persisting an ipv4 default gateway. The specific check is: Compare ip route default with nmcli connection ipv4.gateway properties.
Inspect nmcli connection show for autoconnect and active profile state. This check is relevant to enabling automatic activation of a connection but not the most targeted diagnosis of persisting an ipv4 default gateway. The specific check is: Compare ip route default with nmcli connection ipv4.gateway properties.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: An administrator overwrites a stub /etc/resolv.conf link on a system using systemd-resolved and later loses DNS after service restart. Which step MOST directly corrects the specific problem described?
Reconcile the resolver link and configure the approved DNS servers through the actual active resolver manager. This targets the observed issue, resolver file managed by systemd-resolved, rather than a separate Linux configuration. Underlying behavior: A systemd-resolved stub listener and managed resolv.conf link are part of the resolver configuration path. Verify the action by checking: resolvectl status and the effective resolver path agree after restart.
Identify the active network-management service and edit the appropriate systemd-networkd configuration. This is an appropriate response to a different issue (recognizing systemd-networkd management) but does not MOST directly address the explicit resolver file managed by systemd-resolved failure.
Change the relevant NetworkManager connection DNS properties and reactivate the profile. This is an appropriate response to a different issue (persisting dns settings through networkmanager) but does not MOST directly address the explicit resolver file managed by systemd-resolved failure.
Use dig with an explicit @server target to query each resolver independently. This is an appropriate response to a different issue (querying a specific dns server directly) but does not MOST directly address the explicit resolver file managed by systemd-resolved failure.
A Linux team is checking the acceptance evidence for this specific situation: An administrator overwrites a stub /etc/resolv.conf link on a system using systemd-resolved and later loses DNS after service restart. Which observation BEST confirms that this particular issue has been corrected?
resolvectl status and the effective resolver path agree after restart. That evidence specifically demonstrates recovery from resolver file managed by systemd-resolved. The technical reason is: A systemd-resolved stub listener and managed resolv.conf link are part of the resolver configuration path.
hostnamectl reports the intended static hostname after a controlled restart. This can validate persisting the system hostname, but it does not establish that the described resolver file managed by systemd-resolved issue is fixed. The case-specific evidence is: resolvectl status and the effective resolver path agree after restart.
systemd-networkd reports a managed interface with the intended persistent addresses after restart. This can validate recognizing systemd-networkd management, but it does not establish that the described resolver file managed by systemd-resolved issue is fixed. The case-specific evidence is: resolvectl status and the effective resolver path agree after restart.
The gateway's neighbor entry resolves to the expected link-layer destination. This can validate inspecting neighbor discovery for an ipv4 gateway, but it does not establish that the described resolver file managed by systemd-resolved issue is fixed. The case-specific evidence is: resolvectl status and the effective resolver path agree after restart.
A Linux engineer reviews the underlying behavior in this particular case: An administrator overwrites a stub /etc/resolv.conf link on a system using systemd-resolved and later loses DNS after service restart. Which technical behavior BEST explains this particular failure and its remedy?
A systemd-resolved stub listener and managed resolv.conf link are part of the resolver configuration path. This Linux behavior explains the observed symptoms and supports the precise remedy: Reconcile the resolver link and configure the approved DNS servers through the actual active resolver manager.
A client must know where to send DNS questions, whether via resolv.conf or a resolver manager. This describes another behavior (setting an approved resolver nameserver) and does not explain the stated resolver file managed by systemd-resolved failure. The operative behavior is: A systemd-resolved stub listener and managed resolv.conf link are part of the resolver configuration path.
Persistent interface profiles recreate routes when interfaces are activated. This describes another behavior (persisting an ipv4 default gateway) and does not explain the stated resolver file managed by systemd-resolved failure. The operative behavior is: A systemd-resolved stub listener and managed resolv.conf link are part of the resolver configuration path.
The configured hostname is distinct from a shell prompt variable or transient display text. This describes another behavior (persisting the system hostname) and does not explain the stated resolver file managed by systemd-resolved failure. The operative behavior is: A systemd-resolved stub listener and managed resolv.conf link are part of the resolver configuration path.
A Linux operating control has not corrected the following specific problem: An administrator overwrites a stub /etc/resolv.conf link on a system using systemd-resolved and later loses DNS after service restart. Which outcome is the MOST directly associated operational risk if this problem remains?
Ad-hoc file changes may disconnect clients from the active stub resolver. This is the directly relevant consequence of leaving the resolver file managed by systemd-resolved problem unresolved. The appropriate preventive change is: Reconcile the resolver link and configure the approved DNS servers through the actual active resolver manager.
A false connectivity test can hide a genuine remote outage. This consequence is connected to ipv6 loopback diagnosis rather than the MOST direct exposure in the stated resolver file managed by systemd-resolved problem. The specific consequence is: Ad-hoc file changes may disconnect clients from the active stub resolver.
A reboot can leave an unattended network client offline. This consequence is connected to enabling automatic activation of a connection rather than the MOST direct exposure in the stated resolver file managed by systemd-resolved problem. The specific consequence is: Ad-hoc file changes may disconnect clients from the active stub resolver.
Applications can connect to retired addresses despite healthy authoritative DNS. This consequence is connected to host lookup precedence between files and dns rather than the MOST direct exposure in the stated resolver file managed by systemd-resolved problem. The specific consequence is: Ad-hoc file changes may disconnect clients from the active stub resolver.
A Linux troubleshooter is gathering specific evidence for this situation: An administrator overwrites a stub /etc/resolv.conf link on a system using systemd-resolved and later loses DNS after service restart. Which check MOST directly diagnoses or confirms the technical condition described?
Inspect ls -l /etc/resolv.conf and resolvectl status rather than editing blindly. This check targets the relevant state for resolver file managed by systemd-resolved and directly assesses the observed behavior. The result should be evaluated against: resolvectl status and the effective resolver path agree after restart.
Inspect the source address, NAT translations and Internet edge routing tables. This check is relevant to private ipv4 address identification but not the most targeted diagnosis of resolver file managed by systemd-resolved. The specific check is: Inspect ls -l /etc/resolv.conf and resolvectl status rather than editing blindly.
Inspect nmcli connection show for autoconnect and active profile state. This check is relevant to enabling automatic activation of a connection but not the most targeted diagnosis of resolver file managed by systemd-resolved. The specific check is: Inspect ls -l /etc/resolv.conf and resolvectl status rather than editing blindly.
Check nmcli device show DNS information and the effective resolv.conf ownership. This check is relevant to persisting dns settings through networkmanager but not the most targeted diagnosis of resolver file managed by systemd-resolved. The specific check is: Inspect ls -l /etc/resolv.conf and resolvectl status rather than editing blindly.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A replacement NIC has a new interface name and the saved NetworkManager profile remains tied to the old interface. Which step MOST directly corrects the specific problem described?
Update the profile's interface binding to the actual device and reactivate it. This targets the observed issue, networkmanager connection bound to wrong interface, rather than a separate Linux configuration. Underlying behavior: A NetworkManager profile can be restricted to a named interface or hardware identity. Verify the action by checking: The intended profile activates on the new interface and applies its saved settings.
Identify the active network-management service and edit the appropriate systemd-networkd configuration. This is an appropriate response to a different issue (recognizing systemd-networkd management) but does not MOST directly address the explicit networkmanager connection bound to wrong interface failure.
Use iproute2 tools such as ip address and ip link for current interface inspection. This is an appropriate response to a different issue (recognizing legacy net-tools alternatives) but does not MOST directly address the explicit networkmanager connection bound to wrong interface failure.
Configure the intended static address in the persistent NetworkManager connection profile using nmcli. This is an appropriate response to a different issue (persistent static ipv4 with networkmanager) but does not MOST directly address the explicit networkmanager connection bound to wrong interface failure.
A Linux team is checking the acceptance evidence for this specific situation: A replacement NIC has a new interface name and the saved NetworkManager profile remains tied to the old interface. Which observation BEST confirms that this particular issue has been corrected?
The intended profile activates on the new interface and applies its saved settings. That evidence specifically demonstrates recovery from networkmanager connection bound to wrong interface. The technical reason is: A NetworkManager profile can be restricted to a named interface or hardware identity.
systemd-networkd reports a managed interface with the intended persistent addresses after restart. This can validate recognizing systemd-networkd management, but it does not establish that the described networkmanager connection bound to wrong interface issue is fixed. The case-specific evidence is: The intended profile activates on the new interface and applies its saved settings.
The expected TCP listener appears bound to the authorized local or public interface address. This can validate identifying local listening tcp sockets, but it does not establish that the described networkmanager connection bound to wrong interface issue is fixed. The case-specific evidence is: The intended profile activates on the new interface and applies its saved settings.
hostnamectl reports the intended static hostname after a controlled restart. This can validate persisting the system hostname, but it does not establish that the described networkmanager connection bound to wrong interface issue is fixed. The case-specific evidence is: The intended profile activates on the new interface and applies its saved settings.
A Linux engineer reviews the underlying behavior in this particular case: A replacement NIC has a new interface name and the saved NetworkManager profile remains tied to the old interface. Which technical behavior BEST explains this particular failure and its remedy?
A NetworkManager profile can be restricted to a named interface or hardware identity. This Linux behavior explains the observed symptoms and supports the precise remedy: Update the profile's interface binding to the actual device and reactivate it.
A client must know where to send DNS questions, whether via resolv.conf or a resolver manager. This describes another behavior (setting an approved resolver nameserver) and does not explain the stated networkmanager connection bound to wrong interface failure. The operative behavior is: A NetworkManager profile can be restricted to a named interface or hardware identity.
ip addr changes runtime kernel interface state; NetworkManager connection profiles store persistent settings. This describes another behavior (persistent static ipv4 with networkmanager) and does not explain the stated networkmanager connection bound to wrong interface failure. The operative behavior is: A NetworkManager profile can be restricted to a named interface or hardware identity.
NetworkManager's autoconnect property governs automatic connection activation. This describes another behavior (enabling automatic activation of a connection) and does not explain the stated networkmanager connection bound to wrong interface failure. The operative behavior is: A NetworkManager profile can be restricted to a named interface or hardware identity.
A Linux operating control has not corrected the following specific problem: A replacement NIC has a new interface name and the saved NetworkManager profile remains tied to the old interface. Which outcome is the MOST directly associated operational risk if this problem remains?
A healthy new NIC may remain unmanaged with no persistent IP configuration. This is the directly relevant consequence of leaving the networkmanager connection bound to wrong interface problem unresolved. The appropriate preventive change is: Update the profile's interface binding to the actual device and reactivate it.
Ad-hoc file changes may disconnect clients from the active stub resolver. This consequence is connected to resolver file managed by systemd-resolved rather than the MOST direct exposure in the stated networkmanager connection bound to wrong interface problem. The specific consequence is: A healthy new NIC may remain unmanaged with no persistent IP configuration.
Name resolution can fail despite a reachable DNS server. This consequence is connected to dns request transport awareness rather than the MOST direct exposure in the stated networkmanager connection bound to wrong interface problem. The specific consequence is: A healthy new NIC may remain unmanaged with no persistent IP configuration.
A host may lose network service after restart despite a successful temporary test. This consequence is connected to persistent static ipv4 with networkmanager rather than the MOST direct exposure in the stated networkmanager connection bound to wrong interface problem. The specific consequence is: A healthy new NIC may remain unmanaged with no persistent IP configuration.
A Linux troubleshooter is gathering specific evidence for this situation: A replacement NIC has a new interface name and the saved NetworkManager profile remains tied to the old interface. Which check MOST directly diagnoses or confirms the technical condition described?
Inspect nmcli connection interface-name and nmcli device status. This check targets the relevant state for networkmanager connection bound to wrong interface and directly assesses the observed behavior. The result should be evaluated against: The intended profile activates on the new interface and applies its saved settings.
Compare ip route default with nmcli connection ipv4.gateway properties. This check is relevant to persisting an ipv4 default gateway but not the most targeted diagnosis of networkmanager connection bound to wrong interface. The specific check is: Inspect nmcli connection interface-name and nmcli device status.
Check nmcli device show DNS information and the effective resolv.conf ownership. This check is relevant to persisting dns settings through networkmanager but not the most targeted diagnosis of networkmanager connection bound to wrong interface. The specific check is: Inspect nmcli connection interface-name and nmcli device status.
Compare the remote interface IPv6 address with the local loopback route. This check is relevant to ipv6 loopback diagnosis but not the most targeted diagnosis of networkmanager connection bound to wrong interface. The specific check is: Inspect nmcli connection interface-name and nmcli device status.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (120 Questions, Last Updated on Nov 10, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.