70-740 Exam Simulation-CBT NUGGETS 1

06/03/2019 70-740 Exam Simulation
Quick Quiz March 6, 2019 Test ID: 94470532
Question #1 of 50 Question ID: 1138246
You manage a set of servers for a department that is in the verigon.com domain. The department has servers that
run Windows Server 2016.
You attempt to install a Windows 8 client into a generation 2 virtual machine that you booted from an ISO image of
Windows 8. During the installation process, you are unable to use the keyboard to enter the product key.
You need to install a client operating system on the generation 2 virtual machine. Which of the following are
possible solutions? (Choose two.)
✗ A) Use an ISO image of Windows 7 to install on the virtual machine
✓ B) Use an ISO image of Windows 8.1 to install on the virtual machine
✓ C) Use the dism utility to add the software keyboard driver from the CAB file
that contains the Integration Service for Windows 8.1
✗ D) Disable Secure Boot on the virtual machine
✗ E) Use the dism utility to add the hardware keyboard driver from the CAB file that
contains the Integration Service for Windows 8
Explanation
You can do either of the following to fix the keyboard issue:
Use an ISO image of Windows 8.1 or Windows 10 to install on the virtual machine
Use the dism utility to add the software keyboard driver from the CAB file that contains the Integration Service
for Windows 8.1
A generation 2 virtual machine does not contain an emulated i8042 keyboard device or a hardware keyboard driver.
There is only a software-based keyboard available with a generation 2 virtual machine. Unfortunately, there is no
software keyboard drive available with a Windows 8 or Windows 7 ISO image. There is one available with a
Windows 8.1 or Windows 10 ISO.
You can do an initial boot to an ISO containing a Windows 8.1 PE and launch the operating system installation from
there. You could also use the dism utility to add the software keyboard driver from the CAB file that contains the
Integration Service for Windows 8.1.
You cannot use a hardware keyboard driver with a generation 2 virtual machine because they do not contain an
emulated i8042 keyboard device.
You should not disable Secure Boot on the virtual machine. The Secure Boot feature of a generation 2 virtual
machine helps prevent unauthorized code from running at boot time.
https://www.kaplanlearn.com/education/test/print/27994229?testId=94470532 1/83
Objective:
Implement Hyper-V
Sub-Objective:
Configure virtual machine (VM) settings
References:
TechNet > Windows Server 2016 > Compute > Hyper-V > Should I create a generation 1 or 2 virtual machine in
Hyper-V?
TechNet > Windows Server 2016 > Compute > Hyper-V > Hyper-V feature compatibility by generation and guest
TechNet Library > Windows Server > Windows Server 2012 R2 and Windows Server 2012 > Server Roles and
Technologies > Hyper-V > Feature Overviews > Generation 2 Virtual Machine Overview
TechNet Blogs John Howard - Senior Program Manager in the Hyper-V team at Microsoft Hyper-V generation 2
virtual machines part 4
You have a Hyper-V host named HyperV1 that is a Windows Server 2016 server. You plan to add another physical
disk to HyperV1. You plan to create a VM named SQL1 that runs an Oracle database server on HyperV1. You plan
to store SQL1 and its virtual hard disk on the new physical disk. SQL1 will have four databases that write 8,192-
byte records for each database.
What allocation unit size should you configure on the new physical disk for HyperV1?
✗ A) 512 bytes
✗ B) 64 KB
✗ C) 32 KB
✗ D) 4 KB
✓ E) 8 KB
✗ F) 1 KB
✗ G) 16 KB
Explanation
You should configure the allocation unit size on the new physical disk as 8 KB. You should match the sector size,
referred to as the allocation unit size, closely to the typical file or record size that will be written to the disk. In this
scenario, the database server writes 8,192-byte records. You should configure the optimum allocation unit size
(sector size) as 8 KB. The 8 KB setting would allow for the server to write a complete database record in a sector
on the disk.
If you used a smaller allocation unit size, that you would have to split the record across multiple allocation units. For
example, a 4 KB allocation unit size would split the record across two allocation units. If you used a larger allocation
unit than 8KB, then you would be wasting space. If your allocation unit was 16KB, you could add an 8 KB record
into a 16 KB allocation unit, but you would be wasting 8 KB of space.
You should set the allocation unit at least as large as the record size. This configuration would reduce the workload
on the server's disk subsystem.
Objective:
Implement Storage Solutions
Sub-Objective:
Configure Disks and Volumes
References:
Avoid using virtual hard disks with a sector size less than the sector size of the physical storage that stores the
virtual hard disk file
You are the administrator for the Nutex Corporation. You want to list all available container base images with the
PowerShell cmdlet Find-ContainerImage. You get the following error message:
Find-ContainerImage: The term 'Find-ContainerImage' is not recognized as the name of a

cmdlet, function, script file, or operable program. Check the spelling of the name, or if a
path was included, verify that the path is correct and try again.
Which must you run to prepare your computer to run the Find-ContainerImage cmdlet?
✗ A) Install-ContainerImage
✗ B) Save-ContainerImage
✓ C) Import-ContainerImage
✓ D) Install-PackageProvider
Explanation
You should run the Install-PackageProvider and the Import-ContainerImage cmdlet to install the package
provider. Both of these cmdlets together will install the provider. The package provider is required to download the
PowerShell module with Container cmdlets.
You should not run the Save-ContainerImage cmdlet because this cmdlet downloads and saves a container image
without installation. However, before you can use any Docker PowerShell cmdlet, you have to install the package
provider and import the Docker PowerShell module.
You should not run the Install-ContainerImage cmdlet because this cmdlet installs the container image itself. For
example, the following installs the container image:
Install-ContainerImage -Name WindowsServerCore
Objective:
Implement Windows Containers
Sub-Objective:
Deploy Windows Containers
References:
Microsoft Docs > Windows Containers Quick Start > Windows container requirements
github / Microsoft / Docker-PowerShell / releases
github / Microsoft / PowerShell/ContainerProvider
MSDN > Windows and Windows Server Automation with Windows PowerShell > Windows PowerShell 5.1 >
PackageManagement > Install-PackageProvider
github / Microsoft / Docker-PowerShell / src / Docker.PowerShell / Help / Import-ContainerImage.md
You are the administrator for the Nutex Corporation. You have to install a Windows Server 2016 Nano Server VM as
a container host for testing purposes. The Nano Server will have an IP address of 172.16.1.122 and the Hyper-V
host will have an IP address of 172.16.1.100.
Which are the necessary steps to install the Containers feature on the Nano Server VM? Choose the required steps
from the left and place them in the correct order on the right.
{UCMS id=5630470576406528 type=Activity}
Explanation
Before you can create a Windows Server 2016 Nano Server virtual machine, you have to download the evaluation
VHD from Microsoft. Using this VHD, you can create a virtual machine, start the machine, and connect to the Nano
Server VM. After the VM is started, you will need to set the administrative password. You can do that inside the
Nano Server Recovery Console with F11.
You have to enumerate the IP address of the Nano Server in the Nano Server Recovery Console and add the Nano
Server IP address into the Trusted Hosts list. You should run Set-Item
WSMan:\localhost\Client\TrustedHosts 172.16.1.122 from the PowerShell prompt to allow remote
management of the Nano Server Hyper-V VM.
Because Nano Server cannot be configured locally, you have to enter into a PowerShell Remote Session from the
Hyper-V host using the Enter-PSSession PowerShell cmdlet. For this scenario, you should run Enter-PSSession
-Computername -172.16.1.122 -Credential Nutex\Administrator.
After entering the remote session, you have to install the Nano Server package provider by running Install-
PackageProvider NanoServerPackage from the PowerShell prompt. This step will allow you to install the
Containers feature.
Finally, you should install the Containers feature itself using the Install-NanoServerPackage -Name
Microsoft-NanoServer-Containers-Package command. As of this writing, Microsoft recommends that you
finish by installing critical Windows updates and restarting the computer.
You should not run Install-NanoServerPackage Microsoft-NanoServer-Compute-Package from the

PowerShell prompt because this command installs the Hyper-V role on the Nano Server VM. The Hyper-V role
does not have to be installed.
You should not run Set-item WSMan:\localhost\Client\TrustedHosts 172.16.1.100 from the PowerShell
prompt. The IP address of 172.16.1.100 is for the Hyper-V host and not for the Nano Server VM.
You should not run & $env:ProgramFiles'\docker\dockerd.exe' --register-service . This command

installs Docker as a Windows service. Docker is needed to work with Windows containers, but this scenario only
requires you to install the Containers feature, not perform detailed work on it.
You should not run Start-Service Docker. You do not have to install or start the Docker service on the Nano
Server VM to install the Containers feature on the Nano Server.
Objective:
Sub-Objective:
References:
Container host deployment Nano Server
Install And Configure Windows Nano Server As A Container Host
Microsoft Docs > Windows Containers on Windows Server
You plan to have a Web site that will benefit from Network Load Balancing (NLB). You plan to create an NLB that
will load balance traffic from clients on TCP ports 80. The following servers are available in the network:
You want to configure a NLB cluster. Which of the servers can be hosts in the NLB cluster?
✗ A) Web1 can host using unicast, Web2 can host using multicast, Web3 can host
using unicast, and Web4 can host using multicast
✗ B) Web1, Web2, and Web4 can be hosts with all adapters using unicast mode
✗ C) Web1, Web2, Web3, and Web4 can be hosts with all adapters using unicast
mode
✗ D) Web1 can host using multicast, Web2 can host using unicast, Web3 can host
using multicast, and Web4 can host using unicast
✗ E) Web1, Web2, Web3, and Web4 can be hosts with all adapters using multicast
mode
✓ F) Web1, Web2, and Web3 can be hosts with all adapters using unicast mode
✗ G) Web1, Web2, and Web4 can be hosts with all adapters using multicast mode
✗ H) Web1 can host using multicast, Web2 can host using unicast, Web3 can host
using multicast
Explanation
You can configure Web1, Web2, and Web3 as hosts with all adapters using either unicast mode or multicast mode.
The deployment requirements for NLB are the following:
All hosts must be on the same subnet.

All network adapters within a NLB cluster must have a static IP address. DHCP is disabled on each network
adapter that participates in the NLB cluster.
All network adapters within a NLB cluster must be configured the same, whether as unicast or multicast. You
cannot configure an NLB cluster with a mixture of unicast and multicast adapters. If you choose unicast, the
network adapter must support changing its MAC address.
In this scenario, Web1, Web2, and Web3 are on the 192.168.0.32/27 subnet. Web4 is on the 192.168.0.64/27
subnet. You can determine the IP address of a computer on a subnet by ANDing the IP address of computer on the
subnet by its subnet mask. The process of ANDing is to multiply the binary representation of the IP address against
the subnet mask. When you multiply a number by 1 the result is the original number, and when you multiply a
number by zero, the result is zero. For example, ANDing the IP address and subnet mask of WEB2 will yield the
following:
192.168.0.58 = 11000000.10101000.00000000.00111010
255.255.255.224 = 11111111.11111111.11111111.11100000
==================================================
192.168.0.32 = 11000000.10101000.00000000.00100000
The following graph shows subnets that are available with the /27 or 255.255.255.224 subnet masks:
You cannot have a Web4 as a host in a NLB cluster with Web1, Web2, or Web3 because Web4 is on a different
subnet than those servers.
All network adapters in the NLB cluster must be either unicast or multicast mode.
Objective:
Implement High Availability
Sub-Objective:
Implement Network Load Balancing (NLB)
References:
TechNet > Windows Server 2016 > Networking > Network Load Balancing
Technologies > Networking > Network Load Balancing Overview
TechNet Library > Windows Server > Windows Server 2008 R2 and Windows Server 2008 > Windows Server
Content by Category > Windows Server 2008 Content by Category > Installed Help for Windows Server 2008 >
Availability and Scalability > Network Load Balancing > Setting Network Load Balancing Parameters > Configure
Network Load Balancing Cluster Operation Mode
Microsoft System Center > How to Configure NLB for a Service Tier
Your company has a single Active Directory domain named nutex.com. All servers on the nutex.com network run
Windows Server 2012 R2. You have four servers with the Hyper-V role installed, named Host1, Host2, Host3,
andHost4. Their configurations and characteristics are shown in the following chart:
Host1 hosts a virtual machine named VSRV1, and is in the nutex.com forest. You have several other hosts that in
the nutex.com root domain or the south.nutex.com sub domain. You have one host that is not in a domain,
named Host3. You need to move the virtual hard drives (VHD) of VSRV1 to another Hyper-V host with the following
conditions:
VSRV1 must stay powered on during the move

During the move, VSRV1 should not experience any downtime
To which server and by which method should you move VSRV1? (Choose all that apply.)
✗ A) To Host6 by using live migration

✗ B) To Host3 by using live migration
✓ C) To Host5 by using live migration
✗ D) To Host4 by using live migration
Explanation
You can move to Host5 by using live migration. The live migration feature enables you to migrate a virtual machine
from one host to another without downtime. You can perform live migration if the virtual machines are highly
available or not. You can perform a live migration between Hyper-V hosts if the following requirements are met:
Hyper-V hosts that use processors from the same manufacturer. For example, all AMD or all Intel.
Hyper-V hosts that belong to either the same Active Directory domain, or to domains that trust each other such
as a sub domain or domains that are trusted by a forest trust.
VMs on the Hyper-V hosts have to be configured not to use physical disks, but virtual hard disks or virtual Fibre
Channel disks
Use of an isolated network such as a VLAN
If you have a cluster and want to perform a live migration in the cluster, the following conditions must be met:
Windows Failover Clustering is enabled and configured on the Hyper-V host.

