The answer is that the systemd daemon has not been reloaded after enabling the new service. When you add a new unit file to /etc/systemd/system, systemd does not automatically recognize it; you must run `systemctl daemon-reload` to refresh its internal cache. Even though `systemctl enable myapp.service` successfully creates the symlink to multi-user.target, the daemon still holds an outdated view of available units, so at boot it reports "Unit not found." On the CompTIA Linux+ XK0-005 exam, this scenario tests your understanding of the unit lifecycle: creating a file, reloading the daemon, then enabling. A common trap is assuming that a successful enable command implies systemd already knows about the unit. Remember the mnemonic **C.R.E.** — Create, Reload, Enable — to avoid this pitfall.
XK0-005 System Management Practice Question
This XK0-005 practice question tests your understanding of system management. 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 system administrator notices that a service fails to start at boot with the message "Failed to start MyApp.service: Unit not found". The administrator checks the service unit file at /etc/systemd/system/myapp.service. The target wanted-by is multi-user.target. The administrator runs `systemctl enable myapp.service` successfully, but the service still does not start at boot. 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.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The systemd daemon has not been reloaded after enabling.
When a new unit file is added, systemctl daemon-reload must be run before systemd recognizes the unit. Even though enable succeeded, if daemon-reload was not performed after creating the unit file, systemd may not have the unit in its internal cache and may fail to find it at boot. Option A would produce a different error. Option B is incorrect because enable creates the symlink. Option C would show a dependency error.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 systemd daemon has not been reloaded after enabling.
Why this is correct
After adding a new unit file, daemon-reload is required. Even though enable succeeded, systemd's in-memory state might be stale.
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 unit file has a syntax error.
Why it's wrong here
A syntax error would show a parsing error, not 'Unit not found'.
✗
The service requires a dependency that is not installed.
Why it's wrong here
Missing dependency would show a different error, like dependency failed.
✗
The service is not symlinked into the correct .wants directory.
Why it's wrong here
systemctl enable creates the symlink; if it succeeded, the symlink exists.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Trap categories for this question
Command / output trap
A syntax error would show a parsing error, not 'Unit not found'.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the XK0-005 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this XK0-005 question in full detail.
Identify which XK0-005 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
System Management — This question tests System Management — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The systemd daemon has not been reloaded after enabling. — When a new unit file is added, systemctl daemon-reload must be run before systemd recognizes the unit. Even though enable succeeded, if daemon-reload was not performed after creating the unit file, systemd may not have the unit in its internal cache and may fail to find it at boot. Option A would produce a different error. Option B is incorrect because enable creates the symlink. Option C would show a dependency error.
What should I do if I get this XK0-005 question wrong?
Identify which XK0-005 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
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 →
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.
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.