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 technician changes the current shell prompt's hostname appearance but the real host identity remains unchanged after reboot. Which check MOST directly diagnoses or confirms the technical condition described?
Compare hostnamectl status with the effective hostname command after reboot. This check targets the relevant state for persisting the system hostname and directly assesses the observed behavior. The result should be evaluated against: hostnamectl reports the intended static hostname after a controlled restart.
Inspect DNS packet transport, port 53 firewall counters and resolver retries. This check is relevant to dns request transport awareness but not the most targeted diagnosis of persisting the system hostname. The specific check is: Compare hostnamectl status with the effective hostname command after reboot.
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 persisting the system hostname. The specific check is: Compare hostnamectl status with the effective hostname command after reboot.
Inspect systemctl status systemd-networkd and networkctl status for the interface. This check is relevant to recognizing systemd-networkd management but not the most targeted diagnosis of persisting the system hostname. The specific check is: Compare hostnamectl status with the effective hostname command after reboot.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: An application resolves an old local mapping even though the DNS server has the correct address for the name. Which step MOST directly corrects the specific problem described?
Check /etc/nsswitch.conf host lookup order and remove the stale authorized /etc/hosts override. This targets the observed issue, host lookup precedence between files and dns, rather than a separate Linux configuration. Underlying behavior: NSS host lookup may consult local files before DNS according to its configured source order. Verify the action by checking: getent hosts returns the approved effective address for the application.
Use resolvectl status to inspect the upstream servers managed by systemd-resolved. This is an appropriate response to a different issue (distinguishing a systemd-resolved stub from external dns) but does not MOST directly address the explicit host lookup precedence between files and dns 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 host lookup precedence between files and dns failure.
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 host lookup precedence between files and dns failure.
A Linux team is checking the acceptance evidence for this specific situation: An application resolves an old local mapping even though the DNS server has the correct address for the name. Which observation BEST confirms that this particular issue has been corrected?
getent hosts returns the approved effective address for the application. That evidence specifically demonstrates recovery from host lookup precedence between files and dns. The technical reason is: NSS host lookup may consult local files before DNS according to its configured source order.
The effective resolver matches the approved servers after reconnect. This can validate persisting dns settings through networkmanager, but it does not establish that the described host lookup precedence between files and dns issue is fixed. The case-specific evidence is: getent hosts returns the approved effective address for the application.
The route table includes the approved default gateway and off-subnet probes succeed. This can validate diagnosing a missing default route, but it does not establish that the described host lookup precedence between files and dns issue is fixed. The case-specific evidence is: getent hosts returns the approved effective address for the application.
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 host lookup precedence between files and dns issue is fixed. The case-specific evidence is: getent hosts returns the approved effective address for the application.
A Linux engineer reviews the underlying behavior in this particular case: An application resolves an old local mapping even though the DNS server has the correct address for the name. Which technical behavior BEST explains this particular failure and its remedy?
NSS host lookup may consult local files before DNS according to its configured source order. This Linux behavior explains the observed symptoms and supports the precise remedy: Check /etc/nsswitch.conf host lookup order and remove the stale authorized /etc/hosts override.
The hosts file provides local name-to-address mappings for clients whose NSS configuration uses it. This describes another behavior (static hosts mapping without dns changes) and does not explain the stated host lookup precedence between files and dns failure. The operative behavior is: NSS host lookup may consult local files before DNS according to its configured source order.
A network manager can regenerate resolver settings from its active connection profiles. This describes another behavior (persisting dns settings through networkmanager) and does not explain the stated host lookup precedence between files and dns failure. The operative behavior is: NSS host lookup may consult local files before DNS according to its configured source order.
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 host lookup precedence between files and dns failure. The operative behavior is: NSS host lookup may consult local files before DNS according to its configured source order.
A Linux operating control has not corrected the following specific problem: An application resolves an old local mapping even though the DNS server has the correct address for the name. Which outcome is the MOST directly associated operational risk if this problem remains?
Applications can connect to retired addresses despite healthy authoritative DNS. This is the directly relevant consequence of leaving the host lookup precedence between files and dns problem unresolved. The appropriate preventive change is: Check /etc/nsswitch.conf host lookup order and remove the stale authorized /etc/hosts override.
Local connectivity may mask a complete loss of Internet access. This consequence is connected to diagnosing a missing default route rather than the MOST direct exposure in the stated host lookup precedence between files and dns problem. The specific consequence is: Applications can connect to retired addresses despite healthy authoritative DNS.
Manual resolver edits may vanish and cause intermittent name resolution. This consequence is connected to persisting dns settings through networkmanager rather than the MOST direct exposure in the stated host lookup precedence between files and dns problem. The specific consequence is: Applications can connect to retired addresses despite healthy authoritative DNS.
A healthy new NIC may remain unmanaged with no persistent IP configuration. This consequence is connected to networkmanager connection bound to wrong interface rather than the MOST direct exposure in the stated host lookup precedence between files and dns problem. The specific consequence is: Applications can connect to retired addresses despite healthy authoritative DNS.
A Linux troubleshooter is gathering specific evidence for this situation: An application resolves an old local mapping even though the DNS server has the correct address for the name. Which check MOST directly diagnoses or confirms the technical condition described?
Compare getent hosts output, /etc/hosts and a direct dig query. This check targets the relevant state for host lookup precedence between files and dns and directly assesses the observed behavior. The result should be evaluated against: getent hosts returns the approved effective address for the application.
Compare ip route default with nmcli connection ipv4.gateway properties. This examines the different Linux issue 'Persisting an IPv4 default gateway', not the specific host lookup precedence between files and dns in this question. The appropriate scenario-specific evidence or remedy is: Compare getent hosts output, /etc/hosts and a direct dig query.
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 host lookup precedence between files and dns. The specific check is: Compare getent hosts output, /etc/hosts and a direct dig query.
Inspect UDP 123 counters and the NTP client's peer statistics. This check is relevant to ntp port and udp transport but not the most targeted diagnosis of host lookup precedence between files and dns. The specific check is: Compare getent hosts output, /etc/hosts and a direct dig query.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A training VM needs one temporary local hostname mapping, but there is no permission to edit the organization's DNS zone. Which step MOST directly corrects the specific problem described?
Add a narrowly scoped entry to /etc/hosts on that VM and verify NSS behavior. This targets the observed issue, static hosts mapping without dns changes, rather than a separate Linux configuration. Underlying behavior: The hosts file provides local name-to-address mappings for clients whose NSS configuration uses it. Verify the action by checking: getent hosts on the VM resolves the local alias without modifying external DNS records.
Compare getent hosts with dig and inspect name service switch policy. This is an appropriate response to a different issue (checking nss host resolution versus dns-only queries) but does not MOST directly address the explicit static hosts mapping without dns changes failure.
Configure the intended IPv4 gateway in the persistent network profile rather than relying on a runtime ip route add. This is an appropriate response to a different issue (persisting an ipv4 default gateway) but does not MOST directly address the explicit static hosts mapping without dns changes failure.
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 static hosts mapping without dns changes failure.
A Linux team is checking the acceptance evidence for this specific situation: A training VM needs one temporary local hostname mapping, but there is no permission to edit the organization's DNS zone. Which observation BEST confirms that this particular issue has been corrected?
getent hosts on the VM resolves the local alias without modifying external DNS records. That evidence specifically demonstrates recovery from static hosts mapping without dns changes. The technical reason is: The hosts file provides local name-to-address mappings for clients whose NSS configuration uses it.
The effective resolver matches the approved servers after reconnect. This can validate persisting dns settings through networkmanager, but it does not establish that the described static hosts mapping without dns changes issue is fixed. The case-specific evidence is: getent hosts on the VM resolves the local alias without modifying external DNS records.
The two endpoint interfaces receive usable addresses from the same /30 network. This can validate recognizing a point-to-point ipv4 prefix, but it does not establish that the described static hosts mapping without dns changes issue is fixed. The case-specific evidence is: getent hosts on the VM resolves the local alias without modifying external DNS records.
resolvectl status and the effective resolver path agree after restart. This can validate resolver file managed by systemd-resolved, but it does not establish that the described static hosts mapping without dns changes issue is fixed. The case-specific evidence is: getent hosts on the VM resolves the local alias without modifying external DNS records.
A Linux engineer reviews the underlying behavior in this particular case: A training VM needs one temporary local hostname mapping, but there is no permission to edit the organization's DNS zone. Which technical behavior BEST explains this particular failure and its remedy?
The hosts file provides local name-to-address mappings for clients whose NSS configuration uses it. This Linux behavior explains the observed symptoms and supports the precise remedy: Add a narrowly scoped entry to /etc/hosts on that VM and verify NSS behavior.
NSS host lookup may consult local files before DNS according to its configured source order. This describes another behavior (host lookup precedence between files and dns) and does not explain the stated static hosts mapping without dns changes failure. The operative behavior is: The hosts file provides local name-to-address mappings for clients whose NSS configuration uses it.
The iproute2 address view reports the kernel's current interface addressing state. This describes another behavior (inspecting local interface addresses with iproute2) and does not explain the stated static hosts mapping without dns changes failure. The operative behavior is: The hosts file provides local name-to-address mappings for clients whose NSS configuration uses it.
Wireless association and authentication precede DHCP or static IP connectivity. This describes another behavior (managing wi-fi association in networkmanager) and does not explain the stated static hosts mapping without dns changes failure. The operative behavior is: The hosts file provides local name-to-address mappings for clients whose NSS configuration uses it.
A Linux operating control has not corrected the following specific problem: A training VM needs one temporary local hostname mapping, but there is no permission to edit the organization's DNS zone. Which outcome is the MOST directly associated operational risk if this problem remains?
A mistaken global DNS change could affect unrelated users. This is the directly relevant consequence of leaving the static hosts mapping without dns changes problem unresolved. The appropriate preventive change is: Add a narrowly scoped entry to /etc/hosts on that VM and verify NSS behavior.
Logs and monitoring can continue reporting an unexpected host identity. This consequence is connected to persisting the system hostname rather than the MOST direct exposure in the stated static hosts mapping without dns changes problem. The specific consequence is: A mistaken global DNS change could affect unrelated users.
Manual resolver edits may vanish and cause intermittent name resolution. This consequence is connected to persisting dns settings through networkmanager rather than the MOST direct exposure in the stated static hosts mapping without dns changes problem. The specific consequence is: A mistaken global DNS change could affect unrelated users.
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 static hosts mapping without dns changes problem. The specific consequence is: A mistaken global DNS change could affect unrelated users.
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.
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.