Pass LPI 102-500 Exam in First Attempt Easily
Real LPI 102-500 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts
3 products

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
$79.99 $149.97

Purchase Individually

  • Premium File

    120 Questions & Answers
    Last Update: Nov 10, 2026

    $76.99
    $69.99
  • Training Course

    126 Lectures

    $43.99
    $39.99
  • Study Guide

    962 Pages

    $43.99
    $39.99

LPI Level 1 102-500 Practice Test 59

Question 580

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?

  1. Inspect ip route default, ARP neighbor state and gateway reachability.
  2. Check nmcli device show DNS information and the effective resolv.conf ownership.
  3. Compare ip route default with nmcli connection ipv4.gateway properties.
  4. Inspect nmcli connection show for autoconnect and active profile state.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

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.

B:

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.

D:

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.

Question 581

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?

  1. Identify the active network-management service and edit the appropriate systemd-networkd configuration.
  2. Reconcile the resolver link and configure the approved DNS servers through the actual active resolver manager.
  3. Change the relevant NetworkManager connection DNS properties and reactivate the profile.
  4. Use dig with an explicit @server target to query each resolver independently.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

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.

C:

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.

D:

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.

Question 582

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?

  1. hostnamectl reports the intended static hostname after a controlled restart.
  2. systemd-networkd reports a managed interface with the intended persistent addresses after restart.
  3. resolvectl status and the effective resolver path agree after restart.
  4. The gateway's neighbor entry resolves to the expected link-layer destination.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

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.

B:

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.

D:

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.

Question 583

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?

  1. A client must know where to send DNS questions, whether via resolv.conf or a resolver manager.
  2. Persistent interface profiles recreate routes when interfaces are activated.
  3. A systemd-resolved stub listener and managed resolv.conf link are part of the resolver configuration path.
  4. The configured hostname is distinct from a shell prompt variable or transient display text.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

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.

B:

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.

D:

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.

Question 584

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?

  1. A false connectivity test can hide a genuine remote outage.
  2. Ad-hoc file changes may disconnect clients from the active stub resolver.
  3. A reboot can leave an unattended network client offline.
  4. Applications can connect to retired addresses despite healthy authoritative DNS.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

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.

C:

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.

D:

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.

Question 585

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?

  1. Inspect the source address, NAT translations and Internet edge routing tables.
  2. Inspect nmcli connection show for autoconnect and active profile state.
  3. Check nmcli device show DNS information and the effective resolv.conf ownership.
  4. Inspect ls -l /etc/resolv.conf and resolvectl status rather than editing blindly.

Explanation

Correct Answer

D:

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.

Incorrect Answers

A:

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.

B:

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.

C:

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.

Question 586

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?

  1. Update the profile's interface binding to the actual device and reactivate it.
  2. Identify the active network-management service and edit the appropriate systemd-networkd configuration.
  3. Use iproute2 tools such as ip address and ip link for current interface inspection.
  4. Configure the intended static address in the persistent NetworkManager connection profile using nmcli.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

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.

C:

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.

D:

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.

Question 587

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?

  1. The intended profile activates on the new interface and applies its saved settings.
  2. systemd-networkd reports a managed interface with the intended persistent addresses after restart.
  3. The expected TCP listener appears bound to the authorized local or public interface address.
  4. hostnamectl reports the intended static hostname after a controlled restart.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

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.

C:

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.

D:

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.

Question 588

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?

  1. A client must know where to send DNS questions, whether via resolv.conf or a resolver manager.
  2. A NetworkManager profile can be restricted to a named interface or hardware identity.
  3. ip addr changes runtime kernel interface state; NetworkManager connection profiles store persistent settings.
  4. NetworkManager's autoconnect property governs automatic connection activation.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

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.

C:

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.

D:

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.

Question 589

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?

  1. A healthy new NIC may remain unmanaged with no persistent IP configuration.
  2. Ad-hoc file changes may disconnect clients from the active stub resolver.
  3. Name resolution can fail despite a reachable DNS server.
  4. A host may lose network service after restart despite a successful temporary test.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

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.

C:

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.

D:

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.

Question 590

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?

  1. Compare ip route default with nmcli connection ipv4.gateway properties.
  2. Check nmcli device show DNS information and the effective resolv.conf ownership.
  3. Inspect nmcli connection interface-name and nmcli device status.
  4. Compare the remote interface IPv6 address with the local loopback route.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

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.

B:

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.

D:

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.

LPI Level 1 (102-500) Practice Tests

Purchase Individually

  • Premium File

    120 Questions & Answers
    Last Update: Nov 10, 2026

    $76.99
    $69.99
  • Training Course

    126 Lectures

    $43.99
    $39.99
  • Study Guide

    962 Pages

    $43.99
    $39.99

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports