Question 540
A student has implemented the following configuration: A previously working swap LV disappears after restart because no persistent swap entry was configured. What repeatable control best reduces regressions or unsafe changes?
Explanation
Correct Answer
Audit swap entries and device UUIDs after storage migrations. This guards against recurrence of: `swapon` applies at runtime but does not automatically create persistent boot activation. Confirm the lab's final state by: `swapon --show` lists the LV after controlled reboot and `findmnt --verify` finds no fstab error.
Incorrect Answers
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: `swapon` applies at runtime but does not automatically create persistent boot activation.
Record PV mapping before hardware maintenance and always verify device identification. That control is best suited to a separate scenario: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. It is not the best safeguard for the current mechanism: `swapon` applies at runtime but does not automatically create persistent boot activation.
Track approved PV additions in capacity records and test before growing filesystems. That control is best suited to a separate scenario: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. It is not the best safeguard for the current mechanism: `swapon` applies at runtime but does not automatically create persistent boot activation.