LPI 102-500 Bundle

That option does not correct the stated dependency. In this case, dig can direct a query at a chosen DNS endpoint for comparative troubleshooting; implement Run dig @server example.name with the intended record type and check The response identifies the queried server and the requested record.

This option serves the scenario “In an LPIC-1 102-500 administration task, A system using systemd-resolved shows generated /etc/resolv.conf and an administrator edits it persistently”. The safest fitting response is Configure the upstream DNS through the responsible resolver or network manager. The present scenario is distinguished by “Run dig @server example.name with the intended record type”.

This command or configuration addresses a different case: A workstation needs a human-readable alias for a private IP without configuring an external DNS zone. Here, dig can direct a query at a chosen DNS endpoint for comparative troubleshooting, so the targeted action is Run dig @server example.name with the intended record type.

This would test another scenario: A user who cannot operate a physical keyboard needs to enter login data with a pointing device. Here the acceptance evidence is The program renders only in the approved user's display session.

This option serves the scenario “An operator assumes every graphical Linux deployment must use Xorg even though a Wayland compositor is active”. Verify that A session inspection identifies the active protocol and the GUI launches compatibly. This question instead requires “The program renders only in the approved user's display session”.

The option would apply to “An X11 program launches on the server instead of appearing on an authorized remote workstation”. Acceptance requires The test client renders on the specified remote display without broad access relaxation. The present scenario is distinguished by “The program renders only in the approved user's display session”.

This alternative addresses the separate case “A technician edits /etc/resolv.conf directly but NetworkManager replaces it on reconnect”. The main exposure is Manual changes to generated resolver files can be lost unexpectedly. The deciding requirement here is “Automatic reconnection to untrusted Wi-Fi can expose traffic”.

It is not the most direct failure mode. The relevant mechanism is Connection profiles can be enabled for manual use without autojoining untrusted SSIDs, which risks Automatic reconnection to untrusted Wi-Fi can expose traffic.

The related but distinct situation is “A DHCP-enabled workstation needs to switch to a managed static IPv4 address”. The most direct risk is Leaving automatic DHCP enabled can override manually intended values. For the stated problem, “Automatic reconnection to untrusted Wi-Fi can expose traffic” addresses the central condition.

The alternative can apply elsewhere, but Standard password utilities update authentication databases safely and consistently is the governing fact here; test by checking The user authenticates with the new password and the old one is rejected.

That statement explains another situation: An account must be temporarily prevented from login after a suspected credential compromise. The current observation instead depends on Standard password utilities update authentication databases safely and consistently.

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 “Standard password utilities update authentication databases safely and consistently”.

It is less specific than CUPS can route jobs to local devices or remote print services, which directly explains the scenario and supports Inspect CUPS printer configuration and the configured remote device URI.

It is less specific than CUPS can route jobs to local devices or remote print services, which directly explains the scenario and supports Inspect CUPS printer configuration and the configured remote device URI.

This alternative addresses the separate case “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 deciding requirement here is “CUPS can route jobs to local devices or remote print services”.

The related but distinct situation is “A department requires an existing user to join the audit group without losing other supplementary groups”. The main exposure is Using usermod -G without append can silently remove existing group access. The deciding requirement here is “Global override can silently defeat individual localization choices”.

The case is most directly exposed to Global override can silently defeat individual localization choices; the alternative describes a different operational risk.

This alternative addresses the separate case “A shell script's sorted output differs between English and German systems”. The most direct risk is Unspecified collation rules can break reproducible hashes or batch comparisons. For the stated problem, “Global override can silently defeat individual localization choices” addresses the central condition.

This option serves the scenario “An administrator sees a suspicious process holding an apparently deleted log file open”. Expect The audit identifies the responsible process and allows controlled cleanup. The present scenario is distinguished by “The contractor can restart only the approved service and cannot run unrelated root commands”.

This alternative addresses the separate case “An operator stores the private SSH identity in a world-readable shared directory”. The best evidence is An unprivileged user cannot read the key and the owner can authenticate normally. The deciding requirement here is “The contractor can restart only the approved service and cannot run unrelated root commands”.

The proposed check does not prove the intended behavior. A directly relevant test must show The contractor can restart only the approved service and cannot run unrelated root commands.

A passing result on that unrelated check cannot certify the present correction; require The unwanted port remains closed after reboot and normal required services work.

This would test another scenario: A network daemon is not required but systemd starts it through socket activation after service disable. Here the acceptance evidence is The unwanted port remains closed after reboot and normal required services work.

The related but distinct situation is “A compliance reviewer needs to prove that a GPG-signed release manifest was not altered”. Verify that The valid signature passes for the unmodified file and fails after a test alteration. The deciding requirement here is “The unwanted port remains closed after reboot and normal required services work”.

This would be the main explanation for A server is reinstalled and clients receive a changed SSH host-key warning. It does not account for A team wants to restrict which private key SSH tries for one sensitive repository host.

The related but distinct situation is “A user must authenticate to an SSH host without typing a password for an approved automation task”. The decisive distinction is SSH public-key authentication uses a private client key and authorized server-side public key. For the stated problem, “SSH client config can select a specific identity instead of offering every loaded key” addresses the central condition.

The alternative can apply elsewhere, but SSH client config can select a specific identity instead of offering every loaded key is the governing fact here; test by checking ssh -v shows only the approved identity offered to the repository server.

The related but distinct situation is “A user without authorization attempts to create one-time at tasks despite a deny policy”. The safest fitting response is Check /etc/at.allow and /etc/at.deny according to the installed at policy. The deciding requirement here is “Include the required user field in the system crontab entry and check command paths”.

Although that change may be valid elsewhere, it responds to An administrator must run log cleanup at 02:30 every weekday, not to this system state. The relevant fix is Include the required user field in the system crontab entry and check command paths.

That option does not correct the stated dependency. In this case, System crontab entries add a username field not present in normal user crontabs; implement Include the required user field in the system crontab entry and check command paths and check The entry runs under the intended identity in a controlled test.

The proposed check does not prove the intended behavior. A directly relevant test must show A noninteractive elevated invocation runs the intended tool without alias expansion.

The required verification is A noninteractive elevated invocation runs the intended tool without alias expansion, not a result meant for An operator writes backup.sh with Bash arrays but invokes it through sh on a non-Bash system.

The related but distinct situation is “A shell script prints an updated working directory but the parent terminal remains unchanged”. The best evidence is pwd in the invoking terminal reports the intended directory after sourcing. For the stated problem, “A noninteractive elevated invocation runs the intended tool without alias expansion” addresses the central condition.