Question 140
A student has implemented the following configuration: A trainee needs to delete one unused partition on a disposable GPT disk but proposes erasing the whole disk. What repeatable control best reduces regressions or unsafe changes?
Explanation
Correct Answer
Confirm exact partition number, holders and backups before partition deletion. This guards against recurrence of: Removing one GPT partition differs from overwriting the entire partition table. Confirm the lab's final state by: `parted -s /dev/vdb print` no longer lists partition 2 and remaining partition metadata is intact.
Incorrect Answers
Include a full storage dependency diagram in change requests. That control is best suited to a separate scenario: An operator confuses a partition number with an LVM logical volume name when looking for a mounted database. It is not the best safeguard for the current mechanism: Removing one GPT partition differs from overwriting the entire partition table.
Plan allocations with PV placement requirements as well as aggregate capacity. That control is best suited to a separate scenario: A training PV reports little free space while its VG appears to have ample total capacity across a second PV. It is not the best safeguard for the current mechanism: Removing one GPT partition differs from overwriting the entire partition table.
Document whether requests are byte sizes or extents before provisioning LVM. That control is best suited to a separate scenario: An LV should consume precisely 20% of remaining free extents for a training scratch workload. It is not the best safeguard for the current mechanism: Removing one GPT partition differs from overwriting the entire partition table.