AZ-801 · Question #66
You have three servers named Server1, Server2, Server3 that run Windows Server and have the Hyper-V server role installed. You plan to create a hyper-converged cluster to host Hyper-V virtual…
This question tests knowledge of the correct deployment sequence for Storage Spaces Direct (S2D) in a Windows Server hyper-converged cluster. S2D uses locally attached disks across cluster nodes as a shared, software-defined storage pool.
Question
Explanation
This question tests knowledge of the correct deployment sequence for Storage Spaces Direct (S2D) in a Windows Server hyper-converged cluster. S2D uses locally attached disks across cluster nodes as a shared, software-defined storage pool.
Approach. The correct three-step sequence is: (1) Create a failover cluster using all three servers - S2D requires an underlying Windows Server Failover Cluster, so this must come first (via New-Cluster or Failover Cluster Manager). (2) Enable Storage Spaces Direct on the cluster - run Enable-ClusterStorageSpacesDirect, which discovers local disks, creates a storage pool, and activates the S2D subsystem. (3) Create a volume to use as a Cluster Shared Volume (CSV) - run New-Volume to provision storage from the S2D pool, which then becomes accessible to all nodes for hosting Hyper-V VMs. Each step is a prerequisite for the next: S2D cannot be enabled without a cluster, and volumes cannot be created from S2D until it is enabled.
Concept tested. Storage Spaces Direct (S2D) hyper-converged deployment sequence - specifically the dependency order: Failover Cluster creation → Enable-ClusterStorageSpacesDirect → New-Volume (CSV provisioning).
Reference. Microsoft Learn: Deploy Storage Spaces Direct - https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/deploy-storage-spaces-direct
Topics
Community Discussion
No community discussion yet for this question.