Drag and Drop Question You have a disaggregated cluster deployment. The deployment contains a scale-out file server (SOFS) cluster that runs Windows Server and a compute cluster that has the Hyper-V…

Question

Exhibit

Answer Area

Explanation

To implement Storage QoS for a disaggregated cluster, New-StorageQosPolicy is used on the SOFS cluster to define policies, and Set-VMHardDiskDrive is used on the Hyper-V cluster to apply those policies to virtual disks.

Approach. The scenario requires implementing Storage Quality of Service (QoS) to control bandwidth usage between a Scale-Out File Server (SOFS) cluster and a Hyper-V compute cluster. Storage QoS in this context involves defining policies on the storage provider and then applying those policies to the virtual disks consumed by virtual machines.

1. SOFS Cluster - New-StorageQosPolicy: The SOFS cluster acts as the storage provider. Storage QoS policies, which define minimum and maximum IOPS or bandwidth limits for virtual disks, are created on the storage provider. Therefore, the New-StorageQosPolicy cmdlet, which is used to define such policies, should be run on the SOFS cluster.
2. Hyper-V Cluster - Set-VMHardDiskDrive: The Hyper-V cluster hosts the virtual machines that consume storage from the SOFS. To apply the defined Storage QoS policies to specific virtual hard disks (VHDX files) or to set individual QoS limits, the Set-VMHardDiskDrive cmdlet is used. This cmdlet allows you to link a virtual hard disk to a pre-defined Storage QoS policy or directly configure its minimum/maximum IOPS/bandwidth. This cmdlet is run on the Hyper-V host (or cluster) where the virtual machines and their virtual hard disks reside.

Common mistakes.

• common_mistake. 1. Using Set-VMSan: The Set-VMSan cmdlet is used to configure Virtual Machine SAN (VMSAN) settings, which are typically associated with Fibre Channel storage for Hyper-V. The scenario specifies a Scale-Out File Server (SOFS) cluster, which typically provides storage over SMB 3.0, not Fibre Channel. Therefore, Set-VMSan is irrelevant to this deployment type.

1. Swapping New-StorageQosPolicy and Set-VMHardDiskDrive: Running Set-VMHardDiskDrive on the SOFS cluster makes no sense as the SOFS cluster is the storage provider and defines policies, not configures individual virtual disks for Hyper-V VMs directly. Conversely, running New-StorageQosPolicy on the Hyper-V cluster is incorrect because the Hyper-V cluster consumes storage and applies policies to its VMs, but does not define the central storage QoS policies themselves; those are defined on the storage provider (SOFS).

Concept tested. Windows Server Storage Quality of Service (QoS), specifically its implementation in disaggregated Hyper-V deployments leveraging Scale-Out File Servers (SOFS). This tests the understanding of where storage policies are defined (storage provider) and where they are applied (storage consumer, i.e., Hyper-V VMs).

No community discussion yet for this question.