A company has a highly-secure network infrastructure environment. All servers in the environment run
Windows Server 2012 R2.
You must create a new virtual machine (VM) that meets the following requirements:
The VM must minimize the risk that unauthorized firmware will run when the VM starts.
The VM must load the operating system only if all operating system files have a valid signature.
You need to create the new VM. What should you do?
A.
Create a Generation 2 VM and disable Secure Boot.
B.
Create a Generation 1 VM and use a synthetic network adapter.
C.
Create a Generation 1 VM and enable Secure Boot.
D.
Create a Generation 2 VM with the default settings.
Generation 2 – This Virtual machine generation provides the following new functionality to a virtual machine:
Secure Boot (enabled by default)
Boot from a SCSI virtual hard drive
Boot from a SCSI virtual DVD drive
PXE boot using a standard network adapter
UEFI firmware support
IDE drives and legacy network adapter support has been removed
Secure Boot is essentially a signature checking mechanism during the OS loader to validate that only approved components are allowed to be run. Secure Boot is defined as part of the UEFI specification. Hyper-V implements a subset which allows Windows 8 and Windows 8.1 with default policies to load in a virtual machine with Secure Boot enabled.