Question 220
A Linux administrator evaluates: A branch schedules a recurring task across daylight-saving transitions and needs a predictable zone policy. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A branch schedules a recurring task across daylight-saving transitions and needs a predictable zone policy), the acceptance evidence is: A controlled schedule invocation records the intended user, environment, timestamp and job result. This verifies the action (Choose crontab, at, or a supported systemd timer based on recurrence and missed-run requirements, and verify schedule, timezone and execution context.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: A job defined in the wrong user crontab or scheduled at an incorrect time may never run when required.
The observed Linux condition is: A branch schedules a recurring task across daylight-saving transitions and needs a predictable zone policy. The recommended direct administrative response is: Choose crontab, at, or a supported systemd timer based on recurrence and missed-run requirements, and verify schedule, timezone and execution context. The relevant failure or security risk is: A job defined in the wrong user crontab or scheduled at an incorrect time may never run when required. Validate success with: A controlled schedule invocation records the intended user, environment, timestamp and job result.
Incorrect Answers
Systemd timers and journal-based execution checks (2.5) would demonstrate or implement: systemctl list-timers, unit status and journalctl show the expected scheduled activation and last execution result. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: A controlled schedule invocation records the intended user, environment, timestamp and job result.
Linux symbolic versus hard links (2.1) addresses another technical failure: A hard link cannot span filesystem boundaries; a symlink can become dangling after the named target is removed. The required paired action and test concerns Recurring and one-time job scheduling; a passing result for this alternative could leave that requirement unresolved.
Container port publishing and network isolation (2.6) would demonstrate or implement: Publishing a service on all host interfaces can expose sensitive container ports even if the application was intended for loopback only. The paired-answer requirement concerns Recurring and one-time job scheduling; this alternative does not provide the matching intervention and separate acceptance evidence.