LPI 102-500 Bundle

This alternative addresses the separate case “After reboot, journalctl --list-boots shows only the current boot and auditors require previous boot history”. Expect After a controlled restart journalctl --list-boots includes the earlier boot. The deciding requirement here is “A simulated timezone boundary preserves the correct UTC instant after reboot”.

That observation may validate A Linux host keeps accurate software time but its hardware RTC is configured to a different local timezone, but it does not establish that A simulated timezone boundary preserves the correct UTC instant after reboot for the current case.

This would test another scenario: A script requires a fixed global time reference and must not depend on the user's configured TZ. Here the acceptance evidence is A simulated timezone boundary preserves the correct UTC instant after reboot.

That statement explains another situation: A user wants to print a PDF to a named printer rather than the system default. The current observation instead depends on lpstat reports print-service state, configured queues and queued work.

The proposed principle does not identify the crucial dependency in this case: lpstat reports print-service state, configured queues and queued work.

This would be the main explanation for Printing stops after an operator disables a CUPS queue during maintenance. It does not account for An administrator needs to see current CUPS printer status, destinations and pending jobs.

It fails to address the actual requirement, A system administrator switches from a user account to root and wants an audit trail of delegated commands. The needed change is Use policy-controlled sudo rather than sharing the root password or routinely invoking su; verify The audit associates each approved privileged action with its original user.

The alternative fits A team must encrypt a confidential file for one specific recipient using GnuPG. The reported issue instead calls for Use policy-controlled sudo rather than sharing the root password or routinely invoking su, as sudo supports command-level authorization and attributable privileged execution.

This alternative addresses the separate case “An administrator sees a suspicious process holding an apparently deleted log file open”. The safest fitting response is Use lsof or fuser to identify the process retaining the file handle. The deciding requirement here is “Use policy-controlled sudo rather than sharing the root password or routinely invoking su”.

The related but distinct situation is “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 authorized application displays locally through the SSH session without xhost +”.

This would test another scenario: A host still exposes Telnet but policy allows only encrypted remote administration. Here the acceptance evidence is The authorized application displays locally through the SSH session without xhost +.

The option would apply to “A workstation user types an SSH private-key passphrase repeatedly for several short sessions”. Expect Subsequent authorized SSH connections use the agent while the key remains protected. The present scenario is distinguished by “The authorized application displays locally through the SSH session without xhost +”.

This option serves the scenario “A hardening scan finds an unfamiliar TCP listener on a production Linux host”. Expect The audit identifies the exact unexpected process and its listening socket. The present scenario is distinguished by “Recipients can read the unchanged policy and verify its detached signature”.

The option would apply to “A compliance reviewer needs to prove that a GPG-signed release manifest was not altered”. Verify that The valid signature passes for the unmodified file and fails after a test alteration. This question instead requires “Recipients can read the unchanged policy and verify its detached signature”.

The related but distinct situation is “An operator stores the private SSH identity in a world-readable shared directory”. The best evidence is An unprivileged user cannot read the key and the owner can authenticate normally. For the stated problem, “Recipients can read the unchanged policy and verify its detached signature” addresses the central condition.

The option would apply to “A host cannot reach a DNS server because its IPv4 interface has an incorrect subnet mask”. The most direct risk is A wrong subnet mask can produce invalid neighbor requests or missing gateway routing. The present scenario is distinguished by “A wrong specific route can cause unreachable local services or packet leakage”.

The case is most directly exposed to A wrong specific route can cause unreachable local services or packet leakage; the alternative describes a different operational risk.

That danger is associated more closely with A host has two default routes and traffic unexpectedly exits the wrong network interface. Here the primary exposure is A wrong specific route can cause unreachable local services or packet leakage.

The alternative fits A central rsyslog host should accept events from a known remote client while rejecting unexpected sources. The reported issue instead calls for Configure the user's ~/.forward file with the correct recipient, as Traditional local MTAs support per-user forwarding via a .forward file.

That option does not correct the stated dependency. In this case, Traditional local MTAs support per-user forwarding via a .forward file; implement Configure the user's ~/.forward file with the correct recipient and check A test message to the local username arrives in the authorized mailbox.

This alternative addresses the separate case “In an LPIC-1 102-500 administration task, A Linux server must deliver mail addressed to root to an on-call administrator”. The safest fitting response is Configure the system mail alias for root and rebuild the aliases database with newaliases. The deciding requirement here is “Configure the user's ~/.forward file with the correct recipient”.

That statement explains another situation: A host uses a /26 mask but a technician assumes every subnet has 254 usable addresses. The current observation instead depends on systemd-networkd and NetworkManager are separate host network configuration systems.

This option serves the scenario “A system has two NetworkManager profiles on one NIC and activates the wrong address after restart”. This behavior is explained by NetworkManager profile selection can affect which saved configuration becomes active. This question instead requires “systemd-networkd and NetworkManager are separate host network configuration systems”.

The alternative can apply elsewhere, but systemd-networkd and NetworkManager are separate host network configuration systems is the governing fact here; test by checking The active interface receives the intended settings after applying the relevant .network unit.

It fails to address the actual requirement, A user edits /etc/hostname to rename the system but name resolution fails for the new hostname. The needed change is Update the related local host mapping or DNS configuration as appropriate; verify hostnamectl and getent hosts show a consistent intended name and mapping.

This command or configuration addresses a different case: A server must be assigned a persistent IPv6 address but its only configuration is an ip -6 addr add command. Here, Setting the host identity is separate from resolving that name into an address, so the targeted action is Update the related local host mapping or DNS configuration as appropriate.

The related but distinct situation is “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. For the stated problem, “Update the related local host mapping or DNS configuration as appropriate” addresses the central condition.

This alternative addresses the separate case “A program resolves a name differently than dig because local NSS mappings override DNS”. Here, Applications may use NSS files and services, while dig queries DNS records directly. For the stated problem, “dig can direct a query at a chosen DNS endpoint for comparative troubleshooting” addresses the central condition.

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. The present scenario is distinguished by “dig can direct a query at a chosen DNS endpoint for comparative troubleshooting”.

The related but distinct situation is “A resolver searches external DNS before local /etc/hosts and ignores a deliberate test alias”. The decisive distinction is NSS controls whether files or DNS are consulted first for hostnames. The deciding requirement here is “dig can direct a query at a chosen DNS endpoint for comparative troubleshooting”.

The option would apply to “A service's housekeeping must start five minutes after boot and then repeat every hour using systemd”. Acceptance requires systemctl list-timers shows the timer and the service runs after boot and periodically. This question instead requires “systemctl list-timers reflects the revised next activation time”.

The related but distinct situation is “An internationalized application should prefer the locale declared by the operator without forcing every regional category”. Expect locale reports the expected defaults and targeted time or numeric category choices. For the stated problem, “systemctl list-timers reflects the revised next activation time” addresses the central condition.

This option serves the scenario “A scheduled maintenance command writes to stdout but no file is created and the team assumes nothing ran”. Acceptance requires The next test records the job timestamp and exit status in an accessible log. The present scenario is distinguished by “systemctl list-timers reflects the revised next activation time”.