LPI 102-500 Bundle

This command or configuration addresses a different case: A user can reach a web service by IP but not by hostname and suspects DNS. Here, Generated resolver files may be rewritten by the active network-resolver service, so the targeted action is Configure the upstream DNS through the responsible resolver or network manager.

Although that change may be valid elsewhere, it responds to A security reviewer needs to query a specific DNS server rather than whichever resolver the host currently uses, not to this system state. The relevant fix is Configure the upstream DNS through the responsible resolver or network manager.

The alternative fits A host uses systemd-networkd, but an engineer repeatedly modifies NetworkManager profiles with no effect. The reported issue instead calls for Configure the upstream DNS through the responsible resolver or network manager, as Generated resolver files may be rewritten by the active network-resolver service.

That danger is associated more closely with An engineer must distinguish a globally routable IPv4 address from RFC1918 private space. Here the primary exposure is Treating different /24 subnets as local can prevent ARP and routing from working.

That outcome fits another condition, A user reports packet loss only toward one remote hop and wants to locate the failing segment, rather than the current one.

The case is most directly exposed to Treating different /24 subnets as local can prevent ARP and routing from working; the alternative describes a different operational risk.

This option serves the scenario “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 “Changing DNS will not fix a process bound to 127.0.0.1 only”.

The case is most directly exposed to Changing DNS will not fix a process bound to 127.0.0.1 only; the alternative describes a different operational risk.

That danger is associated more closely with A Linux host can ping its gateway but cannot reach the Internet because no default route exists. Here the primary exposure is Changing DNS will not fix a process bound to 127.0.0.1 only.

The option would apply to “A Linux host can ping its gateway but cannot reach the Internet because no default route exists”. Acceptance requires ip route get for a public destination shows the proper gateway and traffic succeeds. The present scenario is distinguished by “An IPv6 target responds over the expected IPv6 interface and gateway”.

A passing result on that unrelated check cannot certify the present correction; require An IPv6 target responds over the expected IPv6 interface and gateway.

This option serves the scenario “A network interface shows no IP address after a configuration change”. The best evidence is The corrected interface reports the expected link state and address. This question instead requires “An IPv6 target responds over the expected IPv6 interface and gateway”.

It is less specific than Time synchronization requires a reachable usable reference and a healthy time daemon, which directly explains the scenario and supports Check time-source reachability and configuration in the installed ntpd or chrony service.

This option serves the scenario “A server logs show a large time offset but ntpq reports no selected peer”. This behavior is explained by ntpd cannot maintain a reference without an eligible synchronized upstream peer. The present scenario is distinguished by “Time synchronization requires a reachable usable reference and a healthy time daemon”.

This alternative addresses the separate case “A central rsyslog host should accept events from a known remote client while rejecting unexpected sources”. This behavior is explained by Remote log ingestion requires a listening input and deliberate source authorization. The deciding requirement here is “Time synchronization requires a reachable usable reference and a healthy time daemon”.

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. This question instead requires “SSH local forwarding carries traffic for a chosen remote endpoint through an encrypted SSH connection”.

This alternative addresses the separate case “An administrator wants to run a remote X11 tool through an encrypted SSH session”. The governing principle is SSH X11 forwarding tunnels GUI application traffic and supplies scoped authentication. For the stated problem, “SSH local forwarding carries traffic for a chosen remote endpoint through an encrypted SSH connection” addresses the central condition.

The option would apply to “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 “SSH local forwarding carries traffic for a chosen remote endpoint through an encrypted SSH connection”.

This option serves the scenario “A Linux host uses directory-based account resolution and /etc/passwd does not list a known user”. Verify that getent returns the expected directory account while local files remain unchanged. The present scenario is distinguished by “A controlled login fails while the retained home remains available to the authorized reviewer”.

The proposed check does not prove the intended behavior. A directly relevant test must show A controlled login fails while the retained home remains available to the authorized reviewer.

The option would apply to “A user without authorization attempts to create one-time at tasks despite a deny policy”. Acceptance requires An authorized operator can schedule a job while the blocked user is denied. This question instead requires “A controlled login fails while the retained home remains available to the authorized reviewer”.

This alternative addresses the separate case “A user can reach a web service by IP but not by hostname and suspects DNS”. The most direct risk is Changing working IP routes without checking DNS can prolong the outage. For the stated problem, “Conflating local mappings with DNS publication leads to false availability claims” addresses the central condition.

The case is most directly exposed to Conflating local mappings with DNS publication leads to false availability claims; the alternative describes a different operational risk.

That danger is associated more closely with A host uses a /26 mask but a technician assumes every subnet has 254 usable addresses. Here the primary exposure is Conflating local mappings with DNS publication leads to false availability claims.

The related but distinct situation is “An hourly job is moved from a user crontab into /etc/crontab and fails to execute”. This behavior is explained by System crontab entries add a username field not present in normal user crontabs. For the stated problem, “Multiple distinct recurrence requirements should not be compressed into a misleading single expression” addresses the central condition.

This option serves the scenario “An administrator needs to adjust a user's primary group while retaining supplementary team groups”. Here, A primary group is distinct from supplementary groups modified with -G. The present scenario is distinguished by “Multiple distinct recurrence requirements should not be compressed into a misleading single expression”.

This would be the main explanation for A database backup job works interactively but fails through cron because a helper program is not found. It does not account for A monthly security scan requires a reminder on the first day at midnight and a separate weekly report.

The related but distinct situation is “An operator searches for service failures but the journal shows previous boots mixed with today's records”. The main exposure is Mixing boots can produce a false sequence of unrelated failures. The deciding requirement here is “Sending to an unrelated facility can make valid events appear missing”.

This option serves the scenario “A user's local mail should be forwarded to an approved external team mailbox”. Leaving the issue can cause Incorrect forwarding can silently send operational alerts to an obsolete destination. This question instead requires “Sending to an unrelated facility can make valid events appear missing”.

That outcome fits another condition, A server sends logs to two separate files because old rsyslog rules and new journald forwarding overlap, rather than the current one.

The alternative fits A scripted conditional needs to distinguish an empty variable from a nonempty path safely. The reported issue instead calls for Return a nonzero exit status on failure and zero only after successful checks, as The shell communicates success and failure to callers through exit status values.

This command or configuration addresses a different case: A team wants a reusable command group with arguments and local processing instead of a static alias. Here, The shell communicates success and failure to callers through exit status values, so the targeted action is Return a nonzero exit status on failure and zero only after successful checks.

That option does not correct the stated dependency. In this case, The shell communicates success and failure to callers through exit status values; implement Return a nonzero exit status on failure and zero only after successful checks and check The calling scheduler marks the intentionally failed prerequisite as failed.