Select the TWO statements that correctly describe system crontabs (/etc/crontab and files under /etc/cron.d) compared with per-user crontabs.
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
Choose 2.
Correct Lines in /etc/crontab carry an extra field, after the five time fields, naming the user the command runs as.
Correct. That sixth field is the distinguishing feature of the system crontab format, and forgetting it is why a hand-written /etc/crontab line so often fails.
Not correct Running `crontab -e` as root edits /etc/crontab.
Wrong. `crontab -e` always edits the invoking user's own personal crontab, which for root is root's spool file. /etc/crontab is a separate file edited directly with a text editor.
Not correct A user's own crontab is edited by opening the corresponding file in /etc/cron.d with a text editor.
Wrong. User crontabs live in a spool directory such as /var/spool/cron/crontabs (Debian) or /var/spool/cron (Red Hat) and should be edited only through `crontab -e`, which validates the file and signals cron.
Correct Files placed in /etc/cron.d use the same format as /etc/crontab, including the user field.
Correct. /etc/cron.d exists so that packages can drop in their own schedule fragments without editing /etc/crontab, and the format is identical.
Not correct Jobs from /etc/crontab always run as the user nobody for security reasons.
Wrong. They run as whichever user the sixth field names, very often root. There is no such automatic privilege drop.
Why
Two formats exist. User crontabs: five time fields then the command. System crontabs (/etc/crontab, /etc/cron.d/*): five time fields, then a user name, then the command. The run-parts lines in a stock /etc/crontab are what drive /etc/cron.hourly, cron.daily, cron.weekly and cron.monthly, whose contents are executable scripts with no schedule line of their own.
Where this comes from
- Cited
- LPI exam objective 107.2
- What it says
- Know the difference between the user crontab format and the system-wide crontab format.
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