Use this page to practise Storage Management questions for this certification. Focus on how the exam tests storage management in scenario format — understanding the why behind each answer builds more durable knowledge than memorising options.
Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.
Which TWO commands can be used to create a new physical volume for use with LVM? (Choose two.)
Trap 1: mkfs.ext4 /dev/sdb1
mkfs creates a filesystem, not a PV.
Trap 2: pvresize /dev/sdb1
pvresize resizes an existing PV.
Trap 3: fdisk /dev/sdb (then set type to 8e)
This command creates a partition and sets its type to Linux LVM (8e), but does not create a physical volume. A separate `pvcreate` command is needed to initialize the partition as a PV.
Why wrong: This command creates a partition and sets its type to Linux LVM (8e), but does not create a physical volume. A separate `pvcreate` command is needed to initialize the partition as a PV.
E
pvdisplay /dev/sdb1
Why wrong: pvdisplay shows information, does not create.
A system administrator is tasked with setting up a new 2TB disk for a database server. The database requires high read/write performance and redundancy. The server has a hardware RAID controller, but the administrator wants to use Linux software RAID for flexibility. Which of the following RAID levels should the administrator choose to maximize performance while providing fault tolerance, assuming the disk will be part of a larger array in the future?
Trap 1: RAID 5
RAID 5 has write performance penalty due to parity calculation.
Trap 2: RAID 0
RAID 0 offers no fault tolerance, data loss if one disk fails.
Trap 3: RAID 6
RAID 6 has even greater write penalty than RAID 5.
An administrator wants to extend a logical volume named 'lv_data' in volume group 'vg_data' by 5GB. The volume group has free physical extents. Which command should be used?
Trap 1: pvextend -L +5G /dev/vg_data/lv_data
pvextend is not a valid LVM command; the correct command to extend a logical volume is lvextend.
Trap 2: lvresize -L +5G /dev/vg_data/lv_data
lvresize is a valid LVM command that can extend or reduce logical volumes, but lvextend is the more specific command for extension. While lvresize -L +5G achieves the same result, the question expects lvextend.
Trap 3: lvextend -L 5G /dev/vg_data/lv_data
lvextend -L 5G sets the new size to exactly 5GB instead of adding 5GB. The + prefix is required to add to the existing size.
Why wrong: pvextend is not a valid LVM command; the correct command to extend a logical volume is lvextend.
B
lvextend -L +5G /dev/vg_data/lv_data
Correct. lvextend -L +5G adds 5GB to the existing logical volume.
C
lvresize -L +5G /dev/vg_data/lv_data
Why wrong: lvresize is a valid LVM command that can extend or reduce logical volumes, but lvextend is the more specific command for extension. While lvresize -L +5G achieves the same result, the question expects lvextend.
D
lvextend -L 5G /dev/vg_data/lv_data
Why wrong: lvextend -L 5G sets the new size to exactly 5GB instead of adding 5GB. The + prefix is required to add to the existing size.
A storage administrator notices that a newly created XFS filesystem on a logical volume shows only 90% of the expected capacity. The logical volume is 100GB. What is the most likely cause?
Trap 1: The disk has bad blocks that were marked as unusable.
Bad blocks are not typically the cause of a consistent 10% reduction.
Trap 2: The volume group has insufficient physical extents.
The logical volume was created successfully, so VG has enough extents.
Trap 3: The filesystem is mounted with the 'noatime' option.
An administrator needs to mount an XFS filesystem with options to optimize for a database workload. Which mount option would reduce metadata updates to improve performance?
Trap 1: noexec
Prevents execution of binaries, does not reduce metadata updates.
Trap 2: nodiratime
Disables atime updates for directories only, but noatime is more comprehensive.
Trap 3: relatime
Relatime updates atime conditionally, but not as effective as noatime.
You are a Linux administrator at a mid-sized company. The company runs a critical PostgreSQL database on a server running CentOS 7. The database stores its data on a 500GB logical volume (lv_pgdata) in volume group vg_pg. The filesystem is XFS. Recently, the database team reports that write performance is degrading, and the disk is nearly full (95% usage). You have added a new 200GB SSD to the server, and you need to increase the storage capacity and improve write performance for the database. The database can tolerate a brief downtime (less than 5 minutes) for maintenance. You want to use LVM to add the new SSD as a physical volume, extend the volume group, and then extend the logical volume and filesystem. Additionally, you want to improve write performance by placing the frequently written database transaction log on a separate faster storage. However, the database configuration expects the transaction log to be in a subdirectory of the data directory. You have the following options: A. Create a new logical volume for the transaction log, format it as XFS, mount it on the data directory's subdirectory, and move the log files. B. Add the SSD as a PV, extend vg_pg, extend lv_pgdata, and then use LVM's pvmove to move all extents to the SSD. C. Add the SSD as a PV, create a new VG, create a new LV for the transaction log, format as ext4, mount, and reconfigure the database. D. Use LVM's striping (RAID 0) across the existing HDD and new SSD to improve performance, then extend the filesystem. Which option best meets the requirements of increasing capacity and improving write performance with minimal downtime?
Trap 1: Add the SSD as a PV, extend vg_pg, extend lv_pgdata and resize the…
This does not increase capacity (still 500GB) and wastes the HDD.
Trap 2: Use LVM's striping (RAID 0) across the existing HDD and new SSD to…
Striping increases risk of data loss if either disk fails, and requires data migration.
Trap 3: Add the SSD as a PV, create a new VG and LV for the transaction…
Creating a separate VG is unnecessary and ext4 may not be optimal for database logs.
Add the SSD as a PV, extend vg_pg, extend lv_pgdata and resize the filesystem for capacity. Then create a new LV on the SSD, format as XFS, mount it on the transaction log subdirectory, move the log files, and update the database configuration to point to the new location.
This increases capacity and isolates log writes to SSD, improving performance with minimal downtime.
B
Add the SSD as a PV, extend vg_pg, extend lv_pgdata and resize the filesystem for capacity. Then use pvmove to move all data to the SSD, leaving the HDD unused.
Why wrong: This does not increase capacity (still 500GB) and wastes the HDD.
C
Use LVM's striping (RAID 0) across the existing HDD and new SSD to improve performance, then extend the filesystem.
Why wrong: Striping increases risk of data loss if either disk fails, and requires data migration.
D
Add the SSD as a PV, create a new VG and LV for the transaction log, format as ext4, mount, and reconfigure the database to use the new location.
Why wrong: Creating a separate VG is unnecessary and ext4 may not be optimal for database logs.
A system administrator notices that a new 500GB SSD (/dev/sdb) is not being recognized by the system after installation. The server uses UEFI and GPT partitioning. Which command should the administrator run first to verify that the disk is detected by the kernel?
Trap 1: fdisk -l /dev/sdb
`fdisk -l /dev/sdb` is unsuitable for verifying initial kernel detection, especially on a UEFI/GPT system. This command primarily interacts with and displays partition table information, specifically MBR, rather than probing the kernel's device recognition status. If the disk is not detected by the kernel, `fdisk` will likely report an error or fail to access the device. The command is tempting as `fdisk -l` is a common utility for inspecting existing partition tables on disks already recognised by the system, particularly for MBR-partitioned drives.
Trap 2: cat /proc/cpuinfo
This shows CPU info, not disk detection.
Trap 3: lsusb
lsusb lists USB devices, but /dev/sdb may be SATA/SAS, not USB.
Why wrong: `fdisk -l /dev/sdb` is unsuitable for verifying initial kernel detection, especially on a UEFI/GPT system. This command primarily interacts with and displays partition table information, specifically MBR, rather than probing the kernel's device recognition status. If the disk is not detected by the kernel, `fdisk` will likely report an error or fail to access the device. The command is tempting as `fdisk -l` is a common utility for inspecting existing partition tables on disks already recognised by the system, particularly for MBR-partitioned drives.
B
lsblk
lsblk lists all block devices, including /dev/sdb, and does not require root.
C
cat /proc/cpuinfo
Why wrong: This shows CPU info, not disk detection.
D
lsusb
Why wrong: lsusb lists USB devices, but /dev/sdb may be SATA/SAS, not USB.
A Linux administrator needs to create a RAID 5 array using three disks: /dev/sdb, /dev/sdc, and /dev/sdd, each 2TB. The administrator wants to ensure the array can be reassembled automatically after a reboot. Which command should be used to create the array?
A system administrator receives an alert that disk /dev/sda is predicted to fail soon. The server uses LVM, and /dev/sda is part of a volume group named vg_system. Which of the following is the best course of action to replace the failing disk without downtime?
Trap 1: Use dd to clone /dev/sda to a new disk and then replace.
dd may cause downtime and I/O errors.
Trap 2: Use ddrescue to copy data, then replace the disk.
ddrescue is for failing disks but does not handle LVM metadata well.
Trap 3: Remove /dev/sda from the volume group and add a new disk.
Your company runs a critical database server that uses a 2TB XFS filesystem mounted at /data. The filesystem resides on an LVM logical volume (lv_data) within a volume group (vg_data) that spans four physical volumes (each 600GB SSD). You have been receiving low-space alerts: /data is at 95% capacity. After reviewing usage, you determine that the database will need an additional 500GB within the next month. The server has no additional physical disks available, but there is an unused 1TB SSD in inventory that you can install. However, the server is in production and cannot be rebooted. The system uses a 5.10 Linux kernel. Which of the following is the best approach to increase the available space for /data?
Trap 1: Create a RAID 0 array with the existing SSDs and the new SSD using…
RAID 0 would require rebuilding and data migration; not simple expansion.
Trap 2: Shrink other logical volumes in vg_data that are not important to…
Shrinking XFS is not supported online; also may not free enough space.
Trap 3: Backup /data to an external drive, delete the logical volume,…
Create a RAID 0 array with the existing SSDs and the new SSD using mdadm, then format with XFS and mount at a different mount point, then move data.
Why wrong: RAID 0 would require rebuilding and data migration; not simple expansion.
B
Shrink other logical volumes in vg_data that are not important to free up space, then extend lv_data.
Why wrong: Shrinking XFS is not supported online; also may not free enough space.
C
Install the new SSD, create a partition with fdisk, run pvcreate, vgextend vg_data, lvextend -L +500G /dev/vg_data/lv_data, and then run xfs_growfs /data.
Online expansion of XFS is supported; all steps are non-disruptive.
D
Backup /data to an external drive, delete the logical volume, volume group, and physical volumes, then recreate everything including the new SSD to have a single large filesystem, then restore data.
Why wrong: Unnecessary downtime and data restoration risk.
A system administrator needs to create a new ext4 filesystem on /dev/sdb1 with a reserved block percentage of 2% instead of the default 5%. Which command should be used?
Trap 1: mkfs.ext4 -R 2 /dev/sdb1
Incorrect: -R is not a valid option for mkfs.ext4.
Trap 2: mkfs.ext4 -r 2 /dev/sdb1
Incorrect: -r is for RAID stride.
Trap 3: tune2fs -m 2 /dev/sdb1
Incorrect: tune2fs modifies an existing filesystem, not creation.
While mount -a is a valid method to mount filesystems from /etc/fstab, the given command involves two steps: adding an entry to fstab and then running mount -a. The question asks for direct mount commands that mount an NFS filesystem immediately without prior configuration. Additionally, the fstab entry uses 'defaults' which may not include necessary NFS options like 'hard' or 'intr' for proper operation. Therefore, option A is not considered a valid single-step mount method.
echo 'server:/export /mnt nfs defaults 0 0' >> /etc/fstab && mount -a
Why wrong: While mount -a is a valid method to mount filesystems from /etc/fstab, the given command involves two steps: adding an entry to fstab and then running mount -a. The question asks for direct mount commands that mount an NFS filesystem immediately without prior configuration. Additionally, the fstab entry uses 'defaults' which may not include necessary NFS options like 'hard' or 'intr' for proper operation. Therefore, option A is not considered a valid single-step mount method.
B
mount -o hard,intr server:/export /mnt
Correct: NFS mount with options.
C
mount -t cifs server:/share /mnt
Why wrong: Incorrect: -t cifs is for CIFS, not NFS.
Order the steps to configure a cron job that runs a script every day at 2 AM.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5
Trap 1: Step 1: Add the line '0 2 * * * /path/to/script' directly to the…
This is incorrect because you cannot add a line to the crontab without first opening it for editing. The crontab -e command must be run before any line addition.
Trap 2: Step 1: Run 'crontab -e' to open the editor.
Step 2: Save and exit…
This is incorrect because saving before adding the cron line means no job was added. You must add the line before saving.
Trap 3: Step 1: Run 'crontab -l' to verify existing jobs.
Step 2: Run…
This is incorrect because verifying jobs before editing is not necessary and does not affect the configuration. The correct order is to edit first, then verify after saving.
Step 1: Run 'crontab -e' to open the crontab editor.
Step 2: Add the line '0 2 * * * /path/to/script'.
Step 3: Save and exit the editor.
Step 4: Run 'crontab -l' to verify the job is scheduled.
This is the correct sequence. First, you open the crontab file for editing. Then you add the cron expression with correct time fields (minute 0, hour 2, then asterisks for day, month, weekday). After saving, you verify the job exists.
B
Step 1: Add the line '0 2 * * * /path/to/script' directly to the crontab.
Step 2: Run 'crontab -e' to open the editor.
Step 3: Save and exit the editor.
Step 4: Run 'crontab -l' to verify.
Why wrong: This is incorrect because you cannot add a line to the crontab without first opening it for editing. The crontab -e command must be run before any line addition.
C
Step 1: Run 'crontab -e' to open the editor.
Step 2: Save and exit the editor immediately.
Step 3: Add the line '0 2 * * * /path/to/script'.
Step 4: Run 'crontab -l' to verify.
Why wrong: This is incorrect because saving before adding the cron line means no job was added. You must add the line before saving.
D
Step 1: Run 'crontab -l' to verify existing jobs.
Step 2: Run 'crontab -e' to open the editor.
Step 3: Add the line '0 2 * * * /path/to/script'.
Step 4: Save and exit.
Why wrong: This is incorrect because verifying jobs before editing is not necessary and does not affect the configuration. The correct order is to edit first, then verify after saving.
What does the LFCS exam test about Storage Management?
Storage Management questions on this certification test your ability to deploy and manage storage management concepts in scenario-based situations.
How should I use these practice questions?
Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Storage Management questions in a focused session?
Yes — the session launcher on this page draws every question from the Storage Management domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other LFCS topics?
Use the topic links above to move to related areas, or go back to the LFCS question bank to see all topics.
Are these real exam questions or dumps?
These are original practice questions written to test the same concepts the LFCS exam covers. They are not copied from any real exam or dump site.