The answer is that the /logs entry is missing from /etc/fstab. This is the most likely cause because Linux relies entirely on the /etc/fstab file to know which filesystems to mount automatically at boot time. When the administrator manually mounted the logical volumes after creating them, those mounts were temporary and not recorded for persistence. After a reboot, the system reads /etc/fstab to mount all filesystems, and if the /logs entry is absent, the mount fails silently or with an error. On the Red Hat Certified System Administrator EX200 exam, this scenario tests your understanding of LVM mount persistence and the critical role of /etc/fstab in managing filesystem mounts across reboots. A common trap is assuming that a manual mount command will survive a reboot, or that formatting a logical volume automatically creates an fstab entry. Remember: manual mounts are ephemeral; only fstab entries are permanent. A helpful memory tip is “FSTAB for STABLE”—if it’s not in fstab, it won’t survive a reboot.
EX200 Configure local storage Practice Question
This EX200 practice question tests your understanding of configure local storage. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A system administrator is setting up storage for a new application server. The application requires two separate filesystems: one for the database (needs to be at least 10GiB) and one for logs (needs at least 5GiB). The server has a single 20GiB disk /dev/sda. The administrator plans to use LVM and a single volume group 'vg_app'. They create physical volume on /dev/sda, create the volume group, and then create two logical volumes: 'lv_db' of 10GiB and 'lv_logs' of 5GiB. They format lv_db as ext4 and lv_logs as xfs, and mount them at /db and /logs respectively. After rebooting, the system fails to mount /logs. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Clue: "least"
Why it matters: You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The /logs entry is missing from /etc/fstab.
The most likely cause is that the /logs entry is missing from /etc/fstab. After reboot, the system relies on /etc/fstab to mount filesystems automatically. Since the administrator created and mounted the filesystem manually, but did not add an entry for /logs in /etc/fstab, the mount fails on reboot. The database mount may succeed if it was added, but the logs mount fails due to the missing fstab entry.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The logical volume 'lv_logs' overlaps with 'lv_db'.
Why it's wrong here
LVM does not allow overlapping LVs; creation would have failed.
✓
The /logs entry is missing from /etc/fstab.
Why this is correct
Without an fstab entry, the filesystem won't mount automatically at boot.
Clue confirmation
The clue words "most likely", "least" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The physical volume /dev/sda is not recognized by LVM after reboot.
Why it's wrong here
LVM scan at boot typically recognizes PVs; this is unlikely the cause.
✗
The volume group 'vg_app' is not automatically activated.
Why it's wrong here
By default, LVM activates VGs at boot; this is unlikely.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Red Hat often tests the misconception that LVM volumes are automatically mounted after creation, when in fact only the logical volumes are activated; the filesystem mount must be explicitly configured in /etc/fstab.
Detailed technical explanation
How to think about this question
LVM metadata is stored in the first few sectors of each physical volume, allowing the kernel to discover PVs, VGs, and LVs automatically at boot. The systemd unit lvm2-activation.service runs lvm vgchange -a y to activate all volume groups. However, even if the logical volumes are active, the system will not mount filesystems unless corresponding entries exist in /etc/fstab. The mount command with no options or a reboot will fail for any filesystem not listed in fstab. In real-world scenarios, administrators often forget to update fstab after creating new LVs, leading to mount failures on reboot.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the EX200 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Configure local storage — This question tests Configure local storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The /logs entry is missing from /etc/fstab. — The most likely cause is that the /logs entry is missing from /etc/fstab. After reboot, the system relies on /etc/fstab to mount filesystems automatically. Since the administrator created and mounted the filesystem manually, but did not add an entry for /logs in /etc/fstab, the mount fails on reboot. The database mount may succeed if it was added, but the logs mount fails due to the missing fstab entry.
What should I do if I get this EX200 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely", "least". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An administrator needs to ensure that a specific LVM logical volume is automatically mounted at boot with the 'noexec' option. Which configuration file and entry should be used?
hard
A./etc/fstab: /dev/vg/lv /mnt ext4 noexec 0 0
B./etc/rc.d/rc.local: mount /dev/vg/lv /mnt -o noexec
Why C: Option C is correct because /etc/fstab is the standard configuration file for defining filesystem mount points and options that are applied automatically at boot. The entry specifies the logical volume device, mount point, filesystem type, and mount options including 'noexec' to prevent execution of binaries on that filesystem. The 'defaults' keyword ensures standard mount behavior is applied before the 'noexec' option overrides the exec permission.
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.