Cluster Shared Volume (CSV) storage in the cluster is enabled on the Hyper-V host.
You can move a Hyper-V virtual machine in Windows Server 2012 to Hyper-V in Windows Server 2016, However,
you cannot move a Hyper-V virtual machine in Windows Server 2016 to Hyper-V in Windows Server 2012.
In Windows Server 2016, you can use virtual machine load balancing to optimize the utilization of nodes in a
failover cluster by live migrating VMs to idle nodes. Even though you can check the Migrate to a physical
computer with a different processor version setting in Hyper-V or use the -CompatibilityForMigrationEnabled
parameter of the Set-VMProcessor cmdlet, these options only allow you to enable compatibility between the same
CPU manufacturer. You will not be able to perform a live migration between an Intel and AMD CPU.
You cannot perform a live migration to either Host4 or Host6. Live migration requires migration to the same
processor architecture. Any time that you migrate a virtual machine from one host to another host with a different
processor architecture, you may receive the following error:
"Unable to migrate the virtual machine <virtual Machine Name> because the processor is not
compatible with the host <Host Name>"
You cannot perform a live migration to Host3 because Host3 is in a workgroup, and not in a trusted domain.
Objective:
Sub-Objective:
Availability Implement High Availability and Disaster Recovery Options in Hyper-V
References:
TechNet > Windows Server 2016 > Compute > Hyper-V > Manage > Use live migration without Failover Clustering
to move a virtual machine
Virtual Machine Live Migration Overview
Processor Compatibility Mode in Hyper-V
TechNet > Windows Server > Virtual Machine Storage Migration Overviews
TechNet > Windows Server > Server Roles and Technologies > Failover Clustering > What's new in Failover
Clustering in Windows Server 2016
TechNet Library > Windows Server > Windows Server 2012 R2 and Windows Server 2012 > Migrate Roles and
Features to Windows Server > Migrate Roles and Features to Windows Server 2012 R2 > Migrate Cluster Roles to
Windows Server 2012 R2 > Migration Paths for Migrating to a Failover Cluster Running Windows Server 2012 R2
You are the administrator of the Nutex Corporation. You have created a container named NutexCont1 with a data
volume. You want to mount the data volume of NutexCont1 into a new container named NutexCont2 so that all
data of the volume can be used with applications running in container NutexCont2.
What command should use to mount the volume?
✗ A) docker run -it -v c:\volume1 c:\volume2 NutexCont2
✗ B) docker run -it -volumes-from NutexCont2 NutexCont1 cmd
✗ C) docker run -it -v C:\datavolume NutexCont2 cmd
✓ D) docker run -it -volumes-from NutexCont1 NutexCont2 cmd
Explanation
You should run docker run -it -volumes-from NutexCont1 NutexCont2 cmd. This command mounts the data
volumes from the container NutexCont1 into the new container. The important part of the command is -volumes-
from parameter because it tells the source container from which the data volume will be mounted.
You should not run docker run -it -v c:\volume1 c: volume2 NutexCont2. With this command, the source
directory c:\ volume1 is mounted into a container as c:\ volume2.
You should not run docker run -it -volumes-from NutexCont2 NutexCont1 cmd because the data volumes
from container NutexCont2 will be mounted to container NutexCont1. In this scenario, you want to mount the data
volume of NutexCont1 into a new container named NutexCont2.
You should not run docker run -it -v C:\datavolume NutexCont2 cmd because this command creates a data
volume named datavolume. It will be accessible through the running container.
Objective:
Sub-Objective:
Manage Windows Containers
References:
Docker Docs > Get Started > Learn by example > Manage data in containers
Docker Docs > Reference > Engine (docker) CLI > Docker run reference
You are the administrator of the Nutex Corporation. You want to secure your Windows Server 2016 servers,
NutexSRV1 and NutexSRV2, against malware. To do so, you have defined following requirements:
Verify the existence of Windows Defender on the Windows Server 2016 server NutexSRV1 and NutexSRV2
Prepare the NutexSRV2 server to use an antimalware solution other than Windows Defender
Schedule definition updates checks every 4 hours on NutexSRV1
Prevent Windows Defender from sending any files to Microsoft on both NutexSRV1 and NutexSRV2
Which configuration should you choose? (Choose all that apply.)
✓ A) sc query Windefend
✗ B) Stop-Service Windefend
✗ C) Stop-Service Wdnissvc
✗ D) Set-MpPreference -ScanScheduleTime 4
✓ E) Set-MpPreference SubmitSamplesConsent 2
✓ F) Uninstall-WindowsFeature -Name Windows-Server-Antimalware
✓ G) Set-MpPreference -SignatureUpdateInterval 4
✗ H) Set-MpPreference SubmitSamplesConsent 0
Explanation
The sc query Windefend command can query whether Windows Defender is running on the server. The name of
the Windows Defender service is Windefend.
The Uninstall-WindowsFeature -Name Windows-Server-Antimalware command can remove Windows

Defender from your Windows Server 2016 server. Windows Defender is installed by default. In this scenario, you
want to use an antimalware solution other than Windows Defender. You have to uninstall Windows Defender before
installing the other antimalware solution.
The Set-MpPreference -SignatureUpdateInterval 4 PowerShell command can check for definition updates
every 4 hours.
The Set-MpPreference cmdlet configures the preferences for Windows Defender. The submitSamplesConsent 2
parameter determines how Windows Defender checks for user consent. A value of 2 for this parameter tells
Windows Defender to never send any files to Microsoft. Normally it is set to 0, which means that the Windows
Defender service always prompts to confirm submission of files to Microsoft.
You should not use Stop-Service Windefend because this will only stop the Windows Defender service. It will not
remove it from the server. To ensure no conflicts with the other antimalware solution, its best to remove Windows
Defender completely from the server before you install the third-party solution.
You should not use Stop-Service Wdnissvc. This command stops the Wdnissvc service, which is a sub-service of
Windows Defender service named Windefend. You have to remove the Windows Defender feature instead of
stopping a service.
You should not use Set-MpPreference -ScanScheduleTime 4. With this ScanScheduleTime value, Windows
Defender will will launch the scan at 4 minutes after midnight.
You should not use Set-MpPreference SubmitSamplesConsent 0. This is the default value of the
SubmitSamplesConsent value.
Objective:
Maintain and Monitor Server Environments
Sub-Objective:
Maintain Server Installations
References:
TechNet > Windows Server 2016 > Security and Assurance > Windows Defender Overview for Windows Server
2016
TechNet > PowerShell > Defender cmdlets > Set-MpPreference:
You administer the Windows Server 2016 Hyper-V hosts and virtual machine configurations for your network. You
want to enable Virtual Machine Queues (VMQs) functionality on your network adapters. You also want to use
Switch Embedded Teaming (SET).
Which settings you do you have to configure in order to influence network performance? (Choose all that apply.)
✗ A) SR-IOV
✗ B) Live migration
✗ C) QoS
✓ D) RssBaseProcNumber
✓ E) MaxRssProcessors
✓ F) GbE networking
Explanation
You will need to modify the Gigabit Ethernet (GbE), MaxRssProcessors, and RssBaseProcNumber settings.
You should not use 1GbE networking for Virtual Machine Queues (VMQs) with Switch Embedded Teaming (SET)
for performance reasons. Instead you should change the setting to a minimum of 10GbE.
The RssBaseProcNumber setting allows you to configure the interrupt coalescing and to tune VMQ. If you are
configuring more than one NIC, each NIC should have a different value assigned to the RssBaseProcNumber
setting, so that you do not overlap RSS processors.
The MaxRssProcessors setting should be configured to set more MaxRssProcessors. Doing so will provide more
CPU resources with which to tune VMQ performance.
You should not choose live migration. At the time of this writing, the live migration feature is not compatible with
SET. You cannot use live migration to influence network performance in this scenario.
You should not choose QoS. At the time of this writing, the QoS feature is not compatible with SET. You cannot use
the QoS feature to influence network performance in this scenario.
You should not choose SR-IOV. At the time of this writing, the SR-IOV feature is not compatible with SET. You
cannot use the SR-IOV feature to influence network performance in this scenario.
Objective:
Implement Hyper-V
Sub-Objective:
Configure Hyper-V networking
References:
TechNet > Windows Server 2016 > Compute > Hyper-V > What's new in Hyper-V on Windows Server 2016
TechNet > Windows Server 2016 > Networking > NIC Teaming
TechNet > Windows Server 2016 > Networking > What's New in Networking
Resources for IT professionals > Gallery > Networking > Windows Server 2016 NIC and Switch Embedded
Teaming User Guide
SET
VMQ RssBaseProcNumber
You run System Center Data Protection Manager (SCDPM) in a virtual machine in a Hyper-V host cluster. You have
to back up some components of your VDI environment. You want to use a Windows Server 2016 File and Storage
Server as a DPM storage solution to save VHD and VHDX backup files on an SMB share on that file server. You
have to configure the deduplication feature on the relevant volume.
Which usage type of data deduplication should you use?
✗ A) Virtual Desktop Infrastructure (VDI)

✗ B) Hyper-V
✓ C) Virtualized Backup Server
✗ D) General purpose file server
Explanation
You should choose the Backup usage type for virtualized backup applications. Data Deduplication uses the Backup
cmdlets in PowerShell to simplify the configuration for virtualized backup applications.
Data Deduplication has three different usage types for different workloads:
General purpose file servers used for team shares, work folders, folder redirection, or software development
shares.
Virtualized Desktop Infrastructure (VDI) servers.

Virtualized Backup Server - Ideal for backup servers that use virtualized backup applications, such as Microsoft
Data Protection Manager.
The Backup usage type has all relevant deduplication configuration settings needed to support virtualized backup
applications combined. After selecting this, all VHD and VHDX backup files on that volume will be deduplicated. A
backup of a large Virtual Desktop Infrastructure (VDI) deployment can result in very large savings in the range of
70-90+% range since there is typically a large amount of data duplication between the virtual desktop
environments.
You should not use the Default usage type for a general purpose file server. This usage type is used when the
existing data is relatively static with few changes. VHD/VHDX-backup files from a System Center Data Protection
Manager (SCDPM) server are not static files.
You should not use the Virtualized Desktop Infrastructure (VDI) type. This is best for Virtualized Desktop
Infrastructure (VDI) servers. The VDI usage type is a good choice if you want to deduplicate Hyper-V Virtual
machines, and you want to enable the deduplication of in-use files and automatically exclude the configuration file
extensions for virtual machines. VDI allows you to run multiple virtual machines on a physical machine.
There is no usage type called Hyper-V.
Objective:
Sub-Objective:
Implement Data Deduplication
References:
TechNet > Understanding Data Deduplication
TechNet > What's New in Data Deduplication
TechNet >Deduplicate DPM storage
Data Deduplication in Windows Server 2016:
You have a Windows Server 2016 server with the Hyper-V server role installed. You add several disks to the server
with a single partition for the full capacity of the disk.
You want to create three virtual machines (VM) running Windows Server 2016 that use a pass-through disk. When
you attempt to configure a pass-through disk on a virtual machine with a Fibre Channel Adapter, you notice that the
added disks are not listed.
What should you do?
✗ A) Use the Diskpart command to reinitialize the disk

✓ B) On the Hyper-V server, use the Disk Management snap-in to change the
newly added disks to an offline state
✗ C) Configure the pass-through disk on a SCSI controller
✗ D) On the Hyper-V server, use the Diskpart command to bring the newly added
disks online
✗ E) Configure the pass-through disk on IDE controller 1
✗ F) In the Disk Management snap-in, ensure that the disk has a partition marked
as Active
Explanation
You should use the use the Disk Management snap-in to change the newly added disks on the Hyper-V server to
an offline state. The guest operating system must have exclusive access to store on a Hyper-V server to use pass-
through disks. The disks should appear as a raw volume and in the Offline state to be used as a pass-through disk
on a virtual machine.
Pass-through disks provide great performance because they bypass the Hyper-V server file system and have direct
access to the physical disk from inside a virtual machine, thus providing faster access. The host and guest should
not try to use the disk at the same time. Hyper-V needs the disk on the host to be offline from the operating systems
perspective. Pass-through disks will not allow you to create any snapshots, use dynamic disks, or configure
differencing disks.
All other answers are incorrect.
In Windows Server 2012 and higher, the Hyper-V role provides pass-through support for direct MPIO-based iSCSI
and Fibre Channel attached disks. You do not have to have pass-through disks attached to either an IDE controller
or SCSI controller.
The pass-through disk does not have to be configured on the IDE controller1 instead of IDE controller 0. To have
the virtual machine boot from a pass-through disk, the disk must be attached to an IDE controller whether it is IDE
controller 0 or IDE controller 1.
A pass-through disk on a SCSI controller will not prevent a physical disk from appearing. A pass-through disk can
be attached to a SCSI controller, but the physical disk must be offline.
You should not use the Diskpart command to bring the newly added disks online. The physical disks must be
offline to be used as pass-through disks.
You do not have to have disk with a partition that is active on a physical disk to have a pass-through disk, but the
physical disk must be offline.
Objective:
Implement Hyper-V
Sub-Objective:
Configure Hyper-V storage
References:
Technologies > Hyper-V Overview
You have several Windows Server 2016 servers and several Windows Server 2012 R2 servers. Each of the servers
has several volumes.
Which of the following are true? (Choose all that apply.)
✗ A) You cannot use defrag.exe on ReFS formatted volumes on the Windows

Server 2016 servers
✓ B) NTFS volumes support data deduplication in both Windows Server 2012 R2
and Windows Server 2016
✗ C) You must use the GPT partition table format if the hard disk is larger than 1 TB
✓ D) NTFS volumes and ReFS volumes support data deduplication in Windows
Server 2016 only
✗ E) You cannot shrink NTFS volumes on the Windows Server 2016 servers
✗ F) You cannot extend ReFS volumes on the Windows Server 2016 servers
✗ G) ReFS formatted volumes support Encrypted File System (EFS) for files on the
Windows Server 2016 servers
✓ H) You must use the GPT partition table format if the hard disk is larger than 2 TB
✗ I) You can shrink ReFS volumes on the Windows Server 2016 servers
Explanation
You must use the GPT partition table format if the hard disk is larger than 2 TB
NTFS volumes support data deduplication in Windows Server 2012 and Windows Server 2016
Data deduplication is not supported on ReFS-formatted volumes in earlier versions of Windows Server 2016 or
Windows Server 2012 R2. Data deduplication is supported in Windows Server 2016 build 1709 and higher. You
cannot have data deduplication on volumes with multiple tiers.
You can only extend ReFS volumes. You cannot shrink ReFS volumes. The defrag utility with Windows Server 2016
both support and report on ReFS storage health.
The GPT partition table format must be used if the hard disk is larger than 2 TB. You can use the MBR partition
table format for disk drives are NOT larger than 2 TB.
In Windows Server 2012 R2, you could only support data deduplication on NTFS volumes only. However, in
Windows Server 2016, ReFS volumes can support data deduplication. exFAT does not support data deduplication.
You can resize NTFS volumes on both the Windows Server 2016 servers and the Windows Server 2012 R2
servers. This means that you can shrink or extend an NTFS volume.
ReFS does not support Encrypted File System (EFS) for files. Only NTFS supports EFS.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2016 > Storage > Data Deduplication > Data Deduplication interoperability
TechNet > Windows Server 2016 > Storage > ReFS > Resilient File System (ReFS) overview
What's the Difference Between GPT and MBR When Partitioning a Drive?
Windows Server 2012: Does ReFS replace NTFS? When should I use it?
Your company has a single Active Directory domain named nutex.com. You plan to host a Web site with Network
Load Balancing (NLB), so you plan to create an NLB cluster that will load balance traffic from clients. The following
conditions are in place:
The Web site application will be used for e-commerce shopping and must support SSL.
The application must retain products picked by a user in a shopping cart.
You will have four hosts in the NLB cluster.
You need to configure a custom port rule to determine how the hosts will respond to incoming network traffic. How
should you configure the cluster properties?
✗ A) Configure the Load Weight settings to 50

✓ B) Configure the affinity settings to Single
✗ C) Configure the Load Weight settings to 25
✗ D) Configure the affinity settings to None
✗ E) Configure the affinity settings to Network
✗ F) Configure the Load Weight settings to Equal
Explanation
When the user state must be maintained across TCP connections, you should configure the affinity setting to
Single. Single affinity ensures that requests from a specific client's IP address are sent to the same host in the
cluster within a given session, regardless of its traffic load. Applications that use SSL or applications that retain user
information, such as e-commerce shopping cart applications, will maintain their client state.
To specify the affinity setting of a port rule, you should open Network Load Balancing Manager, highlight the cluster
that you want to configure, and choose Cluster Properties.
On the Port Rules tab, choose the appropriate port rule and click Edit.
You should not configure the affinity settings to None. This affinity setting should be used for stateless traffic and to
ensure even load balancing among cluster hosts.
You should not configure the affinity settings to Network. The Network setting is sometimes referred to as Class C.
This affinity setting is used when clients connect from the Internet through proxy servers with different IP addresses
within the same Class C IP address range. ISPs that provide users with access to the Internet may have many
proxy servers. The Network option will direct requests from the same TCP/IP Class C address range.
The load weight settings are used to specify the method for distributing client requests. You can specify the method
as either Equal or Load Weight. The Equal setting distributes client requests across all hosts in a cluster when the
available system resources are the same. The Load Weight setting distributes client requests based on the
available system capacity because of differences in hardware configuration of a host or the applications and
services running on a host. You can configure the load weight values separately on each cluster host. If you specify
a load weight value of 0 for a host, the host will be prevented from handling any client requests. If you specified the
load weight equal across each host, then each host would handle an equal number of client requests.
If you specified ClusterHost1 and ClusterHost2 with the same weight and ClusterHost3 with a value that was half
that of ClusterHost1 and ClusterHost2, you would have each cluster host handling the following percentage of
client requests:
Changing the load weight percentage to Equal or to the same value will not help a client retain their client state.
Objective:
Sub-Objective:
References:
Setting Network Load Balancing Parameters
Server & Tools Blogs > Server & Management Blogs > Clustering and High-Availability> Network Load Balancing in
R2: Extended Affinity
All servers in the nutex.com domain run either Windows Server 2012 R2 or Windows Server 2016. You have a
server named SRV55 that runs Windows Server 2012 R2. You add five hard disks that are 1 TB each to SRV55.
You want to create a storage space that contains the five disks. The data will store financial documents from the
past seven years. You must ensure the following:
Fast performance for storage retrieval

