102-500 · Question #63
Which of the following statements is true regarding systemd timer units?
The correct answer is E. Each systemd timer unit controls a specific systemd service unit. Option E is correct because systemd timer units work in pairs with service units - a .timer file activates a .service file of the same base name (e.g., backup.timer starts backup.service). The timer unit handles when to run, while the service unit defines what to run. Why the…
Question
Options
- ATimer units can only be defined within a service unit's file.
- BThe command executed by the timer is specified in the timer unit's [Cmd] section.
- CA dedicated system service, systemd-cron, handles the execution of timer units.
- DTimer units only exist in the system scope and are not available for users.
- EEach systemd timer unit controls a specific systemd service unit.
How the community answered
(26 responses)- A4% (1)
- B12% (3)
- C4% (1)
- E81% (21)
Explanation
Option E is correct because systemd timer units work in pairs with service units - a .timer file activates a .service file of the same base name (e.g., backup.timer starts backup.service). The timer unit handles when to run, while the service unit defines what to run.
Why the distractors are wrong:
- A - Timer units are separate
.timerfiles, completely independent from.servicefiles, not embedded within them. - B - There is no
[Cmd]section in systemd; the command to execute lives in the paired service unit's[Service]section underExecStart=. - C - No
systemd-crondaemon exists; systemd itself natively manages timer execution through the main daemon. - D - Timer units exist in both system scope and user scope; users can manage their own timers with
systemctl --user.
Memory tip: Think of timer units as an alarm clock (the .timer) paired with a to-do list (the .service) - the alarm tells you when, but the list tells you what. One alarm, one list - always a 1:1 relationship.
Topics
Community Discussion
No community discussion yet for this question.