Question 380
In a Linux incident, an engineer reports: An admin mistakes a filesystem UUID for a partition type UUID while preparing GPT automation. What is the MOST directly supported cause?
Explanation
Correct Answer
Partition type, partition ID and filesystem UUID are distinct identities. This mechanism fits the stated evidence. Validate it by checking that the desired partition and filesystem are mapped without ambiguous identifiers.
Incorrect Answers
The alternative describes filesystem-specific repair utilities are required for different on-disk metadata, which is relevant when an XFS volume has structural corruption but an operator proposes e2fsck to repair it. It does not explain this case because partition type, partition ID and filesystem UUID are distinct identities.
It would account for an ext4 filesystem resides on a larger block device but df still shows the old capacity, not the current evidence. For this incident, partition type, partition ID and filesystem UUID are distinct identities; the alternative mechanism leaves that distinction unexplained.
Changing GPT metadata does not always immediately update active partition devices. That can explain why a partition table was extended but the kernel still reports the old partition boundary, whereas the current evidence supports block identifiers carry different meanings, including filesystem and partition GUIDs.





CompTIA Linux+ (XK0-006) Practice Tests