EX200 Create and configure file systems Practice Question
Which TWO commands can be used to check the UUID of a filesystem on /dev/sda1?
⚠ Common exam trap
Test-takers frequently confuse `e2label` (which only handles labels) with UUID retrieval, or assume `findmnt` shows UUIDs by default when it actually requires explicit column selection.
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
✓
lsblk -o UUID /dev/sda1
The `blkid` command directly queries the UUID of a block device from the libblkid cache or by reading the filesystem superblock, and `lsblk -o UUID` filters the lsblk output to show only the UUID column for the specified device. Both commands reliably retrieve the UUID of /dev/sda1.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
e2label /dev/sda1
Why it's wrong here
e2label /dev/sda1 is a filesystem utility specifically for ext2/ext3/ext4 volume labels; it reads or sets the label stored in the superblock, not the UUID. The UUID is a separate 128-bit identifier in the same superblock, and e2label has no option to display it.
- ✗
findmnt /dev/sda1
Why it's wrong here
findmnt /dev/sda1 prints the mount relationship and defaults to columns like SOURCE, FSTYPE, MOUNTPOINT, and OPTIONS. It does not include UUID by default; you would have to explicitly add -o UUID, and even then it is a mount-aware wrapper, not the primary tool for querying raw device identifiers.
- ✓
lsblk -o UUID /dev/sda1
Why this is correct
lsblk -o UUID /dev/sda1 is correct because lsblk enumerates block devices and can output any column you request, including UUID. This works without mounting the filesystem and is a direct, efficient way to list the UUID for a specific device like /dev/sda1.
- ✓
blkid /dev/sda1
Why this is correct
blkid /dev/sda1 is correct because blkid is the classic utility for probing block devices and reporting filesystem metadata, including UUID and TYPE. It reads the identification data directly from the device and is widely available in RHEL and other Linux systems.
- ✗
file -s /dev/sda1
Why it's wrong here
file -s /dev/sda1 inspects the raw data on the device and identifies the filesystem type (for example, 'Linux rev 1.0 ext4 filesystem data'), but it is not designed to extract or display a UUID. Its purpose is file type magic detection, not filesystem attribute lookup.
Go deeper
Related to this question
About these practice questions
One of 427 original EX200 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This EX200 practice question is part of Courseiva's free Red Hat 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 EX200 exam.