LFCS Storage Management Practice Question
A server has a new disk /dev/sdd that must be mounted at /backup and automatically mounted at boot. The administrator creates a GPT partition table, a single partition /dev/sdd1, and an ext4 filesystem. Which /etc/fstab entry correctly uses a persistent identifier for the filesystem?
⚠ Common exam trap
The trap here is choosing a device path like /dev/sdd1, which looks simple and works immediately but is not persistent across hardware changes.
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=1234-abcd /backup ext4 defaults 0 2
Persistent mounting in /etc/fstab should use a stable identifier such as UUID= or LABEL= rather than a kernel device name. The entry must also specify the correct filesystem type and avoid options like noauto that prevent boot-time mounting. The UUID form with ext4 and a pass value of 2 satisfies all requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
LABEL=backup /backup xfs defaults 0 2
Why it's wrong here
A LABEL= entry can be persistent, but the filesystem type is listed as xfs while the administrator formatted the partition as ext4. The kernel would attempt to mount it as XFS and fail. Additionally, no label was set during mkfs, so the LABEL reference would not resolve.
- ✓
UUID=1234-abcd /backup ext4 defaults 0 2
Why this is correct
Using UUID= in /etc/fstab references the filesystem by its unique identifier, which remains stable even if device names change or disks are reordered. The mount point, filesystem type, options, and dump/pass fields are all valid. The pass value of 2 schedules fsck after the root filesystem during boot, which is appropriate for a non-root filesystem.
- ✗
/dev/sdd1 /backup ext4 defaults 0 2
Why it's wrong here
Referencing /dev/sdd1 directly is not persistent because device names can change when disks are added, removed, or reordered. The question explicitly asks for a persistent identifier. While this entry might work on the current boot, it risks mounting the wrong filesystem or failing to mount after hardware changes.
- ✗
UUID=1234-abcd /backup ext4 noauto 0 2
Why it's wrong here
The noauto option prevents the filesystem from being mounted automatically at boot, which directly contradicts the requirement that it be mounted automatically. The UUID and other fields are otherwise valid, but noauto defeats the purpose of the fstab entry for this scenario.
Go deeper
Related to this question
About these practice questions
This LFCS question is part of Courseiva's 406-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Linux Foundation exam blueprint
This LFCS practice question is part of Courseiva's free Linux Foundation 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 LFCS exam.