EX200 Create and configure file systems Practice Test 5 — 15 Questions

Question 1

Refer to the exhibit. A system administrator wants to add an additional mount option 'noexec' to the /boot filesystem permanently. Which step is necessary before remounting?

Accepted Answer

Edit /etc/fstab to add 'noexec' to the /boot entry, then run mount -o remount /boot. To make the 'noexec' mount option persistent for /boot, you must first edit /etc/fstab to add the option to the /boot entry. Then, running 'mount -o remount /boot' will remount the filesystem with the new options from fstab without needing to unmount it. This ensures the change survives reboots and is applied correctly.

Answer

Run mount -o remount,noexec /boot without editing /etc/fstab

Answer

Run umount /boot, edit /etc/fstab to add 'noexec', then mount /boot

Answer

Edit /etc/fstab to add 'noexec' to the /boot entry, then run mount -a

Question 2

Refer to the exhibit. An administrator extends an XFS filesystem on /data. Which prerequisite step is missing from the output?

Accepted Answer

The filesystem must be mounted before xfs_growfs. The xfs_growfs command requires the XFS filesystem to be mounted because it operates on a live filesystem, resizing it to match the underlying block device. The exhibit shows the administrator running xfs_growfs without first mounting /data, which is the missing prerequisite step. Without mounting, xfs_growfs cannot access the filesystem's superblock to perform the resize.

Answer

The filesystem must be checked with xfs_repair before growing

Answer

The filesystem must be unmounted before xfs_growfs

Answer

The logical volume must be deactivated before xfs_growfs

Question 3

Refer to the exhibit. The filesystem /var/www/html is mounted, but after a reboot, the directory is empty. What is the most likely cause?

Accepted Answer

The logical volume is not activated at boot because the volume group is not set to auto-activate. If the volume group containing the logical volume is not set to auto-activate, the logical volume will not be available after reboot, causing the mount to fail silently or the filesystem to appear empty. The `auto_activation_volume_list` in `/etc/lvm/lvm.conf` controls which volume groups are activated automatically at boot; if the VG is excluded, the LV never becomes visible to the system.

Answer

The filesystem type is incorrectly specified as ext4 in fstab

Answer

The mount point /var/www/html does not exist after reboot

Answer

The device path /dev/vg_data/lv_web is not persistent across reboots

Question 4

Refer to the exhibit. A client at 10.0.0.5 tries to mount /export/restricted but receives 'Permission denied'. What is the issue?

Accepted Answer

The client IP 10.0.0.5 is not in the allowed subnet 192.168.1.0/24. The client at 10.0.0.5 is attempting to mount /export/restricted. The /etc/exports file restricts access to 192.168.1.0/24. Since 10.0.0.5 is not included in that subnet, the NFS server denies the mount with 'Permission denied'. There is no evidence that the entry is missing or that a re-export is needed; the issue is network access control.

Answer

The client's IP is in the allowed subnet but the export entry for /export/restricted is missing from /etc/exports after a change and not re-exported

Answer

The export uses root_squash which maps root to nobody, causing permission issues

Answer

The export /export/restricted has ro (read-only) and the client might be trying to write

Question 5

An administrator needs to add a 1GB swap partition on /dev/sdd1. Which series of commands accomplishes this?

Accepted Answer

fdisk /dev/sdd, create partition, then mkswap /dev/sdd1, swapon /dev/sdd1, and add to /etc/fstab.. It includes all necessary steps: first create the partition with fdisk (since /dev/sdd1 does not exist yet), then format it as swap with mkswap, activate it with swapon, and finally add an entry to /etc/fstab to ensure persistence across reboots. The other options omit the critical partition creation step or fail to make the swap permanent.

Answer

mkswap /dev/sdd1 && echo '/dev/sdd1 swap swap defaults 0 0' >> /etc/fstab

Answer

mkfs.swap /dev/sdd1 && swapon /dev/sdd1

Answer

mkswap /dev/sdd1 && swapon /dev/sdd1

Question 6

A filesystem is reported as 'read-only' after a system crash. The admin runs fsck and sees 'clean' status. What is the most likely reason it remains read-only?

Accepted Answer

The filesystem is XFS, and fsck does not repair XFS.. If fsck reports 'clean', it means no errors were found in the filesystem's journal, so option D is incorrect. Option C is correct because XFS filesystems cannot be repaired by fsck; they require xfs_repair. Running fsck on an XFS filesystem simply reports the clean flag without performing a real check, leaving the kernel to enforce read-only status if any issues persist.

Answer

fsck cannot fix errors on ext4 filesystems.

Answer

The filesystem is still mounted; fsck cannot fix it while mounted.

Answer

fsck detected errors but did not fix them automatically.

Question 7

Which TWO commands are valid for resizing an XFS file system? (Choose exactly two.)

Accepted Answer

xfs_growfs /mnt. `xfs_growfs` is the dedicated command for resizing (growing) an XFS file system while it is mounted. It expands the file system to fill the available space in the underlying device or logical volume, making it the primary tool for XFS resizing operations.

Answer

xfs_admin -L /mnt

Answer

