Question 580
For this Linux administration lab: A team creates an NFS mount locally but cannot write files despite apparently open Unix mode bits. Which safety and lifecycle check best prevents the same problem returning?
Explanation
Correct Answer
Use consistent UID/GID mapping and least-privilege export settings. This guards against recurrence of: NFS access depends on remote export policy and identity mapping in addition to client-side mode bits. Confirm the lab's final state by: A permitted test user writes successfully without using insecure world-writable modes.
Incorrect Answers
Test boot and reconnect behavior with the NFS server intentionally offline in the lab. That control is best suited to a separate scenario: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. It is not the best safeguard for the current mechanism: NFS access depends on remote export policy and identity mapping in addition to client-side mode bits.
Never format before confirming the exact blank lab device and backup status. That control is best suited to a separate scenario: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. It is not the best safeguard for the current mechanism: NFS access depends on remote export policy and identity mapping in addition to client-side mode bits.
Inspect mount users and coordinate termination before maintenance unmounts. That control is best suited to a separate scenario: A student tries to unmount an NFS training mount while another process has its current directory inside it. It is not the best safeguard for the current mechanism: NFS access depends on remote export policy and identity mapping in addition to client-side mode bits.