A customer has a database cluster running in a VCF cluster with the following characteristics: - 40/60 Read/Write ratio. - High IOPS requirement. - No contention on an all-flash OSA vSAN cluster in…

Question

Options

• AFlash Read Cache Reservation
• BRAID 1
• CDeduplication and Compression disabled
• DDeduplication and Compression enabled
• ERAID 5

• A
  7% (3)
• B
  78% (35)
• D
  4% (2)
• E
  11% (5)

Explanation

The database cluster in a VCF 5.2 VI Workload Domain uses an all-flash vSAN Original Storage Architecture (OSA) cluster with a 40/60 read/write ratio, high IOPS needs, and no contention (implying sufficient resources). vSAN configuration impacts performance, especially for Option A: Flash Read Cache Reservation In all-flash vSAN OSA, the cache tier (flash) serves writes, not reads, which are handled by the capacity tier (also flash). The vSAN Planning and Deployment Guide notes that Flash Read Cache Reservation is deprecated for all-flash configurations, as reads don't benefit from caching, making this irrelevant for performance here. Option B: RAID 1 RAID 1 (mirroring) replicates data across hosts, offering high performance and availability (FTT=1). For a 40/60 read/write workload with high IOPS, RAID 1 minimizes latency and maximizes throughput compared to erasure coding (e.g., RAID 5), as it avoids parity calculations. The VCF 5.2 Architectural Guide recommends RAID 1 for performance-critical workloads like databases, especially with no contention. Option C: Deduplication and Compression disabled Disabling deduplication and compression avoids CPU overhead and latency from data processing, critical for high-IOPS workloads. The vSAN Administration Guide advises disabling these for performance-sensitive applications (e.g., databases), as the 60% write ratio benefits from direct I/O over space efficiency, given no contention. Option D: Deduplication and Compression enabled Enabling deduplication and compression reduces storage use but increases latency and CPU load, degrading performance for high-IOPS workloads. The vSAN Planning and Deployment Guide notes this trade-off, making it unsuitable here. Option E: RAID 5 RAID 5 (erasure coding) uses parity, reducing write performance due to calculations, which conflicts with the 60% write ratio and high IOPS needs. The VCF 5.2 Architectural Guide recommends RAID 5 for capacity optimization, not performance, favoring RAID 1 instead.

No community discussion yet for this question.