Quick Answer
The correct first step is to check SELinux contexts and file permissions. This is because a "Permission denied" error in journalctl for a service failure almost always points to a mandatory access control (MAC) block from SELinux or incorrect standard Unix file ownership and mode bits; SELinux can deny access even when traditional permissions appear correct, making it a primary suspect. On the CompTIA Linux+ XK0-005 exam, this scenario tests your understanding of layered security controls and the troubleshooting hierarchy—many candidates mistakenly jump to network or package issues first, but the exam emphasizes verifying access controls at the OS level before deeper debugging. A common trap is overlooking SELinux booleans or contexts when standard permissions are set to 777, which still fails under enforcing mode. Memory tip: think "SELinux first, then chmod"—if the service can't read its config file, check the context label before the permission bits.
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 service fails to start and journalctl shows 'Permission denied'. What should the administrator check first?
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.
Package integrity
Why wrong: Reinstalling may fix corrupted files but is not the first step.
DNS resolution
Why wrong: DNS is unrelated to local service startup.
Firewall rules
Why wrong: Firewall affects network traffic, not local file access.
SELinux contexts and file permissions
SELinux contexts are a common cause of permission denied errors for services.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
SELinux contexts and file permissions
The 'Permission denied' error in journalctl for a service failure typically indicates that the service process lacks the necessary permissions to access a file, directory, or resource. SELinux contexts and file permissions are the most common causes, as SELinux enforces mandatory access controls (MAC) that can block access even when standard Unix permissions are correct. Checking these first aligns with the troubleshooting principle of verifying access controls before other layers like network or package integrity.
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.
Package integrity
Why it's wrong here
Reinstalling may fix corrupted files but is not the first step.
DNS resolution
Why it's wrong here
DNS is unrelated to local service startup.
Firewall rules
Why it's wrong here
Firewall affects network traffic, not local file access.
SELinux contexts and file permissions
Why this is correct
SELinux contexts are a common cause of permission denied errors for services.
Clue confirmation
The clue word "first" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates often jump to firewall rules or package integrity because they associate 'Permission denied' with network or installation issues, but the XK0-005 exam specifically tests SELinux and file permission troubleshooting for service startup failures.
Detailed technical explanation
SELinux uses security contexts (user:role:type:level) assigned to files, processes, and ports; a mismatch, such as a service expecting httpd_sys_content_t but finding unconfined_u:object_r:default_t, triggers an AVC denial logged in /var/log/audit/audit.log. The `ls -Z` and `restorecon -v` commands are used to inspect and restore contexts, while `getenforce` checks the enforcement mode. In a real-world scenario, a web server might fail to serve static files after a restore from backup because SELinux contexts were not preserved, leading to 'Permission denied' despite correct 755 permissions.
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: SELinux contexts and file permissions — The 'Permission denied' error in journalctl for a service failure typically indicates that the service process lacks the necessary permissions to access a file, directory, or resource. SELinux contexts and file permissions are the most common causes, as SELinux enforces mandatory access controls (MAC) that can block access even when standard Unix permissions are correct. Checking these first aligns with the troubleshooting principle of verifying access controls before other layers like network or package integrity.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "first". 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.