Pass LPI 102-500 Exam in First Attempt Easily
Real LPI 102-500 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts
3 products

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
$79.99 $149.97

Purchase Individually

  • Premium File

    120 Questions & Answers
    Last Update: Nov 10, 2026

    $76.99
    $69.99
  • Training Course

    126 Lectures

    $43.99
    $39.99
  • Study Guide

    962 Pages

    $43.99
    $39.99

LPI Level 1 102-500 Practice Test 77

Question 760

A Linux troubleshooter is gathering specific evidence for this situation: An SSH client warns that a server's host key has changed after a maintenance window and the operator wants to disable checking. Which check MOST directly diagnoses or confirms the technical condition described?

  1. Use find with the setuid permission predicate and examine stat ownership and package provenance.
  2. Inspect the key's revocation status and published key updates in controlled tests.
  3. Inspect the remote authorized_keys content and ssh -v authentication trace.
  4. Compare the trusted server fingerprint with the client's known_hosts entry.

Explanation

Correct Answer

D:

Compare the trusted server fingerprint with the client's known_hosts entry. This check targets the relevant state for validating a changed ssh server host key and directly assesses the observed behavior. The result should be evaluated against: The independently confirmed fingerprint matches the server and the SSH warning is resolved safely.

Incorrect Answers

A:

Use find with the setuid permission predicate and examine stat ownership and package provenance. This check is relevant to auditing setuid binaries for unexpected privilege but not the most targeted diagnosis of validating a changed ssh server host key. The specific check is: Compare the trusted server fingerprint with the client's known_hosts entry.

B:

Inspect the key's revocation status and published key updates in controlled tests. This check is relevant to revoking a compromised openpgp key but not the most targeted diagnosis of validating a changed ssh server host key. The specific check is: Compare the trusted server fingerprint with the client's known_hosts entry.

C:

Inspect the remote authorized_keys content and ssh -v authentication trace. This check is relevant to installing the correct authorized ssh public key but not the most targeted diagnosis of validating a changed ssh server host key. The specific check is: Compare the trusted server fingerprint with the client's known_hosts entry.

Question 761

A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: An engineer repeatedly types a protected private-key passphrase for every deployment operation from one approved session. Which step MOST directly corrects the specific problem described?

  1. Use SSH X11 forwarding with appropriate server support and client authorization.
  2. Place the appropriate public key in the remote account's ~/.ssh/authorized_keys with safe permissions.
  3. Start an authorized ssh-agent session and load the key securely for controlled use.
  4. Inspect who or w to identify current sessions and their activity before the change.

Explanation

Correct Answer

C:

Start an authorized ssh-agent session and load the key securely for controlled use. This targets the observed issue, keeping ssh private keys in an agent, rather than a separate Linux configuration. Underlying behavior: ssh-agent stores private-key signing capability for authentication within a managed session. Verify the action by checking: Subsequent SSH operations reuse agent-backed signing without exposing the key file to remote hosts.

Incorrect Answers

A:

Use SSH X11 forwarding with appropriate server support and client authorization. This is an appropriate response to a different issue (forwarding an x11 application over ssh) but does not MOST directly address the explicit keeping ssh private keys in an agent failure.

B:

Place the appropriate public key in the remote account's ~/.ssh/authorized_keys with safe permissions. This is an appropriate response to a different issue (installing the correct authorized ssh public key) but does not MOST directly address the explicit keeping ssh private keys in an agent failure.

D:

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 keeping ssh private keys in an agent failure.

Question 762

A Linux team is checking the acceptance evidence for this specific situation: An engineer repeatedly types a protected private-key passphrase for every deployment operation from one approved session. Which observation BEST confirms that this particular issue has been corrected?

  1. The service can no longer be launched through xinetd and its port is not exposed.
  2. A login using the corresponding private key succeeds only for the authorized account.
  3. Subsequent SSH operations reuse agent-backed signing without exposing the key file to remote hosts.
  4. The independently confirmed fingerprint matches the server and the SSH warning is resolved safely.

Explanation

Correct Answer

C:

Subsequent SSH operations reuse agent-backed signing without exposing the key file to remote hosts. That evidence specifically demonstrates recovery from keeping ssh private keys in an agent. The technical reason is: ssh-agent stores private-key signing capability for authentication within a managed session.

Incorrect Answers

A:

The service can no longer be launched through xinetd and its port is not exposed. This can validate reviewing legacy xinetd service activation, but it does not establish that the described keeping ssh private keys in an agent issue is fixed. The case-specific evidence is: Subsequent SSH operations reuse agent-backed signing without exposing the key file to remote hosts.

