100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 880
A confidential archive must be readable only by an intended recipient, but a colleague proposes signing without encryption. Which THREE case-specific steps cover immediate repair, test evidence and sustained control?
- Disable and stop the corresponding socket unit as well as the service when decommissioning it.
- Compare remotely observed services with local ss listeners and filtering rules.
- Encrypt the archive to the recipient's verified public GPG key.
- Validate recipient public-key identity before protecting sensitive material.
- Use the recipient's private key in a controlled test to decrypt and compare the recovered archive.
- Set and review sudo authentication-cache policy for sensitive shared administrative consoles.
Explanation
Correct Answers
C:Encrypt the archive to the recipient's verified public GPG key. This is appropriate because A signature may authenticate integrity but leaves ordinary plaintext visible without encryption.
D:Validate recipient public-key identity before protecting sensitive material. Sustained checks matter because A signature may authenticate integrity but leaves ordinary plaintext visible without encryption.
E:Use the recipient's private key in a controlled test to decrypt and compare the recovered archive. The test is evidence-based because the underlying failure was: A signature may authenticate integrity but leaves ordinary plaintext visible without encryption.
Incorrect Answers
A: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: A signature may authenticate integrity but leaves ordinary plaintext visible without encryption.
B:This option assumes Local listening state does not account for intervening host firewalls or network ACLs. The reported symptoms instead call for: Encrypt the archive to the recipient's verified public GPG key.
F: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 the recipient's private key in a controlled test to decrypt and compare the recovered archive.
Question 881
An analyst gets a good cryptographic GPG signature but the signer's key identity has never been checked. Which explanation most directly accounts for the failure in this environment?
- A super-server such as xinetd launches enabled services in response to incoming connections.
- Invalid sudoers syntax can break privilege delegation and an unvalidated edit is risky.
- Historical login tools alone do not enumerate current session commands and idle times.
- A mathematically valid signature does not independently establish who owns the public key.
Explanation
Correct Answer
D:A mathematically valid signature does not independently establish who owns the public key. The administrator should distinguish this from unrelated symptoms by checking: Compare the verified fingerprint with the key used by gpg --verify.
Incorrect Answers
A:The test for xinetd service enabled accidentally would be: Scan the service port after restart and inspect the active xinetd configuration. The relevant acceptance check here is: Compare the verified fingerprint with the key used by gpg --verify.
B:The test for edit sudo policy safely would be: Run visudo -c and sudo -l for an authorized test identity. The relevant acceptance check here is: Compare the verified fingerprint with the key used by gpg --verify.
C: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: A mathematically valid signature does not independently establish who owns the public key.
Question 882
An analyst gets a good cryptographic GPG signature but the signer's key identity has never been checked. What should the administrator do to correct this behavior?
- Migrate to distribution-supported shadow password storage with approved permissions.
- Review sudo timestamp_timeout policy through visudo and end the cached authorization with sudo -k when leaving the console.
- Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity.
- Set a policy-approved ulimit -u or equivalent PAM-managed resource limit for the relevant user context.
Explanation
Correct Answer
C:Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity. This is appropriate because A mathematically valid signature does not independently establish who owns the public key.
Incorrect Answers
A:The shadow-password model keeps hashes in restricted /etc/shadow, while passwd contains public account fields. That describes a different fault. Here, A mathematically valid signature does not independently establish who owns the public key.
B:This option assumes sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry. The reported symptoms instead call for: Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity.
D:It would address shell process limits rather than the present problem. The appropriate correction here is: Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity.
Question 883
An analyst gets a good cryptographic GPG signature but the signer's key identity has never been checked. Which check would provide the strongest evidence that the fix worked?
- Compare the verified fingerprint with the key used by gpg --verify.
- Compare ss -ltnp and a controlled remote port scan before and after hardening.
- Inspect account record fields and effective /etc/shadow permissions in a controlled test.
- Test access from an allowed and denied client while observing the active enforcement mechanism.
Explanation
Correct Answer
A:Compare the verified fingerprint with the key used by gpg --verify. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
B:Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port. That describes a different fault. Here, A mathematically valid signature does not independently establish who owns the public key.
C:This option assumes The shadow-password model keeps hashes in restricted /etc/shadow, while passwd contains public account fields. The reported symptoms instead call for: Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity.
D:Test access from an allowed and denied client while observing the active enforcement mechanism. could help with tcp wrappers are legacy; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare the verified fingerprint with the key used by gpg --verify.
Question 884
An analyst gets a good cryptographic GPG signature but the signer's key identity has never been checked. What should the team standardize to prevent similar incidents?
- Record key identity provenance alongside signature validation outcomes.
- Include listener bind addresses, not just port numbers, in host-hardening baselines.
- Maintain a minimal approved service inventory and review listeners periodically.
- Maintain approved service-port inventory and alert on unexpected listeners.
Explanation
Correct Answer
A:Record key identity provenance alongside signature validation outcomes. It preserves the corrective behavior established through: Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity.
Incorrect Answers
B:The test for local-only service binds every interface would be: Use ss -ltnp to confirm the loopback bind and test access from both local and remote clients. The relevant acceptance check here is: Compare the verified fingerprint with the key used by gpg --verify.
C:Maintain a minimal approved service inventory and review listeners periodically. belongs to a situation where Unused enabled services increase attack surface and persist through restarts. Here the evidence supports a different requirement: Record key identity provenance alongside signature validation outcomes.
D:This belongs to find process owning tcp listener, where The listening port may belong to an active local process rather than a stale firewall rule. The current issue instead is: A mathematically valid signature does not independently establish who owns the public key.
Question 885
An analyst gets a good cryptographic GPG signature but the signer's key identity has never been checked. Select TWO justified actions that address this particular problem and confirm closure.
- Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity.
- Inspect account record fields and effective /etc/shadow permissions in a controlled test.
- Compare the verified fingerprint with the key used by gpg --verify.
- Treat service units and socket units as separate controls when reducing attack surface.
- Use w to inspect current users, TTYs, idle times and active commands.
Explanation
Correct Answers
A:Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity. It corrects the mechanism identified in the scenario: A mathematically valid signature does not independently establish who owns the public key.
C:Compare the verified fingerprint with the key used by gpg --verify. It verifies that the targeted action (Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity.) achieved its intended outcome.
Incorrect Answers
B:It would address separate shadow hashes from public identities rather than the present problem. The appropriate correction here is: Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity.
D:That choice responds to a socket activation keeps port open failure. In this incident, A mathematically valid signature does not independently establish who owns the public key.
E:This option assumes Historical login tools alone do not enumerate current session commands and idle times. The reported symptoms instead call for: Verify the signer's public-key fingerprint through an independent trusted channel before relying on identity.
Question 886
A private signing key was compromised, but old recipients still rely on its published public key. Which mechanism best explains the difference between expectation and result?
- The service is bound to all IPv4 interfaces rather than the intended loopback interface, unnecessarily exposing the listener.
- sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry.
- A revocation certificate communicates that a key should no longer be trusted for future decisions.
- Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context.
Explanation
Correct Answer
C:A revocation certificate communicates that a key should no longer be trusted for future decisions. This is the explanation that justifies the specific remedy: Publish an appropriate GPG key revocation and distribute the replacement trust path.
Incorrect Answers
A:That choice responds to a local-only service binds every interface failure. In this incident, A revocation certificate communicates that a key should no longer be trusted for future decisions.
B:This option assumes sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry. The reported symptoms instead call for: Publish an appropriate GPG key revocation and distribute the replacement trust path.
D:This option assumes Unlimited user process creation can exhaust host resources; ulimit exposes shell limits for the current context. The reported symptoms instead call for: Publish an appropriate GPG key revocation and distribute the replacement trust path.
Question 887
A private signing key was compromised, but old recipients still rely on its published public key. What should the administrator do to correct this behavior?
- Publish an appropriate GPG key revocation and distribute the replacement trust path.
- Run sudo -l under the user's identity to enumerate the commands sudo permits.
- Run an authorized nmap scan from the designated assessment subnet against the approved target.
- Disable the relevant xinetd service entry and reload the appropriate supervisor configuration.
Explanation
Correct Answer
A:Publish an appropriate GPG key revocation and distribute the replacement trust path. This is appropriate because A revocation certificate communicates that a key should no longer be trusted for future decisions.
Incorrect Answers
B:This belongs to inspect effective sudo privilege, where Group membership or an assertion is not sufficient evidence of the actual sudoers permissions. The current issue instead is: A revocation certificate communicates that a key should no longer be trusted for future decisions.
C:That choice responds to a external port scan scope failure. In this incident, A revocation certificate communicates that a key should no longer be trusted for future decisions.
D:A super-server such as xinetd launches enabled services in response to incoming connections. That describes a different fault. Here, A revocation certificate communicates that a key should no longer be trusted for future decisions.
Question 888
A private signing key was compromised, but old recipients still rely on its published public key. Which check would provide the strongest evidence that the fix worked?
- Inspect account record fields and effective /etc/shadow permissions in a controlled test.
- Compare ss -ltnp and a controlled remote port scan before and after hardening.
- Import the revocation in a clean test keyring and inspect key validity before signature acceptance.
- Use sudo -k and a controlled sudo command to confirm the expected authentication prompt and timeout.
Explanation
Correct Answer
C:Import the revocation in a clean test keyring and inspect key validity before signature acceptance. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
A:This belongs to separate shadow hashes from public identities, where The shadow-password model keeps hashes in restricted /etc/shadow, while passwd contains public account fields. The current issue instead is: A revocation certificate communicates that a key should no longer be trusted for future decisions.
B:This option assumes Disabling one daemon does not automatically remove permissive network filtering or prove another listener cannot bind the port. The reported symptoms instead call for: Publish an appropriate GPG key revocation and distribute the replacement trust path.
D:This belongs to sudo credential cache on shared console, where sudo may cache recent authentication for a policy-defined period, and that timestamp is independent of account password expiry. The current issue instead is: A revocation certificate communicates that a key should no longer be trusted for future decisions.
Question 889
A private signing key was compromised, but old recipients still rely on its published public key. Which ongoing control would best reduce the chance of the issue returning?
- Maintain approved service-port inventory and alert on unexpected listeners.
- Keep credential hashes in restricted stores and monitor mode drift.
- Set and review sudo authentication-cache policy for sensitive shared administrative consoles.
- Prepare revocation material and recovery plans before key compromise occurs.
Explanation
Correct Answer
D:Prepare revocation material and recovery plans before key compromise occurs. Sustained checks matter because A revocation certificate communicates that a key should no longer be trusted for future decisions.
Incorrect Answers
A: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: Import the revocation in a clean test keyring and inspect key validity before signature acceptance.
B:This belongs to separate shadow hashes from public identities, where The shadow-password model keeps hashes in restricted /etc/shadow, while passwd contains public account fields. The current issue instead is: A revocation certificate communicates that a key should no longer be trusted for future decisions.
C:Set and review sudo authentication-cache policy for sensitive shared administrative consoles. could help with sudo credential cache on shared console; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Import the revocation in a clean test keyring and inspect key validity before signature acceptance.
Question 890
A private signing key was compromised, but old recipients still rely on its published public key. Which THREE actions form a suitable remediation, verification and prevention plan? Select THREE.
- Prepare revocation material and recovery plans before key compromise occurs.
- Import the revocation in a clean test keyring and inspect key validity before signature acceptance.
- Compare remotely observed services with local ss listeners and filtering rules.
- Search appropriate filesystem scopes for the setuid bit using find -perm -4000 and review ownership.
- Publish an appropriate GPG key revocation and distribute the replacement trust path.
- Protect and retain login history centrally for incident reconstruction.
Explanation
Correct Answers
A:Prepare revocation material and recovery plans before key compromise occurs. This control detects or prevents the same mechanism before another incident.
B:Import the revocation in a clean test keyring and inspect key validity before signature acceptance. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
E:Publish an appropriate GPG key revocation and distribute the replacement trust path. It addresses the root cause, while Prepare revocation material and recovery plans before key compromise occurs. reduces future recurrence.
Incorrect Answers
C:Local listening state does not account for intervening host firewalls or network ACLs. That describes a different fault. Here, A revocation certificate communicates that a key should no longer be trusted for future decisions.
D:Search appropriate filesystem scopes for the setuid bit using find -perm -4000 and review ownership. 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: Publish an appropriate GPG key revocation and distribute the replacement trust path.
F:Protect and retain login history centrally for incident reconstruction. 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: Prepare revocation material and recovery plans before key compromise occurs.
LPI Level 1 (102-500) Practice Tests