220-1201 Practice Question: A company's file server uses a RAID 5 array with…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Replace all five drives and restore from backup.

  Why it's wrong here

  Replacing all five drives is an extreme measure that would guarantee data loss and require a full restore from backup, which is time-consuming and disruptive. Since the drives are detected, it suggests a logical issue or a single drive failure within the RAID 5 array, which can typically be rebuilt or recovered without replacing all components. This action would unnecessarily escalate the problem and erase any chance of a simpler recovery.

• ✗

  Initialize the array to clear the failed status.

  Why it's wrong here

  Initializing a RAID array is a destructive operation that formats the drives and recreates the array's metadata, effectively erasing all existing data. While it would clear the "failed" status, it would also permanently destroy the company's file server data, making it an unacceptable solution for data recovery. This action should only be performed when setting up a new array or intentionally wiping data.

• ✓

  Check the RAID controller's event log and attempt to import the array.

  Why this is correct

  Checking the RAID controller's event log is the crucial first diagnostic step, as it provides specific details about which drives have failed or if the array configuration itself has become corrupted or lost. If the configuration is lost but the drives are intact, attempting to import the array can re-read the existing metadata from the drives and restore the array's operational status without data loss. This approach prioritizes diagnosis and non-destructive recovery.

• ✗

  Reseat all SATA cables and power connectors.

  Why it's wrong here

  Reseating cables is a common troubleshooting step for physical connectivity issues, but it is unlikely to resolve a "failed" array status when the drives are still detected by the system. Since the drives are visible, the problem is more likely a logical configuration issue, a drive failure within the array, or a controller problem, rather than a loose physical connection preventing detection. This action would not address the root cause of a detected but failed array.