B:

A login using the corresponding private key succeeds only for the authorized account. This can validate installing the correct authorized ssh public key, but it does not establish that the described keeping ssh private keys in an agent issue is fixed. The case-specific evidence is: Subsequent SSH operations reuse agent-backed signing without exposing the key file to remote hosts.

D:

The independently confirmed fingerprint matches the server and the SSH warning is resolved safely. This can validate validating a changed ssh server host key, but it does not establish that the described keeping ssh private keys in an agent issue is fixed. The case-specific evidence is: Subsequent SSH operations reuse agent-backed signing without exposing the key file to remote hosts.

Question 763

A Linux engineer reviews the underlying behavior in this particular case: An engineer repeatedly types a protected private-key passphrase for every deployment operation from one approved session. Which technical behavior BEST explains this particular failure and its remedy?

  1. GnuPG decryption requires access to the appropriate secret key for the encrypted recipient.
  2. ssh-agent stores private-key signing capability for authentication within a managed session.
  3. Asymmetric SSH authentication proves possession of a private key without transmitting it to the server.
  4. Stopping a running service and disabling future startup are separate service-manager operations.

Explanation

Correct Answer

B:

ssh-agent stores private-key signing capability for authentication within a managed session. This Linux behavior explains the observed symptoms and supports the precise remedy: Start an authorized ssh-agent session and load the key securely for controlled use.

Incorrect Answers

A:

GnuPG decryption requires access to the appropriate secret key for the encrypted recipient. This describes another behavior (decrypting a received gpg-encrypted file) and does not explain the stated keeping ssh private keys in an agent failure. The operative behavior is: ssh-agent stores private-key signing capability for authentication within a managed session.

C:

Asymmetric SSH authentication proves possession of a private key without transmitting it to the server. This describes another behavior (generating an ssh client key pair) and does not explain the stated keeping ssh private keys in an agent failure. The operative behavior is: ssh-agent stores private-key signing capability for authentication within a managed session.

D:

Stopping a running service and disabling future startup are separate service-manager operations. This describes another behavior (disabling an unused systemd service) and does not explain the stated keeping ssh private keys in an agent failure. The operative behavior is: ssh-agent stores private-key signing capability for authentication within a managed session.

Question 764

A Linux operating control has not corrected the following specific problem: An engineer repeatedly types a protected private-key passphrase for every deployment operation from one approved session. Which outcome is the MOST directly associated operational risk if this problem remains?

  1. An invalid or broad sudoers rule can lock out administrators or confer excess privilege.
  2. Sharing a private key can let an attacker impersonate the administrator.
  3. Publishing a private database port could expand external attack exposure.
  4. Uncontrolled agent access can enable unintended authentication during the session.

Explanation

Correct Answer

D:

Uncontrolled agent access can enable unintended authentication during the session. This is the directly relevant consequence of leaving the keeping ssh private keys in an agent problem unresolved. The appropriate preventive change is: Start an authorized ssh-agent session and load the key securely for controlled use.

Incorrect Answers

A:

An invalid or broad sudoers rule can lock out administrators or confer excess privilege. This consequence is connected to safe validation of sudo policy changes rather than the MOST direct exposure in the stated keeping ssh private keys in an agent problem. The specific consequence is: Uncontrolled agent access can enable unintended authentication during the session.

B:

Sharing a private key can let an attacker impersonate the administrator. This consequence is connected to generating an ssh client key pair rather than the MOST direct exposure in the stated keeping ssh private keys in an agent problem. The specific consequence is: Uncontrolled agent access can enable unintended authentication during the session.

C:

Publishing a private database port could expand external attack exposure. This consequence is connected to local ssh port forwarding rather than the MOST direct exposure in the stated keeping ssh private keys in an agent problem. The specific consequence is: Uncontrolled agent access can enable unintended authentication during the session.

Question 765

A Linux troubleshooter is gathering specific evidence for this situation: An engineer repeatedly types a protected private-key passphrase for every deployment operation from one approved session. Which check MOST directly diagnoses or confirms the technical condition described?

  1. Review account status with passwd -S and chage -l and inspect PAM configuration.
  2. Check ssh-add -l before and after loading the specific key.
  3. Inspect SSH_AUTH_SOCK, agent identities and session permissions.
  4. Inspect the recipient key identity and gpg --encrypt output format and recipient list.

Explanation

Correct Answer

C:

Inspect SSH_AUTH_SOCK, agent identities and session permissions. This check targets the relevant state for keeping ssh private keys in an agent and directly assesses the observed behavior. The result should be evaluated against: Subsequent SSH operations reuse agent-backed signing without exposing the key file to remote hosts.

