XK0-005 · Question #131
XK0-005 Question #131: Real Exam Question with Answer & Explanation
The correct answer is B: Change the options to auto,dev,sync,rw,nosuid and run the mount -a command.. To fix a filesystem refusal to mount after being added to /etc/fstab, the administrator should ensure correct mount options are specified, such as auto,dev,sync,rw,nosuid, and then execute mount -a to apply the changes.
Question
A junior systems administrator created a new filesystem /dev/sda1 with mountpoint /data and added it to the /etc/fstab for auto-mounting. When the systems administrator tries to mount the file system, the system refuses. Given the output below: Which of the following steps is necessary?
Options
- AChange the filesystem from /dev/sda1 to /dev/sda2 and reboot.
- BChange the options to auto,dev,sync,rw,nosuid and run the mount -a command.
- CChange the mount point to data and reboot.
- DChange the dump column to 1 and run the mount -a command.
Explanation
To fix a filesystem refusal to mount after being added to /etc/fstab, the administrator should ensure correct mount options are specified, such as auto,dev,sync,rw,nosuid, and then execute mount -a to apply the changes.
Common mistakes.
- A. Changing the filesystem from
/dev/sda1to/dev/sda2is an arbitrary device change without justification and would not resolve anfstaboption issue. - C. Changing the mount point to
data(a relative path) is incorrect; mount points must be absolute paths (e.g.,/data), and the existing/datais already valid. - D. Changing the dump column (the 5th field in
/etc/fstab) to1enablesdumputility backups, which has no bearing on the ability of the filesystem to mount.
Concept tested. Correcting /etc/fstab entries for mounting
Reference. https://man7.org/linux/man-pages/man5/fstab.5.html
Topics
Community Discussion
No community discussion yet for this question.