Your network contains an Active Directory domain named contoso.com. All servers run Windows Server
2008 R2. All domain controllers are installed on physical servers. The network contains several Hyper-V
hosts.
The network contains a Microsoft System Center 2012 infrastructure.
You plan to use domain controller cloning to deploy several domain controllers that will run Windows
Server 2012.
You need to recommend which changes must be made to the network infrastructure before you can use
domain controller cloning.
What should you recommend?

A.
Upgrade a global catalog server to Windows Server 2012. Deploy Virtual Machine Manager (VMM).

B.
Upgrade a global catalog server to Windows Server 2012. Install the Windows Deployment Services
server role on a server that runs Windows Server 2012.

C.
Upgrade the domain controller that has the PDC emulator operations master role to Windows Server
2012. Deploy a Hyper-V host that runs Windows Server 2012.

D.
Upgrade the domain controller that has the infrastructure master operations master role to Windows
Server 2012. Install the Windows Deployment Services server role on a server that runs Windows Server
2012.

Explanation:
We need to deploy Hyper-V host on Windows Server 2012, and there must also be a PDC emulator
running Windows Server 2012.
Note: The requirements for domain controller cloning are:* The hypervisor must support VM-GenerationID. Hyper-V running on Windows Server 2012 supports
this feature. Other virtualization vendors will have the ability to implement this as well, so check with
your vendor to see if it’s supported.
* The source virtual DC must be running Windows Server 2012.
* The PDC emulator role holder must be online and available to the cloned DC and must be running
Windows Server 2012.
Virtual Domain Controller Cloning in Windows Server 2012
https://blogs.technet.microsoft.com/askpfeplat/2012/10/01/virtual-domain-controller-cloning-inwindows-server-2012/