The answer is that the most likely reason is traditional Linux file permissions or ACLs, not SELinux. When you run `setenforce 0`, you switch SELinux to permissive mode, where it logs denials but does not enforce them; if access is still denied after this command, the issue cannot be SELinux enforcement, so you must look at the Discretionary Access Control (DAC) system—standard file permissions and ACLs. On the Red Hat Certified System Administrator EX200 exam, this scenario tests your ability to isolate SELinux from DAC issues, a common trap where candidates blame SELinux without verifying `ls -l` or `getfacl`. Remember the troubleshooting order: always check file ownership and permissions first, then SELinux context, because `setenforce 0` is your definitive test—if it fails to fix the denial, the problem lies in DAC, not SELinux. A handy memory tip: “Permissive proves permissions.”
EX200 Manage security Practice Question
This EX200 practice question tests your understanding of manage security. 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 runs 'getenforce' and sees 'Enforcing'. They then run 'setenforce 0' but SELinux still denies access to a custom application. What is the most likely reason?
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 issue is due to file permissions or ACLs, not SELinux.
Option C is correct because `setenforce 0` switches SELinux to permissive mode, which logs but does not enforce denials. If access is still denied after this command, the issue is not caused by SELinux enforcement but by traditional Linux file permissions (DAC) or ACLs. The administrator should check `ls -l` and `getfacl` to verify the file's ownership and permissions.
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.
✗
SELinux is in enforcing mode and the policy is misconfigured.
Why it's wrong here
setenforce 0 changes to permissive; enforcement stops.
✗
The application's SELinux context is incorrect and needs relabeling.
Why it's wrong here
Even with wrong context, permissive mode allows access.
✓
The issue is due to file permissions or ACLs, not SELinux.
Why this is correct
In permissive mode, SELinux does not deny; thus the denial is from DAC.
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 change requires a reboot to take effect.
Why it's wrong here
setenforce is immediate; no reboot needed.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume any denial after `setenforce 0` must still be SELinux-related, overlooking that traditional Linux permissions (DAC) operate independently and can block access even when SELinux is permissive.
Detailed technical explanation
How to think about this question
SELinux has three modes: enforcing, permissive, and disabled. The `setenforce` command changes the mode at runtime without a reboot, writing to `/sys/fs/selinux/enforce`. In permissive mode, SELinux still checks policy and logs denials (via `audit.log` or `avc` messages) but does not block access. This allows administrators to distinguish between SELinux denials and DAC permission issues. A common real-world scenario is when a custom application fails due to incorrect file ownership (e.g., running as a non-root user without read/write access) while SELinux is already permissive.
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 security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
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.
Manage security — This question tests Manage security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The issue is due to file permissions or ACLs, not SELinux. — Option C is correct because `setenforce 0` switches SELinux to permissive mode, which logs but does not enforce denials. If access is still denied after this command, the issue is not caused by SELinux enforcement but by traditional Linux file permissions (DAC) or ACLs. The administrator should check `ls -l` and `getfacl` to verify the file's ownership and permissions.
What should I do if I get this EX200 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 EX200 practice question is part of Courseiva's free Red Hat 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 EX200 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.