Question 80
A Linux administrator evaluates: A filesystem migration requires proving the correct resize utility was used for the detected on-disk format. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A filesystem migration requires proving the correct resize utility was used for the detected on-disk format. The recommended direct administrative response is: Choose filesystem-specific supported tools such as resize2fs for ext4 and xfs_growfs for mounted XFS; perform repair only under appropriate unmount and recovery conditions. The relevant failure or security risk is: Applying an ext4 repair or resize utility to an XFS volume, or repairing a mounted filesystem improperly, can fail or damage data. Validate success with: Filesystem type and mounted state are confirmed before the operation; integrity checks and usable capacity meet the intended objective afterward.
For the specific observation (A filesystem migration requires proving the correct resize utility was used for the detected on-disk format), the acceptance evidence is: Filesystem type and mounted state are confirmed before the operation; integrity checks and usable capacity meet the intended objective afterward. This verifies the action (Choose filesystem-specific supported tools such as resize2fs for ext4 and xfs_growfs for mounted XFS; perform repair only under appropriate unmount and recovery conditions.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Applying an ext4 repair or resize utility to an XFS volume, or repairing a mounted filesystem improperly, can fail or damage data.
Incorrect Answers
GRUB kernel boot parameter recovery (1.1) would demonstrate or implement: The selected kernel boots to the expected systemd target, and boot logs show the intended parameters without emergency mode. The case states: A filesystem migration requires proving the correct resize utility was used for the detected on-disk format. The most direct paired action and test is: Choose filesystem-specific supported tools such as resize2fs for ext4 and xfs_growfs for mounted XFS; perform repair only under appropriate unmount and recovery conditions.
Route and socket inspection with IP and ss (1.4) would demonstrate or implement: A locally listening service and a reachable default gateway are separate prerequisites; one cannot prove the other. This choice can be useful for that problem, but it does not establish the Ext4 and XFS filesystem repair and growth distinctions control being assessed here.
Shell text processing pipelines (1.5) addresses another technical failure: Grepping an entire unfiltered log or using a wrong delimiter can silently miscount events or report unrelated fields. This case instead tests Ext4 and XFS filesystem repair and growth distinctions; the choice measures or changes another part of the system.