Question 680
Following lab verification, document the preventive or persistence-oriented procedure for: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. Which practice is most suitable?
Explanation
Correct Answer
Use a sticky bit and cleanup policy on any intentionally shared writeable scratch area. This guards against recurrence of: The sticky bit constrains unlink and rename in a shared writable directory. Confirm the lab's final state by: Two test users can create files but one cannot remove the other's file without applicable privilege.
Incorrect Answers
Use consistent UID/GID mapping and least-privilege export settings. That control is best suited to a separate scenario: A team creates an NFS mount locally but cannot write files despite apparently open Unix mode bits. It is not the best safeguard for the current mechanism: The sticky bit constrains unlink and rename in a shared writable directory.
Validate map syntax and restart/enable autofs after controlled changes. That control is best suited to a separate scenario: A large remote home-directory NFS tree should mount on demand rather than all at login. It is not the best safeguard for the current mechanism: The sticky bit constrains unlink and rename in a shared writable directory.
Include filesystem shrink capability in capacity design decisions before provisioning. That control is best suited to a separate scenario: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. It is not the best safeguard for the current mechanism: The sticky bit constrains unlink and rename in a shared writable directory.