LPI 102-500 Exam Dumps, Practice Test Questions

100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

LPI 102-500 Premium Bundle
$79.97
$59.98

102-500 Premium Bundle

  • Premium File: 120 Questions & Answers. Last update: Nov 18, 2026
  • Training Course: 126 Video Lectures
  • Study Guide: 962 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

102-500 Premium Bundle

LPI 102-500 Premium Bundle
  • Premium File: 120 Questions & Answers. Last update: Nov 18, 2026
  • Training Course: 126 Video Lectures
  • Study Guide: 962 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$79.97
$59.98

LPI 102-500 Practice Test 79

Question 780

A help desk sees two simultaneous SSH sessions but needs to know who is currently logged in and their activity. Choose THREE measures that together correct the failure, demonstrate success and reduce recurrence.

  1. Document legacy TCP-wrapper limitations and migrate network policy to supported controls.
  2. Import the revocation in a clean test keyring and inspect key validity before signature acceptance.
  3. Use controlled session visibility during incident triage while honoring privacy policy.
  4. Compare w with who and confirm the intended sessions are present.
  5. Use w to inspect current users, TTYs, idle times and active commands.
  6. Disable and stop the corresponding socket unit as well as the service when decommissioning it.

Explanation

Correct Answers

C:

Use controlled session visibility during incident triage while honoring privacy policy. The underlying risk is Historical login tools alone do not enumerate current session commands and idle times.

D:

Compare w with who and confirm the intended sessions are present. The test is evidence-based because the underlying failure was: Historical login tools alone do not enumerate current session commands and idle times.

E:

Use w to inspect current users, TTYs, idle times and active commands. It is the direct response; verify the result by: Compare w with who and confirm the intended sessions are present.

Incorrect Answers

A:

That choice responds to a tcp wrappers are legacy failure. In this incident, Historical login tools alone do not enumerate current session commands and idle times.

B:

That choice responds to a gpg revoked signing key failure. In this incident, Historical login tools alone do not enumerate current session commands and idle times.

F:

This option assumes A separate systemd .socket unit can listen and activate its associated service on demand. The reported symptoms instead call for: Use w to inspect current users, TTYs, idle times and active commands.

Question 781

A batch user's fork-intensive task exhausts process slots and policy requires a per-session process limit. Which diagnosis is supported by the observations?

  1. Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.
  2. A separate systemd .socket unit can listen and activate its associated service on demand.
  3. A signature may authenticate integrity but leaves ordinary plaintext visible without encryption.
  4. Forwarding an SSH agent exposes its authentication socket to processes with sufficient privilege on the remote host while the connection is active.

Explanation

Correct Answer

A:

Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context. That cause connects the stated symptom to the corrective action: Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.

Incorrect Answers

B:

A separate systemd .socket unit can listen and activate its associated service on demand. 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: Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.

C:

This option assumes A signature may authenticate integrity but leaves ordinary plaintext visible without encryption. The reported symptoms instead call for: Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.

D:

Forwarding an SSH agent exposes its authentication socket to processes with sufficient privilege on the remote host while the connection is active. belongs to a situation where Forwarding an SSH agent exposes its authentication socket to processes with sufficient privilege on the remote host while the connection is active. Here the evidence supports a different requirement: Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.

Question 782

A batch user's fork-intensive task exhausts process slots and policy requires a per-session process limit. What should the administrator do to correct this behavior?

  1. Tighten the allow entry or remove an unintended exception for that daemon and client.
  2. Use ssh -L localport:db-host:dbport bastion after obtaining forwarding approval.
  3. Avoid agent forwarding to the untrusted jump server; use a reviewed jump-host connection without ForwardAgent or a more restrictive design.
  4. Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.

Explanation

Correct Answer

D:

Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context. The change should be accepted only after this test: Run ulimit -a in a new session and exercise a bounded test workload.

Incorrect Answers

A:

This belongs to hosts allow precedence in libwrap, where TCP wrappers normally evaluate a matching hosts.allow rule before hosts.deny. The current issue instead is: Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.

B:

