What it means
Storage resilience and RAID use redundancy, striping, parity, mirroring, monitoring, and rebuild procedures to maintain service through selected device failures.
Why it matters
Redundancy can preserve availability during expected failures, but rebuild stress, correlated devices, and controller faults must be part of the design rather than afterthoughts.
Practical focus
- Define the availability and performance requirements of each storage workload and the security outcome it must support
- Apply appropriate RAID levels, spare strategy, monitoring, controller protection, and tested rebuild procedures through documented, reviewable configuration
- Verify array health, media errors, rebuild duration, capacity headroom, and controller state after changes and on a scheduled basis
- Plan for a second failure or latent error occurring during a rebuild, including rollback, ownership, and escalation
Common mistakes
- Enabling a feature without defining what it should protect
- Relying on defaults or one-time validation
- Granting broad exceptions that erase the control boundary
- Treating a second failure or latent error occurring during a rebuild as an operational surprise instead of a test case
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: