Question
You need to meet the technical requirements for VM1.
Which cmdlet should you run first? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Explanation
Cmdlet selection (left dropdown): Set-VMProcessor — the requirement for VM1 is nested virtualization (running Hyper-V, and therefore a hypervisor-based workload, inside the guest), and that setting lives on the virtual machine's virtual processor, which is configured with Set-VMProcessor. Set-VM changes general VM properties such as memory or automatic start/stop actions, Set-VMFirmware and Set-VMBios control boot order and secure boot for generation 2 and generation 1 VMs respectively, and Set-VMHost configures the Hyper-V host itself rather than VM1's CPU, so none of them can expose the hardware virtualization features to the guest.
Parameter selection (right dropdown): -ExposeVirtualizationExtensions — passing this parameter with a value of $true on a powered-off VM projects the host CPU's hardware virtualization extensions (Intel VT-x / AMD-V) into VM1's virtual processor, which is exactly what the guest operating system needs before the Hyper-V role or any hypervisor-backed feature can be installed inside it. -GuestControlledCacheTypes and -EnableHostResourceProtection are also Set-VMProcessor parameters, but they deal with guest cache-type control and with throttling excessive VM activity that would harm the host, and -NewVMName simply renames a virtual machine, so none of them enable nested virtualization.