This option assumes A local SSH tunnel maps a local listening port to a host and port from the SSH server side. The reported symptoms instead call for: Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.

C:

It would address agent forwarding to an untrusted bastion rather than the present problem. The appropriate correction here is: Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.

Question 783

A batch user's fork-intensive task exhausts process slots and policy requires a per-session process limit. How should the administrator verify the required behavior?

  1. Run ulimit -a in a new session and exercise a bounded test workload.
  2. Attempt access from the formerly matched client and review wrapper logs.
  3. Attempt a test non-root login and confirm rejection plus the displayed notice.
  4. Inspect account record fields and effective /etc/shadow permissions in a controlled test.

Explanation

Correct Answer

A:

Run ulimit -a in a new session and exercise a bounded test workload. This measures the specific result of applying: Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.

Incorrect Answers

B:

TCP wrappers normally evaluate a matching hosts.allow rule before hosts.deny. That describes a different fault. Here, Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.

C:

It would address temporary login blockade rather than the present problem. The appropriate correction here is: Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.

D:

The test for separate shadow hashes from public identities would be: Inspect account record fields and effective /etc/shadow permissions in a controlled test. The relevant acceptance check here is: Run ulimit -a in a new session and exercise a bounded test workload.

Question 784

A batch user's fork-intensive task exhausts process slots and policy requires a per-session process limit. What should the team standardize to prevent similar incidents?

  1. Validate recipient public-key identity before protecting sensitive material.
  2. Manage resource limits in persistent policy rather than manual transient shell commands.
  3. Manage authorized user keys by account and revoke them promptly on offboarding.
  4. Review service state and firewall scope as separate layers of host security.

Explanation

Correct Answer

B:

Manage resource limits in persistent policy rather than manual transient shell commands. Sustained checks matter because Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.

Incorrect Answers

A:

This belongs to gpg recipient encryption, where A signature may authenticate integrity but leaves ordinary plaintext visible without encryption. The current issue instead is: Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.

C:

This option assumes The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely. The reported symptoms instead call for: Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.

D:

This belongs to firewall status versus service status, where Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port. The current issue instead is: Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.

Question 785

A batch user's fork-intensive task exhausts process slots and policy requires a per-session process limit. Which TWO options provide a coherent remediation-and-test response to this incident?

  1. Create an approved /etc/nologin maintenance notice while keeping a tested administrative recovery path.
  2. Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.
  3. Manage server host-key rotation with identity verification rather than disabling checking.
  4. Run ulimit -a in a new session and exercise a bounded test workload.
  5. Use ssh -v to inspect the authentication attempt and verify which server account is selected.

Explanation

Correct Answers

B:

Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context. The change should be accepted only after this test: Run ulimit -a in a new session and exercise a bounded test workload.

D:

Run ulimit -a in a new session and exercise a bounded test workload. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.

Incorrect Answers

A:

It would address temporary login blockade rather than the present problem. The appropriate correction here is: Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.

C:

The test for ssh host identity mismatch would be: Compare the server's trusted host-key fingerprint with the client warning before accepting it. The relevant acceptance check here is: Run ulimit -a in a new session and exercise a bounded test workload.

E:

This belongs to user authorized ssh key, where The matching public key must be authorized for that server account and file permissions must permit sshd to read it securely. The current issue instead is: Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.

Question 786

An operator authenticates with sudo on a shared maintenance console, and another approved command runs without a new prompt during the cached authorization window. What underlying Linux behavior should the administrator identify first?

  1. sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry.
  2. A private key without a protective passphrase increases exposure if its file is stolen.
  3. A separate systemd .socket unit can listen and activate its associated service on demand.
  4. TCP wrappers normally evaluate a matching hosts.allow rule before hosts.deny.

Explanation

Correct Answer

A:

sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry. Addressing the cause requires: Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.

Incorrect Answers

B:

This option assumes A private key without a protective passphrase increases exposure if its file is stolen. The reported symptoms instead call for: Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.

C:

A separate systemd .socket unit can listen and activate its associated service on demand. 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: sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry.

D:

