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: An application resolves a service name through local policy, but dig reports a different record and the engineer calls dig definitive. Which check MOST directly diagnoses or confirms the technical condition described?
Inspect hosts: in /etc/nsswitch.conf and compare getent and dig results. This check targets the relevant state for checking nss host resolution versus dns-only queries and directly assesses the observed behavior. The result should be evaluated against: The application-facing effective result matches NSS configuration and any hosts-file overrides.
Check nmcli device show DNS information and the effective resolv.conf ownership. This check examines persisting dns settings through networkmanager instead of the decisive checking nss host resolution versus dns-only queries condition. Start by checking: Inspect hosts: in /etc/nsswitch.conf and compare getent and dig results.
Inspect /etc/resolv.conf, resolver-manager status and a direct DNS query. This check is relevant to setting an approved resolver nameserver but not the most targeted diagnosis of checking nss host resolution versus dns-only queries. The specific check is: Inspect hosts: in /etc/nsswitch.conf and compare getent and dig results.
Compare dig @server outputs for both resolvers and the relevant record type. This check is relevant to querying a specific dns server directly but not the most targeted diagnosis of checking nss host resolution versus dns-only queries. The specific check is: Inspect hosts: in /etc/nsswitch.conf and compare getent and dig results.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A minimal client has no usable DNS servers listed and IP-literal connections work while all DNS names fail. Which step MOST directly corrects the specific problem described?
Configure an approved nameserver through the system's actual resolver management path. This targets the observed issue, setting an approved resolver nameserver, rather than a separate Linux configuration. Underlying behavior: A client must know where to send DNS questions, whether via resolv.conf or a resolver manager. Verify the action by checking: The effective resolver lists an accessible DNS server and host queries succeed.
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 setting an approved resolver nameserver failure.
Set the intended hosts database lookup order in /etc/nsswitch.conf according to site policy. This is an appropriate response to a different issue (correcting the hosts lookup source order) but does not MOST directly address the explicit setting an approved resolver nameserver 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 setting an approved resolver nameserver failure.
A Linux team is checking the acceptance evidence for this specific situation: A minimal client has no usable DNS servers listed and IP-literal connections work while all DNS names fail. Which observation BEST confirms that this particular issue has been corrected?
The effective resolver lists an accessible DNS server and host queries succeed. That evidence specifically demonstrates recovery from setting an approved resolver nameserver. The technical reason is: A client must know where to send DNS questions, whether via resolv.conf or a resolver manager.
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 setting an approved resolver nameserver issue is fixed. The case-specific evidence is: The effective resolver lists an accessible DNS server and host queries succeed.
The differing A or AAAA responses are attributed to the respective servers. This can validate querying a specific dns server directly, but it does not establish that the described setting an approved resolver nameserver issue is fixed. The case-specific evidence is: The effective resolver lists an accessible DNS server and host queries succeed.
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 setting an approved resolver nameserver issue is fixed. The case-specific evidence is: The effective resolver lists an accessible DNS server and host queries succeed.
A Linux engineer reviews the underlying behavior in this particular case: A minimal client has no usable DNS servers listed and IP-literal connections work while all DNS names fail. Which technical behavior BEST explains this particular failure and its remedy?
A client must know where to send DNS questions, whether via resolv.conf or a resolver manager. This Linux behavior explains the observed symptoms and supports the precise remedy: Configure an approved nameserver through the system's actual resolver management path.
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 setting an approved resolver nameserver failure. The operative behavior is: A client must know where to send DNS questions, whether via resolv.conf or a resolver manager.
NTP commonly uses UDP transport with port 123, not an ordinary TCP connection. This describes another behavior (ntp port and udp transport) and does not explain the stated setting an approved resolver nameserver failure. The operative behavior is: A client must know where to send DNS questions, whether via resolv.conf or a resolver manager.
A direct dig query can bypass the system's default resolver selection to examine a chosen server. This describes another behavior (querying a specific dns server directly) and does not explain the stated setting an approved resolver nameserver failure. The operative behavior is: A client must know where to send DNS questions, whether via resolv.conf or a resolver manager.
A Linux operating control has not corrected the following specific problem: A minimal client has no usable DNS servers listed and IP-literal connections work while all DNS names fail. Which outcome is the MOST directly associated operational risk if this problem remains?
Name-based applications can fail even when routing is healthy. This is the directly relevant consequence of leaving the setting an approved resolver nameserver problem unresolved. The appropriate preventive change is: Configure an approved nameserver through the system's actual resolver management path.
Changing local hosts files will not fix stale data on one upstream resolver. This consequence is connected to querying a specific dns server directly rather than the MOST direct exposure in the stated setting an approved resolver nameserver problem. The specific consequence is: Name-based applications can fail even when routing is healthy.
Missing datagrams may leave files incomplete if the application assumes guaranteed delivery. This consequence is connected to tcp delivery versus udp datagrams rather than the MOST direct exposure in the stated setting an approved resolver nameserver problem. The specific consequence is: Name-based applications can fail even when routing is healthy.
DNS-only tests may miss local overrides that drive actual application behavior. This consequence is connected to checking nss host resolution versus dns-only queries rather than the MOST direct exposure in the stated setting an approved resolver nameserver problem. The specific consequence is: Name-based applications can fail even when routing is healthy.
A Linux troubleshooter is gathering specific evidence for this situation: A minimal client has no usable DNS servers listed and IP-literal connections work while all DNS names fail. Which check MOST directly diagnoses or confirms the technical condition described?
Inspect /etc/resolv.conf, resolver-manager status and a direct DNS query. This check targets the relevant state for setting an approved resolver nameserver and directly assesses the observed behavior. The result should be evaluated against: The effective resolver lists an accessible DNS server and host queries succeed.
Inspect hosts: in /etc/nsswitch.conf and compare getent and dig results. This check is relevant to checking nss host resolution versus dns-only queries but not the most targeted diagnosis of setting an approved resolver nameserver. The specific check is: Inspect /etc/resolv.conf, resolver-manager status and a direct DNS query.
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 setting an approved resolver nameserver. The specific check is: Inspect /etc/resolv.conf, resolver-manager status and a direct DNS query.
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 setting an approved resolver nameserver condition. Start by checking: Inspect /etc/resolv.conf, resolver-manager status and a direct DNS query.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A maintenance script must honor temporary local hosts entries, but /etc/nsswitch.conf queries DNS before files. Which step MOST directly corrects the specific problem described?
Set the intended hosts database lookup order in /etc/nsswitch.conf according to site policy. This targets the observed issue, correcting the hosts lookup source order, rather than a separate Linux configuration. Underlying behavior: NSS host lookup order determines which source is consulted first. Verify the action by checking: getent hosts uses the approved local entry before the external DNS answer.
Use ss -lnt to check the listener address and port on the server. This is an appropriate response to a different issue (identifying local listening tcp sockets) but does not MOST directly address the explicit correcting the hosts lookup source order failure.
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 correcting the hosts lookup source order 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 correcting the hosts lookup source order failure.
A Linux team is checking the acceptance evidence for this specific situation: A maintenance script must honor temporary local hosts entries, but /etc/nsswitch.conf queries DNS before files. Which observation BEST confirms that this particular issue has been corrected?
getent hosts uses the approved local entry before the external DNS answer. That evidence specifically demonstrates recovery from correcting the hosts lookup source order. The technical reason is: NSS host lookup order determines which source is consulted first.
The effective resolver lists an accessible DNS server and host queries succeed. This can validate setting an approved resolver nameserver, but it does not establish that the described correcting the hosts lookup source order issue is fixed. The case-specific evidence is: getent hosts uses the approved local entry before the external DNS answer.
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 correcting the hosts lookup source order issue is fixed. The case-specific evidence is: getent hosts uses the approved local entry before the external DNS answer.
The application-facing effective result matches NSS configuration and any hosts-file overrides. This can validate checking nss host resolution versus dns-only queries, but it does not establish that the described correcting the hosts lookup source order issue is fixed. The case-specific evidence is: getent hosts uses the approved local entry before the external DNS answer.
A Linux engineer reviews the underlying behavior in this particular case: A maintenance script must honor temporary local hosts entries, but /etc/nsswitch.conf queries DNS before files. Which technical behavior BEST explains this particular failure and its remedy?
NSS host lookup order determines which source is consulted first. This Linux behavior explains the observed symptoms and supports the precise remedy: Set the intended hosts database lookup order in /etc/nsswitch.conf according to site policy.
A direct dig query can bypass the system's default resolver selection to examine a chosen server. This describes another behavior (querying a specific dns server directly) and does not explain the stated correcting the hosts lookup source order failure. The operative behavior is: NSS host lookup order determines which source is consulted first.
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 correcting the hosts lookup source order failure. The operative behavior is: NSS host lookup order determines which source is consulted first.
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 correcting the hosts lookup source order failure. The operative behavior is: NSS host lookup order determines which source is consulted first.
A Linux operating control has not corrected the following specific problem: A maintenance script must honor temporary local hosts entries, but /etc/nsswitch.conf queries DNS before files. Which outcome is the MOST directly associated operational risk if this problem remains?
An unexpected lookup order can send applications to the wrong endpoint. This is the directly relevant consequence of leaving the correcting the hosts lookup source order problem unresolved. The appropriate preventive change is: Set the intended hosts database lookup order in /etc/nsswitch.conf according to site policy.
Unverified assumptions can lead to changing the wrong interface. This consequence is connected to inspecting local interface addresses with iproute2 rather than the MOST direct exposure in the stated correcting the hosts lookup source order problem. The specific consequence is: An unexpected lookup order can send applications to the wrong endpoint.
Incorrect diagnosis can prompt removal of a functioning local resolver stub. This consequence is connected to distinguishing a systemd-resolved stub from external dns rather than the MOST direct exposure in the stated correcting the hosts lookup source order problem. The specific consequence is: An unexpected lookup order can send applications to the wrong endpoint.
Changing local hosts files will not fix stale data on one upstream resolver. This consequence is connected to querying a specific dns server directly rather than the MOST direct exposure in the stated correcting the hosts lookup source order problem. The specific consequence is: An unexpected lookup order can send applications to the wrong endpoint.
A Linux troubleshooter is gathering specific evidence for this situation: A maintenance script must honor temporary local hosts entries, but /etc/nsswitch.conf queries DNS before files. Which check MOST directly diagnoses or confirms the technical condition described?
Compare /etc/nsswitch.conf hosts order and getent outputs in a controlled fixture. This check targets the relevant state for correcting the hosts lookup source order and directly assesses the observed behavior. The result should be evaluated against: getent hosts uses the approved local entry before the external DNS answer.
Inspect /etc/resolv.conf, resolver-manager status and a direct DNS query. This check is relevant to setting an approved resolver nameserver but not the most targeted diagnosis of correcting the hosts lookup source order. The specific check is: Compare /etc/nsswitch.conf hosts order and getent outputs in a controlled fixture.
Calculate the host-bit count and compare the proposed prefix with the address plan. This check is relevant to cidr prefix and ipv4 usable hosts but not the most targeted diagnosis of correcting the hosts lookup source order. The specific check is: Compare /etc/nsswitch.conf hosts order and getent outputs in a controlled fixture.
Compare dig @server outputs for both resolvers and the relevant record type. This check is relevant to querying a specific dns server directly but not the most targeted diagnosis of correcting the hosts lookup source order. The specific check is: Compare /etc/nsswitch.conf hosts order and getent outputs in a controlled fixture.
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.