Quick Answer
The answer is that the administrator forgot to run `systemctl daemon-reload` after adding the service file. This is correct because systemd caches unit files in memory for performance; when you place a new or modified `.service` file into `/etc/systemd/system/`, systemd does not automatically scan for it. Without a reload, systemd still references its old cached list, so it returns "Unit not found" even though the file exists on disk. On the CompTIA Linux+ XK0-005 exam, this is a classic trap—candidates often check file permissions or syntax first, but the real issue is the missing reload step. The exam tests your understanding that systemd requires an explicit command to re-read unit directories. A simple memory tip: remember "DR" for Daemon-Reload—if you Drop a file, you must Reload.
This XK0-005 practice question tests your understanding of troubleshooting. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A Linux system is using systemd and a service fails to start. The administrator checks the service journal and sees: 'Failed to start service: Unit not found'. However, the service file exists in /etc/systemd/system/. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
The service is masked
Why wrong: Masked units show 'masked' status.
systemd has not been reloaded (systemctl daemon-reload)
Correct: Requires daemon-reload to recognize new unit.
The service file has incorrect permissions
Why wrong: Permissions issue gives warning, not 'Unit not found'.
The service is enabled but not started
Why wrong: Enabled services are found, not 'Unit not found'.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
systemd has not been reloaded (systemctl daemon-reload)
When a service file is added or modified in /etc/systemd/system/, systemd does not automatically re-read the unit files. The administrator must run 'systemctl daemon-reload' to instruct systemd to scan for new or changed unit files. Without this reload, systemd still references its cached list of units, resulting in 'Unit not found' even though the file exists on disk.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
The service is masked
Why it's wrong here
Masked units show 'masked' status.
systemd has not been reloaded (systemctl daemon-reload)
Why this is correct
Correct: Requires daemon-reload to recognize new unit.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
The service file has incorrect permissions
Why it's wrong here
Permissions issue gives warning, not 'Unit not found'.
The service is enabled but not started
Why it's wrong here
Enabled services are found, not 'Unit not found'.
Common exam traps
The trap here is that candidates assume systemd automatically detects new unit files in the filesystem, when in fact it requires an explicit 'daemon-reload' to refresh its unit cache.
Trap categories for this question
Command / output trap
Masked units show 'masked' status.
Detailed technical explanation
systemd caches unit file information in memory for performance. When a new unit file is placed in /etc/systemd/system/, systemd does not automatically detect it; 'systemctl daemon-reload' triggers a full rescan of all unit directories, rebuilding the dependency tree and loading new units. A common real-world scenario is when a sysadmin copies a unit file and immediately tries to start it without reloading, leading to this exact error.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A network engineer segments a warehouse floor into three subnets: 20 scanners, 5 printers, and 2 management hosts. Picking the wrong mask wastes addresses or leaves too few usable hosts. Exam questions test whether you can apply CIDR notation, calculate block size, and identify the correct usable-host range for a given prefix.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Troubleshooting — study guide chapter
Learn the concepts, then practise the questions
Troubleshooting practice questions
Targeted practice on this topic area only
All XK0-005 questions
510 questions across all exam domains
CompTIA Linux+ XK0-005 study guide
Full concept coverage aligned to exam objectives
XK0-005 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise XK0-005 questions linked to Security.
Practise XK0-005 questions linked to Troubleshooting.
Practise XK0-005 questions linked to Scripting, Containers and Automation.
Practise XK0-005 questions linked to System Management.
Practise XK0-005 questions linked to XK0-005 fundamentals.
Practise XK0-005 questions linked to XK0-005 scenario.
Practise XK0-005 questions linked to XK0-005 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Troubleshooting — This question tests Troubleshooting — Read the scenario before looking for a memorised answer..
The correct answer is: systemd has not been reloaded (systemctl daemon-reload) — When a service file is added or modified in /etc/systemd/system/, systemd does not automatically re-read the unit files. The administrator must run 'systemctl daemon-reload' to instruct systemd to scan for new or changed unit files. Without this reload, systemd still references its cached list of units, resulting in 'Unit not found' even though the file exists on disk.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Read the scenario before looking for a memorised answer.
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 25, 2026
This XK0-005 practice question is part of Courseiva's free CompTIA 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 XK0-005 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.