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 training VM needs one temporary local hostname mapping, but there is no permission to edit the organization's DNS zone. Which check MOST directly diagnoses or confirms the technical condition described?
Inspect /etc/hosts and the effective hosts source order. This check targets the relevant state for static hosts mapping without dns changes and directly assesses the observed behavior. The result should be evaluated against: getent hosts on the VM resolves the local alias without modifying external DNS records.
Compare ip address output with nmcli connection show for the relevant profile. This check is relevant to persistent static ipv4 with networkmanager but not the most targeted diagnosis of static hosts mapping without dns changes. The specific check is: Inspect /etc/hosts and the effective hosts source order.
Compare dig @server outputs for both resolvers and the relevant record type. This check examines querying a specific dns server directly instead of the decisive static hosts mapping without dns changes condition. Start by checking: Inspect /etc/hosts and the effective hosts source order.
Inspect resolvectl status together with resolv.conf and listener addresses. This check examines distinguishing a systemd-resolved stub from external dns instead of the decisive static hosts mapping without dns changes condition. Start by checking: Inspect /etc/hosts and the effective hosts source order.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A minimal server uses systemd-networkd, but an operator repeatedly invokes nmcli and sees no managed NetworkManager connection. Which step MOST directly corrects the specific problem described?
Identify the active network-management service and edit the appropriate systemd-networkd configuration. This targets the observed issue, recognizing systemd-networkd management, rather than a separate Linux configuration. Underlying behavior: systemd-networkd and NetworkManager are different configuration managers that may not both manage an interface. Verify the action by checking: systemd-networkd reports a managed interface with the intended persistent addresses after restart.
Reconcile the resolver link and configure the approved DNS servers through the actual active resolver manager. This is an appropriate response to a different issue (resolver file managed by systemd-resolved) but does not MOST directly address the explicit recognizing systemd-networkd management failure.
Set the static hostname through hostnamectl or supported host identity configuration. This is an appropriate response to a different issue (persisting the system hostname) but does not MOST directly address the explicit recognizing systemd-networkd management failure.
Configure an approved nameserver through the system's actual resolver management path. This is an appropriate response to a different issue (setting an approved resolver nameserver) but does not MOST directly address the explicit recognizing systemd-networkd management failure.
A Linux team is checking the acceptance evidence for this specific situation: A minimal server uses systemd-networkd, but an operator repeatedly invokes nmcli and sees no managed NetworkManager connection. Which observation BEST confirms that this particular issue has been corrected?
systemd-networkd reports a managed interface with the intended persistent addresses after restart. That evidence specifically demonstrates recovery from recognizing systemd-networkd management. The technical reason is: systemd-networkd and NetworkManager are different configuration managers that may not both manage an interface.
The intended profile activates on the new interface and applies its saved settings. This can validate networkmanager connection bound to wrong interface, but it does not establish that the described recognizing systemd-networkd management issue is fixed. The case-specific evidence is: systemd-networkd reports a managed interface with the intended persistent addresses after restart.
The default route reappears after connection reactivation without manual commands. This can validate persisting an ipv4 default gateway, but it does not establish that the described recognizing systemd-networkd management issue is fixed. The case-specific evidence is: systemd-networkd reports a managed interface with the intended persistent addresses after restart.
The active upstream DNS addresses are identified separately from the local stub listener. This can validate distinguishing a systemd-resolved stub from external dns, but it does not establish that the described recognizing systemd-networkd management issue is fixed. The case-specific evidence is: systemd-networkd reports a managed interface with the intended persistent addresses after restart.
A Linux engineer reviews the underlying behavior in this particular case: A minimal server uses systemd-networkd, but an operator repeatedly invokes nmcli and sees no managed NetworkManager connection. Which technical behavior BEST explains this particular failure and its remedy?
systemd-networkd and NetworkManager are different configuration managers that may not both manage an interface. This Linux behavior explains the observed symptoms and supports the precise remedy: Identify the active network-management service and edit the appropriate systemd-networkd configuration.
Persistent interface profiles recreate routes when interfaces are activated. This describes another behavior (persisting an ipv4 default gateway) and does not explain the stated recognizing systemd-networkd management failure. The operative behavior is: systemd-networkd and NetworkManager are different configuration managers that may not both manage an interface.
The IPv6 loopback address ::1 always refers to the local system. This describes another behavior (ipv6 loopback diagnosis) and does not explain the stated recognizing systemd-networkd management failure. The operative behavior is: systemd-networkd and NetworkManager are different configuration managers that may not both manage an interface.
A systemd-resolved stub listener and managed resolv.conf link are part of the resolver configuration path. This describes another behavior (resolver file managed by systemd-resolved) and does not explain the stated recognizing systemd-networkd management failure. The operative behavior is: systemd-networkd and NetworkManager are different configuration managers that may not both manage an interface.
A Linux operating control has not corrected the following specific problem: A minimal server uses systemd-networkd, but an operator repeatedly invokes nmcli and sees no managed NetworkManager connection. Which outcome is the MOST directly associated operational risk if this problem remains?
Using the wrong manager can leave network settings unapplied. This is the directly relevant consequence of leaving the recognizing systemd-networkd management problem unresolved. The appropriate preventive change is: Identify the active network-management service and edit the appropriate systemd-networkd configuration.
Route or resolver changes could obscure the actual cabling failure. This consequence is connected to checking interface admin-up versus physical carrier rather than the MOST direct exposure in the stated recognizing systemd-networkd management problem. The specific consequence is: Using the wrong manager can leave network settings unapplied.
Users may blame IP routing when the device never joined the WLAN. This consequence is connected to managing wi-fi association in networkmanager rather than the MOST direct exposure in the stated recognizing systemd-networkd management problem. The specific consequence is: Using the wrong manager can leave network settings unapplied.
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 recognizing systemd-networkd management problem. The specific consequence is: Using the wrong manager can leave network settings unapplied.
A Linux troubleshooter is gathering specific evidence for this situation: A minimal server uses systemd-networkd, but an operator repeatedly invokes nmcli and sees no managed NetworkManager connection. Which check MOST directly diagnoses or confirms the technical condition described?
Inspect systemctl status systemd-networkd and networkctl status for the interface. This check targets the relevant state for recognizing systemd-networkd management and directly assesses the observed behavior. The result should be evaluated against: systemd-networkd reports a managed interface with the intended persistent addresses after restart.
Inspect ls -l /etc/resolv.conf and resolvectl status rather than editing blindly. This check is relevant to resolver file managed by systemd-resolved but not the most targeted diagnosis of recognizing systemd-networkd management. The specific check is: Inspect systemctl status systemd-networkd and networkctl status for the interface.
Inspect nmcli connection interface-name and nmcli device status. This check is relevant to networkmanager connection bound to wrong interface but not the most targeted diagnosis of recognizing systemd-networkd management. The specific check is: Inspect systemctl status systemd-networkd and networkctl status for the interface.
Inspect resolvectl status together with resolv.conf and listener addresses. This check is relevant to distinguishing a systemd-resolved stub from external dns but not the most targeted diagnosis of recognizing systemd-networkd management. The specific check is: Inspect systemctl status systemd-networkd and networkctl status for the interface.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A server's static address survives reboot but its manually added default route disappears because the connection profile lacks a gateway. Which step MOST directly corrects the specific problem described?
Configure the intended IPv4 gateway in the persistent network profile rather than relying on a runtime ip route add. This targets the observed issue, persisting an ipv4 default gateway, rather than a separate Linux configuration. Underlying behavior: Persistent interface profiles recreate routes when interfaces are activated. Verify the action by checking: The default route reappears after connection reactivation without manual commands.
Inspect ip neigh for the gateway and investigate Layer 2 neighbor resolution if its state fails. This is an appropriate response to a different issue (inspecting neighbor discovery for an ipv4 gateway) but does not MOST directly address the explicit persisting an ipv4 default gateway failure.
Add a narrowly scoped entry to /etc/hosts on that VM and verify NSS behavior. This is an appropriate response to a different issue (static hosts mapping without dns changes) but does not MOST directly address the explicit persisting an ipv4 default gateway 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 persisting an ipv4 default gateway failure.
A Linux team is checking the acceptance evidence for this specific situation: A server's static address survives reboot but its manually added default route disappears because the connection profile lacks a gateway. Which observation BEST confirms that this particular issue has been corrected?
The default route reappears after connection reactivation without manual commands. That evidence specifically demonstrates recovery from persisting an ipv4 default gateway. The technical reason is: Persistent interface profiles recreate routes when interfaces are activated.
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 persisting an ipv4 default gateway issue is fixed. The case-specific evidence is: The default route reappears after connection reactivation without manual commands.
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 persisting an ipv4 default gateway issue is fixed. The case-specific evidence is: The default route reappears after connection reactivation without manual commands.
The intended profile activates on the new interface and applies its saved settings. This can validate networkmanager connection bound to wrong interface, but it does not establish that the described persisting an ipv4 default gateway issue is fixed. The case-specific evidence is: The default route reappears after connection reactivation without manual commands.
A Linux engineer reviews the underlying behavior in this particular case: A server's static address survives reboot but its manually added default route disappears because the connection profile lacks a gateway. Which technical behavior BEST explains this particular failure and its remedy?
Persistent interface profiles recreate routes when interfaces are activated. This Linux behavior explains the observed symptoms and supports the precise remedy: Configure the intended IPv4 gateway in the persistent network profile rather than relying on a runtime ip route add.
NetworkManager's autoconnect property governs automatic connection activation. This describes another behavior (enabling automatic activation of a connection) and does not explain the stated persisting an ipv4 default gateway failure. The operative behavior is: Persistent interface profiles recreate routes when interfaces are activated.
A systemd-resolved stub listener and managed resolv.conf link are part of the resolver configuration path. This describes another behavior (resolver file managed by systemd-resolved) and does not explain the stated persisting an ipv4 default gateway failure. The operative behavior is: Persistent interface profiles recreate routes when interfaces are activated.
NSS host lookup order determines which source is consulted first. This describes another behavior (correcting the hosts lookup source order) and does not explain the stated persisting an ipv4 default gateway failure. The operative behavior is: Persistent interface profiles recreate routes when interfaces are activated.
A Linux operating control has not corrected the following specific problem: A server's static address survives reboot but its manually added default route disappears because the connection profile lacks a gateway. Which outcome is the MOST directly associated operational risk if this problem remains?
The host can reach local peers but not off-subnet services after reboot. This is the directly relevant consequence of leaving the persisting an ipv4 default gateway problem unresolved. The appropriate preventive change is: Configure the intended IPv4 gateway in the persistent network profile rather than relying on a runtime ip route add.
Remote clients cannot reach a service addressed only by a link-local destination. This consequence is connected to ipv6 link-local scope rather than the MOST direct exposure in the stated persisting an ipv4 default gateway problem. The specific consequence is: The host can reach local peers but not off-subnet services after reboot.
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 persisting an ipv4 default gateway problem. The specific consequence is: The host can reach local peers but not off-subnet services after reboot.
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 persisting an ipv4 default gateway problem. The specific consequence is: The host can reach local peers but not off-subnet services after reboot.
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.
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.