On a systemd system you have created /etc/systemd/system/backup.timer containing a [Timer] section with `OnCalendar=*-*-* 03:30:00`. What else is required, and what does that OnCalendar value mean?
LPIC-1 Exam 102-500, objective 107. Administrative tasks hard
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Not correct Nothing else; the command to run is written in the [Timer] section itself
Wrong. A .timer unit has no ExecStart. It carries only the schedule; the work always lives in a separate unit, normally a .service.
Not correct A matching backup.service must exist; the timer fires it 3 hours 30 minutes after boot
Wrong on the schedule. A delay relative to boot is expressed with OnBootSec=, and one relative to the unit's activation with OnUnitActiveSec=. OnCalendar= is absolute wall-clock time.
Not correct An entry in /etc/crontab is still needed, because systemd timers only wake the machine
Wrong. systemd timers are a full replacement for cron entries and do not depend on cron at all. Waking a suspended machine is a separate opt-in setting, WakeSystem=true.
Correct A matching backup.service unit must exist; the timer fires it at 03:30 every day
Correct. A timer activates a unit; by default that is the unit of the same name with a .service suffix (overridable with Unit= in the [Timer] section). The calendar expression is year-month-day hour:minute:second with * as a wildcard, so this matches 03:30:00 on every date.
Why
A timer must be enabled and started (`systemctl enable --now backup.timer`) to have any effect; enabling the .service instead is the usual mistake. `systemctl list-timers` shows the next and last elapse of every active timer, and `systemd-analyze calendar '*-*-* 03:30:00'` expands an expression so you can check it before deploying. Persistent=true makes a timer catch up a run missed while the machine was off, which is systemd's answer to anacron.
Where this comes from
- Cited
- LPI exam objective 107.2
- What it says
- Understand systemd timer units as an alternative to cron.
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 107 and space the ones you get wrong.
More questions on this objective
- The account alice already belongs to the supplementary groups audio and video. You must additionally put her in the group developers while keeping her existing memberships. Which command does that? machine-checked
- A departing employee's account bob must be deleted together with his home directory and mail spool. Which command does all of that in one step? machine-checked
- You want every newly created account to start with a company-standard .bashrc already in its home directory. Where do you place that file? machine-checked
- On a host whose accounts come partly from local files and partly from a directory service, `grep alice /etc/passwd` returns nothing even though `id alice` works. Which command shows alice's account entry the way the system itself resolves it? machine-checked
- Policy says passwords must be changed at least every 90 days, and the account carol must comply. Which command sets that maximum password age? machine-checked
- A line in /etc/group reads `developers:x:1500:alice,bob`. What does the final field contain? machine-checked