An administrator is tasked to create a new VMware vSAN cluster. The following information was provided to the administrator: - Should host high performance application. - Workload is latency…

Question

Options

• AvSAN Original Storage Architecture (OSA) Stretched Cluster
• BvSAN Storage Cluster
• CvSAN Original Storage Architecture (OSA)
• DvSAN Express Storage Architecture (ESA)

• A
  2% (1)
• B
  5% (2)
• C
  10% (4)
• D
  83% (34)

Explanation

vSAN ESA is the correct choice because it is purpose-built for high-performance, latency-sensitive workloads using all-NVMe hardware and a log-structured file system that delivers significantly lower latency than the older OSA architecture - and it keeps compute, workload, and storage co-located in a single cluster by default.

Option A (OSA Stretched Cluster) is wrong on two counts: it uses the older, less performant OSA architecture, and a stretched cluster spans two physical sites, which adds inter-site latency - the opposite of what a latency-dependent workload needs.

Option B (vSAN Storage Cluster) is wrong because this configuration decouples storage from compute, meaning the compute nodes live in a separate cluster that consumes storage remotely - directly violating the requirement that "workload, compute and storage must be in the vSAN cluster."

Option C (OSA) keeps everything in one cluster but uses the legacy disk-group architecture that cannot match ESA's NVMe-optimized, low-latency performance profile.

Memory tip: Think of ESA as the "Express lane" - it's the Express Storage Architecture, built for speed. Whenever you see "high performance + latency-sensitive + modern hardware," reach for ESA.

No community discussion yet for this question.