LPI 102-500 Bundle

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.

This alternative addresses the separate case “An administrator wants new application messages to enter the systemd journal without creating a custom log file”. The main exposure is Relying on unsupervised files can fragment centralized service diagnostics. For the stated problem, “Unread local service mail can conceal unattended job failures” addresses the central condition.

The option would apply to “A Linux server must deliver mail addressed to root to an on-call administrator”. The main exposure is Leaving root mail unattended can hide security and job-failure alerts. The present scenario is distinguished by “Unread local service mail can conceal unattended job failures”.

The case is most directly exposed to Unread local service mail can conceal unattended job failures; the alternative describes a different operational risk.

The alternative can apply elsewhere, but nmap can identify reachable exposed ports when used within authorized test scope is the governing fact here; test by checking The scan report lists known and unexpected ports on the intended host only.

This option serves the scenario “An old host uses xinetd to launch a service that is no longer allowed”. This behavior is explained by xinetd can start daemons on demand through its own configuration. The present scenario is distinguished by “nmap can identify reachable exposed ports when used within authorized test scope”.

This would be the main explanation for A user account must force a password reset on next login after credential rotation. It does not account for A scanner is approved to enumerate open TCP ports on the organization's own development host.

That danger is associated more closely with A VM's clock drifts despite a running NTP daemon because it cannot reach its upstream reference. Here the primary exposure is Local RTC interpretation changes can shift scheduled and logged event times.

That danger is associated more closely with A Linux host keeps accurate software time but its hardware RTC is configured to a different local timezone. Here the primary exposure is Local RTC interpretation changes can shift scheduled and logged event times.

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 Local RTC interpretation changes can shift scheduled and logged event times.

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. The present scenario is distinguished by “Host-key checking is a core defense against connecting to impersonating servers”.

This would be the main explanation for A service listens on all network interfaces though only local clients should use it. It does not account for An SSH server rotates host keys but clients are told to disable strict host checking permanently.

The related but distinct situation is “A server is reinstalled and clients receive a changed SSH host-key warning”. The governing principle is SSH host keys authenticate the server and a changed key may indicate compromise. For the stated problem, “Host-key checking is a core defense against connecting to impersonating servers” addresses the central condition.

It is not the most direct failure mode. The relevant mechanism is Shadow password storage restricts access to credential hashes beyond general account metadata, which risks Moving hashes into broadly readable passwd files increases offline cracking exposure.

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 “Moving hashes into broadly readable passwd files increases offline cracking exposure”.

That outcome fits another condition, A system administrator switches from a user account to root and wants an audit trail of delegated commands, rather than the current one.

It fails to address the actual requirement, A laptop must join a secured Wi-Fi network via NetworkManager from the command line. The needed change is Use nmcli to configure the Wi-Fi connection profile with approved credentials; verify nmcli shows an active authorized Wi-Fi connection after reboot.

The alternative fits An engineer updates a NetworkManager connection but only the stored profile changes. The reported issue instead calls for Use nmcli to configure the Wi-Fi connection profile with approved credentials, as NetworkManager manages wireless profiles including SSID and authentication settings.

This command or configuration addresses a different case: A technician edits /etc/resolv.conf directly but NetworkManager replaces it on reconnect. Here, NetworkManager manages wireless profiles including SSID and authentication settings, so the targeted action is Use nmcli to configure the Wi-Fi connection profile with approved credentials.

That statement explains another situation: An administrator wants new application messages to enter the systemd journal without creating a custom log file. The current observation instead depends on Systemd journals can retain records across distinct system boots.

That statement explains another situation: A security reviewer wants to investigate only error-priority journal entries for yesterday. The current observation instead depends on Systemd journals can retain records across distinct system boots.

The option would apply to “A service needs the current timestamp as ISO text for an audit record”. This behavior is explained by The date utility formats system time and can render an unambiguous offset-bearing timestamp. The present scenario is distinguished by “Systemd journals can retain records across distinct system boots”.

This option serves the scenario “A host cannot reach a DNS server because its IPv4 interface has an incorrect subnet mask”. The appropriate operation is Compare ip addr and ip route data with the intended subnet design. The present scenario is distinguished by “Normalize the intended IPv4 prefixes and verify routing and broadcast behavior”.

It fails to address the actual requirement, A test host uses 255.255.255.0 but another host in the same VLAN uses 255.255.0.0. The needed change is Normalize the intended IPv4 prefixes and verify routing and broadcast behavior; verify Both hosts resolve the same intended local subnet and communicate through correct routes.

That option does not correct the stated dependency. In this case, Inconsistent subnet masks cause peers to disagree about which destinations are on-link; implement Normalize the intended IPv4 prefixes and verify routing and broadcast behavior and check Both hosts resolve the same intended local subnet and communicate through correct routes.

That danger is associated more closely with A network daemon is not required but systemd starts it through socket activation after service disable. Here the primary exposure is Leaving a compromised password active allows continued unauthorized authentication.

The stated concern is possible elsewhere, but the facts here specifically imply Leaving a compromised password active allows continued unauthorized authentication.

The case is most directly exposed to Leaving a compromised password active allows continued unauthorized authentication; the alternative describes a different operational risk.

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”.