Question 780
Original unofficial RHEL 10 RHCSA skill-check scenario: A service uses a bind-mounted directory with mismatched ownership after a deployment. Which ongoing practice best prevents a recurrence?
Explanation
Correct Answer
In this RHEL 10 system administration case: A service uses a bind-mounted directory with mismatched ownership after a deployment. Underlying reason: A bind mount exposes the source filesystem's permissions at another path. The most direct, approved resolution is: Compare the actual mounted source and service account IDs before correcting scoped ownership. Confirm it by checking: The service reads its data and other users retain limited access. Sustain the fix by: Test mount-source identity and ownership after deployments. This is the INTENDED response for the best ongoing operational safeguard. It is a knowledge-check explanation, not a verified hands-on Red Hat exam answer;
Incorrect Answers
Include parent-directory checks in permission troubleshooting. That is not sufficient for the reported RHEL task, because a bind mount exposes the source filesystem's permissions at another path.
Audit mount source and target pairs after changes. That is not sufficient for the reported RHEL task, because a bind mount exposes the source filesystem's permissions at another path.
Check filesystem type before resize commands. That is not sufficient for the reported RHEL task, because a bind mount exposes the source filesystem's permissions at another path.