The answer is that a relative ExecStart path is the most likely cause of the systemd service failure. Systemd strictly requires absolute paths for the ExecStart directive because it does not inherit a shell environment or a working directory by default; when you specify a relative path like `./script.sh` or just `script.sh`, systemd cannot resolve the executable’s location, immediately triggering the 'entered failed state' error. On the CompTIA Linux+ XK0-005 exam, this question tests your understanding of systemd unit file syntax and common pitfalls—a frequent trap is assuming systemd behaves like a shell script, where relative paths work. Remember the memory tip: “Absolute paths for absolute reliability” — if the path doesn’t start with `/`, systemd will fail to start the service.
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.
Exhibit
[Unit]
Description=My custom service
After=network.target
[Service]
ExecStart=./myscript
Restart=always
[Install]
WantedBy=multi-user.target
Refer to the exhibit. A Linux administrator created a systemd service file for a custom script. When starting the service, it fails with 'Unit myservice.service entered failed state.' Which of the following 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 ExecStart path is relative
The most likely cause is that the ExecStart path is relative. Systemd requires absolute paths for ExecStart directives; a relative path (e.g., `./script.sh` or just `script.sh`) will cause the unit to fail immediately because systemd cannot resolve the executable location. The error 'entered failed state' typically results from this path resolution failure.
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 ExecStart path is relative
Why this is correct
Systemd requires absolute paths; a relative path causes the service to fail.
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 type should be forking
Why it's wrong here
The default type 'simple' works for foreground processes.
✗
The service file lacks an [Install] section
Why it's wrong here
The [Install] section is present, so this is not the cause.
✗
The Requires directive is missing
Why it's wrong here
No dependencies are needed for this service.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CompTIA often tests the requirement for absolute paths in ExecStart, and the trap here is that candidates may assume relative paths are acceptable or that the [Install] section is mandatory for starting a service, when in fact it is only for enabling.
Detailed technical explanation
How to think about this question
Systemd resolves ExecStart paths by searching for the executable in the absolute path specified; relative paths are not expanded relative to the service file location or the current working directory. The systemd.exec(5) man page explicitly states that ExecStart must be an absolute path to an executable file. In practice, this means even a seemingly harmless relative path like 'myapp' will fail with 'exec format error' or 'No such file or directory' in the journal, leading to the failed state.
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.
TExam Day Tips
→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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this XK0-005 question in full detail.
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 ExecStart path is relative — The most likely cause is that the ExecStart path is relative. Systemd requires absolute paths for ExecStart directives; a relative path (e.g., `./script.sh` or just `script.sh`) will cause the unit to fail immediately because systemd cannot resolve the executable location. The error 'entered failed state' typically results from this path resolution failure.
What should I do if I get this XK0-005 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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.