100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 830
A libwrap-enabled legacy daemon has a broad hosts.deny rule but still accepts a particular client from a matching hosts.allow entry. Select THREE measures that follow directly from the root cause and lifecycle risk.
- Audit effective privilege grants rather than relying on role names alone.
- Publish an appropriate GPG key revocation and distribute the replacement trust path.
- Attempt access from the formerly matched client and review wrapper logs.
- Connect to localhost:localport and verify it reaches only the intended internal service.
- Review allow and deny policies together when maintaining legacy libwrap services.
- Tighten the allow entry or remove an unintended exception for that daemon and client.
Explanation
Correct Answers
C:Attempt access from the formerly matched client and review wrapper logs. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
E:Review allow and deny policies together when maintaining legacy libwrap services. It makes the outcome of the targeted repair (Tighten the allow entry or remove an unintended exception for that daemon and client.) repeatable.
F:Tighten the allow entry or remove an unintended exception for that daemon and client. It addresses the root cause, while Review allow and deny policies together when maintaining legacy libwrap services. reduces future recurrence.
Incorrect Answers
A:This option assumes Group membership or an assertion is not sufficient evidence of the actual sudoers permissions. The reported symptoms instead call for: Tighten the allow entry or remove an unintended exception for that daemon and client.
B:It would address gpg revoked signing key rather than the present problem. The appropriate correction here is: Tighten the allow entry or remove an unintended exception for that daemon and client.
D:This belongs to local port forwarding to internal database, where A local SSH tunnel maps a local listening port to a host and port from the SSH server side. The current issue instead is: TCP wrappers normally evaluate a matching hosts.allow rule before hosts.deny.
Question 831
A maintenance daemon should accept connections only from the same host, but ss shows it listening on 0.0.0.0. Which failure condition fits the evidence without assuming an unrelated fault?
- A signature may authenticate integrity but leaves ordinary plaintext visible without encryption.
- Local listening state does not account for intervening host firewalls or network ACLs.
- Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.
- The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
Explanation
Correct Answer
D:The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener. A good follow-up is to test this explanation through: Use ss -ltnp to confirm the loopback bind and test access from both local and remote clients.
Incorrect Answers
A:That choice responds to a gpg recipient encryption failure. In this incident, The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
B:Local listening state does not account for intervening host firewalls or network ACLs. could help with external port scan scope; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ss -ltnp to confirm the loopback bind and test access from both local and remote clients.
C:Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context. That describes a different fault. Here, The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
Question 832
A maintenance daemon should accept connections only from the same host, but ss shows it listening on 0.0.0.0. What action should be planned as the next targeted correction?
- Run sudo -l under the user's identity to enumerate the commands sudo permits.
- Configure the application listener to bind to 127.0.0.1 and review firewall access for the service.
- Encrypt the archive to the recipient's verified public GPG key.
- Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.
Explanation
Correct Answer
B:Configure the application listener to bind to 127.0.0.1 and review firewall access for the service. It addresses the root cause, while Include listener bind addresses, not just port numbers, in host-hardening baselines. reduces future recurrence.
Incorrect Answers
A:Run sudo -l under the user's identity to enumerate the commands sudo permits. could help with inspect effective sudo privilege; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ss -ltnp to confirm the loopback bind and test access from both local and remote clients.
C:This option assumes A signature may authenticate integrity but leaves ordinary plaintext visible without encryption. The reported symptoms instead call for: Configure the application listener to bind to 127.0.0.1 and review firewall access for the service.
D:This belongs to shell process limits, where Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context. The current issue instead is: The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
Question 833
A maintenance daemon should accept connections only from the same host, but ss shows it listening on 0.0.0.0. Which check would provide the strongest evidence that the fix worked?
- Use ss -ltnp to confirm the loopback bind and test access from both local and remote clients.
- Compare the permitted command list to the requested restart task without running a destructive command.
- Run ulimit -a in a new session and exercise a bounded test workload.
- Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout.
Explanation
Correct Answer
A:Use ss -ltnp to confirm the loopback bind and test access from both local and remote clients. It verifies that the targeted action (Configure the application listener to bind to 127.0.0.1 and review firewall access for the service.) achieved its intended outcome.
Incorrect Answers
B:This belongs to inspect effective sudo privilege, where Group membership or an assertion is not sufficient evidence of the actual sudoers permissions. The current issue instead is: The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
C:This belongs to shell process limits, where Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context. The current issue instead is: The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
D:Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout. could help with sudo credential cache on shared console; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ss -ltnp to confirm the loopback bind and test access from both local and remote clients.
Question 834
A maintenance daemon should accept connections only from the same host, but ss shows it listening on 0.0.0.0. Which practice is most useful after the immediate repair succeeds?
- Include listener bind addresses, not just port numbers, in host-hardening baselines.
- Manage server host-key rotation with identity verification rather than disabling checking.
- Distinguish confidentiality, integrity and author authentication in evidence workflows.
- Protect and retain login history centrally for incident reconstruction.
Explanation
Correct Answer
A:Include listener bind addresses, not just port numbers, in host-hardening baselines. It prevents repetition of the condition: The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
Incorrect Answers
B:This option assumes The client's known_hosts pin no longer matches the offered server host key, which can also signal interception. The reported symptoms instead call for: Configure the application listener to bind to 127.0.0.1 and review firewall access for the service.
C:This option assumes Encryption protects confidentiality but does not alone prove the author's signing key endorsed the document. The reported symptoms instead call for: Configure the application listener to bind to 127.0.0.1 and review firewall access for the service.
D:It would address previous login attribution rather than the present problem. The appropriate correction here is: Configure the application listener to bind to 127.0.0.1 and review firewall access for the service.
Question 835
A maintenance daemon should accept connections only from the same host, but ss shows it listening on 0.0.0.0. Select TWO justified actions that address this particular problem and confirm closure.
- Run an authorized nmap scan from the designated assessment subnet against the approved target.
- Manage authorized user keys by account and revoke them promptly on offboarding.
- Configure the application listener to bind to 127.0.0.1 and review firewall access for the service.
- Compare the verified fingerprint with the key used by gpg --verify.
- Use ss -ltnp to confirm the loopback bind and test access from both local and remote clients.
Explanation
Correct Answers
C:Configure the application listener to bind to 127.0.0.1 and review firewall access for the service. This is appropriate because The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
E:Use ss -ltnp to confirm the loopback bind and test access from both local and remote clients. This check is tied to the expected behavior rather than mere process uptime.
Incorrect Answers
A:This belongs to external port scan scope, where Local listening state does not account for intervening host firewalls or network ACLs. The current issue instead is: The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
B:That choice responds to a user authorized ssh key failure. In this incident, The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
D:It would address gpg signature from unknown key rather than the present problem. The appropriate correction here is: Configure the application listener to bind to 127.0.0.1 and review firewall access for the service.
Question 836
A host disables an unused service successfully, but a firewall port rule remains broadly open for a different local process. What underlying Linux behavior should the administrator identify first?
- Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
- who lists current sessions; historical successful logins require a login-history facility such as last.
- Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.
- A mathematically valid signature does not independently establish who owns the public key.
Explanation
Correct Answer
A:Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port. The observation is consistent with this mechanism; a targeted repair would be: Review both running listeners and packet-filter policy, then remove obsolete exposed rules.
Incorrect Answers
B:who lists current sessions; historical successful logins require a login-history facility such as last. could help with previous login attribution; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare ss -ltnp and a controlled remote port scan before and after hardening.
C:Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context. That describes a different fault. Here, Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
D:The test for gpg signature from unknown key would be: Compare the verified fingerprint with the key used by gpg --verify. The relevant acceptance check here is: Compare ss -ltnp and a controlled remote port scan before and after hardening.
Question 837
A host disables an unused service successfully, but a firewall port rule remains broadly open for a different local process. Which remedial step follows from the observed mechanism?
- Search appropriate filesystem scopes for the setuid bit using find -perm -4000 and review ownership.
- Review both running listeners and packet-filter policy, then remove obsolete exposed rules.
- Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.
- Use ssh -L localport:db-host:dbport bastion after obtaining forwarding approval.
Explanation
Correct Answer
B:Review both running listeners and packet-filter policy, then remove obsolete exposed rules. It corrects the mechanism identified in the scenario: Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
Incorrect Answers
A:This option assumes Setuid is a special permission bit; ordinary x permission is not evidence of effective-UID elevation. The reported symptoms instead call for: Review both running listeners and packet-filter policy, then remove obsolete exposed rules.
C:Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context. That describes a different fault. Here, Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
D:The test for local port forwarding to internal database would be: Connect to localhost:localport and verify it reaches only the intended internal service. The relevant acceptance check here is: Compare ss -ltnp and a controlled remote port scan before and after hardening.
Question 838
A host disables an unused service successfully, but a firewall port rule remains broadly open for a different local process. How should the administrator verify the required behavior?
- Compare ss -ltnp and a controlled remote port scan before and after hardening.
- Run ulimit -a in a new session and exercise a bounded test workload.
- Compare the permitted command list to the requested restart task without running a destructive command.
- Inspect key usage in a fresh agent session and confirm unlocking is required under policy.
Explanation
Correct Answer
A:Compare ss -ltnp and a controlled remote port scan before and after hardening. The test is evidence-based because the underlying failure was: Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
Incorrect Answers
B:It would address shell process limits rather than the present problem. The appropriate correction here is: Review both running listeners and packet-filter policy, then remove obsolete exposed rules.
C:The test for inspect effective sudo privilege would be: Compare the permitted command list to the requested restart task without running a destructive command. The relevant acceptance check here is: Compare ss -ltnp and a controlled remote port scan before and after hardening.
D:Inspect key usage in a fresh agent session and confirm unlocking is required under policy. belongs to a situation where A private key without a protective passphrase increases exposure if its file is stolen. Here the evidence supports a different requirement: Compare ss -ltnp and a controlled remote port scan before and after hardening.
Question 839
A host disables an unused service successfully, but a firewall port rule remains broadly open for a different local process. What operational safeguard addresses the root cause?
- Review service state and firewall scope as separate layers of host security.
- Review privileged file modes regularly and remove unnecessary setuid programs.
- Track user authentication and server identity keys as distinct lifecycles.
- Use explicitly authorized scan scope and correlate external exposure with host settings.
Explanation
Correct Answer
A:Review service state and firewall scope as separate layers of host security. It prevents repetition of the condition: Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
Incorrect Answers
B:Setuid is a special permission bit; ordinary x permission is not evidence of effective-UID elevation. That describes a different fault. Here, Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
C:Server host keys identify the SSH server; user keys authenticate the connecting client identity. That describes a different fault. Here, Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
D:That choice responds to a external port scan scope failure. In this incident, Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
Question 840
A host disables an unused service successfully, but a firewall port rule remains broadly open for a different local process. Which THREE actions form a suitable remediation, verification and prevention plan? Select THREE.
- Distinguish confidentiality, integrity and author authentication in evidence workflows.
- Use the recipient's private key in a controlled test to decrypt and compare the recovered archive.
- Place the user's approved public key in authorized_keys and verify server host keys separately.
- Compare ss -ltnp and a controlled remote port scan before and after hardening.
- Review service state and firewall scope as separate layers of host security.
- Review both running listeners and packet-filter policy, then remove obsolete exposed rules.
Explanation
Correct Answers
D:Compare ss -ltnp and a controlled remote port scan before and after hardening. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
E:Review service state and firewall scope as separate layers of host security. Sustained checks matter because Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
F:Review both running listeners and packet-filter policy, then remove obsolete exposed rules. It addresses the root cause, while Review service state and firewall scope as separate layers of host security. reduces future recurrence.
Incorrect Answers
A:That choice responds to a gpg sign versus encrypt failure. In this incident, Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
B:Use the recipient's private key in a controlled test to decrypt and compare the recovered archive. could help with gpg recipient encryption; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare ss -ltnp and a controlled remote port scan before and after hardening.
C:Server host keys identify the SSH server; user keys authenticate the connecting client identity. That describes a different fault. Here, Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port.
LPI Level 1 (102-500) Practice Tests