LPI 102-500 Bundle

This option serves the scenario “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 present scenario is distinguished by “The socket table can show listening ports and owning processes when permitted”.

The option would apply to “An IPv6-only server uses ping for an IPv4 literal and mistakenly reports IPv6 routing is broken”. Here, IPv4 and IPv6 use distinct address families and routing tables. This question instead requires “The socket table can show listening ports and owning processes when permitted”.

The alternative can apply elsewhere, but The socket table can show listening ports and owning processes when permitted is the governing fact here; test by checking The suspicious port is mapped to its actual process and approved service state.

The option would apply to “A script expects a simple command-line message to be delivered but its subject line is missing”. Here, The mail user agent constructs a message while the MTA performs its delivery. The present scenario is distinguished by “An MTA can queue outgoing messages when immediate delivery is unavailable”.

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 “An MTA can queue outgoing messages when immediate delivery is unavailable”.

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 command-line mail client reports queued messages and an administrator needs to inspect them.

The case is most directly exposed to Using link-local addressing as globally routable prevents remote connectivity; the alternative describes a different operational risk.

The stated concern is possible elsewhere, but the facts here specifically imply Using link-local addressing as globally routable prevents remote connectivity.

The stated concern is possible elsewhere, but the facts here specifically imply Using link-local addressing as globally routable prevents remote connectivity.

The related but distinct situation is “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 deciding requirement here is “UTF-8 encodes Unicode code points and the selected locale must exist on the host”.

That statement explains another situation: A developer edits a systemd timer file but the system continues following its earlier schedule. The current observation instead depends on UTF-8 encodes Unicode code points and the selected locale must exist on the host.

The option would apply to “An application mixes UTF-8 text with ISO-8859-1 input and produces broken accented characters”. The governing principle is Character encoding describes byte-to-character mapping and differs from locale display selection. The present scenario is distinguished by “UTF-8 encodes Unicode code points and the selected locale must exist on the host”.

This option serves the scenario “A user sets LC_ALL for a one-off task and then wonders why LC_NUMERIC no longer controls decimals”. The main exposure is Global override can silently defeat individual localization choices. The present scenario is distinguished by “Assuming shell profile paths apply to cron can silently skip scheduled backups”.

This alternative addresses the separate case “A weekly snapshot should run automatically after maintenance but an offline machine missed its scheduled window”. Leaving the issue can cause A nonpersistent timer can silently skip work when the host was offline. The deciding requirement here is “Assuming shell profile paths apply to cron can silently skip scheduled backups”.

The stated concern is possible elsewhere, but the facts here specifically imply Assuming shell profile paths apply to cron can silently skip scheduled backups.

That outcome fits another condition, A mail relay must be permitted through a firewall and an operator confuses SMTP with IMAP, rather than the current one.

The option would apply to “A technician must check whether the server can connect to a TCP service on port 443”. The main exposure is A positive ping does not prove the target application listener is available. The present scenario is distinguished by “Successful ping can falsely reassure operators that the SSH daemon is reachable”.

It is not the most direct failure mode. The relevant mechanism is ICMP echo tests network responsiveness but does not establish TCP service reachability, which risks Successful ping can falsely reassure operators that the SSH daemon is reachable.

The stated concern is possible elsewhere, but the facts here specifically imply Mixed prefix assumptions can create asymmetric traffic and ARP failures.

The case is most directly exposed to Mixed prefix assumptions can create asymmetric traffic and ARP failures; the alternative describes a different operational risk.

The stated concern is possible elsewhere, but the facts here specifically imply Mixed prefix assumptions can create asymmetric traffic and ARP failures.

This option serves the scenario “A server in Karachi reports UTC on local console but should display local Pakistan time without changing UTC storage”. Expect timedatectl and date show the intended offset and a consistent instant. This question instead requires “A new user and a corrected existing user each receive the vetted profile”.

The proposed check does not prove the intended behavior. A directly relevant test must show A new user and a corrected existing user each receive the vetted profile.

The option would apply to “An employee password must be changed without directly editing hashed fields in /etc/shadow”. Expect The user authenticates with the new password and the old one is rejected. The present scenario is distinguished by “A new user and a corrected existing user each receive the vetted profile”.

It is less specific than at schedules one-off tasks while cron is designed for recurring execution, which directly explains the scenario and supports Submit a one-time job using at and verify it appears in atq.

This alternative addresses the separate case “An administrator must run log cleanup at 02:30 every weekday”. The governing principle is Cron's five scheduling fields select the times at which recurring jobs execute. The deciding requirement here is “at schedules one-off tasks while cron is designed for recurring execution”.

The option would apply to “An audit requires a password change every ninety days for a specific local user”. The decisive distinction is Password aging policy is maintained separately from the plaintext password itself. This question instead requires “at schedules one-off tasks while cron is designed for recurring execution”.

This alternative addresses the separate case “An administrator must run log cleanup at 02:30 every weekday”. Leaving the issue can cause Confusing month and weekday fields can run destructive cleanup at the wrong time. For the stated problem, “Changing the hardware clock to local time unnecessarily can destabilize timekeeping” addresses the central condition.

The stated concern is possible elsewhere, but the facts here specifically imply Changing the hardware clock to local time unnecessarily can destabilize timekeeping.

This option serves the scenario “A user sets LC_ALL for a one-off task and then wonders why LC_NUMERIC no longer controls decimals”. The main exposure is Global override can silently defeat individual localization choices. This question instead requires “Changing the hardware clock to local time unnecessarily can destabilize timekeeping”.

That danger is associated more closely with A laptop has an active Wi-Fi connection but should prevent automatic connection to an untrusted network. Here the primary exposure is Manual changes to generated resolver files can be lost unexpectedly.

That outcome fits another condition, A server must be assigned a persistent IPv6 address but its only configuration is an ip -6 addr add command, rather than the current one.

That outcome fits another condition, A program resolves a name differently than dig because local NSS mappings override DNS, rather than the current one.