Resiliency by tolerating two disk failures
What should you create?
✓ A) Mirrored space
✗ B) Simple space
✗ C) RAID-5 volume
✗ D) Parity space
✗ E) Striped volume
✗ F) Spanned volume
Explanation
You should create a mirrored space. A storage layout of a mirrored space can support up to two disk failures if you
have at least five disks in a storage pool. In Windows Server 2012 and above, storage pools can group collections
of physical disks into a storage area. These disks can be either SAS or SATA drives and can be installed internally
or externally, such as a JBOD or SAN array. You can use Server Manager to create a storage pool by expanding
File and Storage Services, expanding Servers, expanding Volumes and choosing Storage Pools. From the
Tasks menu, click New Storage Pool:
You should give the storage pool a name and choose the physical disks available to create the storage pool. You
can also use the New-StoragePool cmdlet to create a storage pool.
After the storage pool has been created you can create a virtual disk based on the storage pool, which is called a
storage space. You can also check Create a virtual disk when this wizard closes to be prompted to create a
virtual disk.
In the Virtual Disk Wizard, you can give your virtual disk a name. You can choose the layout of the virtual disk. The
storage layout of a virtual disk that is based on a storage pool can be any of the following storage spaces:
Simple - This layout stripes data across physical disks in the pool, maximizes the capacity, and increases
throughput. This layout only requires one or more disks, but DOES NOT protect from disk failure.
Mirror - This layout duplicates data on two or three physical disks. This layout will increase reliability. If you have
at least two disks, you can be protected from a single disk failure. If you have at least five disks, you can be
protected from two disk failures. Capacity will be limited because you are using some of the storage as a mirror.
Parity - This layout stripes data and parity across physical disks. This storage layout will require three or more
disks and will protect you from a single disk failure. You could not use this layout in a failover cluster prior to
Windows Server 2012 R2.
After you configure the storage layout, you can then choose to specify Thin or Fixed provisioning.
Thin - volume uses space from the storage pool as needed

Fixed - volume uses space from the storage pool equal to the volume size
You would then specify the size of your virtual disk. You can specify up to the size of the storage pool. You can then
use the volume wizard to create a volume and assign a drive letter.
All other options are incorrect.
A simple storage space will not support a disk failure.
Parity storage spaces are not supported on Windows 2012, but are supported on Windows 2012 R2 and later.
Parity storage spaces will support two disk failures if you have at least seven disks.
You do not have to specify the volume type because the underlying storage space will handle the fault tolerance.
You can configure a RAID-5 volume that will support a single disk failure or a striped volume that will not support a
disk failure, but the volume type is not relevant since the storage space is handling fault tolerance.
Objective:
Sub-Objective:
Implement Server Storage
References:
TechNet > Windows Server 2016 > Storage > Understanding > Fault tolerance and storage efficiency in Storage
Spaces Direct
TechNet > Windows Server 2016 > Storage > Storage Spaces Direct in Windows Server 2016
TechNet Library > Windows Server > Windows Server 2012 R2 and Windows Server 2012> Server Roles and
Technologies > File and Storage Services > File and Storage Services Overview
Technologies > File and Storage Services > Storage Spaces > Storage Spaces Overview
Petri IT Knowledgebase > Windows Server 2012 > How to Create a Storage Pool on Windows Server 2012 R2
TechNet > Wiki > TechNet Articles > Storage Spaces Overview
TechNet > Wiki > Storage Spaces Frequently Asked Questions
Your company has a single Active Directory domain named nutex.com, in which all network servers run Windows
Server 2016. You have a multi-node failover cluster that contains a disk witness. You need to restore a single
cluster node from backup. You need to restore the node to normal function without rolling back the cluster
configuration. You want to use the current configuration on the cluster node.
What should you do?
✗ A) perform an authoritative restore

✗ B) run cluster /Cluster:ClusterName node NodeName /force cleanup
✗ C) run cluster /Cluster: ClusterName /force cleanup
✓ D) perform a non-authoritative restore
Explanation
You should perform a non-authoritative restore. When a single node in the cluster is damaged or rebuilt, you use a
non-authoritative restore instead of an authoritative restore. You should use an authoritative restore when the
cluster configuration must be rolled back to a previous point in time. To perform a non-authoritative restore, restore
the system state information to the damaged node. Once the node has been restarted, the node will join the cluster
and receive the latest cluster configuration automatically.
In this scenario, you do not want to use the cluster configuration that is stored in the backup. You want to use the
current configuration on the cluster node. You can perform an authoritative restore by stopping the cluster resource
on each node, and the performing a system recovery (restore system state) on a single node by using Windows
Server Backup. After the restored node restarts the cluster service, the remaining cluster nodes can also start the
cluster service.
The cluster.exe command from previous versions of Windows Server is no longer supported in Windows Server
2012 and higher. The /force cleanup parameter manually restored the configuration of the cluster service on the
specified node to its original state.
Objective:
Sub-Objective:
Implement Failover Clustering
References:
TechNet > Windows Server> Server Roles and Technologies > Failover Clustering > What's New in Failover
TechNet > Windows Server 2008 R2 > Windows Server 2008 R2 Content By Category > Installed Help >
Availability and Scalability > Failover Clusters > Managing a Failover Cluster > Understanding Backup and
Recovery Basics for a Failover Cluster
You have a Hyper-V host named VMHOST1. You have a virtual machine named VM5 that runs Windows Server
2016. VM5 runs an application that all users in your department need to have continuous access to the tax records.
You need to make a backup of VM5.
Which of the following should you perform?
✗ A) From the PowerShell prompt, run the following:

Stop-VM -Name VM5 -Force
Get-VM | Export-VM -Name VM2 -Path D:\Backup
✗ B) In Hyper-V Manager, select VM5

Stop VM5
Export VM5 to an attached disk
✓ C) In Hyper-V Manager, select VM5

✗ D) In Hyper-V Manager, select VM5

Pause VM5
✗ E) From the PowerShell prompt, run the following:

Stop-VM Name VM5 -Force
Get-VM | Import-VM -Name VM2 -Path D:\Backup
✗ F) From the PowerShell prompt, run the following:

Stop-VM -Name VM5
Export-VM -Name VM2 -Path D:\Backup
Explanation
You should select VM5 in Hyper-V Manager and export VM5 to an attached disk.
Beginning with Windows Server 2012 R2, you do NOT have to stop or pause the virtual machine in order to export
the virtual machine. You can use Hyper-V Manager or the Export-VM cmdlet to export a virtual machine. You
should not pause or stop VM5. In this scenario, VM5 contains an app that all users need access.
Although you can export a running VM, when you import a VM, the status of the VM will be OFF.
All other options are incorrect because they pause or stop the VM.
Objective:
Implement Hyper-V
Sub-Objective:
References:
TechNet > Windows Server 2016 > Compute > Hyper-V > Export and Import virtual machines
Importing & Exporting Hyper-V VMs in Windows Server 2012 R2
You were asked to install several Windows Server 2016 servers into the Active Directory named nutex.com. You
installed servers SRV1 and SRV2 as full installations of Windows Server 2016. You installed SRV3 as a Server
Core installation of Windows Server 2016.
SRV2 and SRV3 will be shipped to a branch office. The junior administrator in the branch office had the following
requirements:
SRV2 must have a GUI installation of Windows Server 2016

SRV3 must have a DHCP server and a DNS server
SRV2 must have a FTP server and a WINS server
What should you do to configure SRV2 and SRV3 for these requirements?
✗ A) On SRV3, run Install-WindowsFeature DHCP, DNS

On SRV2, open Server Manager and click Features under the Add Roles
and Features Wizard to install a WINS server and FTP server.
✗ B) On SRV3, run Install-WindowsFeature DHCP, DNS.

On SRV2, open Server Manager and click Server Roles under the Add
Roles and Features Wizard to install a WINS server and FTP server.
✓ C) On SRV3, run Install-WindowsFeature DHCP, DNS

and Features Wizard to install a WINS server.
Roles and Features Wizard to install a Web server (IIS).
✗ D) On SRV3, run Install-WindowsFeature DHCP, DNS

On SRV3, run Uninstall-WindowsFeature Server-Gui-Shell
Restart
Roles and Features Wizard to install a WINS server and FTP server.
On SRV2, run Install-WindowsFeature Server-Gui-Shell Restart
✗ E) On SRV3, open Server Manager and click Server Roles under the Add
Roles and Features Wizard to install a DNS server.
and Features Wizard to install a DHCP server.
✗ F) On SRV3, open Server Manager and click Server Roles under the Add
Roles and Features Wizard to install a DNS and DHCP server.
Explanation
You should do the following:
On SRV3, run Install-WindowsFeature DHCP, DNS.

On SRV2, open Server Manager and click Features under the Add Roles and Features Wizard to install a
WINS server.
On SRV2, open Server Manager and click Server Roles under the Add Roles and Features Wizard to install a
Web server (IIS).
SRV3 is a Server Core installation of Windows Server 2016. You cannot use Server Manager to install any features
or roles on a Server Core edition. You must use the Install-WindowsFeature cmdlet to install features or roles.
You should run Install-WindowsFeature DHCP, DNS on SRV3 to install the DHCP server role and DNS server
role.
SRV2 is a full installation of Windows Server 2016, which will allow you to use GUI management tools such as
Server Manager to install features and roles. To install a WINS server, you must click Features under Add Roles
and Features Wizard. In Windows Server 2016, the WINS server is a feature and not a role.
To install an FTP server on a full installation of Windows Server 2016, you must select FTP Server under Web
Server (IIS).
All other answers are incorrect.
You cannot click Features in the Add Roles and Features Wizard of Server Manager on a full installation of
Windows Server to install a WINS server and FTP server.
You cannot click Server Roles in the Add Roles and Features Wizard of Server Manager on a full installation of
Windows Server to install a WINS server and FTP server.
You do not need to run Uninstall-WindowsFeature Server-Gui-Shell restart on SRV3 because SRV3 is
already a Server Core installation of Windows Server 2016. The Uninstall-WindowsFeature Server-Gui-Shell
cmdlet would uninstall the Server GUI shell on a Windows Server 2012 or Windows Server 2012 R2 server. In
Windows Server 2016, you cannot switch between Server Core and GUI installation types.
On a full installation of Windows Server 2012, Windows Server 2012 R2, or Windows Server 2016, you can use
Server Manager to install a DHCP and DNS server by clicking Server Roles under Add Roles and Features
Wizard. In Windows Server 2012 and above, the DHCP server and DNS server are roles and not features.
You can also use the Install-WindowsFeature cmdlet to install features and roles on a full installation of
Windows Server 2012 and above.
Objective:
Install Windows Servers in Host and Compute Environments
Sub-Objective:
Install, upgrade, and migrate servers and workloads
References:
TechNet > Windows Server 2016 > Management and Automation > Install or Uninstall Roles, Role Services, or
Features
TechNet > Windows Server 2016 > Management and Automation > Install or Uninstall Roles, Role Services, or
Features > Configure Features on Demand in Windows Server
Your container host is virtualized. You need to ensure that virtual machine named SRV55 may change the source
MAC address in outgoing packets to one that is not assigned.
You run the following command:
Get-VMNetworkAdapter -VMName SRV55 | *** M I S S I N G ***
In the space provided, enter the missing part of the command. Do not enter any part of the command that is already
provided. Use the - symbol to designate any parameters and use single quotes to designate any literals with the
command.
Explanation
Acceptable answer(s) for field 1:
Set-VMNetworkAdapter -MacAddressSpoofing On
You can use the following to set MAC address spoofing on the network adapter of the VM:
Set-VMNetworkAdapter -MacAddressSpoofing On
If your container host is virtualized, you must enable MAC address spoofing. MAC address spoofing changes the
source MAC address in outgoing packets to an address not assigned to them.
Objective:
Implement Hyper-V
Sub-Objective:
Configure Hyper-V networking
References:
MSDN > Windows and Windows Server Automation with Windows PowerShell > Windows Server 2016 and
Windows 10 > Hyper-V cmdlets > Set-VmNetworkAdapterIsolation
You need to migrate several server roles, operating system settings, and features from servers running Windows
Server 2012 R2 to servers running Windows Server 2016.
Which of the following should you perform? Choose the proper steps and place them in the correct order.
Explanation
You should do the following:
1. Install Windows Server Migration Tools on servers that run Windows Server 2016
2. Create deployment folders on migration destination servers, for copying to source servers
3. Copy deployment folders from destination servers to source servers

4. Register Windows Server Migration Tools on servers that run Windows Server 2012 R2
You should first install Windows Server Migration Tools on the destination servers, which in this scenario run
Windows Server 2016. You can migrate across subnets and between physical and virtual operating systems.
You should then create a deployment folder on the destination servers, which are Windows Server 2016 servers in
this scenario. You can use the SmigDeploy.exe tool provided in the Server Migration Tools folder to create the
destination folder:
SmigDeploy.exe /package /architecture amd64 /os WS16 /path deployment folder path
After the deployment folder has been created, you should copy it to the local drive of the source server, which is the
Windows Server 2012 R2 server in this scenario. You should then register Windows Server Migration Tools on the
source server using the SmigDeploy.exe tool in the destination folder.
You should not use the Active Directory Migration Tool (ADMT). This tool is used to migrate and restructure Active
Directory domains. You would not use this tool to migrate server roles, operating system settings, and features from
one server to another existing server.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2016 > Get Started > Server Role Upgrade and Migration > Server role upgrade and
migration matrix for Windows Server 2016
Install, Use, and Remove Windows Server Migration Tools
You have several Windows Server 2016 VMs on a cluster node that are not currently cluster resources. You want to
make an existing VM into a failover cluster in Windows Server 2016.
What should you use to create a failover cluster? (Choose all that apply.)
✗ A) Clussvc.exe
✓ B) New-Cluster
✗ C) Cluster.exe
✗ D) ComSvcConfig.exe
✓ E) Failover Cluster Manager
Explanation
You can use Failover Cluster Manager on the Tools menu in Server Manager to create a failover cluster. Once
Failover Cluster Manager is opened, click Create Cluster under Management. You can choose which servers that
you want to add as cluster nodes and enter the name that you want to give the cluster.
You can use the New-Cluster cmdlet to create a new cluster. The following example creates a failover cluster
named Cluster2 with nodes Srv1 and Srv2, assigns the static IP address 10.1.1.1, and adds all eligible storage to
the failover cluster:
New-Cluster -Name Cluster2 -Node Srv1, Srv2 -StaticAddress 10.1.1.1
You should not use the cluster.exe command. In previous versions of Windows Server, this command allowed you
to manage failover clusters via the command line. However, starting with Windows Server 2012, cluster.exe is no
longer installed and is deprecated.
You should not use Clussvc.exe. This executable file is the Cluster service. You cannot use this file to create or
configure a cluster.
You should not use ComSvcConfig.exe. This file is used to configure COM+ applications. You cannot use this file
to create or configure a cluster.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2016 > Compute > Failover Clustering > What's new in Failover Clustering in Windows
Server 2016
Create a Failover Cluster
Make a VM Highly Available in Windows Server 2012
You are the administrator of the Nutex Corporation. You want to remove the SMB 1.x protocol from your servers.
Before you do that, you want to evaluate whether some of your clients are still using SMB 1.x protocol. You have
the following requirements:
You want to use AES-128-GCM algorithm for SMB encryption

