Question 580
A Linux administrator evaluates: A failed recovery involves multiple similarly named disks and the team must prove the intended filesystem identity. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A failed recovery involves multiple similarly named disks and the team must prove the intended filesystem identity. The recommended direct administrative response is: Check the mount error, blkid filesystem type, device state and supported fsck or filesystem-specific recovery conditions before attempting repair. The relevant failure or security risk is: Repairing the wrong device or a mounted writable filesystem risks corrupting the data and delaying recovery. Validate success with: The intended volume mounts cleanly after a supported recovery process, and integrity and application checks pass.
For the specific observation (A failed recovery involves multiple similarly named disks and the team must prove the intended filesystem identity), the acceptance evidence is: The intended volume mounts cleanly after a supported recovery process, and integrity and application checks pass. This verifies the action (Check the mount error, blkid filesystem type, device state and supported fsck or filesystem-specific recovery conditions before attempting repair.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Repairing the wrong device or a mounted writable filesystem risks corrupting the data and delaying recovery.
Incorrect Answers
Memory pressure OOM killer and swapping (5.5) addresses another technical failure: Treating file cache as unavailable RAM or blindly disabling swap can obscure the application responsible for OOM kills. The case states: A failed recovery involves multiple similarly named disks and the team must prove the intended filesystem identity. The most direct paired action and test is: Check the mount error, blkid filesystem type, device state and supported fsck or filesystem-specific recovery conditions before attempting repair.
ACL mask and directory traversal permission failures (5.4) would demonstrate or implement: An authorized process reaches the intended path, while unrelated users still fail read or execute tests. This case instead tests Mount failure and filesystem integrity diagnosis; the choice measures or changes another part of the system.
SELinux denial versus traditional permission fault (5.4) would demonstrate or implement: Turning SELinux off or using chmod 777 cannot reliably solve a labeling issue and can weaken host security. The required paired action and test concerns Mount failure and filesystem integrity diagnosis; a passing result for this alternative could leave that requirement unresolved.