LFCS Storage Management Practice Question
Which TWO commands can be used to mount a filesystem on /dev/sdb1 to /mnt/data?
⚠ Common exam trap
Linux Foundation often tests the argument order of the mount command, trapping candidates who confuse the device and mount point positions, especially when combined with options like `-t` or `-o`.
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
✓
mount /dev/sdb1 /mnt/data
Option B is correct because the standard mount syntax is `mount <device> <mountpoint>`, so `mount /dev/sdb1 /mnt/data` mounts the block device /dev/sdb1 onto the existing directory /mnt/data. Option C is also correct because adding `-t ext4` explicitly specifies the filesystem type, and the device-then-mountpoint order remains valid, so `mount -t ext4 /dev/sdb1 /mnt/data` successfully mounts the ext4 filesystem. Option A is wrong because it reverses the arguments, treating /mnt/data as the device and /dev/sdb1 as the mountpoint. Option D is wrong because `-o loop` is used to mount a regular file as a loopback device, not a real block device like /dev/sdb1. Option E is wrong because it combines an unnecessary `-t auto` with `-o loop`, which is inappropriate for mounting a physical partition.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
mount /mnt/data /dev/sdb1
Why it's wrong here
The arguments are reversed: mount expects the device first and the mount point second, so it attempts to mount /mnt/data onto /dev/sdb1. It is tempting because both operands appear, and the syntax would be right if the source and target were swapped.
- ✓
mount /dev/sdb1 /mnt/data
Why this is correct
The two-argument form lets mount auto-detect the filesystem type from the device's superblock, then attach /dev/sdb1 at /mnt/data. No type or options are required, satisfying the requirement to mount that specific block device at that mount point.
- ✓
mount -t ext4 /dev/sdb1 /mnt/data
Why this is correct
The `-t ext4` flag explicitly declares the filesystem type, so the kernel invokes the ext4 driver rather than probing. This satisfies the stem's requirement to mount the specific block device `/dev/sdb1` at the `/mnt/data` mount point, and works even when automatic detection is unavailable or ambiguous.
- ✗
mount -o loop /dev/sdb1 /mnt/data
Why it's wrong here
The -o loop flag forces a loop device, which only applies to regular files such as ISO images, not to the block device /dev/sdb1. It is tempting because loop mounting is the correct approach when attaching a disk image file instead of a physical partition.
- ✗
mount -t auto /dev/sdb1 /mnt/data -o loop
Why it's wrong here
The -o loop flag binds the mount to a regular file through a loop device, which /dev/sdb1 is not, so the mount fails. It is tempting because loop mounting is genuinely required when attaching an ISO or disk image file rather than a block device.
Visual reference
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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.