Question 470
In a Linux incident, an engineer reports: A service account needs a directory mounted read-only but the current mount is writable. Which technical explanation BEST accounts for it?
Explanation
Correct Answer
File permission bits alone differ from a filesystem-level read-only mount. This mechanism fits the stated evidence. Validate it by checking that attempts to modify files through the mount fail as expected.
Incorrect Answers
The alternative describes xFS growth is performed on the mounted filesystem with xfs_growfs, which is relevant when an XFS filesystem on a grown logical volume still reports its former size. It does not explain this case because file permission bits alone differ from a filesystem-level read-only mount.
It would account for a maintenance script runs fsck against a writable mounted ext4 root filesystem, not the current evidence. For this incident, file permission bits alone differ from a filesystem-level read-only mount; the alternative mechanism leaves that distinction unexplained.
A writable filesystem does not inherently have to permit direct execution. That can explain why a shared scratch filesystem allows users to execute uploaded binaries contrary to policy, whereas the current evidence supports the ro mount option restricts writes through the mounted filesystem.





CompTIA Linux+ (XK0-006) Practice Tests