DRAG DROP
You have a Windows Server 2012 R2 server that has the Hyper-V role installed.
The company has the following requirements for the Hyper-V host server:
Virtual machines (VMs) must only communicate with other VMs and the Hyper-V host server.
You must be able to monitor all TCP/IP packets to and from VMs from the moment that VMs are able to
communicate.
You must support a third-party program that uses the Network Driver Interface Specification (NDIS) APIto
monitor the TCP/IP packets between VMs.
You need to configure the environment.
Which three 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:
why create a private switch and not a internal? as vm’s should connect to each other and host!
Yes I agree. This should be internal network if the VM needs to talk to host as well.
Agreed should be Internal if talking to the host
private only if VM – VM
Internal switch, 2nd box is right (internal)
but what is the correct order?
create internal
Ndis
configure VMs to use int
One more opinion… for good original answer is bad totaly:
Create a private and next configure a internal? what’s up
Agree with mlndsk.
Since the VMs must be able to communicate with the host server as well, the first step would be to create an internal virtual switch, as a private virtual switch would not allow communication with the host server. The second step would be to enable the Microsoft NDIS Packet Capture Filter Driver on the internal virtual switch. The last step would be to configure the VMs to use this internal virtual switch.
Virtual machines (VMs) must only communicate with other VMs and the Hyper-V host server.
So it needs to be internal if not for the host it would be private as it is in question 56 🙂
Question says
Virtual machines (VMs) must only communicate with other VMs and the Hyper-V host server.
so ANSWER will be
1: Create a internal virtual switch
2: Enable the Microsoft NDIS Capture switch extension on the private virtual switch.
3: Configure the VMs to use the internal virtual switch.
——————————————————
If the question was
Virtual machines (VMs) must only communicate with other VMs.
THEN ANSWER WILL BE
1: Create a private virtual switch
2: Enable the Microsoft NDIS Capture switch extension on the private virtual switch.
3: Configure the VMs to use the private virtual switch.