Question 360
A Linux administrator evaluates: A temporary chcon fix disappears after relabeling and operations must create a persistent context rule. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A temporary chcon fix disappears after relabeling and operations must create a persistent context rule. The recommended direct administrative response is: Inspect SELinux enforcement and AVC denials; restore or assign the correct context or supported boolean instead of disabling SELinux. The relevant failure or security risk is: Changing enforcing to disabled hides the mislabeled resource and weakens access controls for unrelated services. Validate success with: The service works with SELinux enforcing and its resources have persistent expected contexts without repeated AVC denials.
For the specific observation (A temporary chcon fix disappears after relabeling and operations must create a persistent context rule), the acceptance evidence is: The service works with SELinux enforcing and its resources have persistent expected contexts without repeated AVC denials. This verifies the action (Inspect SELinux enforcement and AVC denials; restore or assign the correct context or supported boolean instead of disabling SELinux.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Changing enforcing to disabled hides the mislabeled resource and weakens access controls for unrelated services.
Incorrect Answers
Stateful nftables filtering and IP forwarding (3.2) would demonstrate or implement: Accepting unrestricted forwarding or dropping established return packets can either expose networks or break allowed flows. The case states: A temporary chcon fix disappears after relabeling and operations must create a persistent context rule. The most direct paired action and test is: Inspect SELinux enforcement and AVC denials; restore or assign the correct context or supported boolean instead of disabling SELinux.
Linux audit trails with auditd and journalctl (3.1) would demonstrate or implement: A controlled policy event has the intended principal, action, timestamp and searchable retained record. The required paired action and test concerns SELinux context and boolean troubleshooting; a passing result for this alternative could leave that requirement unresolved.
PAM and SSSD identity authentication diagnosis (3.1) addresses another technical failure: A valid directory password cannot bypass a missing NSS identity mapping or restrictive PAM account policy. The paired-answer requirement concerns SELinux context and boolean troubleshooting; this alternative does not provide the matching intervention and separate acceptance evidence.