Question 70
A Linux administrator evaluates: An operator plans a disk swap without first recording the array UUID and current device membership. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (An operator plans a disk swap without first recording the array UUID and current device membership), the acceptance evidence is: The array reaches the expected healthy state with the replacement member synchronized and no new device I/O errors. This verifies the action (Inspect /proc/mdstat and mdadm array details, identify the failed member and follow a documented supported replacement and rebuild process.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Replacing the wrong disk or trusting a degraded mirror without monitoring rebuild can cause avoidable data loss.
The observed Linux condition is: An operator plans a disk swap without first recording the array UUID and current device membership. The recommended direct administrative response is: Inspect /proc/mdstat and mdadm array details, identify the failed member and follow a documented supported replacement and rebuild process. The relevant failure or security risk is: Replacing the wrong disk or trusting a degraded mirror without monitoring rebuild can cause avoidable data loss. Validate success with: The array reaches the expected healthy state with the replacement member synchronized and no new device I/O errors.
Incorrect Answers
Shell text processing pipelines (1.5) would demonstrate or implement: The pipeline returns the expected test rows and field values on representative input, leaving source data unchanged. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The array reaches the expected healthy state with the replacement member synchronized and no new device I/O errors.
Kernel module dependencies with modprobe (1.2) would demonstrate or implement: Directly inserting a module file without resolving its dependencies may fail or leave a driver nonfunctional. This choice can be useful for that problem, but it does not establish the Software RAID health and rebuild with mdadm control being assessed here.
Tar archive creation and extraction integrity (1.6) addresses another technical failure: Mistaking archive packaging for a verified backup or extracting unsafe paths blindly can lose files or overwrite live content. This case instead tests Software RAID health and rebuild with mdadm; the choice measures or changes another part of the system.