LPI 102-500 Bundle

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

The related but distinct situation is “An administrator needs to inspect only exported variables passed to spawned processes”. The governing principle is env displays the process environment whereas set can include shell-local variables. The deciding requirement here is “Sourcing executes shell commands in the current environment rather than a separate process”.

This alternative addresses the separate case “An operator changes PATH in one terminal but new child shells still use the old search path”. The decisive distinction is Child processes inherit exported environment variables rather than arbitrary shell variables. For the stated problem, “Sourcing executes shell commands in the current environment rather than a separate process” addresses the central condition.

The proposed principle does not identify the crucial dependency in this case: Sourcing executes shell commands in the current environment rather than a separate process.

This option serves the scenario “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 “The mail utility depends on a functioning transport path to deliver notifications”.

This would be the main explanation for A user wants to print a PDF to a named printer rather than the system default. It does not account for A node lacks a full mail transport service but a monitoring task assumes local mail delivery.

The option would apply to “A Linux server must deliver mail addressed to root to an on-call administrator”. This behavior is explained by Local mail aliases redirect a recipient without modifying the sender's mail command. This question instead requires “The mail utility depends on a functioning transport path to deliver notifications”.

This alternative addresses the separate case “A network administrator changes the server hostname only with the hostname command and it resets”. Here, Runtime hostnames and persistent system identity can be configured separately. For the stated problem, “Connection profiles can be enabled for manual use without autojoining untrusted SSIDs” addresses the central condition.

That statement explains another situation: A network interface shows no IP address after a configuration change. The current observation instead depends on Connection profiles can be enabled for manual use without autojoining untrusted SSIDs.

The related but distinct situation is “A technician edits /etc/resolv.conf directly but NetworkManager replaces it on reconnect”. The decisive distinction is Network-management services can regenerate resolv.conf from persistent connection settings. The deciding requirement here is “Connection profiles can be enabled for manual use without autojoining untrusted SSIDs”.

The option would apply to “A compliance auditor must demonstrate that normal users cannot read /etc/shadow”. The conclusive result is An unprivileged read fails and the authorized account database still operates. This question instead requires “Ordinary users can read account names without accessing shadow password hashes”.

This would test another scenario: A GnuPG operator must distinguish encryption from a detached signature when distributing policy files. Here the acceptance evidence is Ordinary users can read account names without accessing shadow password hashes.

That observation may validate A server permits interactive authentication for accounts during scheduled emergency lockout, but it does not establish that Ordinary users can read account names without accessing shadow password hashes for the current case.

Although that change may be valid elsewhere, it responds to A GUI tool works under a user's desktop but fails when launched from a root shell without DISPLAY, not to this system state. The relevant fix is Configure targeted X authentication with xauth instead of disabling access controls globally.

That option does not correct the stated dependency. In this case, xhost + broadly relaxes X server connection restrictions and is unsafe on shared systems; implement Configure targeted X authentication with xauth instead of disabling access controls globally and check The authorized user opens the X application while an unrelated network client is refused.

The alternative fits An X11 program launches on the server instead of appearing on an authorized remote workstation. The reported issue instead calls for Configure targeted X authentication with xauth instead of disabling access controls globally, as xhost + broadly relaxes X server connection restrictions and is unsafe on shared systems.

This would test another scenario: Two departments agree to rename a Unix group without changing its existing GID. Here the acceptance evidence is id shows the expected primary GID and the previously authorized supplementary groups.

This alternative addresses the separate case “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. The deciding requirement here is “id shows the expected primary GID and the previously authorized supplementary groups”.

The related but distinct situation is “An audit requires a password change every ninety days for a specific local user”. The conclusive result is chage -l reports the expected maximum age and expiry behavior. For the stated problem, “id shows the expected primary GID and the previously authorized supplementary groups” addresses the central condition.

The proposed check does not prove the intended behavior. A directly relevant test must show The correct profile is active after reboot with the expected address and route.

The related but distinct situation is “A server in 192.168.20.0/24 must communicate with a host in 192.168.21.0/24”. The conclusive result is A route lookup selects the expected next hop and end-to-end ping succeeds. The deciding requirement here is “The correct profile is active after reboot with the expected address and route”.

A passing result on that unrelated check cannot certify the present correction; require The correct profile is active after reboot with the expected address and route.

The option would apply to “A host still exposes Telnet but policy allows only encrypted remote administration”. The governing principle is Unneeded plaintext network login services expand authentication and interception risks. This question instead requires “Disabling unused network services reduces attack surface beyond firewall-only masking”.

This option serves the scenario “An operator stores the private SSH identity in a world-readable shared directory”. The decisive distinction is SSH private keys must remain secret to preserve authentication assurance. The present scenario is distinguished by “Disabling unused network services reduces attack surface beyond firewall-only masking”.

This alternative addresses the separate case “A legacy host consults /etc/hosts.allow but a replacement server uses a modern daemon without wrapper support”. This behavior is explained by TCP wrapper files are not universal network firewalls and many modern services ignore them. The deciding requirement here is “Disabling unused network services reduces attack surface beyond firewall-only masking”.

It is not the most direct failure mode. The relevant mechanism is Login and nonlogin interactive shells can load different initialization files, which risks Editing the wrong startup file creates settings that work only in one terminal type.

The stated concern is possible elsewhere, but the facts here specifically imply Editing the wrong startup file creates settings that work only in one terminal type.

The case is most directly exposed to Editing the wrong startup file creates settings that work only in one terminal type; the alternative describes a different operational risk.

This option serves the scenario “A monthly security scan requires a reminder on the first day at midnight and a separate weekly report”. Here, Multiple distinct recurrence requirements should not be compressed into a misleading single expression. The present scenario is distinguished by “System crontab entries add a username field not present in normal user crontabs”.

This would be the main explanation for An operator needs to list exactly the cron jobs for a specified local account. It does not account for An hourly job is moved from a user crontab into /etc/crontab and fails to execute.

The alternative can apply elsewhere, but System crontab entries add a username field not present in normal user crontabs is the governing fact here; test by checking The entry runs under the intended identity in a controlled test.