100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Question 841
A contractor's SSH client has a valid private key, but the server rejects public-key authentication for the intended user. Which explanation most directly accounts for the failure in this environment?
- TCP wrappers affect only applications built to consult libwrap and do not serve as a universal host firewall.
- A separate systemd .socket unit can listen and activate its associated service on demand.
- TCP wrappers normally evaluate a matching hosts.allow rule before hosts.deny.
- The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely.
Explanation
Correct Answer
D:The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely. That cause connects the stated symptom to the corrective action: Install the approved public key in the intended user's ~/.ssh/authorized_keys with secure ownership and permissions.
Incorrect Answers
A:It would address tcp wrappers are legacy rather than the present problem. The appropriate correction here is: Install the approved public key in the intended user's ~/.ssh/authorized_keys with secure ownership and permissions.
B:This belongs to socket activation keeps port open, where A separate systemd .socket unit can listen and activate its associated service on demand. The current issue instead is: The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely.
C:TCP wrappers normally evaluate a matching hosts.allow rule before hosts.deny. belongs to a situation where TCP wrappers normally evaluate a matching hosts.allow rule before hosts.deny. Here the evidence supports a different requirement: The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely.
Question 842
A contractor's SSH client has a valid private key, but the server rejects public-key authentication for the intended user. What action should be planned as the next targeted correction?
- Review last or equivalent retained authentication logs for historical sessions.
- Configure the application listener to bind to 127.0.0.1 and review firewall access for the service.
- Install the approved public key in the intended user's ~/.ssh/authorized_keys with secure ownership and permissions.
- Disable and stop the corresponding socket unit as well as the service when decommissioning it.
Explanation
Correct Answer
C:Install the approved public key in the intended user's ~/.ssh/authorized_keys with secure ownership and permissions. It addresses the root cause, while Manage authorized user keys by account and revoke them promptly on offboarding. reduces future recurrence.
Incorrect Answers
A:Review last or equivalent retained authentication logs for historical sessions. belongs to a situation where who lists current sessions; historical successful logins require a login-history facility such as last. Here the evidence supports a different requirement: Install the approved public key in the intended user's ~/.ssh/authorized_keys with secure ownership and permissions.
B:Configure the application listener to bind to 127.0.0.1 and review firewall access for the service. could help with local-only service binds every interface; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ssh -v to inspect the authentication attempt and verify which server account is selected.
D:This option assumes A separate systemd .socket unit can listen and activate its associated service on demand. The reported symptoms instead call for: Install the approved public key in the intended user's ~/.ssh/authorized_keys with secure ownership and permissions.
Question 843
A contractor's SSH client has a valid private key, but the server rejects public-key authentication for the intended user. How should the administrator verify the required behavior?
- Inspect systemctl list-sockets and attempt the connection after applying the policy.
- Compare ss -ltnp and a controlled remote port scan before and after hardening.
- Use ssh -v to inspect the authentication attempt and verify which server account is selected.
- Run visudo -c and sudo -l for an authorized test identity.
Explanation
Correct Answer
C:Use ssh -v to inspect the authentication attempt and verify which server account is selected. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely.
Incorrect Answers
A:Inspect systemctl list-sockets and attempt the connection after applying the policy. belongs to a situation where A separate systemd .socket unit can listen and activate its associated service on demand. Here the evidence supports a different requirement: Use ssh -v to inspect the authentication attempt and verify which server account is selected.
B:The test for firewall status versus service status would be: Compare ss -ltnp and a controlled remote port scan before and after hardening. The relevant acceptance check here is: Use ssh -v to inspect the authentication attempt and verify which server account is selected.
D:Invalid sudoers syntax can break privilege delegation and an unvalidated edit is risky. That describes a different fault. Here, The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely.
Question 844
A contractor's SSH client has a valid private key, but the server rejects public-key authentication for the intended user. Which practice is most useful after the immediate repair succeeds?
- Manage authorized user keys by account and revoke them promptly on offboarding.
- Review allow and deny policies together when maintaining legacy libwrap services.
- Document legacy TCP-wrapper limitations and migrate network policy to supported controls.
- Maintain approved service-port inventory and alert on unexpected listeners.
Explanation
Correct Answer
A:Manage authorized user keys by account and revoke them promptly on offboarding. It makes the outcome of the targeted repair (Install the approved public key in the intended user's ~/.ssh/authorized_keys with secure ownership and permissions.) repeatable.
Incorrect Answers
B:TCP wrappers normally evaluate a matching hosts.allow rule before hosts.deny. That describes a different fault. Here, The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely.
C:This belongs to tcp wrappers are legacy, where TCP wrappers affect only applications built to consult libwrap and do not serve as a universal host firewall. The current issue instead is: The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely.
D:Maintain approved service-port inventory and alert on unexpected listeners. could help with find process owning tcp listener; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ssh -v to inspect the authentication attempt and verify which server account is selected.
Question 845
A contractor's SSH client has a valid private key, but the server rejects public-key authentication for the intended user. Which TWO measures belong together as the direct correction and a discriminating verification? Select TWO.
- Install the approved public key in the intended user's ~/.ssh/authorized_keys with secure ownership and permissions.
- Use w to inspect current users, TTYs, idle times and active commands.
- Set and review sudo authentication-cache policy for sensitive shared administrative consoles.
- Attempt access from the formerly matched client and review wrapper logs.
- Use ssh -v to inspect the authentication attempt and verify which server account is selected.
Explanation
Correct Answers
A:Install the approved public key in the intended user's ~/.ssh/authorized_keys with secure ownership and permissions. It is the direct response; verify the result by: Use ssh -v to inspect the authentication attempt and verify which server account is selected.
E:Use ssh -v to inspect the authentication attempt and verify which server account is selected. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
B:This belongs to inspect current logged-in commands, where Historical login tools alone do not enumerate current session commands and idle times. The current issue instead is: The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely.
C:The test for sudo credential cache on shared console would be: Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout. The relevant acceptance check here is: Use ssh -v to inspect the authentication attempt and verify which server account is selected.
D:The test for hosts allow precedence in libwrap would be: Attempt access from the formerly matched client and review wrapper logs. The relevant acceptance check here is: Use ssh -v to inspect the authentication attempt and verify which server account is selected.
Question 846
An administrator receives an SSH changed-host-key warning after a server rebuild and wants to ignore it automatically. Which explanation most directly accounts for the failure in this environment?
- The client's known_hosts pin no longer matches the offered server host key, which can also signal interception.
- A system's login policy can use /etc/nologin to reject standard logins on supporting login services.
- Setuid is a special permission bit; ordinary x permission is not evidence of effective-UID elevation.
- A separate systemd .socket unit can listen and activate its associated service on demand.
Explanation
Correct Answer
A:The client's known_hosts pin no longer matches the offered server host key, which can also signal interception. The administrator should distinguish this from unrelated symptoms by checking: Compare the server's trusted host-key fingerprint with the client warning before accepting it.
Incorrect Answers
B:This option assumes A system's login policy can use /etc/nologin to reject standard logins on supporting login services. The reported symptoms instead call for: Verify the new server host key fingerprint out of band before updating the known_hosts entry.
C:Setuid is a special permission bit; ordinary x permission is not evidence of effective-UID elevation. belongs to a situation where Setuid is a special permission bit; ordinary x permission is not evidence of effective-UID elevation. Here the evidence supports a different requirement: The client's known_hosts pin no longer matches the offered server host key, which can also signal interception.
D:That choice responds to a socket activation keeps port open failure. In this incident, The client's known_hosts pin no longer matches the offered server host key, which can also signal interception.
Question 847
An administrator receives an SSH changed-host-key warning after a server rebuild and wants to ignore it automatically. What action should be planned as the next targeted correction?
- Run an authorized nmap scan from the designated assessment subnet against the approved target.
- Verify the new server host key fingerprint out of band before updating the known_hosts entry.
- Migrate to distribution-supported shadow password storage with approved permissions.
- Create an approved /etc/nologin maintenance notice while keeping a tested administrative recovery path.
Explanation
Correct Answer
B:Verify the new server host key fingerprint out of band before updating the known_hosts entry. This is appropriate because The client's known_hosts pin no longer matches the offered server host key, which can also signal interception.
Incorrect Answers
A:That choice responds to a external port scan scope failure. In this incident, The client's known_hosts pin no longer matches the offered server host key, which can also signal interception.
C:The shadow-password model keeps hashes in restricted /etc/shadow, while passwd contains public account fields. That describes a different fault. Here, The client's known_hosts pin no longer matches the offered server host key, which can also signal interception.
D:This belongs to temporary login blockade, where A system's login policy can use /etc/nologin to reject standard logins on supporting login services. The current issue instead is: The client's known_hosts pin no longer matches the offered server host key, which can also signal interception.
Question 848
An administrator receives an SSH changed-host-key warning after a server rebuild and wants to ignore it automatically. What diagnostic result would demonstrate the target behavior?
- Use ss -ltnp to confirm the loopback bind and test access from both local and remote clients.
- Compare the server's trusted host-key fingerprint with the client warning before accepting it.
- Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout.
- Compare remotely observed services with local ss listeners and filtering rules.
Explanation
Correct Answer
B:Compare the server's trusted host-key fingerprint with the client warning before accepting it. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
A:This belongs to local-only service binds every interface, where The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener. The current issue instead is: The client's known_hosts pin no longer matches the offered server host key, which can also signal interception.
C:It would address sudo credential cache on shared console rather than the present problem. The appropriate correction here is: Verify the new server host key fingerprint out of band before updating the known_hosts entry.
D:Compare remotely observed services with local ss listeners and filtering rules. could help with external port scan scope; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare the server's trusted host-key fingerprint with the client warning before accepting it.
Question 849
An administrator receives an SSH changed-host-key warning after a server rebuild and wants to ignore it automatically. What operational safeguard addresses the root cause?
- Maintain approved service-port inventory and alert on unexpected listeners.
- Set and review sudo authentication-cache policy for sensitive shared administrative consoles.
- Manage server host-key rotation with identity verification rather than disabling checking.
- Treat service units and socket units as separate controls when reducing attack surface.
Explanation
Correct Answer
C:Manage server host-key rotation with identity verification rather than disabling checking. It makes the outcome of the targeted repair (Verify the new server host key fingerprint out of band before updating the known_hosts entry.) repeatable.
Incorrect Answers
A:Maintain approved service-port inventory and alert on unexpected listeners. belongs to a situation where The listening port may belong to an active local process rather than a stale firewall rule. Here the evidence supports a different requirement: Manage server host-key rotation with identity verification rather than disabling checking.
B:The test for sudo credential cache on shared console would be: Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout. The relevant acceptance check here is: Compare the server's trusted host-key fingerprint with the client warning before accepting it.
D:This option assumes A separate systemd .socket unit can listen and activate its associated service on demand. The reported symptoms instead call for: Verify the new server host key fingerprint out of band before updating the known_hosts entry.
Question 850
An administrator receives an SSH changed-host-key warning after a server rebuild and wants to ignore it automatically. Choose THREE measures that together correct the failure, demonstrate success and reduce recurrence.
- Manage resource limits in persistent policy rather than manual transient shell commands.
- Attempt a test non-root login and confirm rejection plus the displayed notice.
- Compare the server's trusted host-key fingerprint with the client warning before accepting it.
- Manage server host-key rotation with identity verification rather than disabling checking.
- Confirm whether the service supports TCP wrappers and otherwise use supported host firewall or application ACL controls.
- Verify the new server host key fingerprint out of band before updating the known_hosts entry.
Explanation
Correct Answers
C:Compare the server's trusted host-key fingerprint with the client warning before accepting it. This check is tied to the expected behavior rather than mere process uptime.
D:Manage server host-key rotation with identity verification rather than disabling checking. It makes the outcome of the targeted repair (Verify the new server host key fingerprint out of band before updating the known_hosts entry.) repeatable.
F:Verify the new server host key fingerprint out of band before updating the known_hosts entry. It is the direct response; verify the result by: Compare the server's trusted host-key fingerprint with the client warning before accepting it.
Incorrect Answers
A:That choice responds to a shell process limits failure. In this incident, The client's known_hosts pin no longer matches the offered server host key, which can also signal interception.
B:This option assumes A system's login policy can use /etc/nologin to reject standard logins on supporting login services. The reported symptoms instead call for: Verify the new server host key fingerprint out of band before updating the known_hosts entry.
E:Confirm whether the service supports TCP wrappers and otherwise use supported host firewall or application ACL controls. belongs to a situation where TCP wrappers affect only applications built to consult libwrap and do not serve as a universal host firewall. Here the evidence supports a different requirement: Verify the new server host key fingerprint out of band before updating the known_hosts entry.
LPI Level 1 (102-500) Practice Tests