You want to allow clients unencrypted access to SMB shares that do not support SMB 3.1.1
Which PowerShell cmdlets should you use? (Choose three.)
✗ A) Set-SmbServerConfiguration -EncryptData $false
✗ B) Set-SmbServerConfiguration -AuditSMB1Access $false
✓ C) Set-SMBServerConfiguration -AuditSMB1Access $true
✗ D) Set-SmbServerConfiguration RejectUnencryptedAccess $true
✓ E) Set-SmbServerConfiguration -EncryptData $true
✓ F) Set-SmbServerConfiguration RejectUnencryptedAccess $false
Explanation
You should use Set-SMBServerConfiguration -AuditSMB1Access $true. This command verifies whether any
client is still trying to use SMB 1.0. To view the SMB 1.0 events, you can use the Get-Eventlog cmdlet:
Get-Eventlog -LogName Microsoft-Windows-SMBServer/Audit
You should use Set-SMBServerConfiguration -EncryptData $true. Since Windows Server 2016, the default
encryption algorithm is AES-128-GCM algorithm, and with this command, you will enable SMB encryption on your
servers.
You should use Set-SmbServerConfiguration RejectUnencryptedAccess $false to allow clients to connect

without encryption to an SMB share.
You should not use Set-SMBServerConfiguration -AuditSMB1Access $false because this command will
disable the possibility of auditing, which is not the requirement.
You should not use Set-SMBServerConfiguration -EncryptData $false because this command will disable
SMB encryption on the servers.
You should not use Set-SmbServerConfiguration RejectUnencryptedAccess $true because this command
will only allow encrypted access to the SMB share.
Objective:
Sub-Objective:
References:
What's new in SMB 3.1.1 in the Windows Server 2016
SMB 3.1.1 encryption
You are the network administrator for your company's Atlanta office. Your company has a branch office in Miami.
The company has deployed Windows Server 2012 and Windows Server 2016 on domain controllers and Windows
10 on client computers. In the Miami office, Windows Server Update Services (WSUS) has been installed on a
Windows Server 2008 R2 domain controller.
Your network experienced an application failure of the entire site in the Atlanta office which was caused by the
installation of an untested update. You decide to implement a test lab containing a representation of all computer
types in the Atlanta office along with a WSUS server on a Windows Server 2016 computer. Your goal is for these
computers to receive updates first, and for the other computers in the Atlanta site to receive the updates after
testing.
Which of the following approaches would achieve this goal in the most efficient manner with the least amount of
administrative effort? (Choose all that apply.)
✗ A) Create a replica server of the Miami WSUS server in the Atlanta office.
✓ B) Only approve updates for the All Computers group after testing them on the
test lab computers.
✓ C) Create the Miami WSUS server as a downstream server of the Atlanta office.
✓ D) Use server-side targeting to populate a group with the test lab computers.
✗ E) Use client-side targeting to populate a group with the test lab computers.
✗ F) Only approve updates for the test lab computers after testing them on the All
Computers group.
Explanation
You should create the Miami WSUS server as a downstream server of the Atlanta office, use server-side targeting
to populate a group with the test lab computers, and only approve updates for the All Computers group after
testing them on the test lab computers.
Computer groups are useful in WSUS for targeting updates to specific sets of computers. Computer groups can be
created with either client-side or server-side targeting. With client-side targeting, changes are made to the clients
(either by registry edits or through Group Policy) that enable them to automatically join an existing computer group.
With server-side targeting, the groups are both created and populated from the Computer page of the WSUS
Administration console. With either method, you can apply specific updates to a set of computers without offering
them to the general computer population. However, since server-side targeting is more efficient, it should be used in
this scenario to populate the group.
You should only approve updates for the All Computers group after testing them on the test lab computers to avoid
another side-wide application failure caused by untested updates. The All Computers group includes all computers
in the site.
You should not use client-side targeting to populate the group with the test lab computers. This requires the use of
either Group Policy or manual registry entries on the test computers. Server-side targeting involves creating and
populating the group on the WSUS server, which is quicker and more administratively efficient.
You should not create a replica server of the Miami WSUS server in the Atlanta office. A replica server will not allow
you to create new computer groups. A replica inherits the groups, updates, and the approval status of updates from
the upstream server.
You should not approve updates for the test lab computers after testing on the All Computers group. This is the
opposite of the scenario requirements. You should approve updates first for the test group only, and then later for
the All Computers group.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2016 > Management and Automation > Windows Server Update Services (WSUS)
TechNet > Windows Server 2016 > Management and Automation > Windows Server Update Services (WSUS) >
Managing WSUS Client computers and WSUS computer Groups
TechNet > Windows Server 2016 > Management and Automation > Windows Server Update Services (WSUS) >
Updates Operations
You are the administrator for the Nutex Corporation. You want to protect your virtualization infrastructure from
emerging threats and protect your VMs from compromised hosts through the use of shielded virtual machines and
guarded hosts.
You have several Hyper-V hosts that run the following virtual machines on a Windows Server 2016 guarded host:
You want to use Windows Server 2016 Nano Server for the shielded virtual machines. You must meet the following
requirements:
Ability to run Windows PowerShell commands in a virtual machine from the host
Ability to use PowerShell Desired State Configuration (DSC) for deploying and managing configuration data
Ability to use the Emergency Management Console to configure base network settings
Lower cost, faster boot and reboot times, smaller VHD size for the VM
Which virtual machines can you use as shielded virtual machines and install with Nano Server on the Windows
Server 2016 guarded host? (Choose all that apply.)
✗ A) VM5
✗ B) VM6
✗ C) VM2
✓ D) VM1
✓ E) VM3
✗ F) VM4
Explanation
You should use VM1 because this virtual machine is running on a host using Windows Server 2016 Datacenter
edition. Only with Datacenter edition can you use the shielded virtual machines feature. This is not possible with
Windows Server 2016 Standard edition.
The DNS-Server role can be installed through PowerShell with the New-NanoServerImage cmdlet:
New-NanoServerImage -MediaPath <path to root of media> -BasePath .\Base
-TargetPath .\NanoServerVM\NanoServerVM.vhd -ComputerName <computer name>
-DeploymentType Guest -packages Microsoft-NanoServer-DNS-Package.
The value Microsoft-NanoServer-DNS-Package for the -packages parameter defines the DNS-Server role to be
installed on the Nano Server in this example.
You should use VM3 because this virtual machine is running on a host using Windows Server 2016 Datacenter
Windows Server 2016 Standard edition. The File Server role can be installed through PowerShell command:
New-NanoServerImage -MediaPath <path to root of media> -BasePath .\Base -TargetPath

.\NanoServerVM\NanoServerVM.vhd -ComputerName <computer name> -DeploymentType Guest -packages
Storage.
The value Storage for the -packages parameter defines the File Server role to be installed on the Nano Server in
this example.
You should not use VM2 because this virtual machine is running on a host using Windows Server 2016 Standard
Windows Server 2016 Standard edition. The Web Server role can be installed through PowerShell:
New-NanoServerImage -MediaPath <path to root of media> -BasePath .\Base -TargetPath

.\NanoServerVM\NanoServerVM.vhd -ComputerName <computer name> -DeploymentType Guest -packages
- Packages Microsoft-NanoServer-IIS-Package.
The value -Packages Microsoft-NanoServer-IIS-Package for the -packages parameter defines the Web Server
role to be installed on the Nano Server in this example.
You should not use VM4 because there is no Nano Server Package option to install a DHCP Server on a Windows
Server 2016 Nano Server. In Windows Server 2016 TP5 you can use the PowerShell command to get a list of all
available Nano Server packages:
Find-NanoServerPackage Name *
edition. Only with Datacenter edition can you use the shielded virtual machines feature. The System Center Virtual
machine Manager Agent (SCVMM) can be installed through New-NanoServerImage cmdlet and the following
package options: Microsoft-NanoServer-SCVMM-Package, Microsoft-NanoServer-SCVMM-Compute-Package.
edition. Only with Datacenter edition can you use the shielded virtual machines feature. The Defender can be
installed through New-NanoServerImage and the package options -Defender.
Objective:
Sub-Objective:
Install and Configure Nano Server
References:
Redmond Magazine > Shield Hyper-V with Microsoft's Host Guardian Service
TechNet > Windows Server 2016 > Security and Assurance > Device Health attestation > Guarded fabric and
shielded VMs > Guarded fabric and shielded VMs overview
TechNet > Windows Server 2016 > Security and Assurance > Device Health attestation > Guarded fabric and
shielded VMs > Deploying the Host Guardian Service for guarded hosts and shielded VMs
TechNet > Server & Tools Blogs > Server & Management Blogs > System Center: Virtual Machine Manager
Engineering Blog > Configuring Guarded Hosts with Microsoft Virtual Machine Manager 2016
Step-by-Step Guide: Deploying Nano Server found in Windows Server 2016 TP5
Find-NanoServerPackage
Your company has a single Active Directory domain named nutex.com. You manage a Windows Server 2012 NLB
cluster that has five nodes and several virtual IP addresses. You want to upgrade the cluster to Windows Server
2016 while preserving the current cluster configuration, with minimal interruption of service to clients. You also want
to create IPv6 virtual IP addresses to handle IPv6 traffic.
Put the correct steps in order to perform a rolling upgrade. (Move the correct steps from the left column to the
column on the right, and place them in the correct order. Not all steps given may be required.)
Explanation
On the first three nodes, drainstop each node and set the initial host state to Stopped. You do not have to choose
three nodes, but you should select more than one and less than N-1, where N is the number of nodes in the cluster.
In this scenario, there are five nodes, so a number less than N-1 would be three.
You should ensure that nodes do not accept new client requests, but handle existing client requests. When you
issue the nlb.exe DRAINSTOP command, this will allow NLB to serve current connections and disable new
connections at the same time. The initial host state for the nodes that you select must be set to Stopped.
You should then upgrade the operating system on the selected nodes to Windows Server 2016. After the upgrade is
complete, you should change the initial host state back and start NLB on that node.
After you have upgraded the first three nodes, you should confirm that the nodes are still part of the NLB cluster
and are in a converged state.
Once that is complete, drainstop the remaining nodes and set the initial host state to Stopped. Then you should
upgrade the operating system to Windows Server 2016. After the upgrade is complete, confirm all nodes are part of
NLB cluster, are in a converged state, and are properly able to handle network traffic.
Once all nodes have had their operating system upgraded to Windows Server 2016, then you are able to create
new IPv6 virtual addresses on all network adapters in the cluster.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2016 > Networking > What's New in Networking
TechNet Library > Windows Server > Windows Server 2008 R2 and Windows Server 2008 > Browse Windows
Server Technologies > Network Load Balancing > Network Load Balancing Deployment Guide > Upgrading an
Existing Network Load Balancing Cluster
TechNet Library > Windows Server > Windows Server 2012 R2 > Server Roles and Technologies > Networking >
Network Load Balancing Overview
TechNet Library > Windows Server > Windows Server 2012 > Management and Tools > Windows PowerShell
Support > Network Load Balancing cmdlets > Stop-NlbCluster
You manage a set of servers for different departments in the verigon.com domain. The Accounting department has
all Windows Server 2008 R2 servers and the Tax department has all Windows Server 2012 R2 servers.
You plan to virtualize storage for both departments by grouping disk enclosures into storage pools, and then
creating virtual disks from the available capacity in the storage pools. You also want to ensure that if you need to
rebuild storage spaces, the storage spaces will automatically be rebuilt from storage pool free space instead of
using hot spares.
What should you do to ensure the servers meet the minimum configuration requirements to perform these tasks?
✗ A) Install the MultiPath I/O feature on the Accounting department servers and Tax
department servers
✓ B) Upgrade all Accounting department servers to Windows Server 2016
✗ C) Upgrade all Accounting department servers to Windows Server 2012
✗ D) Install the EnhancedStorage feature on the Accounting department servers
and Tax department servers
✗ E) Install the Install the BITS feature on the Accounting department servers
✗ F) Install the Message Queuing feature on the Accounting department servers
and Tax department servers
Explanation
You should upgrade all Accounting department servers to Windows Server 2016. With Windows Server 2012 R2
and above, storage spaces are automatically rebuilt from free space of storage pools instead of using hot spares.
Unlike previous versions of Windows, when a disk fails in Windows Server 2012 R2 or above, the data is copied to
multiple physical disks in the pool so that the previous level of resiliency is achieved. In previous versions, a single
hot spare was used to write a copy of the data that was on the failed disk. Once all servers in the Tax and
Accounting department are running Windows Server 2012 R2 or above, the servers can have storage spaces that
will automatically be rebuilt from storage pool free space instead of using hot spares.
You do not need to install the Background Intelligent Transfer Service (BITS) feature. BITS transfer files in
foreground or background, controls the flow of the transfers, and automatically resumes file transfers after the
computer restarts.
You do not need to install the Enhanced Storage feature. This feature provides support for accessing the additional
functions of Enhanced Storage devices.
You do not need to install the Multipath I/O feature. This feature, along with the Device Specific Module (DSM),
provides support for using multiple data paths to a storage device on a Windows Server.
You do not need to install the Message Queuing feature. This feature provides guaranteed message delivery,
efficient routing, security, and priority-based messaging between applications.
Objective:
Sub-Objective:
References:
Spaces Direct
TechNet > Windows Server 2012 R2 > Server Roles and Technologies > Storage Spaces > What's New in Storage
Spaces in Windows Server 2012 R2
You have a Windows Server 2016 server with the Hyper-V server role installed, named HyperV1. You need to
create a virtual machine, named VMSRV1, that will run Windows Server 2016 and require 2.5 TB of storage.
VMSRV1 will run applications with high levels of disk activity.
What should you configure?
✗ A) Create a dynamically expanding disk named SRV1.vhd for VMSRV1

✗ B) Create a differencing disk named SRV1.vhdx for VMSRV1
✗ C) Create a dynamically expanding disk named SRV1.vhdx for VMSRV1
✗ D) Create a differencing disk named SRV1.vhd for VMSRV1
✓ E) Create a fixed disk named SRV1.vhdx for VMSRV1
✗ F) Create a fixed disk named SRV1.vhd for VMSRV1
Explanation
You should create a fixed disk named SRV1.vhdx for VMSRV1. In Windows Server 2012 and above, you can
create a virtual hard disk in the VHD, VHDX, or VHDS format. The VHD format supports virtual hard disks up to 2
TB in size and the VHDX format supports virtual disks up to 64 TB. The VHDS format is used for guest clusters in
Windows Server 2016. It stores checkpoint information about the guest clusters' virtual disk used.
The VHDX format is designed to help protect against data corruption during power failures by logging updates to
the VHDX metadata structures. VHDX virtual hard disks work well on large sector disks. In this scenario, VMSRV1
must support data 2.5 TB of storage and have protection against data corruption during power failures.
You should use a fixed size virtual hard disk instead of dynamically expanding virtual hard disk. A fixed size virtual
hard disk is recommended for servers that have high levels of disk activity. A dynamically expanding virtual hard
disk will create a small initial size file that will expand as needed. Although a fixed size virtual hard disk will provide
better performance than a dynamically expanding virtual hard disk, the size of a fixed size virtual hard disk is
created to the size of the disk that you set. In other words, if you create a 2.5 TB fixed size virtual hard disk, the size
of the file will be 2.5 TB.
You should not create a differencing disk instead of an undo disk for the VHDX disks. A differencing disk isolates
changes to a virtual hard disk or the guest operating system by storing them in a separate file. A differencing disk
uses parent child relationship, whereas the differencing disk is the child to the parent virtual hard disk. An undo disk
also associates changes to a separate file. However, an undo file associates all changes to the virtual machine and
any of the virtual hard disks to the separate file. A differencing disk only associates changes of the parent disk to a
separate file. In this scenario, you would have to create a parent disk for the differencing disk to reference.
When creating a differencing disk, all children must have the same virtual hard disk format as the parent. In other
words, if your parent virtual hard disk is VHDX, your differencing disk must use the VHDX format, not the VHD
format.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2016 > Compute > Hyper-V > Create a virtual machine in Hyper-V
Technologies > Hyper-V > Feature Overviews > Hyper-V Virtual Hard Disk Format Overview
TechNet Library > Other Microsoft Product and Technologies > Virtual Server 2005 > Virtual Server: Operations >
Virtual Server Operations Guide > Using Virtual Server > Managing Virtual Hard Disks > Using differencing disks
You are the administrator of the Nutex Corporation. You have installed a Windows Server 2016 WSUS server
named NutexWSUS. You notice data corruption problems on the WSUSContent folder.
Which PowerShell command will solve the problem?
✗ A) Set-MpPreference -QuarantinePurgeItemsAfterDelay 0
✗ B) Set-MpPreference -DisableAutoExclusions $true
✓ C) Set-MpPreference -DisableAutoExclusions $false
✗ D) Set-MpPreference -ExclusionPath %systemroot%\WSUS\WSUSContent
Explanation
You should use Set-MpPreference -DisableAutoExclusions $false. The Set-MpPreference cmdlet

