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 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.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A host's resolv.conf points at 127.0.0.53 and a technician assumes the real upstream DNS server is the local machine. Which step MOST directly corrects the specific problem described?
Use resolvectl status to inspect the upstream servers managed by systemd-resolved. This targets the observed issue, distinguishing a systemd-resolved stub from external dns, rather than a separate Linux configuration. Underlying behavior: The local 127.0.0.53 stub forwards resolution through configured upstream providers. Verify the action by checking: The active upstream DNS addresses are identified separately from the local stub listener.
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 distinguishing a systemd-resolved stub from external 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 distinguishing a systemd-resolved stub from external dns failure.
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 distinguishing a systemd-resolved stub from external dns failure.
A Linux team is checking the acceptance evidence for this specific situation: A host's resolv.conf points at 127.0.0.53 and a technician assumes the real upstream DNS server is the local machine. Which observation BEST confirms that this particular issue has been corrected?
The active upstream DNS addresses are identified separately from the local stub listener. That evidence specifically demonstrates recovery from distinguishing a systemd-resolved stub from external dns. The technical reason is: The local 127.0.0.53 stub forwards resolution through configured upstream providers.
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 distinguishing a systemd-resolved stub from external dns issue is fixed. The case-specific evidence is: The active upstream DNS addresses are identified separately from the local stub listener.
The active interface's IP and prefix are correctly identified before any route changes. This can validate inspecting local interface addresses with iproute2, but it does not establish that the described distinguishing a systemd-resolved stub from external dns issue is fixed. The case-specific evidence is: The active upstream DNS addresses are identified separately from the local stub listener.
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 distinguishing a systemd-resolved stub from external dns issue is fixed. The case-specific evidence is: The active upstream DNS addresses are identified separately from the local stub listener.
A Linux engineer reviews the underlying behavior in this particular case: A host's resolv.conf points at 127.0.0.53 and a technician assumes the real upstream DNS server is the local machine. Which technical behavior BEST explains this particular failure and its remedy?
The local 127.0.0.53 stub forwards resolution through configured upstream providers. This Linux behavior explains the observed symptoms and supports the precise remedy: Use resolvectl status to inspect the upstream servers managed by systemd-resolved.
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 distinguishing a systemd-resolved stub from external dns failure. The operative behavior is: The local 127.0.0.53 stub forwards resolution through configured upstream providers.
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 distinguishing a systemd-resolved stub from external dns failure. The operative behavior is: The local 127.0.0.53 stub forwards resolution through configured upstream providers.
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 distinguishing a systemd-resolved stub from external dns failure. The operative behavior is: The local 127.0.0.53 stub forwards resolution through configured upstream providers.
A Linux operating control has not corrected the following specific problem: A host's resolv.conf points at 127.0.0.53 and a technician assumes the real upstream DNS server is the local machine. Which outcome is the MOST directly associated operational risk if this problem remains?
Incorrect diagnosis can prompt removal of a functioning local resolver stub. This is the directly relevant consequence of leaving the distinguishing a systemd-resolved stub from external dns problem unresolved. The appropriate preventive change is: Use resolvectl status to inspect the upstream servers managed by systemd-resolved.
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 distinguishing a systemd-resolved stub from external dns problem. The specific consequence is: Incorrect diagnosis can prompt removal of a functioning local resolver stub.
An unexpected lookup order can send applications to the wrong endpoint. This consequence is connected to correcting the hosts lookup source order rather than the MOST direct exposure in the stated distinguishing a systemd-resolved stub from external dns problem. The specific consequence is: Incorrect diagnosis can prompt removal of a functioning local resolver stub.
A misleading ping result could delay resolution of a working service. This consequence is connected to testing a tcp service directly with netcat rather than the MOST direct exposure in the stated distinguishing a systemd-resolved stub from external dns problem. The specific consequence is: Incorrect diagnosis can prompt removal of a functioning local resolver stub.
A Linux troubleshooter is gathering specific evidence for this situation: A host's resolv.conf points at 127.0.0.53 and a technician assumes the real upstream DNS server is the local machine. Which check MOST directly diagnoses or confirms the technical condition described?
Inspect resolvectl status together with resolv.conf and listener addresses. This check targets the relevant state for distinguishing a systemd-resolved stub from external dns and directly assesses the observed behavior. The result should be evaluated against: The active upstream DNS addresses are identified separately from the local stub listener.
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 distinguishing a systemd-resolved stub from external dns. The specific check is: Inspect resolvectl status together with resolv.conf and listener addresses.
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 distinguishing a systemd-resolved stub from external dns. The specific check is: Inspect resolvectl status together with resolv.conf and listener addresses.
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 distinguishing a systemd-resolved stub from external dns. The specific check is: Inspect resolvectl status together with resolv.conf and listener addresses.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A host hardening audit finds a new executable with setuid permissions and the owner cannot explain why it needs elevated identity. Which step MOST directly corrects the specific problem described?
Inventory setuid files, validate each against approved packages and remove unnecessary elevation using controlled change management. This targets the observed issue, auditing setuid binaries for unexpected privilege, rather than a separate Linux configuration. Underlying behavior: The setuid mode bit can cause a program to execute with its file owner's effective identity. Verify the action by checking: No unapproved setuid executables remain and required privileged helpers are documented.
Inspect who or w to identify current sessions and their activity before the change. This is an appropriate response to a different issue (reviewing currently logged-in users) but does not MOST directly address the explicit auditing setuid binaries for unexpected privilege failure.
Verify the new host-key fingerprint through an authenticated independent channel before updating known_hosts. This is an appropriate response to a different issue (validating a changed ssh server host key) but does not MOST directly address the explicit auditing setuid binaries for unexpected privilege failure.
Apply an appropriate per-user process limit through the supported shell or PAM limits mechanism. This is an appropriate response to a different issue (limiting runaway process creation) but does not MOST directly address the explicit auditing setuid binaries for unexpected privilege failure.
A Linux team is checking the acceptance evidence for this specific situation: A host hardening audit finds a new executable with setuid permissions and the owner cannot explain why it needs elevated identity. Which observation BEST confirms that this particular issue has been corrected?
No unapproved setuid executables remain and required privileged helpers are documented. That evidence specifically demonstrates recovery from auditing setuid binaries for unexpected privilege. The technical reason is: The setuid mode bit can cause a program to execute with its file owner's effective identity.
A client connects to the local forwarded port and reaches only the permitted remote service. This can validate local ssh port forwarding, but it does not establish that the described auditing setuid binaries for unexpected privilege issue is fixed. The case-specific evidence is: No unapproved setuid executables remain and required privileged helpers are documented.
The process name, PID and listening socket are tied to the expected approved service. This can validate mapping an open port to its owning process, but it does not establish that the described auditing setuid binaries for unexpected privilege issue is fixed. The case-specific evidence is: No unapproved setuid executables remain and required privileged helpers are documented.
The privileged account reports an enforceable password lifetime within policy. This can validate auditing password expiration for privileged accounts, but it does not establish that the described auditing setuid binaries for unexpected privilege issue is fixed. The case-specific evidence is: No unapproved setuid executables remain and required privileged helpers are documented.
A Linux engineer reviews the underlying behavior in this particular case: A host hardening audit finds a new executable with setuid permissions and the owner cannot explain why it needs elevated identity. Which technical behavior BEST explains this particular failure and its remedy?
The setuid mode bit can cause a program to execute with its file owner's effective identity. This Linux behavior explains the observed symptoms and supports the precise remedy: Inventory setuid files, validate each against approved packages and remove unnecessary elevation using controlled change management.
visudo checks sudoers syntax and avoids an invalid policy file being left in place. This describes another behavior (safe validation of sudo policy changes) and does not explain the stated auditing setuid binaries for unexpected privilege failure. The operative behavior is: The setuid mode bit can cause a program to execute with its file owner's effective identity.
An active agent needs a loaded identity before it can sign challenges for that key. This describes another behavior (adding a specific key to the running ssh agent) and does not explain the stated auditing setuid binaries for unexpected privilege failure. The operative behavior is: The setuid mode bit can cause a program to execute with its file owner's effective identity.
who and w report current login sessions rather than all historical accounts. This describes another behavior (reviewing currently logged-in users) and does not explain the stated auditing setuid binaries for unexpected privilege failure. The operative behavior is: The setuid mode bit can cause a program to execute with its file owner's effective identity.
A Linux operating control has not corrected the following specific problem: A host hardening audit finds a new executable with setuid permissions and the owner cannot explain why it needs elevated identity. Which outcome is the MOST directly associated operational risk if this problem remains?
An unexpected setuid binary may provide a privilege-escalation pathway. This is the directly relevant consequence of leaving the auditing setuid binaries for unexpected privilege problem unresolved. The appropriate preventive change is: Inventory setuid files, validate each against approved packages and remove unnecessary elevation using controlled change management.
Active administrators may be interrupted without notice. This consequence is connected to reviewing currently logged-in users rather than the MOST direct exposure in the stated auditing setuid binaries for unexpected privilege problem. The specific consequence is: An unexpected setuid binary may provide a privilege-escalation pathway.
Ignoring the warning can permit a man-in-the-middle connection to an impostor. This consequence is connected to validating a changed ssh server host key rather than the MOST direct exposure in the stated auditing setuid binaries for unexpected privilege problem. The specific consequence is: An unexpected setuid binary may provide a privilege-escalation pathway.
One account may deny service to other workloads through uncontrolled resource use. This consequence is connected to limiting runaway process creation rather than the MOST direct exposure in the stated auditing setuid binaries for unexpected privilege problem. The specific consequence is: An unexpected setuid binary may provide a privilege-escalation pathway.
A Linux troubleshooter is gathering specific evidence for this situation: A host hardening audit finds a new executable with setuid permissions and the owner cannot explain why it needs elevated identity. Which check MOST directly diagnoses or confirms the technical condition described?
Use find with the setuid permission predicate and examine stat ownership and package provenance. This check targets the relevant state for auditing setuid binaries for unexpected privilege and directly assesses the observed behavior. The result should be evaluated against: No unapproved setuid executables remain and required privileged helpers are documented.
Run visudo -c and test a scoped sudo -l policy for representative accounts. This check is relevant to safe validation of sudo policy changes but not the most targeted diagnosis of auditing setuid binaries for unexpected privilege. The specific check is: Use find with the setuid permission predicate and examine stat ownership and package provenance.
Inspect stat ownership and mode on /etc/shadow and test unprivileged access. This check is relevant to preserving shadow file confidentiality but not the most targeted diagnosis of auditing setuid binaries for unexpected privilege. The specific check is: Use find with the setuid permission predicate and examine stat ownership and package provenance.
Compare nmap results from the approved vantage point with ss listener output. This check is relevant to discovering unexpected listening ports but not the most targeted diagnosis of auditing setuid binaries for unexpected privilege. The specific check is: Use find with the setuid permission predicate and examine stat ownership and package provenance.
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.