You have a Hyper-V host named Server1 that runs Windows Server 2012 R2. Server1 has
the virtual switches listed in the following table.
You create a virtual machine named VM1. VM1 has two network adapters. One network
adapter connects to vSwitch1. The other network adapter connects to vSwitch2. You
configure NIC teaming on VM1.
You need to ensure that if a physical NIC fails on Server1, VM1 remains connected to the
network.
What should you do on Server1?
A.
Run the Set-VmNetworkAdapterRoutingDomainMappingcmdlet
B.
Run the Set-VmNetworkAdapterlsolationcmdlet.
C.
Run the Set-VmNetworkAdapterAdapterFailoverConfigurationcmdlet.
D.
Modify the properties of the network adapters on VM1.
Can’t find reasonable answer.
Nic teaming is in place so you dont need to do anything!
0
0
I don’t really understand this either. From what I can tell the answer above doesn’t really have anything to do with ensuring that VM1 stays connected as it has to do with VPNs and Multi-Tenancy which this question says nothing about. I mean is this really just one of those these are all wrong but which one is the least wrong questions? Mind boggling…
0
0
Seems like A is still the best – https://crowdforce.wordpress.com/category/exam/70-410/
0
0
The answer A that you presented on that link is not the same as the one listed on this question. On your link answer A has the following command Set-VmNetworkAdapter, while here it has Set-VmNetworkAdapterRoutingDomainMapping command.
Either way, i don’t see how can this command would help more than the NIC teaming that’s already been configured. I’m confused here.
In this teste v.3, http://www.aiotestking.com/microsoft/you-need-to-ensure-that-if-a-physical-nic-fails-on-server1-vm1-remains-connected-to-the-network/, a user named “sneed” says the correct answer is in fact Set-VmNetworkAdapterRoutingDomainMapping, but he doesn’t explain why, and i look at the description of the cmdlet, https://technet.microsoft.com/en-us/library/dn464281(v=wps.630).aspx, and it doesn’t help either.
0
0
All these questions are bullshit. Fuck microsoft.
0
0
Answer: D
VM settings /Network Adapter/Advanced Features/NIC Teaming/ “Enable this network adaptor to be part of a team in the guest operating system”
0
0
I think its D. Under “advanced features” it says “When this option is cleared, a team created in the guest operating system will lose connectivity if one of the physical network adapters stops working” which is exactly the case above. So it must be enabled.
0
0
http://windowsitpro.com/hyper-v/solving-nic-team-problems-hyper-v-vm
Set-VMNetworkAdapter -VMName -AllowTeaming On enables the checkmark for the “Enable this network adapter to be part of a team in the guest operating system” option.
When this option is cleared a team created in the guest operating system will los connectivity if one of the physical network adapters stops working.
So D is the correct answer. Also this same question also appears in other versions with answers:
A. Set-VMNetworkadapter
B. Add a new network adapter to VM1.
C. Create a new virtual switch on Server 1
D. Modify the properties of vSwitch1 and vSwitch2
0
0
Question mentions that Nic teaming is configured on Vm1, which is probably on the guest OS. Question asks what should be done on Server1 as in the host OS. Option D allows NIC teaming to be enabled via the advanced features in VM1 settings in Hyper-v Manager.
Option D is correct.
0
0
https://technet.microsoft.com/en-us/library/dn464281.aspx
0
0
D to Enable “Allow teaming” feature…
0
0