configures the preferences for Windows Defender. The DisableAuto Exclusions $false parameter enables
automatic exclusions. This has affected performance and results in data corruption on the WSUSContent folder,
which is automatically excluded from scanning through Windows Defender by default. Therefore, you should re-
enable the automatic exclusions feature.
Auto Exclusion is automatically optimized for Windows Server 2016 and will not scan the following WSUS-relevant
folders: %systemroot%\WSUS\WSUSContent, %systemroot%\WSUS\UpdateServicesDBFiles,
%systemroot%\SoftwareDistribution\ Datastore, %systemroot%\SoftwareDistribution\Download
You should not use Set-MpPreference -DisableAutoExclusions $true. The command cause of the corruption
problems on the WSUSContent folder are the disabled automatic exclusions. This command will disables
automatic exclusions again.
You should not use Set-MpPreference -QuarantinePurgeItemsAfterDelay 0. This command defines the
amount of days to keep files in quarantine. If you specify a value, files stay in quarantine.
You should not use Set-MpPreference -ExclusionPath %systemroot%\WSUS\WSUSContent. This command

specifies a file path to exclude from scheduled and real-time scanning. If automatic exclusions is enabled this path
automatically will be excluded.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2016 > Security and Assurance > Windows Defender > Automatic exclusions for
Windows Defender on Windows Server 2016
TechNet > Windows Server 2016 > Management and Automation > Windows Server Update Services (WSUS)
You are the administrator for the Nutex Corporation. You are responsible for a Windows Server 2016 Hyper-V
failover cluster. There were some intra-cluster communication failures over and over again. In the Failover Cluster
Manager tool some of your VMs have a state of quarantined. After two hours you solved the communication failures
of the cluster node. The hosts VMs are still in quarantined state. You manually want to enforce a running state for
the relevant VMs. For the future, it should possible to rejoin the node after one hour.
Which commands and settings should you use for that? (Choose all that apply.)
✗ A) (Get-Cluster).ResiliencyPeriod = 120
✓ B) Start-ClusterNode -cq
✓ C) (Get-Cluster).QuarantineDuration = 3600
✗ D) Suspend-ClusterNode -forcedrain
Explanation
You should run Start-ClusterNode -cq. This command starts the cluster service on a node in a failover cluster
using the -cq or -ClearQuarantine parameter, which clears the quarantined state. If the cluster node is in the
quarantined state, the node is no longer allowed to join the cluster for two hours by default. A node is quarantined if
it leaves the cluster three times within an hour. After two hours, you can rejoin the node.
You should run (Get-Cluster).QuarantineDuration = 3600. The default QuarantineDuration value is 7200,
which means that during two hours (7200 seconds) the node cannot be added to the cluster again. You have to wait
until the two hours are over.
You should not run Suspend-ClusterNode -forcedrain. This command will move the roles off the draining node,
even if the group cannot move either role. No other node can host this group if it is in a locked state. You want to
enforce a running state for the relevant VMs and want to bring back the VMs on the failed node to a running state.
To accomplish that, the node has to come out of the quarantine state. You will not meet the future requirement to
rejoin the node already after one hour without suspending the node.
You should not run (Get-Cluster).ResiliencyPeriod = 120. This command sets the amount of time in
seconds that the node is allowed to run in isolated state. The default value = 240 seconds (4 minutes).
Objective:
Sub-Objective:
References:
Virtual Machine Compute Reiliency in Windows Server 2016
Suspend-ClusterNode
Windows Server 2016.
You plan to configure a multi-node failover cluster. You have several physical computers and network hardware
components that are certified for Windows Server 2016. All servers that will be nodes in the cluster are members in
the nutex.com domain. All servers will use dc1.nutex.com as their DNS sever. The dc1.nutex.com server is a
domain controller that contains an Active Directory-integrated zone for nutex.com. All servers will run Windows
Server 2016 and will be cloned.
Which of the following are true regarding failover cluster implementation? (Choose all that apply.)
✗ A) The same roles and features should be installed on each node in the cluster,
including the AD DS role.
✗ B) The user account that creates the cluster must be a member of the Server
Operators group on each server in the cluster and have the Add
workstations to the domain permission.
✓ C) All nodes must run an x64-based processor from the same processor family.
✗ D) The network adapters in a cluster network must receive IP addresses from
DHCP.
✓ E) Running the Validate a Configuration Wizard on any imaged nodes will create
a report named %SystemRoot%\Cluster\Reports\Validation Reportdate
and time.html
✓ F) Running the Test-Cluster cmdlet on any imaged nodes will create a report
named %SystemRoot%\Cluster\Reports\Validation Reportdate and
time.html
✗ G) All nodes must run the same edition of Windows Server 2016 in a Server Core
installation only.
✗ H) The user account that creates the cluster must be a member of the Server
Operators group on each server in the cluster and have the Create
Computer Objects permission in the domain.
✗ I) All nodes must run the same edition of Windows Server 2016 in a full
installation only.
✓ J) The network adapters in a cluster network must have static IP addresses.
✓ K) The user account that creates the cluster must be a member of the
Administrators group on each server in the cluster and have the Create
Computer Objects permission in the domain.
✗ L) All nodes must run an x64-based processor in the same processor
architecture, but not the same processor family.
✓ M) The same roles and features should be installed on each node in the cluster,
excluding the AD DS role.
Explanation
The following statements are true regarding failover cluster implementation:
The same roles and features should be installed on each node in the cluster, excluding the AD DS role
The user account that creates the cluster must be a member of the Administrators group on each server in the
cluster and have the Create Computer Objects permission in the domain
All nodes must run a x64-based processor from the same processor family
Running the Validate a Configuration Wizard on any imaged nodes will create a report named
%SystemRoot%\Cluster\Reports\Validation Reportdate and time.html
You can also use the Test-Cluster cmdlet to run all cluster validation tests. When you use the Test-Cluster
PowerShell cmdlet, you can use the -ReportName parameter to specify the name and location of the validation
report.
When creating a failover cluster, your servers and network hardware must be marked with the Certified for Windows
Server logo. The server nodes should be connected to multiple networks for communication redundancy. If the
servers are connected to a single network, you should have redundant network adapters to remove single points of
failure. The network adapters should be identical and have the same speed, duplex, and flow control capabilities.
The nodes in the cluster must use DNS for name resolution and all reside in the same Active Directory domain.
The network adapters in a cluster network must have the same IP address assignment method, which can be either
DHCP leased addresses OR manual assigned static addresses. All the network adapters must use the same
method.
Microsoft recommends that you install the same features and server roles on each cluster in a node, except the AD
DS role. If each cluster node has different server roles and features, instability and performance issues may arise.
The AD DS role allows a server to be a domain controller. Since a domain controller in Active Directory supports a
multimaster read-write copy of the Active Directory database and has its own fault tolerance method, there is no
need to use a failover cluster for fault tolerance.
A user that will create the cluster must be a member of the Administrators group, not the Server Operators
group, on each cluster node. That user will also need the Create Computer Objects permission in the domain to
create the computer accounts for the server nodes in the domain. The Server Operators group cannot install a
node into a cluster. The Add workstations to the domain permission allows a user to create up to 10 computer
accounts on a domain.
Each server node must run the same processor architecture x64-based, which means that each node must have
same processor family. You cannot mix and match different processor families, such Intel Xeon and AMD Opteron.
All nodes must run the same edition of Windows Server 2016. Although the default installation of Windows Server is
the Server Core edition, you can also use the full installation of Windows Server 2016. You are not forced to use
either edition of Windows Server. However, all nodes should have the same service pack and updates.
When servers are cloned or imaged to different hardware, you must run the Validate a Configuration Wizard. You
would need to run the Validate a Configuration Wizard with any new cluster. When you run the Validate a
Configuration Wizard, an output file of the validation report can be found at
%SystemRoot%\Cluster\Reports\Validation Report date and time.html.
Objective:
Sub-Objective:
References:
TechNet Library > Windows Server Failover Clustering > Validate Hardware for a Failover Cluster
TechNet Library > Windows Server > Failover Clustering Hardware Requirements and Storage Options
TechNet Library > Windows Server > Management and Tools > Windows PowerShell Support > Failover Clusters
cmdlets > Test-Cluster
You are the administrator for the Nutex Corporation. You have a host that is part of a failover cluster. The failover
cluster contains four Hyper-V nodes with four 8-core processors that do not have hyperthreading enabled, and a
total of 32 logical processors. The host has four NUMA nodes with eight cores each.
You create a virtual machine named SQL1VM with 16 vCPUs and statically assign half of the host's memory. After
the live migration process has finished and SQL1VM has moved to another Hyper-V host, you notice unacceptable
performance problems on SQL1VM. The new Hyper-V host has enough processor and RAM capacity to run the
virtual machine.
Which configuration setting should you use to solve the performance issues on SQL1VM?
✗ A) Configure the Maximum amount of memory (MB) field

✗ B) Configure the Maximum number of processors field
✓ C) Click Use Hardware Topology
✗ D) Configure the Maximum NUMA nodes allowed on a socket field
Explanation
You should click the Use Hardware Topology button because this will reset the virtual NUMA topology to match
the underlying physical one of the new Hyper-V host. The new Hyper-V host has four cores per NUMA node instead
of the eight cores on the old Hyper-V host. The virtual machine will not be able to learn the new NUMA layout of the
new Hyper-V host unless you manually reset the hardware topology.
You should not configure the Maximum amount of memory (MB) field because this setting defines the maximum
amount of RAM that any NUMA node on any host will have. When you click the Use Hardware Topology button,
this field will be set automatically.
You should not configure the Maximum number of processors field because this defines how the maximum
number of processors will be in any NUMA node that the virtual machine finds on any host. When you click the Use
Hardware Topology button, this field will be set automatically.
You should not configure the Maximum NUMA nodes allowed on a socket field because this setting can range
from 1-64 and is dependent on the available hardware on the host. When you click the Use Hardware Topology
button, this field will be set automatically.
Objective:
Implement Hyper-V
Sub-Objective:
References:
TechNet > How to Configure Virtual NUMA for VMM
A closer look at NUMA Spanning and virtual NUMA settings
You are the administrator of the Nutex Corporation. You have configured a Windows Server 2016 failover cluster
with two Hyper-V nodes, NutexHost1 and NutexHost2. You want to perform a live migration to move a VM named
NutexVM1 from NutexHost1 to NutexHost2. You are logged in at NutexHost1. You want to perform this task
using the least administrative effort while ensuring good security.
You do not want to enable constrained delegation in Active Directory. Which protocol(s) and standard(s) can you
use? (Choose all that apply.)
✓ A) CredSSP
✗ B) NTLM
✓ C) WS-MAN
✗ D) Kerberos
Explanation
You should use CredSSP and WS-MAN. If you use CredSSP, you have to be logged in on the source server to start
the live migration process. CredSSP in Windows Server 2016 allows you to migrate a VM without enabling
Kerberos constrained delegation (KCD).
You should use WS-MAN. In Windows Server 2016, Hyper-V Manager has been updated to communicate with
remote Hyper-V hosts using the WS-Man protocol. WS-MAN permits CredSSP.
You should not use Kerberos. If you use Kerberos for authentication, you have to enable Kerberos constrained
delegation, and this will mean more configuration effort.
You should not use NTLM because this is an older authentication protocol. It is not as secure as Kerberos or
CredSSP.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2016 > Compute > Hyper-V > Manage > Use live migration without Failover Clustering
to move a virtual machine
TechNet > Windows Server 2016 > Compute > Hyper-V > Deploy > Upgrade virtual machine version in Hyper-V on
Windows 10 or Windows Server 2016
TechNet > Windows Server 2016 > What's New in Windows Server 2016
TechNet > Core Modules > PowerShell 5.0 > Microsoft.WsManagement Modules > Enable-WSManCredSSP
You are the administrator for the Nutex Corporation. You have created some Docker containers on a Windows
Server 2016 Nano Server. You want to configure some configuration options for the Docker daemon, like a DNS
server and a default gateway for all containers.
Which file you do you have to edit to set this configurations?
✓ A) %programdata%\docker\config\daemon.json
✗ B) /var/lib/docker/containers/6dd55be/json.log
✗ C) /etc/docker/daemon.json
✗ D) /usr/lib/systemd/system/docker.service
Explanation
You should edit the %programdata%\docker\config\daemon.json file because this is the configuration file for the
Docker daemon on Windows systems. The docker daemon dns 172.16.0.10 command sets the DNS server's IP
address for all Docker containers. The docker daemon default gateway 172.16.0.11 command sets the
gateway IP address for all Docker containers.
You should not edit the /usr/lib/systemd/system/docker.service file. The docker.service file is for options about
the Docker service itself and not for customized Docker configuration options like the DNS server or default
gateway. With the command ps ef, you can only report configuration parameters that are passed via
docker.service.
You should not edit the /var/lib/docker/containers/6dd55be/json.log file because this is the Docker container log
file. "6dd55be" in this example is the container ID.
You should not edit the /etc/docker/daemon.json file because this is the Docker options configuration file on Linux
machines.
Objective:
Sub-Objective:
References:
Docker > Admin Guide > Configure and run Docker on various distributions
Microsoft Docs > Windows Containers > Manage Docker on Windows > Docker Engine on Windows
Docker File Reference
Configuring the Docker json-file Logging Driver
How to check docker daemon options when using daemon.json
Windows Server 2016. You have several Hyper-V hosts that are part of a failover cluster. You need to move virtual
machines from one failover cluster node to another in the same cluster. You need to ensure the following:
Several virtual machines are moved at the same time

Users who are connected to the virtual machine should experience no server outage
What should you do?
✗ A) Perform a live migration on each virtual machine that needs to be moved

✗ B) Multiselect virtual machines for a quick migration
✗ C) Perform a quick migration on each virtual machine that needs to be moved
✓ D) Multiselect virtual machines for a live migration
Explanation
You should perform a live migration by multiselecting multiple virtual machines for a live migration. Live migration is
a feature introduced in Windows Server 2008 R2 Hyper-V that enables you to move running virtual machines
transparently from a failover cluster node to another node in the same cluster, without having a dropped network
connection or downtime. The memory of a running virtual machine is transferred to a new node during a live
migration failover. The ownership of the virtual machine and the shared storage switches to the destination host.
During a live migration the following happens:
The session state is maintained

