Question 320
After completing this practical task on a disposable RHEL10 training node: A trainee enables an SELinux Boolean with `setsebool` but loses the change after restart. Which operational safeguard helps keep the result correct and safe?
Explanation
Correct Answer
Use persistent Boolean changes only when justified and test their effects after restart. This guards against recurrence of: `setsebool` without `-P` changes runtime policy only. Confirm the lab's final state by: The Boolean remains on after reboot and `getsebool` confirms the value.
Incorrect Answers
Verify port-label assignment and firewall exposure separately for nonstandard listener ports. That control is best suited to a separate scenario: A test web daemon is configured to listen on TCP 8088 but SELinux blocks binding despite a matching firewall rule. It is not the best safeguard for the current mechanism: `setsebool` without `-P` changes runtime policy only.
Check existing assignments before modifying SELinux port labels. That control is best suited to a separate scenario: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. It is not the best safeguard for the current mechanism: `setsebool` without `-P` changes runtime policy only.
Keep a verified break-glass console path before tightening authentication methods. That control is best suited to a separate scenario: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. It is not the best safeguard for the current mechanism: `setsebool` without `-P` changes runtime policy only.