LFCS Service Configuration Practice Question
Which THREE of the following are valid systemd unit types?
⚠ Common exam trap
Watch out — candidates often confuse systemd unit types with service configuration directives (like Type=notify) or with generic terms like 'startup', leading them to select invalid options that sound plausible but are not defined in systemd's unit type specification.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
target
Option C (target) is a valid systemd unit type: targets group other units and synchronize boot, replacing SysV runlevels (e.g., multi-user.target). Option D (socket) is valid: socket units describe an IPC or network socket that systemd listens on and activates the corresponding service via socket activation. Option E (service) is valid: service units define and control daemons or oneshot processes managed by systemd (e.g., sshd.service). Options A (notification) and B (startup) are not systemd unit types; notification is not a unit type at all, and startup is not a recognized unit suffix, whereas real types include service, socket, target, device, mount, automount, swap, timer, path, slice, and scope.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
notification
Why it's wrong here
"notification" is not a systemd unit type; systemd defines unit types by filename suffix, such as .service, .socket, .timer, .mount, .target and .path, and no .notification suffix exists. It is tempting because systemd units do send notifications via sd_notify, but that is a service configuration detail, not a unit type.
- ✗
startup
Why it's wrong here
systemd has no startup unit type; boot-time behaviour is handled by targets and service units with dependencies. The name resembles boot-related concepts, which is why it tempts, but valid types include service, socket, timer, mount and target.
- ✓
target
Why this is correct
A target unit groups other units into a synchronisation point, replacing SysV runlevels during boot. It satisfies the stem's requirement for a valid systemd unit type, since systemd recognises targets natively alongside service, socket, device, mount, automount, swap, timer, path, slice and scope units.
- ✓
socket
Why this is correct
Socket units let systemd create and listen on sockets, passing file descriptors to a service only when a connection arrives. This is one of the valid unit types alongside service, target, mount, timer and device, satisfying the question's requirement for a genuine systemd unit type.
- ✓
service
Why this is correct
service is a valid systemd unit type, used to describe daemons and processes managed by systemd, such as httpd.service. Unit types are distinguished by filename suffix, and .service units are controlled through systemctl start, stop and status commands.
Go deeper
Related to this question
About these practice questions
This LFCS question is part of Courseiva's 406-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This LFCS practice question is part of Courseiva's free Linux Foundation certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LFCS exam.