LPI 102-500 Bundle

This option serves the scenario “A Bash function in a profile must be available to the current shell without logging out”. Here, Sourcing executes shell commands in the current environment rather than a separate process. The present scenario is distinguished by “A normally executed script runs in its own process and cannot change its parent's directory”.

The proposed principle does not identify the crucial dependency in this case: A normally executed script runs in its own process and cannot change its parent's directory.

The related but distinct situation is “An automation job needs a temporary locale change without modifying global server defaults”. The relevant Linux mechanism is A variable assignment preceding a command can affect just that command's environment. For the stated problem, “A normally executed script runs in its own process and cannot change its parent's directory” addresses the central condition.

This command or configuration addresses a different case: A technician assumes the window manager is responsible for authenticating users at the graphical login screen. Here, RDP and VNC are distinct remote desktop technologies with different implementations, so the targeted action is Choose and configure an appropriate remote-desktop protocol for the required server and client.

Although that change may be valid elsewhere, it responds to A workstation team wants a lightweight desktop and confuses the desktop environment with its display manager, not to this system state. The relevant fix is Choose and configure an appropriate remote-desktop protocol for the required server and client.

That option does not correct the stated dependency. In this case, RDP and VNC are distinct remote desktop technologies with different implementations; implement Choose and configure an appropriate remote-desktop protocol for the required server and client and check A supported client establishes the authorized graphical session using the selected protocol.

The option would apply to “A worker must make a profile variable available to an application started from the same login”. Leaving the issue can cause Setting a value without exporting can silently deprive child processes of configuration. This question instead requires “A shell-local value may appear correct while tools invoked by child scripts still fail”.

The case is most directly exposed to A shell-local value may appear correct while tools invoked by child scripts still fail; the alternative describes a different operational risk.

The case is most directly exposed to A shell-local value may appear correct while tools invoked by child scripts still fail; the alternative describes a different operational risk.

It fails to address the actual requirement, A host's RTC was changed externally and the OS must read the known UTC hardware time. The needed change is Use hwclock inspection and a controlled clock synchronization procedure; verify Both clock readbacks agree within the accepted time drift tolerance.

The alternative fits A security reviewer wants to investigate only error-priority journal entries for yesterday. The reported issue instead calls for Use hwclock inspection and a controlled clock synchronization procedure, as The hardware clock and the running system clock are separate clock representations.

This command or configuration addresses a different case: An operator changes the visible timezone using TZ but expects the hardware RTC bytes to change. Here, The hardware clock and the running system clock are separate clock representations, so the targeted action is Use hwclock inspection and a controlled clock synchronization procedure.

This option serves the scenario “An SSH client rejects a host after a DNS migration because the stored known_hosts entry no longer matches”. Verify that A verified new fingerprint is recorded and the intended SSH connection completes. The present scenario is distinguished by “A Telnet connection is refused while authorized SSH continues working”.

The proposed check does not prove the intended behavior. A directly relevant test must show A Telnet connection is refused while authorized SSH continues working.

A passing result on that unrelated check cannot certify the present correction; require A Telnet connection is refused while authorized SSH continues working.

This alternative addresses the separate case “The security team must create a new group and set a particular numeric group identifier”. The main exposure is Duplicate or unexpected GIDs may unintentionally share group-based file access. For the stated problem, “Relying solely on password locking can leave key-based access active” addresses the central condition.

The option would apply to “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 present scenario is distinguished by “Relying solely on password locking can leave key-based access active”.

The case is most directly exposed to Relying solely on password locking can leave key-based access active; the alternative describes a different operational risk.

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. This question instead requires “Submit a one-time job using at and verify it appears in atq”.

The related but distinct situation is “A monthly security scan requires a reminder on the first day at midnight and a separate weekly report”. The appropriate operation is Define two independent cron expressions and verify their time fields. For the stated problem, “Submit a one-time job using at and verify it appears in atq” addresses the central condition.

This option serves the scenario “A server's locale must support accented names and a Unicode-based application”. The safest fitting response is Choose an available UTF-8 locale and verify locale -a before applying it. The present scenario is distinguished by “Submit a one-time job using at and verify it appears in atq”.

The related but distinct situation is “A shared workstation has a skeleton .bashrc used for new users but an existing account did not receive it”. Here, Skeleton files are copied at account creation rather than retroactively synchronized. The deciding requirement here is “Account creation must set a login shell and home directory according to user policy”.

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 “Account creation must set a login shell and home directory according to user policy”.

It is less specific than Account creation must set a login shell and home directory according to user policy, which directly explains the scenario and supports Create the account with appropriate useradd home and shell options and verify its passwd entry.

It fails to address the actual requirement, A Linux workstation has a working X server but users cannot get a desktop because the session manager is absent. The needed change is Install and configure the intended desktop environment and its graphical session components; verify After login the expected panel and desktop applications initialize.

That option does not correct the stated dependency. In this case, A display server alone does not provide a complete GNOME, KDE or Xfce user environment; implement Install and configure the intended desktop environment and its graphical session components and check After login the expected panel and desktop applications initialize.

The related but distinct situation is “A support engineer expects RDP to be identical to VNC when accessing a Linux desktop remotely”. The appropriate operation is Choose and configure an appropriate remote-desktop protocol for the required server and client. For the stated problem, “Install and configure the intended desktop environment and its graphical session components” addresses the central condition.

This command or configuration addresses a different case: A laptop has an active Wi-Fi connection but should prevent automatic connection to an untrusted network. Here, Runtime interface changes do not automatically define a persistent connection configuration, so the targeted action is Modify the appropriate persistent NetworkManager connection profile and reactivate it.

The option would apply to “In an LPIC-1 102-500 administration task, A test host uses 255.255.255.0 but another host in the same VLAN uses 255.255.0.0”. The appropriate operation is Normalize the intended IPv4 prefixes and verify routing and broadcast behavior. The present scenario is distinguished by “Modify the appropriate persistent NetworkManager connection profile and reactivate it”.

Although that change may be valid elsewhere, it responds to A server needs a fixed default gateway for a persistent NetworkManager Ethernet profile, not to this system state. The relevant fix is Modify the appropriate persistent NetworkManager connection profile and reactivate it.

The case is most directly exposed to Leaving root mail unattended can hide security and job-failure alerts; the alternative describes a different operational risk.

The case is most directly exposed to Leaving root mail unattended can hide security and job-failure alerts; the alternative describes a different operational risk.

That danger is associated more closely with A server sends logs to two separate files because old rsyslog rules and new journald forwarding overlap. Here the primary exposure is Leaving root mail unattended can hide security and job-failure alerts.