No reconnections are necessary
All clients stay connected to the migrated VM
Address Resolution Protocol (ARP) redirects clients to new node
The old VM is deleted after the VM is successfully migrated
Live migration is more efficient with CSV because the migration is completed within the TCP reconnect window, and
eliminates the need to unmount and remount the volume. A network migration copies a VM over the network using
BITS between a library and a host or a host and another host. A live migration or network migration can occur on an
online CSV volume.
In Windows Server 2016, you can now run multiple live migrations simultaneously instead of running a single live
migration at a time. An administrator can perform multiselect actions to queue live migrations of more than one
virtual machine at a time. In Windows Server 2008 R2, you could only migrate a single virtual machine at a time.
You should not choose quick migration. Live migration is similar to quick migration. Quick migration migrates a VM
in less than a minute by putting the VM into saved state while it is moved from one cluster node to another using the
cluster failover mechanism. Live migration is slower than quick migration because it takes longer to do the actual
move, even though the client remains connected. Unlike the quick migration process, live migration does not save
the state of the virtual machine. Live migration synchronizes the state during failover, which eliminates downtime.
Both quick migration and live migration require Windows Server 2008 or later failover clustering.
Objective:
Sub-Objective:
Manage Virtual Machine Movement in Clustered Nodes
References:
TechNet > Windows Server 2016 > Networking > What's New in Failover Clustering in Windows Server 2016
TechNet Library > Windows Server > Server Roles and Technologies > Hyper-V > Feature Overviews > Virtual
Machine Live Migration Overview
TechNet Library > Windows Server > Windows Server 2012 and Windows Server 2012 R2 > Server Roles and
Technologies > Failover Clustering > What's New in Failover Clustering
TechNet > Windows Server 2016 > Compute > Hyper-V > Deploy > Set up hosts for live migration without Failover
Clustering
Windows Server 2012. You plan to upgrade a two-node failover cluster to Window Server 2016. You only will have
the two servers in the cluster, Node1 and Node2, and will not have any additional computers available for new
cluster nodes.
How should you perform the upgrade? (Move the correct steps from the left column to the column on the right, and
place them in the correct order. Not all steps given may be required.)

Explanation
There are two ways to migrate cluster roles from one server to another: by migrating cluster roles to a new cluster
with new servers, or by performing an in-place migration with only two nodes. In this scenario, you must perform an
in-place migration on a two-node cluster because you do not have another server to add to the cluster. You will
upgrade one of the servers to Windows Server 2016 and allow one existing server to continue running Windows
Server 2012 and the cluster service while you begin the migration process.
To begin migration, you must first remove resources from a node, and then evict that node from a cluster. After you
have completed these actions on the first node (Node1), you should perform a clean installation of Windows Server
2016 on that server.
After Windows Server 2016 is installed, you will install the failover cluster feature and create a one-node failover
cluster. You should then migrate the clustered services and applications from the old cluster node to the new
failover cluster, located on Node1, and then remove Node2 from the old cluster.
The last steps are to install Windows Server 2016 and install the failover cluster feature on Node2. You should then
add the server to the failover cluster. Lastly, you should run validation tests to confirm that the overall configuration
works correctly.
Note that you can use the Cluster Migration Wizard to migrate clustered roles, but the Wizard does not copy data
from one storage location to another. You must copy or move data or folders (including shared folder settings)
during a migration.
Objective:
Sub-Objective:
References:
TechNet > The Storage Team at Microsoft > Deploying DFS Replication on a Windows Failover Cluster
TechNet Library > Windows Server > Windows Server 2012 and Windows Server 2012 R2 > Server Roles and
Technologies > Failover Clustering > What's New in Failover Clustering in Windows Server 2012
HYPERLINK "http://technet.microsoft.com/en-us/library/hh847239.aspx" TechNet Library > Scripting with Windows

PowerShell > Windows and Windows Server > Automation with Windows PowerShell > Failover Clusters cmdlets
Your network contains an Active Directory domain named CDPressinc.com. The servers run Windows Server
2016. You are manually creating a custom data collector set on SRV1, and you are presented with the dialog box
shown below.
Which option would you select to record the amount of Active Directory data replicated between domain
controllers?
✗ A) Performance counter alert

✗ B) System configuration information
✗ C) Event trace data
✓ D) Performance counter
Explanation
You should select Performance counter. The available settings in this dialog box are explained below.
Performance counter - provides metric data about the system's performance.

Event trace data - provides information about activities and system events.
System configuration information - allows you to record the state of, and changes to, registry keys.
Performance Counter Alert - this is chosen if you are creating this set to monitor performance counters rather
than create data logs.
An example of a performance counter alert is shown below. This one is set to automatically run a program when the
amount of total free disk space on Admin1 drops below 10 percent of Capacity:
Data collector sets are used to organize and package information to be collected from systems. The results can be
used also to create logs and trigger actions.
Objective:
Sub-Objective:
Monitor Server Installations
References:
TechNet Library > Windows Server > Create a Data Collector Set Manually
TechNet Library > Windows Server > Create a Data Collector Set to Monitor Performance Counters
Your network contains an Active Directory domain named nutex.com. All servers run Windows Server 2016. All
client computers run Windows 7 or Windows 10.
The server named FS55.nutex.com has a volume named LegalPatentDocs. Several documents were deleted.
You must restore the data for the LegalPatentDocs volume.
Which of the following should you run to restore the volume as quickly as possible?
✓ A) From a command-line prompt, run the wbadmin start recovery command

✗ B) From a PowerShell prompt, run Add-WBSystemState
✗ C) From a command-line prompt, run the wbadmin start sysrecovery command
✗ D) From a PowerShell prompt, run Add-BareMetalRecovery
✗ E) From a command-line prompt, run the wbadmin start systemstaterecovery
command
Explanation
You should run the wbadmin start recovery command. Wbadmin.exe is a command-line tool that allows you to
back up and restore your computer, volume, and files from a command prompt. The wbadmin start recovery
command is used to perform a recovery of the specified volumes, applications, files, or folders. The -itemtype
parameter in the wbadmin start recovery command can be used to specify the type of items to recover. The value
for this parameter must be one of the following: Volume, App, or File. The -backupTarget parameter is used to
specify the storage location that contains the backup that you want to recover.
Before you can recover your server operating system, you must have Windows Server Backup installed on the
Window Server 2016 server. Your account must be a member of the local administrators group or the backup
operators group. Finally, you must have an available backup that contains the critical volumes of the server.
You should not run the wbadmin start sysrecovery command. This command is used to perform a full system
recovery and is used only from within the Windows Recovery Environment (RE). In this scenario, you want to
restore only a volume.
Similarly, you should not run the wbadmin start systemstaterecovery command. The wbadmin start
systemstaterecovery command is used to perform a system state recovery of a Windows Server 2012, Windows
Server 2012 R2, or Windows Server 2016 computer. In this scenario, you want to restore only a volume. Therefore,
the wbadmin start systemstaterecovery command does not need to be used.
You cannot use the Add-WbSystemState cmdlet or the Add-BareMetalRecovery cmdlet to run a backup. The
Add-WbSystemState cmdlet adds the system state to the backup policy so that later you can use backups created
with this policy to perform a system state recovery. The Add-BareMetalRecovery cmdlet adds the items needed to
perform a bare metal recovery to the backup policy so that later you can use backups created with that policy. This
cmdlet does not actually restore the system state.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2016 > Management and Automation > Windows Commands > A-Z list > wbadmin
Use Wbadmin in Windows Server 2016 for Backup and Recovery
You have a Hyper-V host named Hypervisor5. You have several virtual machines on Hypervisor5 that run
Windows Server 2008 R2, Windows Server 2012, or Windows Server 2016. You need to create file-based
snapshots of each virtual machine.
You want to create point-in-time snapshots for all of the VMs that will support them, rather than using saved state
technology. If the virtual machine's guest operating system will not support a point-in-time snapshot, you want to
capture state, data, and hardware configuration of the running virtual machine. These snapshots should allow you
to recreate a specific state or condition of a running virtual machine so that you can troubleshoot any possible
problem.
You plan to create a script to achieve this. Which of the following code snippet should you add to the script?
✗ A) Set-VM -Name $VirtualMachineName AutomaticStopAction Production

Get-VM $VirtualMachineName ComputerName Hypervisor5 |
Checkpoint-VM
✗ B) Set-VM -Name $VirtualMachineName CheckPointType ProductionOnly

Checkpoint-VM
✗ C) Set-VM -Name $VirtualMachineName CheckPointType Standard

Checkpoint-VM
✓ D) Set-VM -Name $VirtualMachineName CheckPointType Production

Checkpoint-VM
✗ E) Set-VM -Name $VirtualMachineName AutomaticStopAction Standard

Checkpoint-VM
✗ F) Set-VM -Name $VirtualMachineName AutomaticStopAction

ProductionOnly
Checkpoint-VM
Explanation
You should add the following code snippet to the script:
Set-VM -Name $VirtualMachineName CheckPointType Production

Get-VM $VirtualMachineName ComputerName Hypervisor5 | Checkpoint-VM
The Set-VM -Name $VirtualMachineName CheckPointType Production command uses the Set-VM cmdlet to
configure any virtual machine in the $VirtualMachineName to use a production checkpoint. The -CheckPoint
parameter configures a virtual machine in Hyper-V with the following variables:
Standard. This value creates standard checkpoints that capture the hardware configuration, state, and data of a
VM running on a Hyper-V host. A standard checkpoint is intended for test scenarios rather than production.
Standard snapshots can recreate a specific state or condition of a running virtual machine for troubleshooting.
Production. If supported by the guest operating system, this value will create production checkpoints. If the
guest operating system does not support production checkpoints, standard checkpoints will be created. Only
Windows Server 10 and Windows Server 2016 support production checkpoints. Older operating systems only
support standard checkpoints.
ProductionOnly. If supported by the guest operating system, this value will create production checkpoints. If the
guest operating system does not support production checkpoints, the operation will fail.
Disabled. No checkpoint can be created on the VM.
Production checkpoints are point in time images of the virtual machine that can be restored later. These types of
checkpoints ensure that applications are in a consistent state when the checkpoint is created. The term snapshot
was used interchangeably with the term checkpoint until Windows Server 2012 R2, when Microsoft changed the
snapshot to checkpoint. Other Hypervisor manufactures still use the term snapshot. Windows Server 2016 refers to
checkpoints.
You should not choose either of the following:
Set-VM -Name $VirtualMachineName CheckPointType Standard

Set-VM -Name $VirtualMachineName CheckPointType ProductionOnly

The CheckPointType Standard value will not allow you to create a checkpoint type of production.
The CheckPointType ProductionOnly value will configure production checkpoints for a guest operating system
that will support it, such as Windows 10 and Windows Server 2016. However, the entire operation will fail if this
parameter is set and the guest operating system only supports standard checkpoints. In this scenario, you have
guest operating systems that do NOT support production checkpoints, including Windows Server 2008 R2 and
Windows Server 2012.
Objective:
Implement Hyper-V
Sub-Objective:
References:
Windows 10 > Hyper-V cmdlets > Set-VM
Windows 10 > Hyper-V cmdlets > Checkpoint-VM
TechNet > Windows Server 2016 > Compute > Hyper-V > Manage > Choose between standard or production
checkpoints in Hyper-V
You are the administrator for the Nutex Corporation. You want to set up Storage Spaces Direct with real-time
storage tiering. You have NVM Express (NVMe), Solid State Drive (SSD), and hard disk drive (HDD) storage
devices. You have to identify the data use cases and which file system you can use for which volume type.
You must apply the relevant use cases and file systems to the relevant volume type:
All data is hot.

All data is cold.
Data is a mix of hot and cold.
Either the ReFS or NTFS file systems are in use.
Only the ReFS file system is in use.
Which of the following graphics shows the correct distribution of resiliency, use case, efficiency, and file system?
✗ A)
✗ B)
✓ C)
✗ D)
Explanation
You should choose the following:
Data can be classified as hot, warm, or cold. When data is frequently accessed, it is considered hot. When data is
accessed less frequently, it is considered to be warm data. It can be on stored slower storage than hot data. If the
data is rarely accessed, it is considered to be cold data. It can reside on the slowest storage.
If all data is hot, you should choose the mirror volume type. This type of volume provides a very good performance
when all data on the volume is hot. This is a good solution for SQL Server OLTP.
If all data is cold, you should use the parity volume type. The parity volume type provides the best storage efficiency
when the data is cold. You can use this type of volume for a backup.
If there is a mix of hot and cold data, you should use the multi-resilient volume type. You can use this volume type
for VMs for the best read/write performance if you have a mix of hot and cold data on the same volume. You can
access the hot data and provide the best storage efficiency for the cold data.
You could use the ReFS or NTFS file system with a mirror volume type. A mirror volume type supports both the
ReFS or NTFS file system.
You could use ReFS or NTFS file system with a parity volume type. The parity volume type supports both the ReFS
or NTFS file system
You should use ReFS only for Multi-Resilient volume type. The ReFS filesystem has capabilities like efficient VM
checkpoints that can benefit virtual machines.
Objective:
Sub-Objective:
References:
Spaces Direct
Server Storage at Microsoft
Your network contains an Active Directory domain named CDPressinc.com. The servers run Windows Server 2012
or Windows Server 2016. You configure a custom Data Collector Set on one of the servers, and you need to ensure
that all log data older than one week is deleted. You right-click the data set and select Data Manager from the
context menu.
On which tab of the resulting dialog box can you make these settings?
✗ A) Data Manager
✗ B) Rules
✗ C) Properties
✓ D) Actions
Explanation
You should click the Actions tab to create folder actions that define what do to do with data of various ages. Here
you could specify that all data a week old should be archived and deleted, or simply deleted. In the example below,
the options are set to delete all files older than a week.
You would not use the Data Manager tab. As shown in the screenshot, this tab allows you to define the minimum
amount of free disk space to be maintained, the maximum number of folders, and the maximum amount of space
used for this set. It also lets you configure whether to delete the largest or oldest files to maintain those limits.
However, you cannot specify that all data over 30 days old is deleted.
You would not select the Rules tab. Rules are .xml files that are used to determine what information is included in
any reports that are generated.
You would not select the Properties tab.The dialog box that appears when you select Data Manager does not
have a Properties tab. You can select Properties from the same context menu where you selected Data Manager.
This is where items such as the collection schedule are set, as shown in the following screenshot:
Objective:
Sub-Objective:
Monitor Server Installations
References:
TechNet Library > Windows Server > Manage Data in Windows Performance Monitor
TechNet Library > Windows Server > Creating Data Collector Sets
You are the administrator for the Nutex Corporation. You have created a Nano Server virtual machine on a
Windows Server 2016 Hyper-V host. You want to add this Nano Server virtual machine as a cluster node to an
existing failover cluster. You have to do this remotely.
On the Windows Server 2016 Hyper-V host you start with the configuration of the PowerShell execution policy
setting of that Nano Server virtual machine. You use PowerShell Direct to create a session. You run the following
script:
Which PowerShell cmdlet is required in line 3 to run the command in the session?
✓ A) Invoke-Command
✗ B) New-PSSession
✗ C) Enable-PSRemoting
✗ D) Enter-PSSession
Explanation
The Invoke-Command cmdlet is required to start a PowerShell Direct remote session from a Windows Server 2016
or Windows 10 host to a Windows Server 2016 or Windows 10 guest machine.
You should not use the New-PSSession cmdlet. With this cmdlet you create a new PowerShell session object that
acts as a persistent connection and can be reused through a variable.
You should not use the Enable-PSRemoting cmdlet because it will prepare a target machine so that you can
remotely connect to it through PowerShell. One of the advantages of PowerShell Direct is that you do not have to
prepare a target virtual machine to be remotely managed.
You should not use the Enter-PSSession cmdlet because it does not support the -ScriptBlock parameter. This
cmdlet starts an interactive session with a remote computer. You can also use this cmdlet for a PowerShell Direct
remote session. The difference between Invoke-Command and Enter-PSSession is that you can use Invoke-
Command for 1:n remote sessions, but Enter-PSSession is only used for 1:1 sessions.
Objective:
Implement Hyper-V
Sub-Objective:
Install and configure Hyper-V
References:
TechNet > Windows Server 2016 > Compute > Hyper-V > Manage > Manage Windows virtual machines with
PowerShell Direct
Windows Server 2016. You plan to implement a multi-node failover cluster, and you need to make a
recommendation for applying Microsoft updates to the cluster nodes.
What should you recommend?
✓ A) Use Cluster-Aware Updating (CAU) to apply updates with the default