This belongs to hosts allow precedence in libwrap, where TCP wrappers normally evaluate a matching hosts.allow rule before hosts.deny. The current issue instead is: sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry.

Question 787

An operator authenticates with sudo on a shared maintenance console, and another approved command runs without a new prompt during the cached authorization window. What action should be planned as the next targeted correction?

  1. Place the user's approved public key in authorized_keys and verify server host keys separately.
  2. Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.
  3. Confirm whether the service supports TCP wrappers and otherwise use supported host firewall or application ACL controls.
  4. Publish an appropriate GPG key revocation and distribute the replacement trust path.

Explanation

Correct Answer

B:

Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console. This is appropriate because sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry.

Incorrect Answers

A:

Place the user's approved public key in authorized_keys and verify server host keys separately. belongs to a situation where Server host keys identify the SSH server; user keys authenticate the connecting client identity. Here the evidence supports a different requirement: Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.

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: sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry.

D:

Publish an appropriate GPG key revocation and distribute the replacement trust path. belongs to a situation where A revocation certificate communicates that a key should no longer be trusted for future decisions. Here the evidence supports a different requirement: Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.

Question 788

An operator authenticates with sudo on a shared maintenance console, and another approved command runs without a new prompt during the cached authorization window. Which test would confirm the suspected Linux mechanism?

  1. Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout.
  2. Connect to localhost:localport and verify it reaches only the intended internal service.
  3. Inspect systemctl list-sockets and attempt the connection after applying the policy.
  4. Compare the verified fingerprint with the key used by gpg --verify.

Explanation

Correct Answer

A:

Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout. It verifies that the targeted action (Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.) achieved its intended outcome.

Incorrect Answers

B:

It would address local port forwarding to internal database rather than the present problem. The appropriate correction here is: Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.

C:

This option assumes A separate systemd .socket unit can listen and activate its associated service on demand. The reported symptoms instead call for: Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.

D:

Compare the verified fingerprint with the key used by gpg --verify. could help with gpg signature from unknown key; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout.

Question 789

An operator authenticates with sudo on a shared maintenance console, and another approved command runs without a new prompt during the cached authorization window. Which practice is most useful after the immediate repair succeeds?

  1. Keep credential hashes in restricted stores and monitor mode drift.
  2. Review service state and firewall scope as separate layers of host security.
  3. Avoid unnecessary private-key copies and scope agent access to trusted sessions.
  4. Set and review sudo authentication-cache policy for sensitive shared administrative consoles.

Explanation

Correct Answer

D:

Set and review sudo authentication-cache policy for sensitive shared administrative consoles. This control detects or prevents the same mechanism before another incident.

Incorrect Answers

A:

That choice responds to a separate shadow hashes from public identities failure. In this incident, sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry.

B:

That choice responds to a firewall status versus service status failure. In this incident, sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry.

C:

Running ssh-agent does not itself load a private key into the agent. That describes a different fault. Here, sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry.

Question 790

An operator authenticates with sudo on a shared maintenance console, and another approved command runs without a new prompt during the cached authorization window. Select THREE measures that follow directly from the root cause and lifecycle risk.

  1. Generate or update a suitable ssh-keygen identity with a strong passphrase and keep the private key protected.
  2. Run ssh-add -l and verify an authenticated connection uses the loaded identity.
  3. Set and review sudo authentication-cache policy for sensitive shared administrative consoles.
  4. Include listener bind addresses, not just port numbers, in host-hardening baselines.
  5. Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout.
  6. Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.

Explanation

Correct Answers

C:

Set and review sudo authentication-cache policy for sensitive shared administrative consoles. This control detects or prevents the same mechanism before another incident.

E:

Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout. It verifies that the targeted action (Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.) achieved its intended outcome.

F:

Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console. It is the direct response; verify the result by: Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout.

Incorrect Answers

A:

That choice responds to a passphrase-protected key generation failure. In this incident, sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry.

B:

It would address ssh agent does not contain key rather than the present problem. The appropriate correction here is: Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.

D:

This option assumes The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener. The reported symptoms instead call for: Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.

LPI Level 1 (102-500) Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.