Troubleshooting Degraded RAID Array Performance and Failure

220-1201 By islever Editorial Last updated

Given a scenario, troubleshoot drive and RAID issues

Short answer

A The technician should check the RAID array status because prolonged slowness followed by complete unavailability of a file share while the server remains online strongly indicates a degraded RAID configuration that has now failed.

Question

A technician receives a report that the network fileshare has been very slow for several weeks, and today it is no longer available. The file server is running, and the technician can establish an RDP connection to it. Which of the following should the technician check next?
  1. RAID array status Correct Answer
  2. Data backup integrity
  3. Network connectivity
  4. Server available memory

Key Takeaways

The main trap is assuming network connectivity is fine because RDP works; however, the symptom timeline (slow then dead) specifically targets storage redundancy failure, not general connectivity.

Learn why a file share slowing down then disappearing points to a RAID array issue rather than network or memory problems. This CompTIA A+ 220-1201 question explains how to diagnose storage failures when the server itself is still responsive.

Common mistake: Many candidates choose Network connectivity because the file share is unreachable, but they overlook that RDP success proves the network layer is operational. They also miss the significance of the 'weeks of slowness' leading to a total outage.

Expert Analysis

The scenario presents a classic progression of storage failure symptoms. The file share was "very slow for several weeks," which indicates that the underlying storage subsystem was under stress or operating in a degraded mode, likely due to redundant disk failures causing read/write overhead. Today, the share is "no longer available," suggesting the RAID array has collapsed completely (e.g., failed beyond its redundancy threshold).

Although the server is running and accessible via RDP, this only confirms that the OS, CPU, RAM, and primary network stack are functional. It does not guarantee the health of the secondary storage subsystem where the file share resides. Therefore, checking Network connectivity (C) is redundant because RDP already proves the network path is active. Checking Server available memory (D) is unlikely to be the cause of a sudden total unavailability after weeks of slowness; memory issues typically manifest as system-wide instability or paging thrashing, not isolated file share outages. Data backup integrity (B) is a post-incident recovery step, not a troubleshooting action to restore service.

The correct next step is to check the RAID array status (A). A degraded RAID array can sustain performance degradation for a period before failing entirely. Verifying the RAID controller's status will confirm if disks have failed and if the array is offline or in a critical state.

Exam Strategy

When troubleshooting, always correlate the timeline of symptoms with the affected subsystem. If a service degrades gradually before failing, suspect hardware redundancy limits (like RAID) rather than transient software or network issues. Use successful connections to other services (like RDP) to rule out broad infrastructure failures like network or power.

Frequently Asked Questions

If RDP works, is the network definitely fine?

Yes, for the purpose of this question. Successful RDP confirms that the server's network interface, IP stack, and basic routing are functional. Issues specific to the file share protocol (SMB/NFS) or the storage backend are separate from general network connectivity.

Could low memory cause file shares to become unavailable?

Low memory usually causes system-wide sluggishness, paging, or application crashes. It rarely causes a specific file share to disappear entirely after weeks of consistent slowness without crashing the OS first. Storage hardware failure is a more direct fit for this pattern.

More 220-1201 FAQ →

Community Votes

A
100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 1 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 1

  1. Afie 👍 1 Answered A
    The file share has been slow for several weeks. Now it is completely unavailable. The server is still running. The technician can RDP into the server, so the server and network connectivity are working. These symptoms strongly suggest a degraded or failed RAID array: A RAID array can operate in a degraded state for some time, causing poor performance. If additional disk failures occur, the array can become unavailable, taking the file share offline. Since the server is reachable via RDP, the problem is more likely related to the storage subsystem than the network.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Practice All 220-1201 Questions

Access 105 questions with complete answers and detailed explanations.

View Full 220-1201 Practice Test →

← Back to 220-1201 Study Guide