Question 154 of 507
LFCS systemctl start Practice Question
A system administrator configures a web server using systemd. After creating a custom service unit file, the administrator runs `systemctl daemon-reload` but the service still fails to start with a 'Unit not found' error. What is the most likely cause?
⚠ Common exam trap
Candidates often overthink the directory paths and forget that a simple typo in the service name is the most common cause of 'Unit not found' errors. The trap is focusing on file placement rather than the exact command used to start the service.
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
✓
The service name was misspelled in the `systemctl start` command.
The 'Unit not found' error after `systemctl daemon-reload` typically indicates that systemd cannot locate a unit with the specified name. While correct placement of unit files is important, systemd scans both /etc/systemd/system/ and /usr/lib/systemd/system/ after a daemon-reload. Therefore, placing a custom unit in /usr/lib/systemd/system/ would not cause this error. The most likely cause is that the service name was misspelled in the `systemctl start` command. A simple typo would lead to a 'Unit not found' message because systemd looks for an exact match. Other options like forgetting `systemctl enable` or group membership do not affect unit discovery at start time.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The administrator forgot to run `systemctl enable` before starting the service.
Why it's wrong here
Running `systemctl enable` creates symlinks for automatic startup but is not required to start a service. The 'Unit not found' error is unrelated to enabling.
- ✗
The unit file is placed in /usr/lib/systemd/system/ instead of /etc/systemd/system/.
Why it's wrong here
While placing custom units in /etc/systemd/system/ is best practice, systemd also scans /usr/lib/systemd/system/ after a daemon-reload. Therefore, this location would not cause a 'Unit not found' error.
- ✗
The administrator is not in the 'systemd' group.
Why it's wrong here
The 'systemd' group is for accessing the systemd journal, not for starting services. Group membership does not affect unit discovery.
- ✓
The service name was misspelled in the `systemctl start` command.
Why this is correct
If the service name is misspelled in `systemctl start`, systemd cannot find the unit and returns 'Unit not found'. This is the most likely cause after a daemon-reload has been performed.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.