EX200 Configure local storage Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  1. pvcreate, 2. vgcreate, 3. lvcreate, 4. mkfs, 5. mount

  Why this is correct

  This is the correct LVM sequence: pvcreate initializes the block devices with LVM metadata and makes them physical volumes; vgcreate combines those PVs into a volume group that provides a pool of physical extents; lvcreate allocates 5 GiB of free extents from the VG and creates the logical volume device; mkfs writes a filesystem (e.g., xfs or ext4) onto that LV device; and mount attaches the filesystem to a directory for access. Each step has a hard dependency on the previous one, and this ordering reflects the LVM object hierarchy: PV -> VG -> LV -> filesystem -> mount point. For a 5 GiB LV, lvcreate -L 5G would be used, and the LV appears under /dev/mapper/ or /dev/VGNAME/LVNAME once created.

• ✗

  1. vgcreate, 2. pvcreate, 3. lvcreate, 4. mkfs, 5. mount

  Why it's wrong here

  This order is invalid because vgcreate itself requires that the underlying devices are already initialized as LVM physical volumes. Running vgcreate first will fail—the commands that add devices to a volume group expect each device to contain an LVM metadata header written by pvcreate. You must run pvcreate on each block device first to label it as a PV, and only then can vgcreate create a VG spanning those PVs.

• ✗

  1. pvcreate, 2. lvcreate, 3. vgcreate, 4. mkfs, 5. mount

  Why it's wrong here

  This order fails at step 2 because lvcreate requires an existing volume group (VG) to allocate logical extents from; the VG is the pool that logical volumes are carved out of. While pvcreate is correctly placed first, lvcreate must wait until after vgcreate has aggregated the physical volumes into that pool. Running lvcreate before vgcreate produces an error like "Volume group not found" because the VG name has no corresponding LVM metadata yet.

• ✗

  1. pvcreate, 2. vgcreate, 3. mkfs, 4. lvcreate, 5. mount

  Why it's wrong here

  This order is invalid because mkfs at step 3 tries to format a logical volume that has not been created yet—lvcreate at step 4 is the tool that actually creates the LV block device. Without an existing LV, mkfs has no device node to target and will fail with an error such as "No such file or directory" when specifying the LV path. The correct progression is to allocate the LV first, then build the filesystem on it, so mkfs must come after lvcreate.

Go deeper

Related to this question