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)
API to 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: See the explanation
Explanation:
Box 1: Create a private virtual switch
Box 2: Enable the Microsoft NDIS Capture switch extension on the private virtual switch.
Box 3: Configure the VMs to use the private virtual switch.Note:
Hyper-V Extensible Switch
The Hyper-V extensible switch supports an interface that allows instances of NDIS filter drivers
(known as extensible switch extensions) to bind within the extensible switch driver stack. After they
are bound and enabled, extensions can monitor, modify, and forward packets to extensible switch
ports. This also allows extensions to reject, redirect, or originate packets to ports that are used by
the Hyper-V partitions.
I think it should be “internal” instead of “private”, because we want the VMs communicate with other VMs and the Hyper-V host server.
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.