Question 260
A Linux administrator evaluates: A team changes OnCalendar in a unit but forgets to reload systemd before checking its schedule. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A team changes OnCalendar in a unit but forgets to reload systemd before checking its schedule. The recommended direct administrative response is: Use a systemd timer and matching service unit for repeatable scheduled work, then inspect timer scheduling and service journal output. The relevant failure or security risk is: An enabled timer without a valid service unit or a misread OnCalendar expression may never execute the task. Validate success with: systemctl list-timers, unit status and journalctl show the expected scheduled activation and last execution result.
For the specific observation (A team changes OnCalendar in a unit but forgets to reload systemd before checking its schedule), the acceptance evidence is: systemctl list-timers, unit status and journalctl show the expected scheduled activation and last execution result. This verifies the action (Use a systemd timer and matching service unit for repeatable scheduled work, then inspect timer scheduling and service journal output.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: An enabled timer without a valid service unit or a misread OnCalendar expression may never execute the task.
Incorrect Answers
Linux symbolic versus hard links (2.1) would demonstrate or implement: A hard link cannot span filesystem boundaries; a symlink can become dangling after the named target is removed. The case states: A team changes OnCalendar in a unit but forgets to reload systemd before checking its schedule. The most direct paired action and test is: Use a systemd timer and matching service unit for repeatable scheduled work, then inspect timer scheduling and service journal output.
Rootless Podman runtime and privilege boundaries (2.6) would demonstrate or implement: Container inspection identifies the intended rootless user and an authorization test confirms no unapproved host access. This case instead tests Systemd timers and journal-based execution checks; the choice measures or changes another part of the system.
Package dependency repair and integrity verification (2.4) addresses another technical failure: Forcing installation around dependency or GPG validation may leave incompatible libraries or install tampered artifacts. The paired-answer requirement concerns Systemd timers and journal-based execution checks; this alternative does not provide the matching intervention and separate acceptance evidence.