LPI 102-500 Bundle

This alternative addresses the separate case “An application binds to port 8443 but remote users cannot connect and the team blames DNS”. Here, A service listening only on loopback cannot accept connections sent to an external interface. The deciding requirement here is “Inconsistent subnet masks cause peers to disagree about which destinations are on-link”.

The proposed principle does not identify the crucial dependency in this case: Inconsistent subnet masks cause peers to disagree about which destinations are on-link.

This would be the main explanation for An IPv6 interface displays an fe80:: address and an operator expects Internet-wide routing. It does not account for A test host uses 255.255.255.0 but another host in the same VLAN uses 255.255.0.0.

It is not the most direct failure mode. The relevant mechanism is Special-purpose service accounts need not permit general human logins, which risks An interactive service account increases the credential attack surface.

The stated concern is possible elsewhere, but the facts here specifically imply An interactive service account increases the credential attack surface.

This option serves the scenario “A user account is deleted but its running processes and file ownership remain on shared storage”. The most direct risk is Reusing the UID prematurely can expose another person's files to a new account. This question instead requires “An interactive service account increases the credential attack surface”.

The stated concern is possible elsewhere, but the facts here specifically imply Editing a text alias alone may leave the MTA using stale routing data.

The case is most directly exposed to Editing a text alias alone may leave the MTA using stale routing data; the alternative describes a different operational risk.

This option serves the scenario “A service's journal uses too much storage even though logrotate handles text logs correctly”. The main exposure is Mistaking journal files for normal rotated text may leave disk use unchecked. The present scenario is distinguished by “Editing a text alias alone may leave the MTA using stale routing data”.

The proposed principle does not identify the crucial dependency in this case: ssh-agent caches unlocked key operations without requiring raw private-key copying to applications.

This option serves the scenario “A user wants to decrypt a GnuPG file received for a different person's key”. This behavior is explained by Encryption to a public key normally requires the corresponding private key for decryption. This question instead requires “ssh-agent caches unlocked key operations without requiring raw private-key copying to applications”.

This alternative addresses the separate case “An operator stores the private SSH identity in a world-readable shared directory”. The decisive distinction is SSH private keys must remain secret to preserve authentication assurance. For the stated problem, “ssh-agent caches unlocked key operations without requiring raw private-key copying to applications” addresses the central condition.

The case is most directly exposed to Assuming a shell-only limit applies to unrelated systemd services can leave gaps; the alternative describes a different operational risk.

It is not the most direct failure mode. The relevant mechanism is Shell resource limits can constrain selected process resources and are inherited by children, which risks Assuming a shell-only limit applies to unrelated systemd services can leave gaps.

It is not the most direct failure mode. The relevant mechanism is Shell resource limits can constrain selected process resources and are inherited by children, which risks Assuming a shell-only limit applies to unrelated systemd services can leave gaps.

A passing result on that unrelated check cannot certify the present correction; require Both blank and spaced test strings lead to the documented conditional branches.

The option would apply to “A nightly cleanup loop processes filenames containing spaces by iterating over unquoted command substitution”. The best evidence is A test fixture with spaced filenames is handled without splitting or deleting the wrong path. The present scenario is distinguished by “Both blank and spaced test strings lead to the documented conditional branches”.

This option serves the scenario “A user appends a directory to ~/.bashrc but a fresh login shell still has a different environment”. Expect Controlled login and interactive tests show the required PATH in both intended contexts. This question instead requires “Both blank and spaced test strings lead to the documented conditional branches”.

This would be the main explanation for An administrator wants new application messages to enter the systemd journal without creating a custom log file. It does not account for A heavily used server has oversized systemd journals and must reclaim space according to policy.

That statement explains another situation: A responder mounts a failed server's disk and needs its saved journal without booting it. The current observation instead depends on journalctl vacuum operations remove archived journal data according to the chosen threshold.

This would be the main explanation for A node lacks a full mail transport service but a monitoring task assumes local mail delivery. It does not account for A heavily used server has oversized systemd journals and must reclaim space according to policy.

This command or configuration addresses a different case: A workstation needs a human-readable alias for a private IP without configuring an external DNS zone. Here, The name service switch determines how host lookups combine files and DNS, so the targeted action is Check and adjust the hosts database order in /etc/nsswitch.conf.

This alternative addresses the separate case “In an LPIC-1 102-500 administration task, A test host uses 255.255.255.0 but another host in the same VLAN uses 255.255.0.0”. The appropriate operation is Normalize the intended IPv4 prefixes and verify routing and broadcast behavior. For the stated problem, “Check and adjust the hosts database order in /etc/nsswitch.conf” addresses the central condition.

It fails to address the actual requirement, An operator wants file-based host mappings to be consulted before DNS on one Linux host. The needed change is Check and adjust the hosts database order in /etc/nsswitch.conf; verify A controlled duplicate name resolves from /etc/hosts when the order specifies files first.

This option serves the scenario “A user sets LC_ALL for a one-off task and then wonders why LC_NUMERIC no longer controls decimals”. The main exposure is Global override can silently defeat individual localization choices. The present scenario is distinguished by “Using usermod -G without append can silently remove existing group access”.

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”. Leaving the issue can cause Reading only supplementary /etc/group entries can misreport effective group membership. The deciding requirement here is “Using usermod -G without append can silently remove existing group access”.

The stated concern is possible elsewhere, but the facts here specifically imply Using usermod -G without append can silently remove existing group access.

That outcome fits another condition, An administrator needs to see current CUPS printer status, destinations and pending jobs, rather than the current one.

The option would apply to “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. The present scenario is distinguished by “Clearing the entire queue can cancel other users' legitimate documents”.

It is not the most direct failure mode. The relevant mechanism is CUPS tracks jobs by queue and identifier so a single job can be removed, which risks Clearing the entire queue can cancel other users' legitimate documents.

The option would apply to “A technician edits /etc/resolv.conf directly but NetworkManager replaces it on reconnect”. Verify that A reconnect retains the intended resolver and DNS queries succeed. This question instead requires “A reconnect test selects only the approved corporate SSID automatically”.

The related but distinct situation is “A DHCP-enabled workstation needs to switch to a managed static IPv4 address”. The best evidence is A reconnect receives the exact approved static information without DHCP changes. For the stated problem, “A reconnect test selects only the approved corporate SSID automatically” addresses the central condition.

This option serves the scenario “A security review confuses TCP's reliable ordered stream with UDP's datagram semantics”. Expect A controlled protocol test illustrates the intended connection and datagram behavior. The present scenario is distinguished by “A reconnect test selects only the approved corporate SSID automatically”.