A customer has a large number of high performance database servers with DAS. They are concerned about isolated data and would also like to re-assign unused storage to avoid additional expenditure…

Question

Options

• AAttach all servers directly to their storage.
• BAttach all servers and storage to redundant SAN fabrics.
• CImplement a DAS RAID 5 solution for the database servers.
• DAdd a NAS option to the storage and deliver data using file services.

• A
  11% (4)
• B
  70% (26)
• C
  5% (2)
• D
  14% (5)

Explanation

Attaching all servers and storage to redundant SAN (Storage Area Network) fabrics solves all three requirements simultaneously: a SAN creates a shared storage pool that eliminates isolated data silos, allows unused storage to be dynamically reallocated across servers (avoiding waste), and the redundant fabric paths prevent unexpected loss of access by eliminating single points of failure.

Why the distractors fail:

• A is essentially describing the current DAS setup - attaching servers "directly to their storage" keeps data isolated and wastes unused capacity, solving nothing.
• C adds resilience against disk failure via RAID 5, but DAS-based RAID still keeps storage isolated per server and doesn't enable reallocation of unused space across servers.
• D (NAS with file services) does allow shared access, but NAS uses file-level protocols (NFS/SMB) which are poorly suited for high-performance database workloads; databases need block-level storage, which SAN provides.

Memory tip: Think of the three customer pain points - Isolated, Inefficient, Inaccessible - and remember that only a SAN fixes all three I's at once by turning scattered DAS into a centralized, shared, redundant block-storage pool.

No community discussion yet for this question.