Microsoft.WindowsUpdatePlugin plug-in on a cluster. Stop using other
methods to install software updates on nodes in the cluster.
✗ B) Enable settings on the cluster nodes for automatic updating by configuring
settings in Group Policy.
✗ C) Enable settings on the cluster nodes for automatic updating through the
Automatic Updates settings in Control Panel.
✗ D) Configure an update system such as Windows Server Update Services
(WSUS) to apply updates to cluster nodes automatically on a fixed schedule.
✗ E) Exclude cluster nodes from all required or automatic updates and use a
configuration management system to apply software updates to computers on
the network.
Explanation
Microsoft recommends that you use Cluster-Aware Updating (CAU) to apply updates with the default
Microsoft.WindowsUpdatePlugin plug-in on a cluster. After implementing CAU, you should stop using other
methods to install software updates on nodes in the cluster. CAU transparently takes each cluster node offline,
installs the updates, restarts the node, brings the node back online, and then moves to update the next node in a
cluster.
You should NOT combine CAU with other methods that update individual nodes automatically on a fixed time
schedule. This action can cause interruptions in service, unplanned downtime and other unpredictable results.
Microsoft recommends that you disable settings on the cluster nodes for automatic updating either through the
Automatic Updates settings in Control Panel, or in settings that are configured using Group Policy. Installation of
updates by CAU can have conflicts with the automatic installation of updates and can cause CAU failures. The
automatic update process triggers a planned failover, and it will cause a transient service interruption for clients.
If you must use the Automatic Updates settings, you should choose settings that allow you to control the timing of
update installations. You should configure the following settings:
Settings to notify before downloading updates and to notify before installation

Settings to automatically download updates and to notify before installation
You should EXCLUDE cluster nodes, not include, from all required or automatic updates if use a configuration
management system to apply software updates to computers on the network.
You should not have automatic updates configured to automatically install updates on any failover cluster node.
You should not configure an update system such as Windows Server Update Services (WSUS) to apply updates
automatically on a fixed time schedule to cluster nodes.
You should configure all cluster nodes to uniformly use the same update source, for example, a WSUS server,
Windows Update, or Microsoft Update.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2012 and Windows Server 2012 R2 > Server Roles and Technologies > Failover
Clustering > Cluster-Aware Updating
Requirements and Best Practices for Cluster-Aware Updating
Your company has a single Active Directory domain named nutex.com. You want to load balance VPN
connections. You create an NLB cluster that will load balance VPN traffic from clients. There are three hosts in the
NLB cluster.
After implementation of the cluster, VPN clients are able to make connections to access services, files and printers
on the network. However, if you add a host to the NLB cluster, make a change to a host, or drain a host, then clients
complain that their VPN connections fail.
What should you do to prevent these issues from occurring? Choose two (each answer is a complete solution).
✓ A) Configure the port rules that govern ports 500 and 1723 to use Network affinity
✓ B) Configure the port rules that govern ports 500 and 1723 to use Single affinity
✗ C) Configure the port rules that govern ports 500 and 1723 to use None affinity
✗ D) Configure the port rules that govern ports 500 and 1723 to use Filter Mode as
Single Host
✗ E) Change the cluster operation mode to Multicast
✗ F) Change the cluster operation mode to Unicast
✗ G) Configure the port rules that govern ports 500 and 1723 to use Filter Mode as
Disable
Explanation
You should configure the port rules that govern ports 500 and 1723 to use Single or Network affinity. Setting the
affinity to Single ensures a client will always be directed to the same host within a given session, regardless of its
traffic load. The Network option will also ensure a client will always be directed to the same host within a given
session, regardless of its traffic load, but the Network affinity setting is used for clients that may use multiple proxy
servers to access the cluster. If a client uses an ISP to access the Internet, it may have many proxy servers. The
Network option will direct requests from the same TCP/IP Class C address range.
In this scenario, when you make a change that causes convergence on your cluster such as issuing a nlb.exe
DRAINSTOP command, then VPN connections are disrupted. When you issue a nlb.exe DRAINSTOP command, it
allows the NLB cluster to serve current connections and disable the new connections at the same time.
You should configure the affinity on the port rule such that clients can be directed to the same host. To specify the
Affinity setting of a port rule, you should open Network Load Balancing Manager, highlight the cluster that you want
to configure, and choose Cluster Properties.
On the Port Rules tab, choose the appropriate port rule and click Edit.
Within the port rule, you can change the filtering mode to Multiple host and to Single or Network.
You should not set the Filter mode to either Single host or Disable. If you select Disable, then this setting prevents
the cluster from responding to a specific type of client traffic. In this case, traffic is VPN traffic from either L2TP or
PPTP. If you select Single host, this setting allows only one cluster host in the cluster to actively respond to client
requests. Having only one cluster host respond to requests, does not offer load balancing. When you set the filter
mode to Single host, if the first host to respond to client requests fails, then the host with the next highest priority
takes over for the failed host.
You should not change the cluster operation mode to Unicast or Multicast. All network adapters within a NLB cluster
must be configured as either all unicast or all multicast. You cannot configure an NLB cluster with a mixture of
unicast and multicast adapters. If you choose unicast, the network adapter must support changing its MAC address.
Changing the operation mode will not affect VPN traffic.
Objective:
Sub-Objective:
References:
TechNet > Windows Server > Installed Help > Availability and Scalability > Network Load Balancing >
Troubleshooting Network Load Balancing Clusters
Server & Tools Blogs > Server & Management Blogs > Clustering and High-Availability> Network Load Balancing in
R2: Extended Affinity
TechNet Library > Windows Server > Server Roles and Technologies > Networking > Network Load Balancing
Overview
You manage a set of servers for a department in the verigon.com domain You have a Windows Server 2016 server
named HyperV installed with the Hyper-V role. Several departments have virtual machines (VMs) on HyperV. You
want to make sure that VMs belonging to the Tax department do not consume excessive storage resources on
HyperV that may impact the VMs that belong to the Sales department.
What should you configure on HyperV?
Move the correct steps from the left column to the column on the right, and place them in the correct order. Not all
steps given may be required.
Explanation
You should choose the following:
1. In Server Manager, open Hyper-V Manager and click Settings in the Action Pane
2. Click SCSI Controller, in the Advanced Features pane, click Enable Quality of Service management to
configure the IOPS values
You can use Storage Quality of Service (QoS) for Hyper-V to provide storage performance isolation in a multitenant
environment. In this scenario, you want to ensure that VMs belonging to the Tax department do not consume
excessive storage resources on HyperV that may impact the VMs belonging to the Sales department. Storage QoS
allows you to specify minimum and maximum input/output operations per second (IOPS) values for your virtual hard
disk. You could throttle the storage I/O to stop the Tax department from consuming excessive storage resources.
You can configure the maximum IOPS allowed for a virtual hard disk that is associated with a virtual machine. You
can use the storage related parameters that are kept in the virtual machine metrics infrastructure to monitor the
performance and chargeback related parameters.
You do not have to disable Secure Boot in Hyper-V. Secure Boot is enabled by default. Secure Boot helps prevent
unauthorized code from running at boot time.
You do not have to install the Multipath I/O feature, the iSNS Server Service feature, or the Enhanced Storage
feature. None of these features are required to use Storage Quality of Service (QoS) for Hyper-V.
Enhanced Storage enables support for accessing additional functions of Enhanced Storage devices. The iSNS
Server Service feature provides discovery services for iSCSI storage area networks. The Multipath I/O feature,
along with the Device Specific Module (DSM), provides support for using multiple data paths to a storage device on
a Windows Server.
Objective:
Implement Hyper-V
Sub-Objective:
References:
TechNet > Windows Server 2016 > Storage > Storage Quality of Service
You are the administrator of the Nutex Corporation. You have installed three Windows containers named Nano1,
Nano2, and Nano3 on a virtualized Windows Server 2016 Hyper-V host named NutexHost. The current container
networking mode is L2 Bridge Mode. You enumerate the following IP addresses:
You have to achieve the following requirements:
All IP addresses have to be assigned dynamically using an external DHCP server

Every container has to be in the same physical subnet as NutexHost
Direct network connectivity must exist between the containers and physical network
Which of the following should you choose to implement the planned changes? (Choose all that apply.)
✓ A) Use Transparent Networking

✗ B) Use Network Address Translation mode
✗ C) Use L2 Tunnel mode
✗ D) Run docker network create driver overlay ContNutexNet to create
the container network
✓ E) Run Get-VMNetworkAdapter -VMName NutexHost | Set-
VMNetworkAdapter -MacAddressSpoofing On to prepare the container host
✗ F) Run docker network create driver bridge ContNutexNet to create the

container network
✓ G) Run docker network create -d transparent ContNutexNet to create
the container network
Explanation
You should choose transparent networking. In this scenario, you want direct network connectivity between the
containers and the physical network as well as the physical Windows Server 2016 Hyper-V host. IP addresses can
be assigned through a physical DHCP server with an IP scope of 192.168.1.0/24.
You should run docker network create -d transparent ContNutexNet. With this docker command, you
create a transparent container network with the name ContNutexNet. You also can create a container network with
the PowerShell command: New-ContainerNetwork -Name ContNutexNet -Mode transparent.
You should run Get-VMNetworkAdapter -VMName NutexHost | Set-VMNetworkAdapter
-MacAddressSpoofing On because the Windows Server 2016 Hyper-V host is a virtual machine, and MAC
address spoofing has to be enabled on the virtual machines network adapter.
You should not choose Network Address Translation mode. With Network Address Translation mode, external
access to the container is not direct. Instead it is flowing through a port mapping between the external IP address
port and the internal IP address port of the container. A WinNAT port mapping table is used for translation and
forwarding. Network Address Translation mode can be used if you quickly want assign a private IP address to a
container. Here the containers have to be assigned through a physical DHCP server and there has to be direct
network connectivity between the containers and the physical network.
You should not choose L2 Tunnel mode because this should only be used in a Microsoft Cloud stack (Microsoft
Azure). With L2 Tunnel Mode, network policies can be enforced through the network controller.
You should not run the Get-VMNetworkAdapter -VMName NutexHost | Set-VMNetworkAdapter-AllowTeaming

On command because in this scenario NIC teaming is not a requirement. The host and all containers have only one
NIC. For NIC teaming you need a minimum of two NICs.
Objective:
Sub-Objective:
Manage Windows Containers
References:
Microsoft Docs > Windows Containers > Manage Docker on Windows > Container Networking
TechNet > Resources for IT professionals > Gallery > Servers > Windows Server Container Manager
Docker Docs > Docker Engine > User Guide > Docker container networking > Understand Docker container
networks
TechNet > Windows 10 and Windows Server 2016 > Hyper-V cmdlets > Set-VMNetworkAdapter
Windows Server 2012 or Windows Server 2016. You have two Windows Server 2016 failover cluster servers named
server1.nutex.com and server2.nutex.com in a Hyper-V failover cluster. The virtual machines all run Windows
Server 2012.
You need to detect if any of the virtualized workloads in the cluster are behaving abnormally. You want the cluster
service to take recovery actions when the workloads are in an unhealthy state. You need to configure VM
Monitoring using the Failover Cluster Manager utility.
What must you configure? (Choose all that apply.)
✓ A) Make the cluster administrator a member of the local Administrators group

on the VMs
✗ B) Make the cluster administrator a member of the local Administrators group
on server1.nutex.com and server2.nutex.com.
✓ C) Enable the Virtual Machine Monitoring firewall rule on the VMs
✗ D) Enable the iSCSI Service firewall rule on server1.nutex.com and

server2.nutex.com
✗ E) Enable the SNMP Trap firewall rule on the VMs
✗ F) Enable the iSCSI Service firewall rule on the VMs
✗ G) Enable the Virtual Machine Monitoring firewall rule on server1.nutex.com and
server2.nutex.com
✗ H) Enable the SNMP Trap firewall rule on server1.nutex.com and
server2.nutex.com
Explanation
You should make the cluster administrator a member of the local Administrators group on the guests (virtual
machines). Since you will be monitoring the workload on the guests, you will need to allow the cluster administrator
the ability to monitor the VMs. You do not have to make the cluster administrator a member of the physical servers
in the cluster because you are monitoring the virtualized workloads.
On each virtual machine that you want to monitor, you will need to enable the Virtual Machine Monitoring firewall
rule, as shown in the following screenshot:
Once you have configured the prerequisite steps, VM Monitoring can be easily configured using the Failover Cluster
Manager.
Virtual Machine Monitoring must be set on the guests, not on the physical servers in the cluster.
All other answers are incorrect because they are not required to monitor the virtualized workload.
The iSCSI Service Firewall rule allows you to monitor the iSCSI service.
The SNMP Trap Firewall rule allows you to monitor SNMP alerts that are sent to a SNMP MIB.
Objective:
Sub-Objective:
Manage Failover Clustering
References:
TechNet > Windows Server 2016 > Networking > What's New in Failover Clustering in Windows Server 2016
Technologies > Failover Clustering > What's New in Failover Clustering in Windows Server 2012 R2TechNet Library
> Windows Server > Server Roles and Technologies > Failover Clustering > What's New in Failover Clustering in
Windows Server
MSDN Blogs > Clustering and High-Availability > How to configure VM Monitoring in Windows Server 2012
You are the administrator of the Nutex Corporation. You have downloaded the Assessment and Deployment Toolkit
(ADK). You want to edit a Windows Server 2016 reference image. You need to define a MDT deployment share rule
and the LTI Suspend feature.
Which ADK components you have to edit for that?
✗ A) .wim file
✓ B) .wsf-file
✗ C) CustomSettings.ini
✓ D) Bootstrap.ini
Explanation
You should use a .wsf file because you need the LTISuspend.wsf script as a custom action in the task scheduler
sequence. This script suspends the task sequence. You can resume the task sequence by clicking the Resume
Task Sequence shortcut icon on the desktop.
You should use Bootstrap.ini because in this file the MDT deployment rules are defined. The deployment server
and share can be defined through the DEPLOYROOT value in this file.
You should not use a .wim file because you cannot go directly into the .wim image file. You can edit the image
through customizing it with the task sequences and additional files in ADK.
You should not use CustomSettings.ini because you can edit the Bootstrap.ini directly. The purpose of the
Bootstrap.ini file is to provide enough information to find the CustomSettings.ini file. This file is stored on the
server in the deployment share in the control folder.
Objective:
Sub-Objective:
Create, Manage and Maintain images for deployment
References:
How to install ADK and MDT in Windows Server 2016
Create a Windows 10 reference image
Your company has an Active Directory domain named nutex.com. All domain controllers run Windows Server
2016. All member servers in the domain run Windows Server 2008 SP2, Windows Server 2012, or Windows Server
2016. All client computers run Windows 7 or Windows 10.
Your company is transitioning away from traditional backups using Windows Server Backup to cloud-based
backups. You need to decide on a backup method for servers in the Engineering OU. You need to ensure the
following can be restored:
System state backups of domain controllers

