Question 650
A Linux administrator evaluates: A Linux administrator wants to prove an access denied fault is due to labels rather than the directory execute bit. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A Linux administrator wants to prove an access denied fault is due to labels rather than the directory execute bit), the acceptance evidence is: The target service accesses its file with enforcing mode active and no matching denial appears in new audit events. This verifies the action (Correlate AVC records, file labels and discretionary file ownership before selecting a context-specific SELinux remediation.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Turning SELinux off or using chmod 777 cannot reliably solve a labeling issue and can weaken host security.
The observed Linux condition is: A Linux administrator wants to prove an access denied fault is due to labels rather than the directory execute bit. The recommended direct administrative response is: Correlate AVC records, file labels and discretionary file ownership before selecting a context-specific SELinux remediation. The relevant failure or security risk is: Turning SELinux off or using chmod 777 cannot reliably solve a labeling issue and can weaken host security. Validate success with: The target service accesses its file with enforcing mode active and no matching denial appears in new audit events.
Incorrect Answers
SLO-based monitoring and actionable alert thresholds (5.1) would demonstrate or implement: A controlled service degradation crosses the documented threshold and produces an actionable alert with the relevant host and timestamp. This choice can be useful for that problem, but it does not establish the SELinux denial versus traditional permission fault control being assessed here.
Linux boot failure recovery using journal and GRUB evidence (5.2) addresses another technical failure: Blindly reinstalling the kernel or disabling essential units can destroy the evidence and leave the actual root-device fault unresolved. This case instead tests SELinux denial versus traditional permission fault; the choice measures or changes another part of the system.
MTU and path fragmentation troubleshooting (5.3) would demonstrate or implement: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. The paired-answer requirement concerns SELinux denial versus traditional permission fault; this alternative does not provide the matching intervention and separate acceptance evidence.