- A
Disable SELinux temporarily with setenforce 0.
Why wrong: Disabling SELinux reduces security and does not fix the underlying label issue.
- B
Change the file ownership to root:root using chown.
Why wrong: Changing ownership to root would prevent the apache user from reading the file.
- C
Execute restorecon -R /var/www/html to restore SELinux contexts.
Restores default SELinux labels, which may have been corrupted during power loss.
- D
Set the SELinux boolean httpd_can_network_connect to on.
Why wrong: This boolean controls network connections, not file system access.
Quick Answer
The answer is to execute `restorecon -R /var/www/html` to restore SELinux contexts. This is correct because the `httpd permission denied SELinux enforcing fix` requires resetting the file’s security context to `httpd_sys_content_t`, which Apache needs to read web content. After a power loss, SELinux contexts on files can revert or become corrupted even when standard Linux permissions (like `-rw-r--r--` and `apache:apache` ownership) appear correct. On the CompTIA Linux+ XK0-005 exam, this scenario tests your understanding that SELinux enforces its own labeling system independent of `chmod` or `chown`; a common trap is trying `chcon` manually or restarting httpd without addressing the context. Remember: when SELinux is enforcing and Apache gets “Permission denied,” the first diagnostic step is checking the context with `ls -Z`, and the fix is `restorecon`—think “restore the context, not the permissions.”
XK0-005 Troubleshooting Practice Question
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 CentOS 7 web server experienced an abrupt power loss. Upon reboot, the httpd service fails to start. The administrator runs `systemctl status httpd` and sees 'Active: failed (Result: exit-code)'. The journal displays 'Permission denied: "/var/www/html/index.html"'. The file `/var/www/html/index.html` has permissions `-rw-r--r--` and is owned by `apache:apache`. SELinux is in enforcing mode. Which action should the administrator take to resolve the issue?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Execute restorecon -R /var/www/html to restore SELinux contexts.
The httpd service fails because SELinux is in enforcing mode and the file /var/www/html/index.html has an incorrect SELinux context, likely httpd_sys_content_t. The restorecon -R /var/www/html command restores the default SELinux security contexts for the directory and its contents, allowing Apache to read the file. This is the standard fix when SELinux contexts are lost or corrupted, such as after a power loss or file restoration.
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.
- ✗
Disable SELinux temporarily with setenforce 0.
Why it's wrong here
Disabling SELinux reduces security and does not fix the underlying label issue.
- ✗
Change the file ownership to root:root using chown.
Why it's wrong here
Changing ownership to root would prevent the apache user from reading the file.
- ✓
Execute restorecon -R /var/www/html to restore SELinux contexts.
Why this is correct
Restores default SELinux labels, which may have been corrupted during power loss.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Set the SELinux boolean httpd_can_network_connect to on.
Why it's wrong here
This boolean controls network connections, not file system access.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse file permissions (rw-r--r--) with SELinux contexts, or assume ownership changes are needed, when the real issue is a missing or incorrect SELinux label that restorecon fixes.
Detailed technical explanation
How to think about this question
SELinux contexts are stored as extended attributes (security.selinux) on the filesystem. When a file is moved or created without proper context, or after a power loss that corrupts metadata, the context may default to unconfined_u:object_r:unlabeled_t or a non-httpd type. The restorecon command uses the file_contexts database to apply the correct type (e.g., httpd_sys_content_t for /var/www/html), which is essential for Apache to read files under SELinux enforcing mode.
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 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
Got this wrong? Here's your next step.
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
Related XK0-005 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Security practice questions
Practise XK0-005 questions linked to Security.
Troubleshooting practice questions
Practise XK0-005 questions linked to Troubleshooting.
Scripting, Containers and Automation practice questions
Practise XK0-005 questions linked to Scripting, Containers and Automation.
System Management practice questions
Practise XK0-005 questions linked to System Management.
XK0-005 fundamentals practice questions
Practise XK0-005 questions linked to XK0-005 fundamentals.
XK0-005 scenario practice questions
Practise XK0-005 questions linked to XK0-005 scenario.
XK0-005 troubleshooting practice questions
Practise XK0-005 questions linked to XK0-005 troubleshooting.
Practice this exam
Start a free XK0-005 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this XK0-005 question test?
Troubleshooting — This question tests Troubleshooting — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Execute restorecon -R /var/www/html to restore SELinux contexts. — The httpd service fails because SELinux is in enforcing mode and the file /var/www/html/index.html has an incorrect SELinux context, likely httpd_sys_content_t. The restorecon -R /var/www/html command restores the default SELinux security contexts for the directory and its contents, allowing Apache to read the file. This is the standard fix when SELinux contexts are lost or corrupted, such as after a power loss or file restoration.
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.
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 →
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.