Sensitive documents on the TechDocuments folder of the FS55.nutex.com server, which runs Windows
Server 2008 SP2
Bare metal restores of file servers
Which of the following should you perform? (Choose all that apply.)
✗ A) Use Azure Backup for backups of sensitive documents on the network share
\\FS19.nutex.com\TechDocuments
✓ B) Use Azure Backup for backups of sensitive documents on the local
d:\TechDocuments folder of the FS55.nutex.com server
✗ C) Use Azure Backup on servers that have ReFS volumes and NTFS volumes
✓ D) Use Azure Backup for system state restores of domain controllers
✓ E) Use Azure Backup for bare metal restores of file servers
✗ F) Use setup.exe to install the Azure Backup Agent
Explanation
You can perform the following:
Use Azure Backup for system state restores of domain controllers

Use Azure Backup for backups of sensitive documents on the local d:\TechDocuments folder of the
FS55.nutex.com server
Use Azure Backup for bare metal restores (BMR) of file servers
You can use Azure Backup in most file archive scenarios. You can use Azure Backup in the following scenarios:
System state restores of domain controllers running Windows 2008 SP2 or higher
Bare metal restores of servers running Windows 2008 SP2 or higher
You could not use Windows Azure Online Backup in previous incarnations of Azure to perform BMR or system state
backups.
You can use Azure Backup for backups of sensitive documents on the local folder d:\TechDocuments folder of the
FS55.nutex.com server or any folders on a server. You cannot use Azure Backup to perform backups on network
shares. The folders must be local. Therefore, you cannot use Azure Backup for backups of sensitive documents on
the network share \\FS19.nutex.com\TechDocuments.
Microsoft Azure Recovery Services (MARS) Agent allows you to schedule backups from your Windows Server
2016, Windows Server 2012, or Windows Server 2012 R2 server to a cloud-based storage service that is managed
by Microsoft.
To install the Azure Backup Agent you would run the MarsAgentInstaller.exe installer, not setup.exe.
You can only use Azure Backup to backup NTFS volumes, not ReFS volumes.
Objective:
Sub-Objective:
References:
Azure Backup service- FAQ
Azure > Backup > Get Started > First look: back up files and folders in Resource Manager deployment
Microsoft Azure > Backup > Work with Azure Backup > Registers Servers with Windows Azure Backup
TechNet Blogs > Blain Barton's Blog > Article: Building Certificates for Windows Server 2012 R2/Windows Azure
Recovery Services for the Backup Vault (Private Cloud Certificates)
Azure > Backup > How To > Back up and restore Windows machines > Windows Server using the classic
deployment model
Use Wbadmin in Windows Server 2016 for Backup and Recovery
You manage a set of servers for a department that is in the verigon.com domain.
The department has servers that run Windows Server 2012 and Windows Server 2016.
Users in your department run several virtual machines (VMs). These VMs were originally created on a Windows
Server 2012 server running Hyper-V. Later the VMs will be migrated to the Hyper-V role of a Windows Server 2016
server. New technical requirements from the IT department require the existing virtual machines to do the following:
Have a boot disk that can support a MBR partition table

Support virtual hard drives in the VHDX format
Have the ability to boot from a device attached to a SCSI controller
Have the ability to boot using IPv4
What change should you make to the VMs to ensure the requirements are met?
✗ A) Add a legacy network adapter to ensure that you can boot using IPv4
✗ B) Ensure that the device attached to a SCSI controller is a virtual hard drive in
the VHD format
✗ C) Use the Convert-VmState cmdlet to convert the virtual machines to

generation 2 virtual machines
✗ D) Use the Set-VmState cmdlet to convert the virtual machines to generation 2
virtual machines
✓ E) Migrate the virtual machines to generation 2 virtual machines
✗ F) Ensure that the device attached to a SCSI controller is a virtual hard drive in
the VHDX format
✗ G) Ensure that the boot disk is a virtual hard drive in the VHDX format
✗ H) Ensure that the boot disk is a virtual hard drive in the VHD format
Explanation
You should migrate the virtual machines to generation 2 virtual machines. Generation 2 virtual machines support
the ability to boot from a device attached to a SCSI controller. Generation 1 virtual machines do not. Because these
virtual machines are running on a Hyper-V role of a Windows Server 2012 server, they must be generation 1 virtual
machines because the Hyper-V role of Windows Server 2012 does not have an option for generation 2 virtual
machines.
You can migrate the generation 1 virtual machines to another server as generation 2 virtual machines. You can
perform a manual migration or you can use the PowerShell script named Convert-VMGeneration.ps1 to perform a
migration of a generation 1 virtual machine to a generation 2 virtual machine.
You do not have to ensure that boot disk is a virtual hard drives in either the VHD format or VHDX format. All
generation 1 virtual machines support VHD and VHDX formats. Generation 2 virtual machines support only the
VHDX format.
You would not have to add a legacy network adapter to ensure that you can boot using IPv4. Any network adapter
can be used to boot using IPv4. All generation 1 virtual machines support this feature. A legacy network adapter is
not available in a generation 2 virtual machine.
Only a generation 2 virtual machine has the ability to boot from a device attached to a SCSI controller. Ensuring that
the device attached to a SCSI controller is a virtual hard drives in the VHDX or VHD format will not matter because
the existing VMs are generation 1 virtual machines.
You should not use the Convert-VmState cmdlet or the Set-VmState cmdlet to convert the virtual machines to
generation 2 virtual machines. These cmdlets will discover and manipulate the virtual machine states, but will not
convert the virtual machines to generation 2 virtual machines.
Objective:
Implement Hyper-V
Sub-Objective:
References:
TechNet > Windows Server 2016 > Compute > Hyper-V > Should I create a generation 1 or 2 virtual machine in
Hyper-V?
TechNet > Windows Server 2016 > Compute > Hyper-V > Hyper-V feature compatibility by generation and guest
TechNet > Windows Server 2016 > Compute > Hyper-V > Create a virtual machine in Hyper-V
You are responsible for establishing new clusters in multiple branch offices for the Nutex Corporation. You have to
determine which type of technology is valid for your clustered file server deployments.
Which of the following statements are correct? (Choose all that apply.)
✗ A) An Active/Active Cluster uses a file server for general use

✓ B) CSV-independent uses a file server for general use
✗ C) Parallel SMB-client request handling uses a file server for general use
✓ D) Storage Spaces Direct uses a Scale-Out File Server (SoFS) for application
data
✓ E) Simultaneous active shares use a Scale-Out File Server (SoFS) for application
data
✓ F) An Active/Active Cluster uses a Scale-Out File Server (SoFS) for application
data
✗ G) CSV-independent uses a Scale-Out File Server (SoFS) for application data
✗ H) An Active/Passive Cluster uses a Scale-Out File Server (SoFS) for application

data
✗ I) Simultaneous active shares use a file server for general use
✓ J) Parallel SMB-client request handling uses a Scale-Out File Server (SoFS) for
application data
✓ K) QoS technology uses a Scale-Out File Server (SoFS) for application data
✗ L) QoS technology uses a file server for general use
✓ M) An Active/Passive Cluster uses a file server for general use
✗ N) Storage Spaces Direct uses a file server for general use
Explanation
The following clustered file technologies are appropriate for each deployment scenario:
Deploying a Scale-Out File Server for general use provides these failover clustering technologies:
Active/Active cluster
Parallel SMB client request handling
Simultaneous active shares
Storage Spaces Direct
QoS technology
Scale-Out File Servers add highly available Active/Active file data access for application data workloads to
Windows Server clusters through SMB. In a scale-out FS failover cluster, you can add up to eight nodes. Because
of the Active/Active possibility, the scale-out FS failover cluster can handle parallel SMB client requests. A scale-out
FS failover cluster can easily be scaled through adding a new node to the cluster, and you have the advantage of
automated failover in the case of a failed cluster node.
A Scale-Out FS failover cluster is an Active/Active cluster where all nodes are active. The SMB-client requests can
be handled from all cluster nodes in parallel.
In a Scale-out FS failover cluster, all nodes make a share active and simultaneously accessible. It does not matter
which nodes share you connect to. You automatically connect to another node through SMB Transparent Failover.
Windows Server 2016 has a new feature called Storage Spaces Direct. With this feature, the nodes of a failover
cluster can use local storage of the node as cluster storage. A Scale-out FS failover cluster also can use that
feature.
Windows Server 2016 has a new feature called Storage QoS. You have to set up Storage QoS policies to manage
storage performance for virtual machines using Hyper-V and SOFS. For example, you can define minimum and
maximum IOS for your storage.
Deploying a file server for general use provides these failover clustering technologies:
Active/Passive Cluster
CSV-independent
A file server for general use in a failover cluster can only be on node hosts running the File Server role
(active/passive cluster). All other nodes are passive. In the case of a failed active node, another passive node
becomes the active node and will have the File Server role applied.
For a file server for general use in a failover cluster, you cannot use a Cluster Shared Volume. It is a CSV-
independent solution. You should not use SoFS, instead a file server for general use in a failover cluster especially
if your workload generates a high number of metadata operations like opening, closing, creating or renaming files.
Objective:
Sub-Objective:
References:
TechNet > Windows Server > Server Roles and Technologies > Failover Clustering > What's New in Failover
TechNet > Windows Server 2016 > Storage > What's new in storage in Windows Server 2016
TechNet > Windows Server > Windows Server 2016 Storage QoS
Server & Tools Blogs > Server & Management Blogs > Server Storage at Microsoft > To scale out or not to scale
out, that is the question
TechNet Library > Windows Server 2012 R2 and Windows Server 2012 > Technical Scenarios > Increase Server,
Storage, and Network Availability > Scale-Out File Server for Application Data > Deploy Scale-Out File Server
Windows Server 2016 SoFS QoS
Hyper-V Storage QoS in Windows Server 2016 works on SoFS
You manage a set of servers for a department in the verigon.com domain. The department contains servers that
run Windows Server 2016.
From SRV1.verigon.com, you add a server named SRV55 that is in a workgroup to Server Manager. However, the
Manageability column of the Servers tile for SRV55 in Server Manager displays a Credentials not valid error
while trying to collect data from SRV55.
What should you do to fix the error?
✗ A) On SRV55, run the following command:

djoin /provision /domain verigon.com /machine SRV1
✗ B) On SRV55, use the following command:

Set-Item wsman:\localhost\Client\TrustedHosts SRV1.verigon.com
-Concatenate -Force
✗ C) On SRV1.verigon.com, run the following command:

djoin /provision /domain verigon.com /machine SRV55
✗ D) On SRV1.verigon.com, run the following command:

Enter-PSSession -Computer SRV55
✗ E) On SRV55, run the following command:

Enter-PSSession -Computer SRV1.verigon.com
✓ F) On SRV1.verigon.com, run the following command:

Set-Item wsman:\localhost\Client\TrustedHosts SRV55 -
Concatenate -Force
Explanation
You should run the following command on SRV1.verigon.com:
Set-Item wsman:\localhost\Client\TrustedHosts SRV55 -Concatenate -Force
When you add a non-domain server that is in a workgroup to a Server Manager server pool, you may receive a
Credentials not valid error. You can avoid this error by adding the workgroup server name to the TrustedHosts
list, which is a requirement of NTLM authentication. Since the server is in a workgroup and not a domain, the
authentication will be NTLM instead of Kerberos.
You should not run the following command on SRV55:
Set-Item wsman:\localhost\Client\TrustedHosts SRV1.verigon.com -Concatenate -Force
In this scenario, you need to add the workgroup server, SRV55, to the TrustedHosts list, and not
SRV1.verigon.com, which is a member of the domain
You should not use the djoin.exe command to add a non-domain computer to Server Manager. You can use
djoin.exe to perform an offline domain join for computers that may not be able to contact a domain controller. You
can run djoin.exe at an elevated command prompt to provision the computer account metadata. You should run the
djoin.exe /provision command to create computer account metadata for the computer and save the metadata to a
file. You should then run the djoin.exe /requestODJ command to insert the computer account metadata from the
file into the Windows directory of the destination computer.
You should not use the Enter-PSSession cmdlet in this scenario. The cmdlet starts an interactive session with
another computer. The Enter-PSSession cmdlet will not work in this scenario because a WinRM setting called
TrustedHosts is not configured.
Objective:
Sub-Objective:
References:
TechNet > Windows Server 2016 > Management and Automation > Server Manager > Configure remote
Management in Server Manager
TechNet > Windows Server 2016 > Management and Automation > Server Manager > Add Servers to Server
Manager
TechNet > Windows Server 2012 R2 > Management and Tools > Add Servers to Server Manager
Windows PowerShell WinRm and WSMan

70-740 Exam Simulation-CBT NUGGETS 1

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

70-740 Exam Simulation-CBT NUGGETS 1

Uploaded by

Copyright:

Available Formats

06/03/2019 70-740 Exam Simulation

Quick Quiz March 6, 2019 Test ID: 94470532

Question #1 of 50 Question ID: 1138246

✗ A) Use an ISO image of Windows 7 to install on the virtual machine

✓ B) Use an ISO image of Windows 8.1 to install on the virtual machine

✗ D) Disable Secure Boot on the virtual machine

You can do either of the following to fix the keyboard issue:

Question #2 of 50 Question ID: 1148517

Question #3 of 50 Question ID: 1148587

Find-ContainerImage: The term 'Find-ContainerImage' is not recognized as the name of a

Install-ContainerImage -Name WindowsServerCore

github / Microsoft / Docker-PowerShell / releases

github / Microsoft / PowerShell/ContainerProvider

github / Microsoft / Docker-PowerShell / src / Docker.PowerShell / Help / Import-ContainerImage.md

Question #4 of 50 Question ID: 1161633

{UCMS id=5630470576406528 type=Activity}

You should not run Install-NanoServerPackage Microsoft-NanoServer-Compute-Package from the

You should not run & $env:ProgramFiles'\docker\dockerd.exe' --register-service . This command

Container host deployment Nano Server

Install And Configure Windows Nano Server As A Container Host

Microsoft Docs > Windows Containers on Windows Server

Question #5 of 50 Question ID: 1161656

All hosts must be on the same subnet.

Question #6 of 50 Question ID: 1161639

VSRV1 must stay powered on during the move

✗ A) To Host6 by using live migration

Windows Failover Clustering is enabled and configured on the Hyper-V host.

Virtual Machine Live Migration Overview

Processor Compatibility Mode in Hyper-V

Question #7 of 50 Question ID: 1148597

What command should use to mount the volume?

✗ A) docker run -it -v c:\volume1 c:\volume2 NutexCont2

✗ B) docker run -it -volumes-from NutexCont2 NutexCont1 cmd

✗ C) docker run -it -v C:\datavolume NutexCont2 cmd

✓ D) docker run -it -volumes-from NutexCont1 NutexCont2 cmd

Question #8 of 50 Question ID: 1161664

Which configuration should you choose? (Choose all that apply.)

The Uninstall-WindowsFeature -Name Windows-Server-Antimalware command can remove Windows

TechNet > PowerShell > Defender cmdlets > Set-MpPreference:

Question #9 of 50 Question ID: 1138277

Question #10 of 50 Question ID: 1161596

Which usage type of data deduplication should you use?

✗ A) Virtual Desktop Infrastructure (VDI)

Virtualized Desktop Infrastructure (VDI) servers.

There is no usage type called Hyper-V.

TechNet > Understanding Data Deduplication

TechNet > What's New in Data Deduplication

TechNet >Deduplicate DPM storage

Data Deduplication in Windows Server 2016:

Question #11 of 50 Question ID: 1138263

What should you do?

✗ A) Use the Diskpart command to reinitialize the disk

All other answers are incorrect.

Question #12 of 50 Question ID: 1161578

Which of the following are true? (Choose all that apply.)

✗ A) You cannot use defrag.exe on ReFS formatted volumes on the Windows

Question #13 of 50 Question ID: 1161657

✗ A) Configure the Load Weight settings to 50

Setting Network Load Balancing Parameters

Question #14 of 50 Question ID: 1161589

Fast performance for storage retrieval

What should you create?

Thin - volume uses space from the storage pool as needed

Get-VMNetworkAdapter -VMName SRV55 | * M I S S I N G *