LPI 102-500 Bundle

The option would apply to “A compliance reviewer needs to prove that a GPG-signed release manifest was not altered”. The governing principle is A digital signature binds file content to the private signing key and permits public verification. This question instead requires “SSH public-key authentication uses a private client key and authorized server-side public key”.

This option serves the scenario “A host still exposes Telnet but policy allows only encrypted remote administration”. The governing principle is Unneeded plaintext network login services expand authentication and interception risks. The present scenario is distinguished by “SSH public-key authentication uses a private client key and authorized server-side public key”.

This alternative addresses the separate case “A team must encrypt a confidential file for one specific recipient using GnuPG”. This behavior is explained by Public-key encryption uses the recipient's public key so their private key can decrypt. The deciding requirement here is “SSH public-key authentication uses a private client key and authorized server-side public key”.

The related but distinct situation is “A legacy application uses lpr and lpq but the host now uses CUPS”. The decisive distinction is CUPS can provide lpr, lpq and lprm-compatible client interfaces. The deciding requirement here is “Postfix and other MTAs can expose sendmail-compatible submission commands”.

This alternative addresses the separate case “An administrator is asked to identify whether Exim, Sendmail or Postfix is responsible for local mail”. The relevant Linux mechanism is Several MTAs implement compatible submission interfaces with different service backends. For the stated problem, “Postfix and other MTAs can expose sendmail-compatible submission commands” addresses the central condition.

The option would apply to “A command-line mail client reports queued messages and an administrator needs to inspect them”. This behavior is explained by An MTA can queue outgoing messages when immediate delivery is unavailable. The present scenario is distinguished by “Postfix and other MTAs can expose sendmail-compatible submission commands”.

This option serves the scenario “A script expects a simple command-line message to be delivered but its subject line is missing”. Verify that A test mail arrives with the intended subject and body content. The present scenario is distinguished by “The print configuration points to the approved server and a test reaches its queue”.

The required verification is The print configuration points to the approved server and a test reaches its queue, not a result meant for A user wants to print a PDF to a named printer rather than the system default.

The option would apply to “Printing stops after an operator disables a CUPS queue during maintenance”. Verify that lpstat -t reports a usable queue and a test page processes successfully. This question instead requires “The print configuration points to the approved server and a test reaches its queue”.

The option would apply to “A script must run a fallback check only when the primary check exits unsuccessfully”. The safest fitting response is Connect the commands with the shell OR-OR operator or an equivalent test of the previous exit code. The present scenario is distinguished by “Capture $? immediately or test the validation command directly in an if condition”.

The related but distinct situation is “A Bash function in a profile must be available to the current shell without logging out”. The safest fitting response is Source the profile with a dot command or source in the current Bash process. The deciding requirement here is “Capture $? immediately or test the validation command directly in an if condition”.

That option does not correct the stated dependency. In this case, Each subsequent shell command changes the most recently available exit status; implement Capture $? immediately or test the validation command directly in an if condition and check The alert executes only when the deliberately failing validation command fails.

The option would apply to “A log processor interprets bytes with the wrong character set after importing archival text”. The most direct risk is Changing LANG alone does not repair incorrectly encoded file contents. This question instead requires “Lack of terminal output is not proof that cron failed to execute”.

That danger is associated more closely with A monthly security scan requires a reminder on the first day at midnight and a separate weekly report. Here the primary exposure is Lack of terminal output is not proof that cron failed to execute.

It is not the most direct failure mode. The relevant mechanism is Cron's command output routing differs from interactive terminal output, which risks Lack of terminal output is not proof that cron failed to execute.

The proposed principle does not identify the crucial dependency in this case: A primary group is distinct from supplementary groups modified with -G.

This alternative addresses the separate case “A support team needs to inspect one user's groups but /etc/group alone seems to omit the primary group”. This behavior is explained by The primary GID is stored in the passwd record and can be resolved through group databases. For the stated problem, “A primary group is distinct from supplementary groups modified with -G” addresses the central condition.

The option would apply to “A monthly security scan requires a reminder on the first day at midnight and a separate weekly report”. Here, Multiple distinct recurrence requirements should not be compressed into a misleading single expression. The present scenario is distinguished by “A primary group is distinct from supplementary groups modified with -G”.

The case is most directly exposed to Cross-family tests can falsely diagnose a working IPv6 path as failed; the alternative describes a different operational risk.

It is not the most direct failure mode. The relevant mechanism is IPv4 and IPv6 use distinct address families and routing tables, which risks Cross-family tests can falsely diagnose a working IPv6 path as failed.

The stated concern is possible elsewhere, but the facts here specifically imply Cross-family tests can falsely diagnose a working IPv6 path as failed.

That danger is associated more closely with A developer must access a remote PostgreSQL service securely via an intermediate SSH host. Here the primary exposure is Overly permissive shadow access can expose credentials to ordinary users.

The related but distinct situation is “A service listens on all network interfaces though only local clients should use it”. Leaving the issue can cause Unnecessary public listeners expose sensitive services to outside networks. The deciding requirement here is “Overly permissive shadow access can expose credentials to ordinary users”.

That outcome fits another condition, A host still exposes Telnet but policy allows only encrypted remote administration, rather than the current one.

A passing result on that unrelated check cannot certify the present correction; require The incident report distinguishes live sessions from past successful logins.

This option serves the scenario “A process consumes too much address space and a shell session needs a temporary limit”. The best evidence is A controlled child process observes the configured limit. The present scenario is distinguished by “The incident report distinguishes live sessions from past successful logins”.

This alternative addresses the separate case “An SSH server rotates host keys but clients are told to disable strict host checking permanently”. The best evidence is A test session accepts only the verified new fingerprint. The deciding requirement here is “The incident report distinguishes live sessions from past successful logins”.

That danger is associated more closely with A script must run a fallback check only when the primary check exits unsuccessfully. Here the primary exposure is Combining streams unknowingly can corrupt machine-readable results.

This alternative addresses the separate case “A maintenance script captures the literal text $(hostname) instead of the machine name”. The main exposure is Incorrect single quotes can prevent required substitution from occurring. For the stated problem, “Combining streams unknowingly can corrupt machine-readable results” addresses the central condition.

The option would apply to “A script launched by sudo expects an administrator's custom shell alias to be available”. The main exposure is Assuming sudo inherits interactive aliases can break high-privilege maintenance. The present scenario is distinguished by “Combining streams unknowingly can corrupt machine-readable results”.

That outcome fits another condition, A service account should not receive diagnostic mail at an unmonitored local mailbox, rather than the current one.

That danger is associated more closely with A server sends logs to two separate files because old rsyslog rules and new journald forwarding overlap. Here the primary exposure is Cyclic forwarding can consume resources and generate repeated delivery failures.

The related but distinct situation is “An administrator is asked to identify whether Exim, Sendmail or Postfix is responsible for local mail”. Leaving the issue can cause Applying instructions for the wrong daemon can disrupt mail delivery. For the stated problem, “Cyclic forwarding can consume resources and generate repeated delivery failures” addresses the central condition.