Question 20
For this Linux administration lab: A disposable VM has several added disks and the operator must identify which blank disk is safe before partitioning. Which safety and lifecycle check best prevents the same problem returning?
Explanation
Correct Answer
Require a signed disk-to-VM inventory and backup review before changing partition tables. This guards against recurrence of: Device names can change and `lsblk` alone does not authorize destructive partition operations. Confirm the lab's final state by: The selected disk has no filesystem, partition or mount dependencies and matches the lab's disk ID.
Incorrect Answers
Audit swap entries and device UUIDs after storage migrations. That control is best suited to a separate scenario: A previously working swap LV disappears after restart because no persistent swap entry was configured. It is not the best safeguard for the current mechanism: Device names can change and `lsblk` alone does not authorize destructive partition operations.
Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot. That control is best suited to a separate scenario: A server has an approved lab LV mounted through `/dev/vdb1` and the device name changes after adding another disk. It is not the best safeguard for the current mechanism: Device names can change and `lsblk` alone does not authorize destructive partition operations.
Test swap capacity and persist the selected UUID in `/etc/fstab` for future boots. That control is best suited to a separate scenario: A VM needs a dedicated 1 GiB swap partition on an explicitly empty GPT training disk instead of an LVM swap LV. It is not the best safeguard for the current mechanism: Device names can change and `lsblk` alone does not authorize destructive partition operations.