LPI 102-500 Bundle

This option serves the scenario “A reporting script displays decimals with commas after an administrator changes regional settings”. The governing principle is Locale numeric category can change decimal punctuation and parsing expectations. The present scenario is distinguished by “LANG supplies a default locale while individual LC_* variables can override categories”.

The option would apply to “A weekly snapshot should run automatically after maintenance but an offline machine missed its scheduled window”. The governing principle is A persistent calendar timer can catch up a missed occurrence after a host returns. This question instead requires “LANG supplies a default locale while individual LC_* variables can override categories”.

That statement explains another situation: A user sets LC_ALL for a one-off task and then wonders why LC_NUMERIC no longer controls decimals. The current observation instead depends on LANG supplies a default locale while individual LC_* variables can override categories.

The alternative fits An operator changes PATH in one terminal but new child shells still use the old search path. The reported issue instead calls for Connect the commands with the shell OR-OR operator or an equivalent test of the previous exit code, as The shell executes the right side of OR-OR when the left command fails.

The alternative fits A script schedules an alert if validation fails but the next command overwrites the exit status before checking it. The reported issue instead calls for Connect the commands with the shell OR-OR operator or an equivalent test of the previous exit code, as The shell executes the right side of OR-OR when the left command fails.

This command or configuration addresses a different case: A maintenance script captures the literal text $(hostname) instead of the machine name. Here, The shell executes the right side of OR-OR when the left command fails, so the targeted action is Connect the commands with the shell OR-OR operator or an equivalent test of the previous exit code.

The required verification is ip route get for the office subnet selects the intended internal next hop, not a result meant for A Linux host can ping its gateway but cannot reach the Internet because no default route exists.

A passing result on that unrelated check cannot certify the present correction; require ip route get for the office subnet selects the intended internal next hop.

This option serves the scenario “A host has two default routes and traffic unexpectedly exits the wrong network interface”. The conclusive result is ip route get for the destination reports the approved outgoing interface. The present scenario is distinguished by “ip route get for the office subnet selects the intended internal next hop”.

The related but distinct situation is “A support script uses the sendmail-compatible interface on a host running Postfix”. The governing principle is Postfix and other MTAs can expose sendmail-compatible submission commands. The deciding requirement here is “Several MTAs implement compatible submission interfaces with different service backends”.

That statement explains another situation: A legacy application uses lpr and lpq but the host now uses CUPS. The current observation instead depends on Several MTAs implement compatible submission interfaces with different service backends.

The option would apply to “A service account should not receive diagnostic mail at an unmonitored local mailbox”. Here, Service email aliases allow local notifications to reach responsible humans. The present scenario is distinguished by “Several MTAs implement compatible submission interfaces with different service backends”.

It fails to address the actual requirement, A firewall rule permits port 53 only over TCP and small DNS queries work intermittently. The needed change is Allow the required DNS traffic over UDP and TCP according to the environment; verify Both appropriate UDP and TCP DNS tests succeed under the approved policy.

The alternative fits A developer assumes HTTPS normally uses TCP port 80 like unencrypted HTTP. The reported issue instead calls for Allow the required DNS traffic over UDP and TCP according to the environment, as DNS commonly uses UDP for queries and TCP for larger responses and zone transfers.

Although that change may be valid elsewhere, it responds to A security review confuses TCP's reliable ordered stream with UDP's datagram semantics, not to this system state. The relevant fix is Allow the required DNS traffic over UDP and TCP according to the environment.

The proposed principle does not identify the crucial dependency in this case: NSS controls whether files or DNS are consulted first for hostnames.

The option would apply to “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. The present scenario is distinguished by “NSS controls whether files or DNS are consulted first for hostnames”.

This option serves the scenario “A security reviewer needs to query a specific DNS server rather than whichever resolver the host currently uses”. The governing principle is dig can direct a query at a chosen DNS endpoint for comparative troubleshooting. This question instead requires “NSS controls whether files or DNS are consulted first for hostnames”.

The option would apply to “An administrator needs to see current CUPS printer status, destinations and pending jobs”. Here, lpstat reports print-service state, configured queues and queued work. This question instead requires “Rsyslog rules select messages by facility and priority and route to configured outputs”.

The proposed principle does not identify the crucial dependency in this case: Rsyslog rules select messages by facility and priority and route to configured outputs.

This would be the main explanation for A server sends logs to two separate files because old rsyslog rules and new journald forwarding overlap. It does not account for A daemon sends messages to syslog but urgent alerts are not forwarded to the collector.

Although that change may be valid elsewhere, it responds to A compliance reviewer needs to prove that a GPG-signed release manifest was not altered, not to this system state. The relevant fix is Use a scoped nmap scan only against the authorized target and approved port range.

This command or configuration addresses a different case: A Linux security review needs to find root-owned files with the SUID bit set. Here, nmap can identify reachable exposed ports when used within authorized test scope, so the targeted action is Use a scoped nmap scan only against the authorized target and approved port range.

The option would apply to “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 present scenario is distinguished by “Use a scoped nmap scan only against the authorized target and approved port range”.

This alternative addresses the separate case “A workstation needs a human-readable alias for a private IP without configuring an external DNS zone”. The best evidence is A supported resolver query maps the chosen alias to the intended private address. The deciding requirement here is “Address-classification tests flag private addresses and a documented public address correctly”.

The required verification is Address-classification tests flag private addresses and a documented public address correctly, not a result meant for An administrator assigns the IPv4 address 10.1.1.0 with a /24 mask to a host.

The related but distinct situation is “A mail relay must be permitted through a firewall and an operator confuses SMTP with IMAP”. Verify that The firewall and connectivity tests allow the documented SMTP endpoint only. For the stated problem, “Address-classification tests flag private addresses and a documented public address correctly” addresses the central condition.

This would test another scenario: A host's RTC was changed externally and the OS must read the known UTC hardware time. Here the acceptance evidence is ntpq -p identifies an accepted peer and subsequent offsets fall within tolerance.

This would test another scenario: An administrator needs to see current CUPS printer status, destinations and pending jobs. Here the acceptance evidence is ntpq -p identifies an accepted peer and subsequent offsets fall within tolerance.

The related but distinct situation is “An administrator needs to verify a server's NTP synchronization status under chrony”. Acceptance requires The tracking report shows an accepted synchronized source with bounded offset. The deciding requirement here is “ntpq -p identifies an accepted peer and subsequent offsets fall within tolerance”.

The option would apply to “Two departments agree to rename a Unix group without changing its existing GID”. The relevant Linux mechanism is Group names can change independently of the numerical identifier used by file ownership. This question instead requires “Locale collation rules can change ordering of otherwise identical text input”.

This option serves the scenario “A reporting script displays decimals with commas after an administrator changes regional settings”. The governing principle is Locale numeric category can change decimal punctuation and parsing expectations. The present scenario is distinguished by “Locale collation rules can change ordering of otherwise identical text input”.

This alternative addresses the separate case “A deployment parser depends on English month names while a server's locale uses translated names”. Here, Locale settings can change date output and text formatting in command-line tools. The deciding requirement here is “Locale collation rules can change ordering of otherwise identical text input”.