Question 730
The lab examiner asks for evidence after this assignment: An operator confuses a partition number with an LVM logical volume name when looking for a mounted database. What is the decisive verification step?
Explanation
Correct Answer
The resulting mapping identifies filesystem to LV to VG to PV without changing data. This check confirms the expected effect of: Use `lsblk -f` plus `lvs` and `findmnt` to resolve which block layer currently backs `/srv/db`. It distinguishes the intended result from the original failure mechanism: Device mapper LVM layers and GPT partition names represent different levels of storage.
Incorrect Answers
`lvs /dev/vg_training/lv_db` reports the requested LV and does not show a filesystem automatically. That verifies a separate lab task: An LVM volume group `vg_training` exists and a test database requires a new 2 GiB logical volume. It does not validate the implementation required here: Use `lsblk -f` plus `lvs` and `findmnt` to resolve which block layer currently backs `/srv/db`.
The expected device appears under the lab inventory ID and no device is formatted during discovery. That verifies a separate lab task: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. It does not validate the implementation required here: Use `lsblk -f` plus `lvs` and `findmnt` to resolve which block layer currently backs `/srv/db`.
The volume group reports sufficient free extents before the successful resize. That verifies a separate lab task: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. It does not validate the implementation required here: Use `lsblk -f` plus `lvs` and `findmnt` to resolve which block layer currently backs `/srv/db`.