Which RAID level is used for a database requiring minimal write requests, high read activity, and fault tolerance?

Which RAID level is used for a database requiring minimal write requests, high read activity, and fault tolerance?

• A. RAID 10
• B. RAID 1
• C. RAID 5
• D. RAID 0

Answer: (C)

This question focuses on choosing a RAID level that balances fault tolerance, read performance, and write overhead for a read-heavy database. RAID 5 stripes data across multiple disks with distributed parity, so it can tolerate a single disk failure and provides strong read throughput because reads come from multiple disks in parallel. The parity information gives fault tolerance without duplicating all data, which keeps capacity efficient. Writes, however, require updating parity, which adds some overhead, but if writes are infrequent, that cost remains acceptable. Other options either offer no redundancy, require full data replication across disks, or impose higher write penalties, making them less suitable for a read-heavy workload with occasional writes. So RAID 5 best fits the scenario.

This question focuses on choosing a RAID level that balances fault tolerance, read performance, and write overhead for a read-heavy database. RAID 5 stripes data across multiple disks with distributed parity, so it can tolerate a single disk failure and provides strong read throughput because reads come from multiple disks in parallel. The parity information gives fault tolerance without duplicating all data, which keeps capacity efficient. Writes, however, require updating parity, which adds some overhead, but if writes are infrequent, that cost remains acceptable. Other options either offer no redundancy, require full data replication across disks, or impose higher write penalties, making them less suitable for a read-heavy workload with occasional writes. So RAID 5 best fits the scenario.