Quick Answer
The answer is `journalctl -u sshd.service`, as this command isolates the systemd journal logs for the sshd service, providing the precise error messages and timestamps needed to diagnose why the service failed. When troubleshooting service logs, `journalctl` with the `-u` flag filters the journal by unit, making it the fastest way to access root-cause details without sifting through unrelated system messages. On the CompTIA Linux+ XK0-005 exam, this tests your understanding of systemd’s logging architecture and the principle of checking logs before restarting or modifying a service—a common trap is jumping to `systemctl restart sshd` or `systemctl status sshd`, which only shows the current state, not the historical failure reason. Remember the mnemonic: “Unit first, then fix”—always use `journalctl -u` to see the unit’s story before taking action.
This XK0-005 practice question tests your understanding of scripting, containers and automation. 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.
An administrator views the exhibit output. Which command should be used first to investigate why sshd failed?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "first"
Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Clue: "which command"
Why it matters: Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
systemctl status sshd.service
Why wrong: Shows status but not full logs.
systemctl restart sshd.service
Why wrong: Restarts without investigation.
journalctl -u sshd.service
Shows the service logs for diagnosis.
systemctl list-units
Why wrong: Lists all units, not specific logs.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
journalctl -u sshd.service
The `journalctl -u sshd.service` command is the correct first step because it displays the systemd journal logs specifically for the sshd service, providing detailed error messages and timestamps that explain why the service failed. This diagnostic approach follows the principle of checking logs before attempting to restart or modify a service, as the logs contain the root cause information needed for troubleshooting.
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 status sshd.service
Why it's wrong here
Shows status but not full logs.
systemctl restart sshd.service
Why it's wrong here
Restarts without investigation.
journalctl -u sshd.service
Why this is correct
Shows the service logs for diagnosis.
Clue confirmation
The clue words "first", "which command" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
systemctl list-units
Why it's wrong here
Lists all units, not specific logs.
Common exam traps
The trap here is that candidates often jump to `systemctl status` or `systemctl restart` out of habit, not realizing that the journal logs provide the specific error details needed to diagnose a failure, and that restarting without investigation can hide the root cause.
Trap categories for this question
Command / output trap
Shows status but not full logs.
Detailed technical explanation
Under the hood, `journalctl -u sshd.service` queries the systemd journal, which stores structured binary logs with metadata such as priority levels, timestamps, and unit identifiers. This command is particularly useful when sshd fails due to configuration errors (e.g., invalid `sshd_config` syntax), missing host keys, or port conflicts, as the journal will contain explicit error messages from the sshd daemon itself. In real-world scenarios, administrators often use `journalctl -u sshd.service -n 50 --no-pager` to view the last 50 lines without paging, enabling rapid root cause analysis.
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.
Scripting, Containers and Automation — study guide chapter
Learn the concepts, then practise the questions
Scripting, Containers and Automation 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
Scripting, Containers and Automation — This question tests Scripting, Containers and Automation — Read the scenario before looking for a memorised answer..
The correct answer is: journalctl -u sshd.service — The `journalctl -u sshd.service` command is the correct first step because it displays the systemd journal logs specifically for the sshd service, providing detailed error messages and timestamps that explain why the service failed. This diagnostic approach follows the principle of checking logs before attempting to restart or modify a service, as the logs contain the root cause information needed for troubleshooting.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "first", "which command". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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.