Question 17

Explanation

The correct answer: RAID 5 (Striping with Parity) would be the most suitable choice for this scenario. RAID 5 offers a combination of data striping, which provides performance benefits, and parity, which provides resilience against data loss. The data and parity information are distributed among all disks, and the parity information enables data recovery in case of a single disk failure. It requires a minimum of three disks, making it a more cost-effective solution compared to RAID 6, and provides a good balance between performance, storage efficiency, and fault tolerance. RAID 5 is a fitting choice for scenarios requiring both high performance and resilience, provided a robust backup strategy is in place, as recovery from a second simultaneous disk failure is not possible. The incorrect answers: RAID 0 (Striping) provides the highest performance among all RAID levels as it distributes data across all disks, allowing multiple data parts to be accessed simultaneously, but it offers no data protection or fault tolerance. In the context of the scenario, where the organization handles critical and sensitive data, RAID 0 would not be an appropriate choice due to its lack of resilience. RAID 1 (Mirroring) offers a high level of data protection by duplicating all data from one drive to another, enabling complete data access even if one drive fails. But, it doesn't provide the speed benefits of striping and only provides 50% storage efficiency, making it less suitable in scenarios where both performance and resilience are required. RAID 6 (Striping with Double Parity) provides the highest level of data protection among the options, allowing for the failure of up to two drives. Although it does offer performance benefits from striping, it also requires a minimum of four disks and has significant write performance overhead due to the calculation and writing of double parity information. RAID 6 might be considered overkill for scenarios requiring a balance of speed and resilience, especially if budgetary constraints are in place.