LPI 102-500 Bundle

The option would apply to “A responder mounts a failed server's disk and needs its saved journal without booting it”. Acceptance requires The responder extracts the old boot events from the offline disk safely. This question instead requires “The report contains matching error entries from the requested interval only”.

The required verification is The report contains matching error entries from the requested interval only, not a result meant for A systemd service fails intermittently and an engineer needs logs only for that unit in the current boot.

This option serves the scenario “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 present scenario is distinguished by “The report contains matching error entries from the requested interval only”.

The related but distinct situation is “A newly hired analyst has a Linux account but no home directory or default shell”. The most direct risk is Leaving the home directory absent can prevent profile initialization and normal user work. The deciding requirement here is “Deleting the home as the first step can destroy retained evidence”.

This option serves the scenario “Two departments agree to rename a Unix group without changing its existing GID”. Leaving the issue can cause Deleting and recreating the group with a different ID can orphan shared permissions. This question instead requires “Deleting the home as the first step can destroy retained evidence”.

This alternative addresses the separate case “A developer edits a systemd timer file but the system continues following its earlier schedule”. Leaving the issue can cause Editing a unit without reloading can leave the old schedule active. For the stated problem, “Deleting the home as the first step can destroy retained evidence” addresses the central condition.

The case is most directly exposed to Relying on obsolete wrapper-only controls creates false assurance of network isolation; the alternative describes a different operational risk.

That danger is associated more closely with A scanner is approved to enumerate open TCP ports on the organization's own development host. Here the primary exposure is Relying on obsolete wrapper-only controls creates false assurance of network isolation.

It is not the most direct failure mode. The relevant mechanism is TCP wrapper files are not universal network firewalls and many modern services ignore them, which risks Relying on obsolete wrapper-only controls creates false assurance of network isolation.

This alternative addresses the separate case “A server logs show a large time offset but ntpq reports no selected peer”. Leaving the issue can cause Manually jumping time without fixing NTP can produce recurring drift. For the stated problem, “Continuing unsynchronized time can invalidate TLS and distributed log correlation” addresses the central condition.

That outcome fits another condition, A newly provisioned node should use the shared organizational NTP pool instead of an arbitrary public peer, rather than the current one.

This option serves the scenario “A custom application's logs grow indefinitely because no rotation policy exists”. The most direct risk is Unlimited log growth can exhaust /var storage and disrupt services. This question instead requires “Continuing unsynchronized time can invalidate TLS and distributed log correlation”.

The case is most directly exposed to Changing only an existing administrator's profile will not provision new accounts; the alternative describes a different operational risk.

That outcome fits another condition, A script must run a fallback check only when the primary check exits unsuccessfully, rather than the current one.

The case is most directly exposed to Changing only an existing administrator's profile will not provision new accounts; the alternative describes a different operational risk.

It is not the most direct failure mode. The relevant mechanism is xhost + broadly relaxes X server connection restrictions and is unsafe on shared systems, which risks Open X server access can permit other clients to observe or control the desktop.

The case is most directly exposed to Open X server access can permit other clients to observe or control the desktop; the alternative describes a different operational risk.

The stated concern is possible elsewhere, but the facts here specifically imply Open X server access can permit other clients to observe or control the desktop.

This command or configuration addresses a different case: A responder mounts a failed server's disk and needs its saved journal without booting it. Here, Systemd journals can retain records across distinct system boots, so the targeted action is Specify journalctl -b or select the relevant boot ID when querying logs.

That option does not correct the stated dependency. In this case, Systemd journals can retain records across distinct system boots; implement Specify journalctl -b or select the relevant boot ID when querying logs and check The investigation output corresponds to the known boot that hosted the incident.

The related but distinct situation is “A systemd service fails intermittently and an engineer needs logs only for that unit in the current boot”. The safest fitting response is Use journalctl -b -u service-name to filter the systemd journal. For the stated problem, “Specify journalctl -b or select the relevant boot ID when querying logs” addresses the central condition.

It is not the most direct failure mode. The relevant mechanism is Persistent gateway settings belong to the active network configuration manager, which risks A transient route added only with ip route may vanish after reboot.

That outcome fits another condition, A system using systemd-resolved shows generated /etc/resolv.conf and an administrator edits it persistently, rather than the current one.

This option serves the scenario “A workstation needs a human-readable alias for a private IP without configuring an external DNS zone”. Leaving the issue can cause Editing external DNS unnecessarily may leak internal-only hostnames. This question instead requires “A transient route added only with ip route may vanish after reboot”.

The stated concern is possible elsewhere, but the facts here specifically imply Unquoted shell tests can fail or misinterpret values with whitespace.

The related but distinct situation is “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. For the stated problem, “Unquoted shell tests can fail or misinterpret values with whitespace” addresses the central condition.

The case is most directly exposed to Unquoted shell tests can fail or misinterpret values with whitespace; the alternative describes a different operational risk.

This command or configuration addresses a different case: A shared workstation has a skeleton .bashrc used for new users but an existing account did not receive it. Here, The at access files determine who may submit one-time scheduled work, so the targeted action is Check /etc/at.allow and /etc/at.deny according to the installed at policy.

This command or configuration addresses a different case: An hourly job is moved from a user crontab into /etc/crontab and fails to execute. Here, The at access files determine who may submit one-time scheduled work, so the targeted action is Check /etc/at.allow and /etc/at.deny according to the installed at policy.

This command or configuration addresses a different case: A project account should be allowed to run cron while arbitrary guest accounts are forbidden. Here, The at access files determine who may submit one-time scheduled work, so the targeted action is Check /etc/at.allow and /etc/at.deny according to the installed at policy.

This option serves the scenario “A privileged application account should not have an ordinary interactive login shell”. The governing principle is Special-purpose service accounts need not permit general human logins. The present scenario is distinguished by “Name service switch resolution can include accounts not stored in local passwd files”.

The proposed principle does not identify the crucial dependency in this case: Name service switch resolution can include accounts not stored in local passwd files.

The related but distinct situation is “A support team needs to inspect one user's groups but /etc/group alone seems to omit the primary group”. This behavior is explained by The primary GID is stored in the passwd record and can be resolved through group databases. For the stated problem, “Name service switch resolution can include accounts not stored in local passwd files” addresses the central condition.