Note: This question is part of a series of
questions that use the same scenario. For your convenience, the scenario is repeated in each question. Each question presents a different goal and answer choices, but the text of the scenario is exactly the same in each question in this series.
A company
named Contoso, Ltd. has several servers that run Windows Server 2016. Contoso has a Hyper-V environment that uses failover clustering and Windows Server Update Services (WSUS). The environment contains several Windows containers and several virtual machine
s.
The WSUS deployment contains one upstream server that is located on the company-s perimeter network and several downstream servers located on the internal network. A firewall separates the upstream server from the downstream servers.
You plan to deplo
y a human resources application to a new server named HRServer5. HRServer5 contains a FAT32-formatted data volume.
The CIO of Contoso identifies the following requirements for the company-s IT department:
Deploy a failover cluster to two new virtual machi
nes.
Store all application databases by using Encrypted File System (EFS).
Ensure that each Windows container has a dedicated IP address assigned by a DHCP server.
Produce a report that lists the processor time used by all of the processes on a server name
d Server1 for five hours.
Encrypt all communication between the internal network and the perimeter network, including all WSUS communications.
Automatically load balance the virtual machines hosted in the Hyper-V cluster when processor utilization exceeds
70 percent.
You need to modify the Hyper-V cluster to meet the load balancing requirement for the virtual machine.
Which command should you run?
A.
(Get-ClusterParameter).AutoBalancerMode=2
B.
(Get-Cluster).AutoBalancerMode=2
C.
(Get-ClusterParameter).A
utoBalancerLevel=2
D.
(Get-Cluster).AutoBalancerLevel=2
https://docs.microsoft.com/en-us/windows-server/failover-clustering/vm-load-balancing-deep-dive
AutoBalancerLevel Aggressiveness Behavior
1 (default) Low Move when host is more than 80% loaded
2 Medium Move when host is more than 70% loaded
3 High Average nodes and move when host is more than 5% above average
0
0