Pass LPI 102-500 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
LPI 102-500 Practice Test 88
Question 870
At fictional Eastgate Commerce, the Linux security administration team is working while investigating an observed production-like support incident. The Linux scenario is: A developer can connect with an explicit identity file but SSH agent authentication fails after a new login. The decisive evidence is: ssh-add -l reports no identities although the intended private key exists with correct permissions. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
To close the incident, demonstrate that an authorized SSH connection succeeds using the expected offered identity without exposing key material. That addresses ssh-add -l reports no identities although the intended private key exists with correct permissions and reflects the rule that ssh-agent holds unlocked key identities for client authentication without repeatedly reading passphrases.
Incorrect Answers
A test that scoped correction: Correlate current and historical session tools, verify the account owner and apply approved access review. Independent acceptance: An audit report identifies the historical session and the now-disabled unapproved access is tested would not demonstrate closure of this condition. The needed proof is an authorized SSH connection succeeds using the expected offered identity without exposing key material.
Scoped correction: Edit and validate a least-privilege sudoers rule with visudo and specific command restrictions. Independent acceptance: The operator can perform the authorized restart but an unrelated root command is denied. That does not demonstrate the case-specific success condition: an authorized SSH connection succeeds using the expected offered identity without exposing key material. Ssh-agent holds unlocked key identities for client authentication without repeatedly reading passphrases.
Scoped correction: Use the supported service configuration and current host firewall controls while documenting legacy TCP-wrapper applicability. Independent acceptance: A permitted client can connect and a prohibited client is denied in a controlled network test. That result does not test the original problem, identified by ssh-add -l reports no identities although the intended private key exists with correct permissions. Recovery must show that an authorized SSH connection succeeds using the expected offered identity without exposing key material.
Question 871
At fictional Northfield Manufacturing, the Linux security administration team is working during a controlled system-configuration acceptance test. The Linux scenario is: A team receives a signed release package and assumes the signature makes the archive confidential. The diagnostic evidence is: gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Which bounded step BEST resolves the described problem?
Explanation
Correct Answer
Gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality. The case-specific correction is to use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required. Preserve this constraint during the change: Never publish sensitive plaintext merely because a valid signature accompanies it.
Incorrect Answers
Another possible response is to restore distribution-appropriate shadow ownership and restrictive permissions and review potential disclosure. The case evidence instead shows that gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
Investigate the binary's provenance and remove or correct excessive privilege and directory access under change control. This does not address the reported incident: a team receives a signed release package and assumes the signature makes the archive confidential. Gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. The case-specific correction is to use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required.
One alternative would be to apply an approved per-service open-file limit and check system-wide file limits and resource usage. The observed evidence instead shows that gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. The more relevant correction is to use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required.
Question 872
At fictional Northfield Manufacturing, the Linux security administration team is working during a controlled system-configuration acceptance test. The Linux scenario is: A team receives a signed release package and assumes the signature makes the archive confidential. Which observation MOST directly supports the underlying diagnosis before any changes are made?
Explanation
Correct Answer
Gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. That observation distinguishes the reported incident because OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality. The appropriate response is to use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required.
Incorrect Answers
A competing Linux diagnostic finding for Northfield Manufacturing is: Permission inspection shows /etc/shadow accessible to users outside the intended privileged account context. It does not account for the observation gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file in the reported situation.
At Northfield Manufacturing, another diagnostic finding is: find permissions output shows the SUID bit and path ownership inconsistent with baseline policy. This would indicate another failure; here gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
At Northfield Manufacturing, a different observation is: The process ulimit -n is lower than the expected simultaneous file and socket count. It concerns another dependency. This incident is distinguished by gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
Question 873
At fictional Northfield Manufacturing, the Linux security administration team is working during a controlled system-configuration acceptance test. The Linux scenario is: A team receives a signed release package and assumes the signature makes the archive confidential. The proposed intervention is: Use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required. Which independent result BEST demonstrates a successful correction?
Explanation
Correct Answer
Verify the change by checking that a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder. The original clue was gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. The test is meaningful because OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
Incorrect Answers
At Northfield Manufacturing, another acceptance finding might be: A test unprivileged account cannot read password hashes and normal authentication continues functioning. That would still leave the reported failure unproven. An acceptance test must show that a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
At Northfield Manufacturing, a different acceptance result would be: A repeat inventory matches the approved SUID baseline and ordinary users cannot alter the helper. It may validate a separate setting, but not the required action: use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required. The required observation is a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
The independent acceptance evidence for Northfield Manufacturing is: A representative load processes the expected connections within monitored limits without unrelated resource exhaustion. The evidence relevant to this incident is gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Confirm the corresponding recovery result: A signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
Question 874
At fictional Northfield Manufacturing, the Linux security administration team is working during a controlled system-configuration acceptance test. The Linux scenario is: A team receives a signed release package and assumes the signature makes the archive confidential. The relevant evidence is: gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Which Linux administration principle MOST accurately explains the correct response?
Explanation
Correct Answer
The underlying rule is that OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality. Gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. A suitable correction is to use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required.
Incorrect Answers
A competing Linux principle for Northfield Manufacturing is: Linux shadow password storage separates sensitive hash data from publicly readable account attributes. The decisive observation, gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file, requires a different explanation: OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
A different principle is: the relevant Linux system principle for Northfield Manufacturing is: SUID/SGID permission bits can elevate execution privileges and require controlled ownership. The causal link actually supported by gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file is OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
A competing Linux principle for Northfield Manufacturing is: Per-process resource limits can constrain workloads independently of physical system capacity. However, it does not explain gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. The applicable principle is that OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
Question 875
At fictional Northfield Manufacturing, the Linux security administration team is working during a controlled system-configuration acceptance test. The Linux scenario is: A team receives a signed release package and assumes the signature makes the archive confidential. The decisive evidence is: gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
The acceptance evidence is a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder. This checks the intended outcome of use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required. OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
Incorrect Answers
Even verifying scoped correction: Restore distribution-appropriate shadow ownership and restrictive permissions and review potential disclosure. Independent acceptance: A test unprivileged account cannot read password hashes and normal authentication continues functioning leaves the reported failure unproven. An acceptance test must show that a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
The alternative outcome is scoped correction: Investigate the binary's provenance and remove or correct excessive privilege and directory access under change control. Independent acceptance: A repeat inventory matches the approved SUID baseline and ordinary users cannot alter the helper. It may validate a separate setting, but not the required action: use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required. The required observation is a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
Scoped correction: Apply an approved per-service open-file limit and check system-wide file limits and resource usage. Independent acceptance: A representative load processes the expected connections within monitored limits without unrelated resource exhaustion. The evidence relevant to this incident is gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Confirm the corresponding recovery result: A signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
Question 876
At fictional Clearbrook Works, the Linux security administration team is working while investigating an observed production-like support incident. The Linux scenario is: A team receives a signed release package and assumes the signature makes the archive confidential. The diagnostic evidence is: gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Which bounded step BEST resolves the described problem?
Explanation
Correct Answer
A team receives a signed release package and assumes the signature makes the archive confidential. The clue gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file supports the bounded action: Use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required. Confirm that a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder. Preserve this constraint during the change: Never publish sensitive plaintext merely because a valid signature accompanies it.
Incorrect Answers
Restore distribution-appropriate shadow ownership and restrictive permissions and review potential disclosure. It could be useful for another problem, but it does not change gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. The response needs to use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required.
An alternative action is investigate the binary's provenance and remove or correct excessive privilege and directory access under change control. This incident instead involves gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Confirm the scoped change through a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
Apply an approved per-service open-file limit and check system-wide file limits and resource usage. That would not correct the reported gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. The supported response is to use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required.
Question 877
At fictional Clearbrook Works, the Linux security administration team is working while investigating an observed production-like support incident. The Linux scenario is: A team receives a signed release package and assumes the signature makes the archive confidential. Which observation MOST directly supports the underlying diagnosis before any changes are made?
Explanation
Correct Answer
Gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality. This finding supports the targeted response: Use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required.
Incorrect Answers
A competing Linux diagnostic finding for Clearbrook Works is: Permission inspection shows /etc/shadow accessible to users outside the intended privileged account context. That finding does not isolate the reported issue: a team receives a signed release package and assumes the signature makes the archive confidential. The determining evidence is gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file.
At Clearbrook Works, that alternative suggests: find permissions output shows the SUID bit and path ownership inconsistent with baseline policy. The actual diagnostic record shows gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file instead. The difference matters because OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
At Clearbrook Works, another potential finding is: The process ulimit -n is lower than the expected simultaneous file and socket count. That would not establish the cause here. Gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. The case-specific correction is to use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required.
Question 878
At fictional Clearbrook Works, the Linux security administration team is working while investigating an observed production-like support incident. The Linux scenario is: A team receives a signed release package and assumes the signature makes the archive confidential. The proposed intervention is: Use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required. Which independent result BEST demonstrates a successful correction?
Explanation
Correct Answer
A signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder. This measures whether the response corrected gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file rather than merely completing a configuration step.
Incorrect Answers
A separate test at Clearbrook Works could show: A test unprivileged account cannot read password hashes and normal authentication continues functioning. That would not demonstrate closure of this condition. The needed proof is a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
The independent acceptance evidence for Clearbrook Works is: A repeat inventory matches the approved SUID baseline and ordinary users cannot alter the helper. That does not demonstrate the case-specific success condition: a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder. OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
The independent acceptance evidence for Clearbrook Works is: A representative load processes the expected connections within monitored limits without unrelated resource exhaustion. That result does not test the original problem, identified by gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Recovery must show that a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
Question 879
At fictional Clearbrook Works, the Linux security administration team is working while investigating an observed production-like support incident. The Linux scenario is: A team receives a signed release package and assumes the signature makes the archive confidential. The relevant evidence is: gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Which Linux administration principle MOST accurately explains the correct response?
Explanation
Correct Answer
OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality. The reported symptom arises where gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Address it through use GPG signing to authenticate integrity and encrypt separately to approved recipients when confidentiality is required.
Incorrect Answers
At Clearbrook Works, another Linux system principle is: Linux shadow password storage separates sensitive hash data from publicly readable account attributes. The present evidence is gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file, which instead follows from OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
A competing Linux principle for Clearbrook Works is: SUID/SGID permission bits can elevate execution privileges and require controlled ownership. This describes another relationship, not the cause of a team receives a signed release package and assumes the signature makes the archive confidential. OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
At Clearbrook Works, a different Linux system principle is: Per-process resource limits can constrain workloads independently of physical system capacity does not account for gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. This case is governed by OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
Question 880
At fictional Clearbrook Works, the Linux security administration team is working while investigating an observed production-like support incident. The Linux scenario is: A team receives a signed release package and assumes the signature makes the archive confidential. The decisive evidence is: gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
A signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder. Without that result, the finding gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file would remain unresolved.
Incorrect Answers
A test that scoped correction: Restore distribution-appropriate shadow ownership and restrictive permissions and review potential disclosure. Independent acceptance: A test unprivileged account cannot read password hashes and normal authentication continues functioning would not demonstrate closure of this condition. The needed proof is a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
Scoped correction: Investigate the binary's provenance and remove or correct excessive privilege and directory access under change control. Independent acceptance: A repeat inventory matches the approved SUID baseline and ordinary users cannot alter the helper. That does not demonstrate the case-specific success condition: a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder. OpenPGP signatures prove authenticity and integrity whereas encryption protects content confidentiality.
Scoped correction: Apply an approved per-service open-file limit and check system-wide file limits and resource usage. Independent acceptance: A representative load processes the expected connections within monitored limits without unrelated resource exhaustion. That result does not test the original problem, identified by gpg --verify succeeds but the artifact remains readable in plaintext to anyone with the file. Recovery must show that a signature verifies publisher identity while a separate encrypted test can be decrypted only by the intended keyholder.
LPI Level 1 (102-500) Practice Tests
- LPI 102-500 Practice Test 86 - 10 Questions (Last Reviewed 19-Oct-2026)
- LPI 102-500 Practice Test 87 - 10 Questions (Last Reviewed 18-Oct-2026)
- LPI 102-500 Practice Test 88 - 10 Questions (Last Reviewed 17-Oct-2026)
- LPI 102-500 Practice Test 89 - 10 Questions (Last Reviewed 16-Oct-2026)
- LPI 102-500 Practice Test 90 - 10 Questions (Last Reviewed 15-Oct-2026)
