Question 510
During a Linux operations review, the team observes: A RAID1 array reports one member failed but the volume still serves reads. What is the MOST directly supported cause?
Explanation
Correct Answer
RAID1 tolerates a member failure but does not remain fully protected until rebuild. This explains the symptom rather than a coincidental service condition. Verification: The replacement member synchronizes and the array returns healthy.
Incorrect Answers
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 mirroring allows remaining members to serve data while redundancy is degraded.
The alternative describes xFS growth is performed on the mounted filesystem with xfs_growfs, which is relevant when an XFS filesystem on a grown logical volume still reports its former size. It does not explain this case because rAID1 tolerates a member failure but does not remain fully protected until rebuild.
A replacement disk listed in an array is not instantly a full synchronized mirror. That can explain why a new RAID member was added but /proc/mdstat shows recovery progressing, whereas the current evidence supports mirroring allows remaining members to serve data while redundancy is degraded.





CompTIA Linux+ (XK0-006) Practice Tests