HOTSPOT
Your network contains an Active Directory domain named contoso.com.
Technicians use Windows Deployment Services {WDS) to deploy Windows Server 2012 R2.
The network contains a server named Server1 that runs Windows Server 2012 R2. Server1
has the Hyper-V server role installed.
You need to ensure that you can use WDS to deploy Windows Server 2012 R2 to a virtual
machine named VM1.
Which settings should you configure?
To answer, select the appropriate settings in the answer area.
Answer: 
Explanation:
WDS Allows network-based installation of Windows operating systems, which reduces the
complexity and cost when compared to manual installations. Thus you should configure the
appropriate network settings.
References:
http://technet.microsoft.com/en-us/library/hh831764.aspx
This answer is not totally clear, since you need a legacy network adapter to boot from PXE, but you also need to change BIOS settings in order to boot from the legacy network adapter, and on the exhibit, BIOS clearly states “Boot from CD”, so in this case we would have to change the startup order to “network legacy adapter”.
Since you already have legacy network adapter on VM1, what i would change would be “BIOS” and not the leagcy network adapter.
Please, correct me if i’m wrong.
https://technet.microsoft.com/en-us/library/jj648426.aspx#WDS_InstallingWindowsDeploymentServicesintegratedwithActiveDirectory
https://technet.microsoft.com/en-us/library/cc770380.aspx
0
0
This answer is not totally clear, since you need a legacy network adapter to boot from PXE, but you also need to change BIOS settings in order to boot from the legacy network adapter, and on the exhibit, BIOS clearly states “Boot from CD”, so in this case we would have to change the startup order to “network legacy adapter”.
Since you already have legacy network adapter on VM1, what i would change would be “BIOS” and not the leagcy network adapter.
Please, correct me if i’m wrong.
https://technet.microsoft.com/en-us/library/jj648426.aspx#WDS_InstallingWindowsDeploymentServicesintegratedwithActiveDirectory
https://technet.microsoft.com/en-us/library/cc770380.aspx
0
0
I think you are right also, once the legacy network adapter is added, nothing more needs to be configured or can be configured for PXE booting, the adapter has clearly already been added in the picture, the only thing that would need to be changed is the boot order under BIOS, as the default boot order is CD->IDE->Legacy Network Adapter->Floppy for a gen 1 VM.
http://www.danielclasson.com/guide-how-to-get-pxe-boot-to-work-in-hyper-v/
0
0
Actually looking at the picture the Legacy Network Adapter is “Not connected” to a virtual switch, so that would need to be set up correctly too, so both actually need to be configured. They shouldn’t have questions like this.
0
0
But the trick is that if it cannot boot from CD it continues to search for boot device in IDE and then via the network adapter, so even if it’s not configured at first it will come there eventually.
0
0
From memory though if it gets to a HDD/IDE and there’s nothing on it, it will just come up with “OS not found” and then just sit there, or if there is something on it that will boot, both conditions will mean that the NIC will never be reached in the list.
0
0