Your network contains an Active Directory Domain Services (AD DS) domain. The domain contains two Windows Server Failover Cluster (WSFC) instances named Cluster1 and Cluster2. Cluster1 hosts Hyper-V virtual machines. Cluster2 does NOT have any high availability roles configured.You need to create a Storage Spaces Direct cluster in Cluster2 that will store the virtual machine hard disk files for Cluster1.Which role should you configure for Cluster2? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.
Answer(s): C,D
To use this Windows Server Failover Cluster (Cluster A) to store VM hard disk files for another cluster (Cluster B), you'll need to add the File Server role to Cluster A and then add the Hyper-V Replica Broker role to it after installing the Hyper-V role on its nodes. Configure the File Server role on Cluster A to provide a shared network location (SMB share), then in Cluster B's Hyper-V Manager, enable replication to Cluster A's Hyper-V Replica Broker, using the shared location for the initial replication.
https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/set-up-hyper-v-replica
HOTSPOT (Drag and Drop is not supported)You have a Hyper-V failover cluster named Cluster1 that contains two nodes named Node1 and Node2, and a Hyper-V host named Host1.You have the virtual machines shown in the following table.The Balancer settings for Cluster1 are shown in the following exhibit.For each of the following statements, select Yes if the statement is true. Otherwise, select No.Note: Each correct selection is worth one point.Hot Area:
Answer(s): A
Box 1: YesYes - If you add a new Hyper-V node to Cluster1, a virtual machine will migrate automatically to the new node.In the exhibit we see the following two options being selected:Enable Automatic Balancing of Virtual MachinesLoad balance to a node when it joins.Note: In a Hyper-V failover cluster, the "Load balance to a node when it joins" option specifies that when a new server node is added to the cluster, virtual machines will be automatically live-migrated from the newly joined node to other cluster nodes, or from existing nodes to the new node, to create a more even distribution of virtual machine workloads and to optimize resource utilization across all hosts.Note 2: When a new machine is addedWhen you join a new machine to your system, the VM load balancing feature automatically balances capacity from the existing machines to the newly added machine in the following order:1. The memory pressure and CPU utilization are evaluated on the existing machines in the system.2. All machines exceeding the threshold are identified.3. The machines with the highest memory pressure and CPU utilization are identified to determine priority of balancing.4. VMs are live migrated (with no downtime) from a machine that exceeds the threshold to the newly added machine in the system.Box 2: NoNo - Within one hour of running the commands, a virtual machine from Node1 will migrate to Node2 automatically.We see: Aggressiveness: MediumNode2 is 60%, and is not more than 70% loaded.Note: Heuristics for BalancingVM Load Balancing evaluates a node's load based on the following heuristics:Current Memory pressure : Memory is the most common resource constraint on a Hyper-V hostCPU utilization of the Node averaged over a 5 minute window: Mitigates a node in the cluster becoming overcommittedControlling Aggressiveness of BalancingThe aggressiveness of balancing based on the Memory and CPU heuristics can be configured using the by the cluster common property `AutoBalancerLevel'. To control the aggressiveness run the following in PowerShell:(Get-Cluster).AutoBalancerLevel = <value>Box 3: NoNo - If VM6 is deployed to Node1, one of the existing machines will migrate to Node2 automatically.The CPU utilization on Node2 is below the threshold.Note: Recurring load balancingBy default, VM load balancing is configured for periodic balancing: the memory pressure and CPU utilization on each machine in the system are evaluated for balancing every 30 minutes. Here's the flow of the steps:1. The memory pressure and CPU utilization are evaluated on all machines in the system.2. All machines exceeding the threshold and those below the threshold are identified.3. The machines with the highest memory pressure and CPU utilization are identified to determine priority of balancing.4. VMs are live migrated (with no downtime) from a machine that exceeds the threshold to another machine that is under the minimum threshold.
https://learn.microsoft.com/en-us/azure/azure-local/manage/vm-load-balancing https://techcommunity.microsoft.com/blog/failoverclustering/failover-cluster-vm-load-balancing-in-windows- server-2016/372084
HOTSPOT (Drag and Drop is not supported)Your network contains an Active Directory Domain Services (AD DS) domain.You need to implement a Storage Spaces Direct cluster. The solution must ensure that the cluster supports delimiting the allocation of volumes.What is the minimum number of servers required, and which type of resiliency is required for the cluster volumes? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: 6Minimum number of serversDelimit the allocation of volumes in Storage Spaces DirectPrerequisitesConsider using this option if:Your cluster has six or more servers; andYour cluster uses only three-way mirror resiliencyDo not use this option if:Your cluster has fewer than six servers; orYour cluster uses parity or mirror-accelerated parity resiliencyBox 2: Three-way mirror onlyVolume resiliency type
https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/delimit-volume-allocation
HOTSPOT (Drag and Drop is not supported)You have a Windows Server Failover Cluster (WSFC) named Cluster1 that contains two nodes named Node1 and Node2. The local disks for Node1 and Node2 are configured as shown in the Disk Management exhibit.(Click the Disk Management tab.)The storage disks for Cluster are configured as shown in the Failover Cluster Manager exhibit. (Click the Failover Cluster Manager tab.)How many disk volume letters are used on each node? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: 3Node1Both Node1 and Node2 have Disk 0 with volume letter C, and Disk1 with volume letter E.Cluster Disk 2 is owned by Node1, but a Windows Server Failover Cluster (WSFC) Disk Witness does not use a volume letter.Cluster Disk1 is owned by Node1, and is assigned to Available storage. A disk assigned to an existing volume within a Windows Server Failover Cluster (WSFC) can be assigned a drive letter.Box 2: 2Node2Node2 has only Disk 0 with volume letter C, and Disk1 with volume letter E. The Cluster Shared Volume on Node2 does not use a volume letter.Note: In a Windows Server Failover Cluster (WSFC), the number of disk volume letters used on each node can vary significantly and is not a fixed number; it is determined by the specific clustered applications, services, and their storage configurations, which may include physical disks with traditional drive letters or Cluster Shared Volumes (CSVs) which do not use drive letters. While traditional failover to a secondary node requires the same drive letters to be present, using mount points or CSVs allows for a more flexible and efficient use of storage, avoiding the 26-letter limit and enabling more shared storage.Factors influencing the number of volume letters:Type of Storage:Traditional Disks: Disks designated as physical disk resources in the cluster will have a drive letter, and this letter must be available on all nodes.Cluster Shared Volumes (CSVs): C, S, Vs do not use drive letters; instead, they are accessed through a folder path under C:\ClusterStorage (e.g., C:\ClusterStorage\Volume1). This method is particularly useful for workloads like Hyper-V and SQL Server.
https://learn.microsoft.com/en-us/windows-server/failover-clustering/failover-cluster-csvs
HOTSPOT (Drag and Drop is not supported)You have four servers that run Windows Server. Each server has the direct-attached storage (DAS) devices shown in the following table.You need to deploy Storage Spaces Direct.Which types of devices will be used for the cache, and what will be the default cache behavior? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: NVMe onlyDevice types for cacheThree-Tier (NVMe, SSD, HDD): When all three types of drives are present, the NVMe drives automatically serve as the cache. The SSDs and HDDs then provide the capacity for the data. NVMe cache accelerates both read and write operations for the capacity drives.Note: Cache drives are selected automaticallyIn deployments with multiple types of drives, Storage Spaces Direct automatically uses all drives of the fastest type for caching. The remaining drives are used for capacity.Which type is "fastest" is determined according to the following hierarchy.Box 2: Read/write and write-only.Cache behaviorCache behavior is set automaticallyThe behavior of the cache is determined automatically based on the type(s) of drives that are being cached for. When caching for flash drives (such as NVMe caching for SSDs), only writes are cached. When caching for rotating disk drives (such as SSDs caching for HDDs), both reads and writes are cached.
https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/cache
Post your Comments and Discuss Microsoft AZ-801 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-801 content, but please register or login to continue.