LPI 102-500 Bundle

That statement explains another situation: A support engineer expects RDP to be identical to VNC when accessing a Linux desktop remotely. The current observation instead depends on A display server alone does not provide a complete GNOME, KDE or Xfce user environment.

That statement explains another situation: A workstation team wants a lightweight desktop and confuses the desktop environment with its display manager. The current observation instead depends on A display server alone does not provide a complete GNOME, KDE or Xfce user environment.

This alternative addresses the separate case “A technician assumes the window manager is responsible for authenticating users at the graphical login screen”. This behavior is explained by The display manager handles authentication and session selection, while the window manager manages windows. The deciding requirement here is “A display server alone does not provide a complete GNOME, KDE or Xfce user environment”.

That option does not correct the stated dependency. In this case, LANG supplies a default locale while individual LC_* variables can override categories; implement Set LANG appropriately and override only specific LC_* categories when required and check locale reports the expected defaults and targeted time or numeric category choices.

That option does not correct the stated dependency. In this case, LANG supplies a default locale while individual LC_* variables can override categories; implement Set LANG appropriately and override only specific LC_* categories when required and check locale reports the expected defaults and targeted time or numeric category choices.

The option would apply to “An administrator needs to remove a pending one-time job identified in the at queue”. The appropriate operation is Use atq to verify its job number and atrm to remove that specific job. The present scenario is distinguished by “Set LANG appropriately and override only specific LC_* categories when required”.

This option serves the scenario “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 present scenario is distinguished by “A digital signature binds file content to the private signing key and permits public verification”.

This alternative addresses the separate case “A team must encrypt a confidential file for one specific recipient using GnuPG”. This behavior is explained by Public-key encryption uses the recipient's public key so their private key can decrypt. The deciding requirement here is “A digital signature binds file content to the private signing key and permits public verification”.

It is less specific than A digital signature binds file content to the private signing key and permits public verification, which directly explains the scenario and supports Use gpg --verify against the signed data and validate the trusted signing key.

The case is most directly exposed to Opening an unauthenticated wide log listener can enable spoofing and log flooding; the alternative describes a different operational risk.

That danger is associated more closely with A VM's clock drifts despite a running NTP daemon because it cannot reach its upstream reference. Here the primary exposure is Opening an unauthenticated wide log listener can enable spoofing and log flooding.

The related but distinct situation is “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. The deciding requirement here is “Opening an unauthenticated wide log listener can enable spoofing and log flooding”.

The alternative fits A server needs a fixed default gateway for a persistent NetworkManager Ethernet profile. The reported issue instead calls for Inspect ip route and add the correct default route through the authorized gateway, as Traffic for destinations outside connected prefixes requires a selected route.

The related but distinct situation is “A host cannot reach a DNS server because its IPv4 interface has an incorrect subnet mask”. The appropriate operation is Compare ip addr and ip route data with the intended subnet design. For the stated problem, “Inspect ip route and add the correct default route through the authorized gateway” addresses the central condition.

The alternative fits An IPv6-only server uses ping for an IPv4 literal and mistakenly reports IPv6 routing is broken. The reported issue instead calls for Inspect ip route and add the correct default route through the authorized gateway, as Traffic for destinations outside connected prefixes requires a selected route.

The related but distinct situation is “A CUPS printer queue contains a stuck job and the user needs to cancel just that job”. Verify that The stuck job disappears and unrelated queued jobs remain. The deciding requirement here is “The audit line includes complete date, clock time and timezone offset”.

The proposed check does not prove the intended behavior. A directly relevant test must show The audit line includes complete date, clock time and timezone offset.

This alternative addresses the separate case “A VM's clock drifts despite a running NTP daemon because it cannot reach its upstream reference”. Verify that Source status shows a valid peer and the time offset declines to the policy limit. For the stated problem, “The audit line includes complete date, clock time and timezone offset” addresses the central condition.

This alternative addresses the separate case “A server permits interactive authentication for accounts during scheduled emergency lockout”. The main exposure is Unplanned global login denial can lock out operators during an incident. The deciding requirement here is “Removing an application binary without disabling xinetd can leave service exposure confusing”.

The stated concern is possible elsewhere, but the facts here specifically imply Removing an application binary without disabling xinetd can leave service exposure confusing.

The stated concern is possible elsewhere, but the facts here specifically imply Removing an application binary without disabling xinetd can leave service exposure confusing.

The alternative fits An administrator sees a suspicious process holding an apparently deleted log file open. The reported issue instead calls for Use passwd or chage policy to expire the existing password for that account, as Password aging metadata can require a change without revealing stored password hashes.

The related but distinct situation is “A team must encrypt a confidential file for one specific recipient using GnuPG”. The safest fitting response is Import or validate the recipient public key and use gpg --encrypt --recipient. The deciding requirement here is “Use passwd or chage policy to expire the existing password for that account”.

This option serves the scenario “A system administrator switches from a user account to root and wants an audit trail of delegated commands”. The appropriate operation is Use policy-controlled sudo rather than sharing the root password or routinely invoking su. This question instead requires “Use passwd or chage policy to expire the existing password for that account”.

The related but distinct situation is “A user without authorization attempts to create one-time at tasks despite a deny policy”. This behavior is explained by The at access files determine who may submit one-time scheduled work. For the stated problem, “systemd timers activate related units according to monotonic time expressions” addresses the central condition.

This option serves the scenario “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 “systemd timers activate related units according to monotonic time expressions”.

This would be the main explanation for A developer edits a systemd timer file but the system continues following its earlier schedule. It does not account for A service's housekeeping must start five minutes after boot and then repeat every hour using systemd.

The related but distinct situation is “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. The deciding requirement here is “Inspecting a different user's crontab can miss critical scheduled work”.

This alternative addresses the separate case “A weekly snapshot should run automatically after maintenance but an offline machine missed its scheduled window”. Leaving the issue can cause A nonpersistent timer can silently skip work when the host was offline. For the stated problem, “Inspecting a different user's crontab can miss critical scheduled work” addresses the central condition.

The option would apply to “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. The present scenario is distinguished by “Inspecting a different user's crontab can miss critical scheduled work”.

It is not the most direct failure mode. The relevant mechanism is NSS controls whether files or DNS are consulted first for hostnames, which risks Assuming a hosts-file edit always wins can break local overrides.

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.

That outcome fits another condition, A firewall rule permits port 53 only over TCP and small DNS queries work intermittently, rather than the current one.