DRAG DROP
You are planning to set up a proof-of-concept network virtualization environment. The
environment will contain three servers. The servers will be configured as shown in the following table.
You need to enable network connectivity between the virtual machines and Server3.
Which four actions should you perform in sequence? To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.
Answer: 
Explanation:
Is this correct?
I vote that the question and answer have no relation and we get a full refund for our money,wait this is free he he.
Well it happens a lets hope it gets corrected.
Yeah I don’t think this makes any sense.
I just got dumber from readying this.
see… I can’t even spell “reading”… darn u testking!!!
add host, add service, UAG, NAT is correct
Isn’t UAG a secure remote access solution? Surely in this situation WSG is a better option as it doesn’t say anything about remote access being needed?
These links might describe the situation in the question.
Windows Server Gateway
https://technet.microsoft.com/library/dn313101.aspx
Windows Server Gateway integration with Hyper-V Network Virtualization
Windows Server Gateway is integrated with Hyper-V Network Virtualization, and is able to route network traffic effectively in circumstances where there are many different customers – or tenants – who have isolated virtual networks in the same datacenter.
Configuring VM Networks and Gateways in VMM
https://technet.microsoft.com/en-us/library/jj721575.aspx
And the procedure itself:
How to Add a Windows Server Gateway in VMM in System Center 2012 R2
https://technet.microsoft.com/en-us/library/dn249417.aspx
After going through the procedure above the answer might be:
1)add an additional Hyper-V host
add a network service
deploy Windows Server Gateway
enable NAT
These links might describe the situation in the question.
Windows Server Gateway
https://technet.microsoft.com/library/dn313101.aspx
Windows Server Gateway integration with Hyper-V Network Virtualization
Windows Server Gateway is integrated with Hyper-V Network Virtualization, and is able to route network traffic effectively in circumstances where there are many different customers – or tenants – who have isolated virtual networks in the same datacenter.
Configuring VM Networks and Gateways in VMM
https://technet.microsoft.com/en-us/library/jj721575.aspx
And the procedure itself:
How to Add a Windows Server Gateway in VMM in System Center 2012 R2
https://technet.microsoft.com/en-us/library/dn249417.aspx
After going through the procedure above the answer might be:
1) add an additional Hyper-V host
2) add a network service
3) deploy Windows Server Gateway
4) enable NAT
… where there are many different customers – or tenants – who have isolated virtual networks in the same datacenter….
or
The environment will contain three servers.
I don’t know, but this seems to miss the point entirely. Seriously, I don’t know about HyperV but I am VCP. Default vSwitch with one physical ehternet to LAN. VM has 1 NIC connected to said vSwitch. That’s it. It gets DHCP from the LAN and you can connect to Server3.
Maybe a large part of the question is missing and the given options are there to answer a more complicated situation. Arguing over whether or not the given solution is correct or not should be an argument about when will the question be correct.
John Smith is correct.
I checked with Test Lab Guide: Windows Server 2012 R2 Hyper-V Network Virtualization with System Center 2012 R2 VMM
https://www.microsoft.com/en-us/download/confirmation.aspx?id=39284
What determines what comes first? Window Server Gateway, or add Network Service?
1) add an additional Hyper-V host
2) add a network service
3) deploy Windows Server Gateway
4) enable NAT
or
1) add an additional Hyper-V host
2) deploy Windows Server Gateway
3) add a network service
4) enable NAT
Checked and double checked.
Add Resources > Network Service > wizard pops up > Next > select Microsoft Windows Server Gateway
This is the correct order:
1) add an additional Hyper-V host
2) add a network service
3) deploy Windows Server Gateway
4) enable NAT