Quick Answer
The correct choices are `systemctl status myservice` and `journalctl -u myservice`. These two commands work together to provide a complete picture of a service failure: `systemctl status` gives you the immediate state, exit code, and a short tail of recent logs, while `journalctl -u` dives into the full systemd journal for that specific unit, revealing deeper issues like missing dependencies, permission errors, or configuration typos. On the CompTIA Linux+ XK0-005 exam, this pairing tests your ability to differentiate between a quick status check and a thorough log review—a common trap is choosing only `systemctl status` and forgetting that the journal holds the detailed failure reason. Remember the memory tip: "Status shows the crash, journal shows the cause."
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 system administrator is troubleshooting a custom systemd service that fails to start. Which of the following commands should be used to diagnose the issue? (Choose two.)
systemctl daemon-reload
Why wrong: Reloads unit files, does not diagnose failures.
systemctl status myservice
Displays service status and recent log entries.
systemctl enable myservice
Why wrong: Enables service at boot, not diagnostic.
systemctl list-units
Why wrong: Lists all units, not diagnostic.
journalctl -u myservice
Shows full journal for the specified unit.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
systemctl status myservice
The `systemctl status myservice` command (B) is correct because it shows the current state of the service, including whether it is active, failed, or inactive, along with recent log entries and the exit code. The `journalctl -u myservice` command (E) is correct because it retrieves the full systemd journal logs specifically for that unit, which is essential for diagnosing why the service failed to start, such as missing dependencies or configuration errors.
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.
systemctl daemon-reload
Why it's wrong here
Reloads unit files, does not diagnose failures.
systemctl status myservice
Why this is correct
Displays service status and recent log entries.
Related concept
Read the scenario before looking for a memorised answer.
systemctl enable myservice
Why it's wrong here
Enables service at boot, not diagnostic.
systemctl list-units
Why it's wrong here
Lists all units, not diagnostic.
journalctl -u myservice
Why this is correct
Shows full journal for the specified unit.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates often pick `systemctl daemon-reload` (A) thinking it will fix the issue by reloading unit files, but it does not provide diagnostic output; the exam tests the distinction between reloading configuration and retrieving failure logs.
Detailed technical explanation
Under the hood, `systemctl status` reads the unit's state from the systemd manager's internal state machine and displays the last few log messages from the journal, while `journalctl -u` queries the binary journal files directly, allowing filtering by unit name and time range. A subtle behavior is that if the service fails very early (e.g., before `ExecStart` runs), `systemctl status` may show only a generic 'failed' status, but `journalctl -u` will capture the exact error message from the service's stderr or the systemd executor. In real-world scenarios, a missing environment file or a permission denied error on an executable is often only visible in the journal, not in the status output.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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.
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: systemctl status myservice — The `systemctl status myservice` command (B) is correct because it shows the current state of the service, including whether it is active, failed, or inactive, along with recent log entries and the exit code. The `journalctl -u myservice` command (E) is correct because it retrieves the full systemd journal logs specifically for that unit, which is essential for diagnosing why the service failed to start, such as missing dependencies or configuration errors.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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.