Incorrect Answers

A:

Review account status with passwd -S and chage -l and inspect PAM configuration. This check is relevant to checking effective shadow authentication state but not the most targeted diagnosis of keeping ssh private keys in an agent. The specific check is: Inspect SSH_AUTH_SOCK, agent identities and session permissions.

B:

Check ssh-add -l before and after loading the specific key. This check is relevant to adding a specific key to the running ssh agent but not the most targeted diagnosis of keeping ssh private keys in an agent. The specific check is: Inspect SSH_AUTH_SOCK, agent identities and session permissions.

D:

Inspect the recipient key identity and gpg --encrypt output format and recipient list. This check is relevant to encrypting a file to a gnupg recipient but not the most targeted diagnosis of keeping ssh private keys in an agent. The specific check is: Inspect SSH_AUTH_SOCK, agent identities and session permissions.

Question 766

A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: The SSH agent is running but login still prompts for an unavailable key because the intended identity was never loaded. Which step MOST directly corrects the specific problem described?

  1. Inspect the protected shadow state and applicable authentication policy before concluding that the account is enabled.
  2. Load the intended private key using ssh-add and verify the agent's identity list.
  3. Issue and distribute the appropriate revocation certificate and replace the compromised signing identity.
  4. Use GnuPG encryption with the intended recipient's trusted public key before transfer.

Explanation

Correct Answer

B:

Load the intended private key using ssh-add and verify the agent's identity list. This targets the observed issue, adding a specific key to the running ssh agent, rather than a separate Linux configuration. Underlying behavior: An active agent needs a loaded identity before it can sign challenges for that key. Verify the action by checking: ssh-add -l shows the correct identity and an authorized SSH connection uses it.

Incorrect Answers

A:

Inspect the protected shadow state and applicable authentication policy before concluding that the account is enabled. This is an appropriate response to a different issue (checking effective shadow authentication state) but does not MOST directly address the explicit adding a specific key to the running ssh agent failure.

C:

Issue and distribute the appropriate revocation certificate and replace the compromised signing identity. This is an appropriate response to a different issue (revoking a compromised openpgp key) but does not MOST directly address the explicit adding a specific key to the running ssh agent failure.

D:

Use GnuPG encryption with the intended recipient's trusted public key before transfer. This is an appropriate response to a different issue (encrypting a file to a gnupg recipient) but does not MOST directly address the explicit adding a specific key to the running ssh agent failure.

Question 767

A Linux team is checking the acceptance evidence for this specific situation: The SSH agent is running but login still prompts for an unavailable key because the intended identity was never loaded. Which observation BEST confirms that this particular issue has been corrected?

  1. ssh-add -l shows the correct identity and an authorized SSH connection uses it.
  2. The independently confirmed fingerprint matches the server and the SSH warning is resolved safely.
  3. The decrypted output matches the expected controlled sample and has protected file permissions.
  4. The process name, PID and listening socket are tied to the expected approved service.

Explanation

Correct Answer

A:

ssh-add -l shows the correct identity and an authorized SSH connection uses it. That evidence specifically demonstrates recovery from adding a specific key to the running ssh agent. The technical reason is: An active agent needs a loaded identity before it can sign challenges for that key.

Incorrect Answers

B:

The independently confirmed fingerprint matches the server and the SSH warning is resolved safely. This can validate validating a changed ssh server host key, but it does not establish that the described adding a specific key to the running ssh agent issue is fixed. The case-specific evidence is: ssh-add -l shows the correct identity and an authorized SSH connection uses it.

C:

The decrypted output matches the expected controlled sample and has protected file permissions. This can validate decrypting a received gpg-encrypted file, but it does not establish that the described adding a specific key to the running ssh agent issue is fixed. The case-specific evidence is: ssh-add -l shows the correct identity and an authorized SSH connection uses it.

D:

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 adding a specific key to the running ssh agent issue is fixed. The case-specific evidence is: ssh-add -l shows the correct identity and an authorized SSH connection uses it.

Question 768

A Linux engineer reviews the underlying behavior in this particular case: The SSH agent is running but login still prompts for an unavailable key because the intended identity was never loaded. Which technical behavior BEST explains this particular failure and its remedy?

  1. Asymmetric SSH authentication proves possession of a private key without transmitting it to the server.
  2. An active agent needs a loaded identity before it can sign challenges for that key.
  3. The shadow password database stores sensitive credential hashes separately from publicly readable account data.
  4. The server checks the client's public key against authorized_keys during public-key authentication.

