LPI 102-500 Bundle

The option would apply to “An operator writes backup.sh with Bash arrays but invokes it through sh on a non-Bash system”. The most direct risk is Using /bin/sh for Bash-only syntax can fail on dash or another POSIX shell. This question instead requires “An incorrect && chain can run fallback only on success”.

The case is most directly exposed to An incorrect && chain can run fallback only on success; the alternative describes a different operational risk.

This option serves the scenario “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. The present scenario is distinguished by “An incorrect && chain can run fallback only on success”.

The alternative can apply elsewhere, but A variable assignment preceding a command can affect just that command's environment is the governing fact here; test by checking The program prints stable C-locale output while later commands retain their original locale.

This alternative addresses the separate case “A new analyst logs in through SSH but a custom tool in /opt/tools is not found by name”. Here, An exported PATH controls command lookup for processes launched from that shell. For the stated problem, “A variable assignment preceding a command can affect just that command's environment” addresses the central condition.

The option would apply to “A worker must make a profile variable available to an application started from the same login”. The relevant Linux mechanism is Export marks a shell variable for inheritance in the environment of children. The present scenario is distinguished by “A variable assignment preceding a command can affect just that command's environment”.

The alternative can apply elsewhere, but A persistent calendar timer can catch up a missed occurrence after a host returns is the governing fact here; test by checking The snapshot executes after a controlled missed-schedule restart under the documented policy.

That statement explains another situation: An administrator needs to remove a pending one-time job identified in the at queue. The current observation instead depends on A persistent calendar timer can catch up a missed occurrence after a host returns.

The related but distinct situation is “An internationalized application should prefer the locale declared by the operator without forcing every regional category”. Here, LANG supplies a default locale while individual LC_* variables can override categories. For the stated problem, “A persistent calendar timer can catch up a missed occurrence after a host returns” addresses the central condition.

This alternative addresses the separate case “An hourly job is moved from a user crontab into /etc/crontab and fails to execute”. The best evidence is The entry runs under the intended identity in a controlled test. For the stated problem, “The same fixture sorts in identical order under the script's declared locale” addresses the central condition.

That observation may validate A server's locale must support accented names and a Unicode-based application, but it does not establish that The same fixture sorts in identical order under the script's declared locale for the current case.

This option serves the scenario “A reporting script displays decimals with commas after an administrator changes regional settings”. The conclusive result is A test reports a decimal point in the machine-readable export while UI locale remains intact. This question instead requires “The same fixture sorts in identical order under the script's declared locale”.

The option would apply to “In an LPIC-1 102-500 administration task, A system using systemd-resolved shows generated /etc/resolv.conf and an administrator edits it persistently”. The safest fitting response is Configure the upstream DNS through the responsible resolver or network manager. This question instead requires “Identify the active network manager and edit the correct systemd-networkd .network unit”.

That option does not correct the stated dependency. In this case, systemd-networkd and NetworkManager are separate host network configuration systems; implement Identify the active network manager and edit the correct systemd-networkd .network unit and check The active interface receives the intended settings after applying the relevant .network unit.

That option does not correct the stated dependency. In this case, systemd-networkd and NetworkManager are separate host network configuration systems; implement Identify the active network manager and edit the correct systemd-networkd .network unit and check The active interface receives the intended settings after applying the relevant .network unit.

It fails to address the actual requirement, A developer wants to revoke an exposed GnuPG certificate and communicate the revocation. The needed change is Generate or use an appropriate revocation certificate and publish it through the trusted channel; verify A refreshed key lookup recognizes the revocation and rejects use of the compromised key.

This command or configuration addresses a different case: A team must encrypt a confidential file for one specific recipient using GnuPG. Here, Revocation informs relying parties that the old key should no longer be trusted, so the targeted action is Generate or use an appropriate revocation certificate and publish it through the trusted channel.

The option would apply to “A user must authenticate to an SSH host without typing a password for an approved automation task”. The safest fitting response is Generate an appropriate SSH keypair and install its public key in the authorized account. The present scenario is distinguished by “Generate or use an appropriate revocation certificate and publish it through the trusted channel”.

This option serves the scenario “An application listens on UDP 123 and a colleague wrongly associates it with SSH”. Here, Well-known service assignments distinguish NTP clock synchronization from SSH login. The present scenario is distinguished by “Well-known service port mappings distinguish encrypted HTTPS from HTTP traffic”.

This alternative addresses the separate case “A service uses TCP 636 and a firewall review labels it plain LDAP on port 389”. The decisive distinction is Different service variants can use separate well-known ports and security behavior. The deciding requirement here is “Well-known service port mappings distinguish encrypted HTTPS from HTTP traffic”.

The related but distinct situation is “A workstation needs a human-readable alias for a private IP without configuring an external DNS zone”. Here, The hosts file provides local mappings considered by standard name service resolution. For the stated problem, “Well-known service port mappings distinguish encrypted HTTPS from HTTP traffic” addresses the central condition.

This alternative addresses the separate case “A user wants to decrypt a GnuPG file received for a different person's key”. The appropriate operation is Use the matching authorized private key and confirm its owner can decrypt. For the stated problem, “Generate an appropriate SSH keypair and install its public key in the authorized account” addresses the central condition.

The alternative fits A developer wants to revoke an exposed GnuPG certificate and communicate the revocation. The reported issue instead calls for Generate an appropriate SSH keypair and install its public key in the authorized account, as SSH public-key authentication uses a private client key and authorized server-side public key.

That option does not correct the stated dependency. In this case, SSH public-key authentication uses a private client key and authorized server-side public key; implement Generate an appropriate SSH keypair and install its public key in the authorized account and check A restricted test login succeeds with the approved key and no shared password.

The option would apply to “A Linux host can ping its gateway but cannot reach the Internet because no default route exists”. The governing principle is Traffic for destinations outside connected prefixes requires a selected route. This question instead requires “An interface can be administratively up while lacking a usable IP configuration”.

The related but distinct situation is “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. For the stated problem, “An interface can be administratively up while lacking a usable IP configuration” addresses the central condition.

This option serves the scenario “A new static IPv4 connection created with nmcli disappears after reboot because it was not saved correctly”. The decisive distinction is Runtime interface changes do not automatically define a persistent connection configuration. The present scenario is distinguished by “An interface can be administratively up while lacking a usable IP configuration”.

Although that change may be valid elsewhere, it responds to A server sends logs to two separate files because old rsyslog rules and new journald forwarding overlap, not to this system state. The relevant fix is Configure persistent journald storage and ensure /var/log/journal is available.

The alternative fits An incident report shows Linux time jumping after daylight saving changes when hardware clock is kept in local time. The reported issue instead calls for Configure persistent journald storage and ensure /var/log/journal is available, as Volatile journal storage may be lost at reboot, whereas persistent storage retains prior boots.

Although that change may be valid elsewhere, it responds to A service's journal uses too much storage even though logrotate handles text logs correctly, not to this system state. The relevant fix is Configure persistent journald storage and ensure /var/log/journal is available.

This option serves the scenario “A Bash function in a profile must be available to the current shell without logging out”. Here, Sourcing executes shell commands in the current environment rather than a separate process. The present scenario is distinguished by “A normally executed script runs in its own process and cannot change its parent's directory”.

The proposed principle does not identify the crucial dependency in this case: A normally executed script runs in its own process and cannot change its parent's directory.

The related but distinct situation is “An automation job needs a temporary locale change without modifying global server defaults”. The relevant Linux mechanism is A variable assignment preceding a command can affect just that command's environment. For the stated problem, “A normally executed script runs in its own process and cannot change its parent's directory” addresses the central condition.