An architect is tasked with updating the design for an existing VMware Cloud Foundation (VCF) deployment to include four vSAN ESA ready nodes.
The existing deployment comprises the following:
Four homogenous vSAN ESXi ready nodes in the management domain.
Four homogenous ESXi nodes with iSCSI principal storage in workload domain A.
What should the architect recommend when including this additional capacity for application workloads?
Correct Answer: D
The task involves adding four vSAN ESA (Express Storage Architecture) ready nodes to an existing VCF 5.2 deployment for application workloads. The current setup includes a vSAN-based Management Domain and a workload domain (A) using iSCSI storage. In VCF, workload domains are logical units with consistent storage and lifecycle management via vSphere Lifecycle Manager (vLCM).
Let's analyze each option:
Option A: Commission the four new nodes into the existing workload domain A cluster Workload domain A uses iSCSI storage, while the new nodes are vSAN ESA ready. VCF 5.2 doesn't support mixing principal storage types (e.g., iSCSI and vSAN) within a single cluster, as per the VCF 5.2 Architectural Guide. Commissioning vSAN nodes into an iSCSI cluster would require converting the entire cluster to vSAN, which isn't feasible with existing workloads and violates storage consistency, making this impractical.
Option B: Create a new vLCM image workload domain with the four new nodes This phrasing is ambiguous. vLCM manages ESXi images and baselines, but "vLCM image workload domain" isn't a standard VCF term. It might imply a new workload domain with a custom vLCM image, but lacks clarity compared to standard options (C, D). The VCF 5.2 Administration Guide uses "baseline" or "image-based" distinctly, so this is less precise.
Option C: Create a new vLCM baseline cluster in the existing workload domain with the four new nodes Adding a new cluster to an existing workload domain is possible in VCF, but clusters within a domain must share the same principal storage (iSCSI in workload domain A). The VCF 5.2 Administration Guide states that vSAN ESA requires a dedicated cluster and can't coexist with iSCSI in the same domain configuration, rendering this option invalid.
Option D: Create a new vLCM baseline workload domain with the four new nodes A new workload domain with vSAN ESA as the principal storage aligns with VCF 5.2 design principles. vLCM baselines ensure consistent ESXi versioning and firmware for the new nodes. The VCF 5.2 Architectural Guide recommends separate workload domains for different storage types or workload purposes (e.g., application capacity). This leverages the vSAN ESA nodes effectively, isolates them from the iSCSI-based domain A, and supports application workloads seamlessly.
Conclusion:
Option D is the best recommendation, creating a new vSAN ESA-based workload domain managed by vLCM, meeting capacity needs while adhering to VCF 5.2 storage and domain consistency rules.
Reference: VMware Cloud Foundation 5.2 Architectural Guide (docs.vmware.com): Workload Domain Design and vSAN ESA.
VMware Cloud Foundation 5.2 Administration Guide (docs.vmware.com): vLCM and Cluster Expansion.
vSAN ESA Planning and Deployment Guide (docs.vmware.com): Storage Requirements.
