LPI 102-500 Bundle

That danger is associated more closely with A program resolves a name differently than dig because local NSS mappings override DNS. Here the primary exposure is Manual changes to managed resolver files can vanish after reboot.

That danger is associated more closely with A server needs a fixed default gateway for a persistent NetworkManager Ethernet profile. Here the primary exposure is Manual changes to managed resolver files can vanish after reboot.

It is not the most direct failure mode. The relevant mechanism is Generated resolver files may be rewritten by the active network-resolver service, which risks Manual changes to managed resolver files can vanish after reboot.

It is less specific than Skeleton files are copied at account creation rather than retroactively synchronized, which directly explains the scenario and supports Review /etc/skel behavior and deploy the approved file to existing users separately.

This option serves the scenario “A local user is renamed while their previous username remains in automated scripts”. Here, The login name and home directory are distinct account properties that may need coordinated changes. This question instead requires “Skeleton files are copied at account creation rather than retroactively synchronized”.

The option would apply to “A newly hired analyst has a Linux account but no home directory or default shell”. The relevant Linux mechanism is Account creation must set a login shell and home directory according to user policy. The present scenario is distinguished by “Skeleton files are copied at account creation rather than retroactively synchronized”.

This option serves the scenario “Printing stops after an operator disables a CUPS queue during maintenance”. The safest fitting response is Reenable the approved printer destination and verify it accepts jobs. The present scenario is distinguished by “Inspect CUPS printer configuration and the configured remote device URI”.

This alternative addresses the separate case “An administrator needs to verify a server's NTP synchronization status under chrony”. The appropriate operation is Use chronyc tracking and sources to inspect the selected reference and estimated offset. The deciding requirement here is “Inspect CUPS printer configuration and the configured remote device URI”.

The related but distinct situation is “A legacy application uses lpr and lpq but the host now uses CUPS”. The appropriate operation is Use CUPS-provided LPD compatibility tools and validate the selected queue. For the stated problem, “Inspect CUPS printer configuration and the configured remote device URI” addresses the central condition.

This alternative addresses the separate case “A heavily used server has oversized systemd journals and must reclaim space according to policy”. The decisive distinction is journalctl vacuum operations remove archived journal data according to the chosen threshold. For the stated problem, “journalctl can inspect archived journal files from another filesystem location” addresses the central condition.

The option would apply to “A legacy application uses lpr and lpq but the host now uses CUPS”. The decisive distinction is CUPS can provide lpr, lpq and lprm-compatible client interfaces. The present scenario is distinguished by “journalctl can inspect archived journal files from another filesystem location”.

It is less specific than journalctl can inspect archived journal files from another filesystem location, which directly explains the scenario and supports Use journalctl --directory or --file to read the mounted journal data.

That statement explains another situation: A host's hostname is present in /etc/hosts but its external DNS lookup returns an NXDOMAIN. The current observation instead depends on Applications may use NSS files and services, while dig queries DNS records directly.

The related but distinct situation is “A firewall rule permits port 53 only over TCP and small DNS queries work intermittently”. The governing principle is DNS commonly uses UDP for queries and TCP for larger responses and zone transfers. For the stated problem, “Applications may use NSS files and services, while dig queries DNS records directly” addresses the central condition.

This option serves the scenario “A resolver searches external DNS before local /etc/hosts and ignores a deliberate test alias”. The decisive distinction is NSS controls whether files or DNS are consulted first for hostnames. The present scenario is distinguished by “Applications may use NSS files and services, while dig queries DNS records directly”.

The required verification is A function called with two test parameters processes each correctly, not a result meant for A new analyst logs in through SSH but a custom tool in /opt/tools is not found by name.

This alternative addresses the separate case “A nightly cleanup loop processes filenames containing spaces by iterating over unquoted command substitution”. The best evidence is A test fixture with spaced filenames is handled without splitting or deleting the wrong path. For the stated problem, “A function called with two test parameters processes each correctly” addresses the central condition.

The option would apply to “An administrator needs to inspect only exported variables passed to spawned processes”. Expect A deliberately unexported test variable is absent from env output. The present scenario is distinguished by “A function called with two test parameters processes each correctly”.

This command or configuration addresses a different case: A blind operator needs to navigate desktop controls and receive spoken feedback. Here, Desktop accessibility features can improve visibility without changing application data, so the targeted action is Enable supported large-print themes, magnification and higher contrast in accessibility settings.

This alternative addresses the separate case “A user with tremor repeatedly triggers accidental double keystrokes in a Linux desktop”. The safest fitting response is Configure supported slow or bounce key accessibility options and test typing behavior. The deciding requirement here is “Enable supported large-print themes, magnification and higher contrast in accessibility settings”.

That option does not correct the stated dependency. In this case, Desktop accessibility features can improve visibility without changing application data; implement Enable supported large-print themes, magnification and higher contrast in accessibility settings and check The user confirms legible controls under the approved large-print and contrast profile.

This would be the main explanation for A compliance auditor must demonstrate that normal users cannot read /etc/shadow. It does not account for An administrator wants to run a remote X11 tool through an encrypted SSH session.

The option would apply to “A developer must access a remote PostgreSQL service securely via an intermediate SSH host”. This behavior is explained by SSH local forwarding carries traffic for a chosen remote endpoint through an encrypted SSH connection. The present scenario is distinguished by “SSH X11 forwarding tunnels GUI application traffic and supplies scoped authentication”.

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. The deciding requirement here is “SSH X11 forwarding tunnels GUI application traffic and supplies scoped authentication”.

That outcome fits another condition, A workstation team wants a lightweight desktop and confuses the desktop environment with its display manager, rather than the current one.

The case is most directly exposed to Assuming protocol interchangeability can expose insecure ports and break remote access; the alternative describes a different operational risk.

That danger is associated more closely with A technician assumes the window manager is responsible for authenticating users at the graphical login screen. Here the primary exposure is Assuming protocol interchangeability can expose insecure ports and break remote access.

It fails to address the actual requirement, A command-line mail client reports queued messages and an administrator needs to inspect them. The needed change is Use mailq or the installed MTA's equivalent queue-inspection interface; verify The queue listing identifies the affected message and its delivery state.

This command or configuration addresses a different case: An administrator needs to see current CUPS printer status, destinations and pending jobs. Here, An MTA can queue outgoing messages when immediate delivery is unavailable, so the targeted action is Use mailq or the installed MTA's equivalent queue-inspection interface.

Although that change may be valid elsewhere, it responds to A mail alias is added to /etc/aliases but messages still go to the old address, not to this system state. The relevant fix is Use mailq or the installed MTA's equivalent queue-inspection interface.

The required verification is An authorized operator can schedule a job while the blocked user is denied, not a result meant for An automated task must run at system startup even if no user logs into a shell.

This alternative addresses the separate case “A terminated contractor should no longer log in while the home directory is retained for legal review”. Verify that A controlled login fails while the retained home remains available to the authorized reviewer. The deciding requirement here is “An authorized operator can schedule a job while the blocked user is denied”.

The related but distinct situation is “An administrator needs to remove a pending one-time job identified in the at queue”. Acceptance requires The chosen job number disappears from atq while unrelated entries remain. For the stated problem, “An authorized operator can schedule a job while the blocked user is denied” addresses the central condition.