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 has a configured IP but cannot reach any LAN peer and the network interface reports no carrier. Which check MOST directly diagnoses or confirms the technical condition described?
Check ip link details and interface carrier indicators. This check targets the relevant state for checking interface admin-up versus physical carrier and directly assesses the observed behavior. The result should be evaluated against: The link reports carrier and an operational UP state after the cable or switch issue is resolved.
Check ip neigh show and switch VLAN or link details for the gateway. This check is relevant to inspecting neighbor discovery for an ipv4 gateway but not the most targeted diagnosis of checking interface admin-up versus physical carrier. The specific check is: Check ip link details and interface carrier indicators.
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 checking interface admin-up versus physical carrier. The specific check is: Check ip link details and interface carrier indicators.
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 checking interface admin-up versus physical carrier. The specific check is: Check ip link details and interface carrier indicators.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: Two resolver servers disagree on a host address and a technician wants to isolate which one returns stale data. Which step MOST directly corrects the specific problem described?
Use dig with an explicit @server target to query each resolver independently. This targets the observed issue, querying a specific dns server directly, rather than a separate Linux configuration. Underlying behavior: A direct dig query can bypass the system's default resolver selection to examine a chosen server. Verify the action by checking: The differing A or AAAA responses are attributed to the respective servers.
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 querying a specific dns server directly 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 querying a specific dns server directly 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 querying a specific dns server directly failure.
A Linux team is checking the acceptance evidence for this specific situation: Two resolver servers disagree on a host address and a technician wants to isolate which one returns stale data. Which observation BEST confirms that this particular issue has been corrected?
The differing A or AAAA responses are attributed to the respective servers. That evidence specifically demonstrates recovery from querying a specific dns server directly. The technical reason is: A direct dig query can bypass the system's default resolver selection to examine a chosen server.
getent hosts uses the approved local entry before the external DNS answer. This can validate correcting the hosts lookup source order, but it does not establish that the described querying a specific dns server directly issue is fixed. The case-specific evidence is: The differing A or AAAA responses are attributed to the respective servers.
A remote IPv6 connection reaches the intended host instead of the local machine. This can validate ipv6 loopback diagnosis, but it does not establish that the described querying a specific dns server directly issue is fixed. The case-specific evidence is: The differing A or AAAA responses are attributed to the respective servers.
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 querying a specific dns server directly issue is fixed. The case-specific evidence is: The differing A or AAAA responses are attributed to the respective servers.
A Linux engineer reviews the underlying behavior in this particular case: Two resolver servers disagree on a host address and a technician wants to isolate which one returns stale data. Which technical behavior BEST explains this particular failure and its remedy?
A direct dig query can bypass the system's default resolver selection to examine a chosen server. This Linux behavior explains the observed symptoms and supports the precise remedy: Use dig with an explicit @server target to query each resolver independently.
The local 127.0.0.53 stub forwards resolution through configured upstream providers. This describes another behavior (distinguishing a systemd-resolved stub from external dns) and does not explain the stated querying a specific dns server directly failure. The operative behavior is: A direct dig query can bypass the system's default resolver selection to examine a chosen server.
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 querying a specific dns server directly failure. The operative behavior is: A direct dig query can bypass the system's default resolver selection to examine a chosen server.
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 querying a specific dns server directly failure. The operative behavior is: A direct dig query can bypass the system's default resolver selection to examine a chosen server.
A Linux operating control has not corrected the following specific problem: Two resolver servers disagree on a host address and a technician wants to isolate which one returns stale data. Which outcome is the MOST directly associated operational risk if this problem remains?
Changing local hosts files will not fix stale data on one upstream resolver. This is the directly relevant consequence of leaving the querying a specific dns server directly problem unresolved. The appropriate preventive change is: Use dig with an explicit @server target to query each resolver independently.
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 querying a specific dns server directly problem. The specific consequence is: Changing local hosts files will not fix stale data on one upstream resolver.
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 querying a specific dns server directly problem. The specific consequence is: Changing local hosts files will not fix stale data on one upstream resolver.
DNS changes will not repair a broken local gateway path. This consequence is connected to testing the local gateway before remote hosts rather than the MOST direct exposure in the stated querying a specific dns server directly problem. The specific consequence is: Changing local hosts files will not fix stale data on one upstream resolver.
A Linux troubleshooter is gathering specific evidence for this situation: Two resolver servers disagree on a host address and a technician wants to isolate which one returns stale data. Which check MOST directly diagnoses or confirms the technical condition described?
Compare dig @server outputs for both resolvers and the relevant record type. This check targets the relevant state for querying a specific dns server directly and directly assesses the observed behavior. The result should be evaluated against: The differing A or AAAA responses are attributed to the respective servers.
Check command -v for both tool families and compare supported interface output. This check is relevant to recognizing legacy net-tools alternatives but not the most targeted diagnosis of querying a specific dns server directly. The specific check is: Compare dig @server outputs for both resolvers and the relevant record type.
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 querying a specific dns server directly. The specific check is: Compare dig @server outputs for both resolvers and the relevant record type.
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 querying a specific dns server directly. The specific check is: Compare dig @server outputs for both resolvers and the relevant record type.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: An application resolves a service name through local policy, but dig reports a different record and the engineer calls dig definitive. Which step MOST directly corrects the specific problem described?
Compare getent hosts with dig and inspect name service switch policy. This targets the observed issue, checking nss host resolution versus dns-only queries, rather than a separate Linux configuration. Underlying behavior: getent uses the system's configured name-service databases; dig queries DNS directly. Verify the action by checking: The application-facing effective result matches NSS configuration and any hosts-file overrides.
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 checking nss host resolution versus dns-only queries failure.
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 checking nss host resolution versus dns-only queries failure.
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 checking nss host resolution versus dns-only queries failure.
A Linux team is checking the acceptance evidence for this specific situation: An application resolves a service name through local policy, but dig reports a different record and the engineer calls dig definitive. Which observation BEST confirms that this particular issue has been corrected?
The application-facing effective result matches NSS configuration and any hosts-file overrides. That evidence specifically demonstrates recovery from checking nss host resolution versus dns-only queries. The technical reason is: getent uses the system's configured name-service databases; dig queries DNS directly.
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 checking nss host resolution versus dns-only queries issue is fixed. The case-specific evidence is: The application-facing effective result matches NSS configuration and any hosts-file overrides.
getent hosts uses the approved local entry before the external DNS answer. This can validate correcting the hosts lookup source order, but it does not establish that the described checking nss host resolution versus dns-only queries issue is fixed. The case-specific evidence is: The application-facing effective result matches NSS configuration and any hosts-file overrides.
getent hosts returns the approved effective address for the application. This can validate host lookup precedence between files and dns, but it does not establish that the described checking nss host resolution versus dns-only queries issue is fixed. The case-specific evidence is: The application-facing effective result matches NSS configuration and any hosts-file overrides.
A Linux engineer reviews the underlying behavior in this particular case: An application resolves a service name through local policy, but dig reports a different record and the engineer calls dig definitive. Which technical behavior BEST explains this particular failure and its remedy?
getent uses the system's configured name-service databases; dig queries DNS directly. This Linux behavior explains the observed symptoms and supports the precise remedy: Compare getent hosts with dig and inspect name service switch policy.
The local 127.0.0.53 stub forwards resolution through configured upstream providers. This describes another behavior (distinguishing a systemd-resolved stub from external dns) and does not explain the stated checking nss host resolution versus dns-only queries failure. The operative behavior is: getent uses the system's configured name-service databases; dig queries DNS directly.
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 checking nss host resolution versus dns-only queries failure. The operative behavior is: getent uses the system's configured name-service databases; dig queries DNS directly.
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 checking nss host resolution versus dns-only queries failure. The operative behavior is: getent uses the system's configured name-service databases; dig queries DNS directly.
A Linux operating control has not corrected the following specific problem: An application resolves a service name through local policy, but dig reports a different record and the engineer calls dig definitive. Which outcome is the MOST directly associated operational risk if this problem remains?
DNS-only tests may miss local overrides that drive actual application behavior. This is the directly relevant consequence of leaving the checking nss host resolution versus dns-only queries problem unresolved. The appropriate preventive change is: Compare getent hosts with dig and inspect name service switch policy.
Name-based applications can fail even when routing is healthy. This consequence is connected to setting an approved resolver nameserver rather than the MOST direct exposure in the stated checking nss host resolution versus dns-only queries problem. The specific consequence is: DNS-only tests may miss local overrides that drive actual application behavior.
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 checking nss host resolution versus dns-only queries problem. The specific consequence is: DNS-only tests may miss local overrides that drive actual application behavior.
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 checking nss host resolution versus dns-only queries problem. The specific consequence is: DNS-only tests may miss local overrides that drive actual application behavior.
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.
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.