Explanation

Correct Answer

B:

An active agent needs a loaded identity before it can sign challenges for that key. This Linux behavior explains the observed symptoms and supports the precise remedy: Load the intended private key using ssh-add and verify the agent's identity list.

Incorrect Answers

A:

Asymmetric SSH authentication proves possession of a private key without transmitting it to the server. This describes another behavior (generating an ssh client key pair) and does not explain the stated adding a specific key to the running ssh agent failure. The operative behavior is: An active agent needs a loaded identity before it can sign challenges for that key.

C:

The shadow password database stores sensitive credential hashes separately from publicly readable account data. This describes another behavior (preserving shadow file confidentiality) and does not explain the stated adding a specific key to the running ssh agent failure. The operative behavior is: An active agent needs a loaded identity before it can sign challenges for that key.

D:

The server checks the client's public key against authorized_keys during public-key authentication. This describes another behavior (installing the correct authorized ssh public key) and does not explain the stated adding a specific key to the running ssh agent failure. The operative behavior is: An active agent needs a loaded identity before it can sign challenges for that key.

Question 769

A Linux operating control has not corrected the following specific problem: The SSH agent is running but login still prompts for an unavailable key because the intended identity was never loaded. Which outcome is the MOST directly associated operational risk if this problem remains?

  1. Sharing a private key can let an attacker impersonate the administrator.
  2. Uncontrolled agent access can enable unintended authentication during the session.
  3. A missing identity can cause needless account password fallbacks.
  4. A mistaken assumption could leave unauthorized accounts accessible or block legitimate users.

Explanation

Correct Answer

C:

A missing identity can cause needless account password fallbacks. This is the directly relevant consequence of leaving the adding a specific key to the running ssh agent problem unresolved. The appropriate preventive change is: Load the intended private key using ssh-add and verify the agent's identity list.

Incorrect Answers

A:

Sharing a private key can let an attacker impersonate the administrator. This consequence is connected to generating an ssh client key pair rather than the MOST direct exposure in the stated adding a specific key to the running ssh agent problem. The specific consequence is: A missing identity can cause needless account password fallbacks.

B:

Uncontrolled agent access can enable unintended authentication during the session. This consequence is connected to keeping ssh private keys in an agent rather than the MOST direct exposure in the stated adding a specific key to the running ssh agent problem. The specific consequence is: A missing identity can cause needless account password fallbacks.

D:

A mistaken assumption could leave unauthorized accounts accessible or block legitimate users. This consequence is connected to checking effective shadow authentication state rather than the MOST direct exposure in the stated adding a specific key to the running ssh agent problem. The specific consequence is: A missing identity can cause needless account password fallbacks.

Question 770

A Linux troubleshooter is gathering specific evidence for this situation: The SSH agent is running but login still prompts for an unavailable key because the intended identity was never loaded. Which check MOST directly diagnoses or confirms the technical condition described?

  1. Inspect the key's revocation status and published key updates in controlled tests.
  2. Inspect lsof -i or ss -lntp for the specific port.
  3. Inspect the signature result and independently validated signer fingerprint.
  4. Check ssh-add -l before and after loading the specific key.

Explanation

Correct Answer

D:

Check ssh-add -l before and after loading the specific key. This check targets the relevant state for adding a specific key to the running ssh agent and directly assesses the observed behavior. The result should be evaluated against: ssh-add -l shows the correct identity and an authorized SSH connection uses it.

Incorrect Answers

A:

Inspect the key's revocation status and published key updates in controlled tests. This check is relevant to revoking a compromised openpgp key but not the most targeted diagnosis of adding a specific key to the running ssh agent. The specific check is: Check ssh-add -l before and after loading the specific key.

B:

Inspect lsof -i or ss -lntp for the specific port. This check is relevant to mapping an open port to its owning process but not the most targeted diagnosis of adding a specific key to the running ssh agent. The specific check is: Check ssh-add -l before and after loading the specific key.

C:

Inspect the signature result and independently validated signer fingerprint. This check is relevant to verifying a detached gpg signature but not the most targeted diagnosis of adding a specific key to the running ssh agent. The specific check is: Check ssh-add -l before and after loading the specific key.

LPI Level 1 (102-500) Practice Tests

Purchase Individually

  • Premium File

    120 Questions & Answers
    Last Update: Nov 10, 2026

    $76.99
    $69.99
  • Training Course

    126 Lectures

    $43.99
    $39.99
  • Study Guide

    962 Pages

    $43.99
    $39.99

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

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

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

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

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports