LPIC-1 Devices, Filesystems and FHS Practice Question
Exhibit
$ lsblk -o NAME,FSTYPE,LABEL,MOUNTPOINT NAME FSTYPE LABEL MOUNTPOINT sda ├─sda1 ext4 boot /boot ├─sda2 ext4 root / ├─sda3 swap swap [SWAP] └─sda4 ext4 data /mnt/data sdb └─sdb1 ext4 backup /mnt/backup $ blkid /dev/sda4 /dev/sda4: UUID="abc-123" TYPE="ext4" LABEL="data"
Refer to the exhibit. An administrator wants to mount /dev/sda4 persistently by its UUID. Which line should be added to /etc/fstab?
⚠ Common exam trap
Many exam-takers choose the device path option (D) out of habit, forgetting that device names are not persistent, or they confuse the 'noauto' option (B) as a valid way to mount persistently, when in fact it prevents automatic mounting.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
UUID=abc-123 /mnt/data ext4 defaults 0 2
It uses the UUID= syntax to identify the filesystem by its universally unique identifier, which is the persistent method requested. The mount point is /mnt/data, the filesystem type is ext4, the mount options are defaults, and the dump and fsck order values (0 and 2) are appropriate for a non-root filesystem. This line ensures the device is mounted automatically at boot regardless of device name changes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
UUID=abc-123 /mnt/data ext4 defaults 0 2
Why this is correct
The UUID= form identifies the filesystem independently of device name ordering, which /dev/sda4 cannot guarantee across reboots. Field six set to 2 schedules fsck after root, and ext4 with defaults matches the filesystem, giving a persistent, correctly ordered mount.
- ✗
UUID=abc-123 /mnt/data ext4 noauto 0 2
Why it's wrong here
The noauto option prevents the filesystem from being mounted at boot, contradicting the requirement for a persistent mount. noauto suits removable or on-demand filesystems; a UUID entry intended to mount automatically needs default options instead.
- ✗
LABEL=data /mnt/data ext4 defaults 0 2
Why it's wrong here
The LABEL= form resolves a filesystem label, not a UUID, so it fails the requirement to mount by UUID. Labels are valid fstab identifiers when a volume carries a unique label, but the stem explicitly demands UUID-based persistence.
- ✗
/dev/sda4 /mnt/data ext4 defaults 0 2
Why it's wrong here
Specifying /dev/sda4 mounts by device node, which can shift between boots, so the UUID requirement is unmet. It is tempting because device paths are the traditional fstab format and work fine on stable hardware; UUID= entries exist precisely to survive device reordering.
Go deeper
Related to this question
About these practice questions
Courseiva writes every LPIC-1 question from scratch — 402 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This LPIC-1 practice question is part of Courseiva's free LPI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LPIC-1 exam.