resize2fs /dev/sda1

Answer

xfs_repair /dev/sda1

Question 8

A system administrator needs to create a file system on a new 10GB partition /dev/sdb1 for use with a database that requires high reliability and supports snapshots. Which file system type should be chosen?

Accepted Answer

xfs. XFS is the correct choice because it is a high-performance, 64-bit journaling file system that supports snapshots via LVM or external tools, and is designed for large files and partitions. For a database requiring high reliability and snapshot capabilities, XFS provides robust data integrity features and is the default file system in Red Hat Enterprise Linux 8 and later, making it the recommended option for this scenario.

Answer

ext4

Answer

vfat

Answer

btrfs

Question 9

A technician runs 'mkfs.xfs /dev/sdb1' and later mounts it. The file system is reported as having a block size of 1024 bytes. What is the most likely reason?

Accepted Answer

The partition size is less than 1GB, so mkfs.xfs automatically used a 1024-byte block size.. Mkfs.xfs automatically selects a 1024-byte block size when the underlying partition is smaller than 1 GB. This is a built-in heuristic in the XFS filesystem to optimize metadata overhead and space utilization on small volumes. The technician did not specify a block size, so the tool applied this default behavior based on partition size.

Answer

The administrator used the -b size=1024 option.

Answer

The block size setting was ignored due to a kernel limitation.

Answer

The default block size for XFS is 1024 bytes.

Question 10

Which command displays the UUID of all file systems on the system?

Accepted Answer

blkid. The `blkid` command is the correct choice because it is specifically designed to locate and display block device attributes, including the UUID, filesystem type, and label, for all filesystems on the system. It reads data from the `/dev/disk/by-uuid/` directory and the `udev` database, making it the most direct and reliable tool for querying UUIDs without requiring root privileges for basic output.

Answer

dumpe2fs -h

Answer

lsblk

Answer

fdisk -l

Question 11

An administrator wants to ensure that a file system is automatically mounted at boot. Which file should be edited?

Accepted Answer

/etc/fstab. The /etc/fstab file is the standard configuration file that defines how disk partitions, block devices, and remote filesystems should be mounted into the filesystem tree, including options for automatic mounting at boot time. The system reads this file during the boot process (via systemd or the traditional mount -a command) to mount all filesystems listed with the 'auto' or nofail option.

Answer

/etc/rc.local

Answer

/boot/grub2/grub.cfg

Answer

/etc/mtab

Question 12

A server has an LVM volume group vg01 with a physical volume /dev/sdb. The administrator wants to move all physical extents from /dev/sdb to /dev/sdd which is also in the same volume group. Which command sequence is correct?

Accepted Answer

pvmove /dev/sdb; vgreduce vg01 /dev/sdb. The correct sequence is to first use `pvmove /dev/sdb` to relocate all physical extents from /dev/sdb to other physical volumes in the same volume group (vg01), and then use `vgreduce vg01 /dev/sdb` to remove the now-empty physical volume from the volume group. This ensures no data loss and that the volume group metadata is properly updated.

Answer

vgreduce vg01 /dev/sdb; pvmove

Answer

pvmove /dev/sdb; pvremove /dev/sdb

Answer

pvmove /dev/sdb /dev/sdd

Question 13

In /etc/fstab, which values in the dump and pass fields enable automatic file system checking at boot?

Accepted Answer

dump=0, pass=1. The `pass` field in `/etc/fstab` controls the order of file system checks at boot. A value of 1 means the root file system is checked first, and a value of 2 or higher means other file systems are checked after root. The `dump` field is for backup utility (dump) and is not related to boot-time checking; it must be 0 to disable dump. Thus, `dump=0, pass=1` enables automatic file system checking (fsck) at boot for the root file system.

Answer

dump=1, pass=0

Answer

dump=0, pass=0

Answer

dump=1, pass=1

Question 14

The administrator attempts to run 'xfs_growfs /dev/vg00/lvol1' but receives an error. What is the most likely cause?

Accepted Answer

The logical volume is not mounted. The `xfs_growfs` command requires the XFS filesystem to be mounted in order to resize it. If the logical volume `/dev/vg00/lvol1` is not mounted, the kernel cannot access the filesystem's superblock and allocation group information, causing the command to fail with an error such as 'XFS filesystem not mounted' or 'No such file or directory'.

Answer

The file system is not XFS

Answer

Unmet dependencies

Answer

The volume group is full

Question 15

The administrator wants to reduce the file system size to 40GB. Which command sequence should be used?

Accepted Answer

It is not possible to shrink an XFS file system. XFS is a high-performance 64-bit journaling file system that does not support online or offline shrinking. Once an XFS file system is created, its size cannot be reduced; the only way to reclaim space is to back up the data, destroy the file system, recreate it at the desired size, and restore the data. Therefore, any attempt to shrink an XFS file system using lvreduce or similar tools will corrupt the file system.

Answer

xfs_repair; lvreduce

Answer

umount /mnt/data; lvreduce -L 40G; mount; xfs_growfs

Answer

lvreduce -L 40G /dev/vg00/lvol0; xfs_growfs