LPI 102-500 Bundle

The required verification is timedatectl and date show the intended offset and a consistent instant, not a result meant for A deployment parser depends on English month names while a server's locale uses translated names.

This option serves the scenario “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. The present scenario is distinguished by “timedatectl and date show the intended offset and a consistent instant”.

That observation may validate A server's locale must support accented names and a Unicode-based application, but it does not establish that timedatectl and date show the intended offset and a consistent instant for the current case.

The case is most directly exposed to Using /bin/sh for Bash-only syntax can fail on dash or another POSIX shell; the alternative describes a different operational risk.

The case is most directly exposed to Using /bin/sh for Bash-only syntax can fail on dash or another POSIX shell; the alternative describes a different operational risk.

That danger is associated more closely with An interactive Bash alias is available locally but missing in a noninteractive cron task. Here the primary exposure is Using /bin/sh for Bash-only syntax can fail on dash or another POSIX shell.

The proposed check does not prove the intended behavior. A directly relevant test must show The approved time client reaches the NTP server on UDP 123.

The required verification is The approved time client reaches the NTP server on UDP 123, not a result meant for A service uses TCP 636 and a firewall review labels it plain LDAP on port 389.

The option would apply to “A developer assumes HTTPS normally uses TCP port 80 like unencrypted HTTP”. The best evidence is A connection to the approved HTTPS endpoint succeeds on TCP 443. This question instead requires “The approved time client reaches the NTP server on UDP 123”.

The case is most directly exposed to Manually jumping time without fixing NTP can produce recurring drift; the alternative describes a different operational risk.

The related but distinct situation is “An operator searches for service failures but the journal shows previous boots mixed with today's records”. The main exposure is Mixing boots can produce a false sequence of unrelated failures. The deciding requirement here is “Manually jumping time without fixing NTP can produce recurring drift”.

This option serves the scenario “A host's RTC was changed externally and the OS must read the known UTC hardware time”. The most direct risk is Unreviewed writes between software and hardware clocks can make drift worse. This question instead requires “Manually jumping time without fixing NTP can produce recurring drift”.

The option would apply to “An X11 program launches on the server instead of appearing on an authorized remote workstation”. The relevant Linux mechanism is X11 clients use DISPLAY to choose an X server and need authorization to connect. This question instead requires “Wayland and X11 use different compositing and client architecture”.

That statement explains another situation: A GUI tool works under a user's desktop but fails when launched from a root shell without DISPLAY. The current observation instead depends on Wayland and X11 use different compositing and client architecture.

This would be the main explanation for A support engineer expects RDP to be identical to VNC when accessing a Linux desktop remotely. It does not account for An operator assumes every graphical Linux deployment must use Xorg even though a Wayland compositor is active.

The alternative fits A Linux host can ping its gateway but cannot reach the Internet because no default route exists. The reported issue instead calls for Inspect /etc/nsswitch.conf host lookup order and validate getent hosts, as NSS controls whether files or DNS are consulted first for hostnames.

Although that change may be valid elsewhere, it responds to A user can reach a web service by IP but not by hostname and suspects DNS, not to this system state. The relevant fix is Inspect /etc/nsswitch.conf host lookup order and validate getent hosts.

This command or configuration addresses a different case: A program resolves a name differently than dig because local NSS mappings override DNS. Here, NSS controls whether files or DNS are consulted first for hostnames, so the targeted action is Inspect /etc/nsswitch.conf host lookup order and validate getent hosts.

This option serves the scenario “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. The present scenario is distinguished by “The name service switch determines how host lookups combine files and DNS”.

The option would apply to “A system using systemd-resolved shows generated /etc/resolv.conf and an administrator edits it persistently”. The governing principle is Generated resolver files may be rewritten by the active network-resolver service. This question instead requires “The name service switch determines how host lookups combine files and DNS”.

The related but distinct situation is “A user edits /etc/hostname to rename the system but name resolution fails for the new hostname”. The relevant Linux mechanism is Setting the host identity is separate from resolving that name into an address. For the stated problem, “The name service switch determines how host lookups combine files and DNS” addresses the central condition.

It fails to address the actual requirement, A mail alias is added to /etc/aliases but messages still go to the old address. The needed change is Run newaliases or the supported MTA alias-map rebuild procedure; verify A new test message resolves the alias to the updated address.

The related but distinct situation is “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 “Run newaliases or the supported MTA alias-map rebuild procedure”.

The alternative fits An administrator wants new application messages to enter the systemd journal without creating a custom log file. The reported issue instead calls for Run newaliases or the supported MTA alias-map rebuild procedure, as Alias source changes may require regeneration of the lookup database.

This would be the main explanation for A GnuPG operator must distinguish encryption from a detached signature when distributing policy files. It does not account for A system administrator switches from a user account to root and wants an audit trail of delegated commands.

This option serves the scenario “An administrator edits /etc/sudoers directly and syntax errors block future privilege escalation”. The governing principle is visudo checks sudoers syntax and guards against unsafe concurrent edits. The present scenario is distinguished by “sudo supports command-level authorization and attributable privileged execution”.

That statement explains another situation: A contractor should be able to restart one service without receiving unrestricted root shell privileges. The current observation instead depends on sudo supports command-level authorization and attributable privileged execution.

A passing result on that unrelated check cannot certify the present correction; require The permitted client connects and the disallowed client is rejected on the test system.

This would test another scenario: A scanner is approved to enumerate open TCP ports on the organization's own development host. Here the acceptance evidence is The permitted client connects and the disallowed client is rejected on the test system.

That observation may validate A server permits interactive authentication for accounts during scheduled emergency lockout, but it does not establish that The permitted client connects and the disallowed client is rejected on the test system for the current case.

This option serves the scenario “A mail alias is added to /etc/aliases but messages still go to the old address”. The main exposure is Editing a text alias alone may leave the MTA using stale routing data. The present scenario is distinguished by “A running chronyd process alone does not prove its clock is synchronized”.

The option would apply to “An operator changes the visible timezone using TZ but expects the hardware RTC bytes to change”. The most direct risk is Conflating display timezone with clock state can cause needless clock corrections. This question instead requires “A running chronyd process alone does not prove its clock is synchronized”.

The related but distinct situation is “A script requires a fixed global time reference and must not depend on the user's configured TZ”. The most direct risk is A locale-dependent timestamp can be misinterpreted by downstream automation. For the stated problem, “A running chronyd process alone does not prove its clock is synchronized” addresses the central condition.