LPI 102-500 Bundle

The option would apply to “A service's housekeeping must start five minutes after boot and then repeat every hour using systemd”. Acceptance requires systemctl list-timers shows the timer and the service runs after boot and periodically. This question instead requires “systemctl list-timers reflects the revised next activation time”.

The related but distinct situation is “An internationalized application should prefer the locale declared by the operator without forcing every regional category”. Expect locale reports the expected defaults and targeted time or numeric category choices. For the stated problem, “systemctl list-timers reflects the revised next activation time” addresses the central condition.

This option serves the scenario “A scheduled maintenance command writes to stdout but no file is created and the team assumes nothing ran”. Acceptance requires The next test records the job timestamp and exit status in an accessible log. The present scenario is distinguished by “systemctl list-timers reflects the revised next activation time”.

The related but distinct situation is “A service listens on all network interfaces though only local clients should use it”. Leaving the issue can cause Unnecessary public listeners expose sensitive services to outside networks. The deciding requirement here is “Encrypting to the sender's key by mistake prevents the intended recipient from reading it”.

It is not the most direct failure mode. The relevant mechanism is Public-key encryption uses the recipient's public key so their private key can decrypt, which risks Encrypting to the sender's key by mistake prevents the intended recipient from reading it.

It is not the most direct failure mode. The relevant mechanism is Public-key encryption uses the recipient's public key so their private key can decrypt, which risks Encrypting to the sender's key by mistake prevents the intended recipient from reading it.

That option does not correct the stated dependency. In this case, A TCP socket test validates a specific port rather than only ICMP reachability; implement Use a suitable netcat connection test or other protocol-aware TCP probe and check The probe reports successful TCP connection to the intended host and port.

This command or configuration addresses a different case: A network engineer uses netstat on a minimal modern Linux host and discovers it is not installed. Here, A TCP socket test validates a specific port rather than only ICMP reachability, so the targeted action is Use a suitable netcat connection test or other protocol-aware TCP probe.

Although that change may be valid elsewhere, it responds to An IPv6-only server uses ping for an IPv4 literal and mistakenly reports IPv6 routing is broken, not to this system state. The relevant fix is Use a suitable netcat connection test or other protocol-aware TCP probe.

That danger is associated more closely with A network daemon is not required but systemd starts it through socket activation after service disable. Here the primary exposure is Assuming modern applications universally honor TCP wrappers can leave controls ineffective.

The case is most directly exposed to Assuming modern applications universally honor TCP wrappers can leave controls ineffective; the alternative describes a different operational risk.

The case is most directly exposed to Assuming modern applications universally honor TCP wrappers can leave controls ineffective; the alternative describes a different operational risk.

The alternative can apply elsewhere, but Local mail aliases redirect a recipient without modifying the sender's mail command is the governing fact here; test by checking A controlled mail to root reaches the approved on-call mailbox.

The alternative can apply elsewhere, but Local mail aliases redirect a recipient without modifying the sender's mail command is the governing fact here; test by checking A controlled mail to root reaches the approved on-call mailbox.

This option serves the scenario “A script expects a simple command-line message to be delivered but its subject line is missing”. Here, The mail user agent constructs a message while the MTA performs its delivery. The present scenario is distinguished by “Local mail aliases redirect a recipient without modifying the sender's mail command”.

The required verification is id for the service reports a nonzero UID and permissions tests pass minimally, not a result meant for A department requires an existing user to join the audit group without losing other supplementary groups.

This option serves the scenario “A server in Karachi reports UTC on local console but should display local Pakistan time without changing UTC storage”. Expect timedatectl and date show the intended offset and a consistent instant. This question instead requires “id for the service reports a nonzero UID and permissions tests pass minimally”.

That observation may validate A support team needs to inspect one user's groups but /etc/group alone seems to omit the primary group, but it does not establish that id for the service reports a nonzero UID and permissions tests pass minimally for the current case.

This option serves the scenario “A host still exposes Telnet but policy allows only encrypted remote administration”. The appropriate operation is Disable the legacy Telnet service or socket and enforce approved SSH access. The present scenario is distinguished by “Correlate ss or netstat listener data with process ownership and approved service inventory”.

That option does not correct the stated dependency. In this case, An open port should be mapped to the responsible process before remedial action; implement Correlate ss or netstat listener data with process ownership and approved service inventory and check The audit identifies the exact unexpected process and its listening socket.

The option would apply to “An administrator sees a suspicious process holding an apparently deleted log file open”. The safest fitting response is Use lsof or fuser to identify the process retaining the file handle. This question instead requires “Correlate ss or netstat listener data with process ownership and approved service inventory”.

That option does not correct the stated dependency. In this case, The socket table can show listening ports and owning processes when permitted; implement Use ss -ltnp with appropriate privileges to inspect socket-to-process mapping and check The suspicious port is mapped to its actual process and approved service state.

It fails to address the actual requirement, An operator needs to identify which process owns an unexpected listening socket. The needed change is Use ss -ltnp with appropriate privileges to inspect socket-to-process mapping; verify The suspicious port is mapped to its actual process and approved service state.

Although that change may be valid elsewhere, it responds to A laptop must join a secured Wi-Fi network via NetworkManager from the command line, not to this system state. The relevant fix is Use ss -ltnp with appropriate privileges to inspect socket-to-process mapping.

The option would apply to “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 test graphical session starts with the intended keyboard layout and normal logs”.

The related but distinct situation is “A workstation team wants a lightweight desktop and confuses the desktop environment with its display manager”. Expect The pilot launches the chosen desktop after authentication with the intended window system. For the stated problem, “The test graphical session starts with the intended keyboard layout and normal logs” addresses the central condition.

This option serves the scenario “A GUI tool works under a user's desktop but fails when launched from a root shell without DISPLAY”. Acceptance requires The program renders only in the approved user's display session. The present scenario is distinguished by “The test graphical session starts with the intended keyboard layout and normal logs”.

This option serves the scenario “A system using systemd-resolved shows generated /etc/resolv.conf and an administrator edits it persistently”. The governing principle is Generated resolver files may be rewritten by the active network-resolver service. This question instead requires “Persistent gateway settings belong to the active network configuration manager”.

This would be the main explanation for A DHCP-enabled workstation needs to switch to a managed static IPv4 address. It does not account for A server needs a fixed default gateway for a persistent NetworkManager Ethernet profile.

The option would apply to “A technician edits /etc/resolv.conf directly but NetworkManager replaces it on reconnect”. The decisive distinction is Network-management services can regenerate resolv.conf from persistent connection settings. The present scenario is distinguished by “Persistent gateway settings belong to the active network configuration manager”.

That statement explains another situation: A hardening scan finds an unfamiliar TCP listener on a production Linux host. The current observation instead depends on Revocation informs relying parties that the old key should no longer be trusted.

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 “Revocation informs relying parties that the old key should no longer be trusted”.

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. This question instead requires “Revocation informs relying parties that the old key should no longer be trusted”.