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. 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:
Configure the VMs to use the Private Virtual Switch (not internal)
I think this is the same Q as 56.. and the answer should be Internal virtual switch and not Private… correct?
Read the question carefully and do your research on Internal and Private Switches
This one should definitely be private, as it cannot communicate with the host.
I agree with Shezy2 and Codemonk, “VMs must only comunícate with other VMs” only private network is posible… the original answer is illogical
private-internal-internal??? good
1. Create a private virtual switch.
2. Enable the Microsoft NDIS Capture switch extension on the private virtual switch.
3. Configure the VM’s to use the private virtual switch.
How to Configure Network Settings on a Hyper-V Host in VMM
http://technet.microsoft.com/en-us/library/gg610603.aspx
External – Use this type when you want to allow virtual machines to communicate with each other and with externally located servers, and optionally with the host operating system. The External type is bound to a physical network adapter. This type can be used to allow virtual machines to access a perimeter network and not expose the host operating system.
Internal – Use this type when you want to allow communication between virtual machines on the same host and between the virtual machines and the host. The Internal type is not bound to a physical network adapter. It is typically used to build a test environment where you want to connect to the virtual machines from the host operating system, but do not want to allow virtual machines on the host to communicate with external networks.
Private – Use this type when you want to allow communication between virtual machines on the same host but not with the host or with external networks. The Private type does not have a virtual network adapter in the host operating system, nor is it bound to a physical network adapter. The Private type is typically used when you want to isolate virtual machines from network traffic in the host operating system and in the external networks.
Question says
Virtual machines (VMs) must only communicate with other VMs.
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.
—————————————————–
If the question is
Virtual machines (VMs) must only communicate with other VMs and the Hyper-V host server.
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.
—————————————
NOTE – SAME QUESTION but with slight different requirements.
1.communicate with VMs only : use PRIVATE
2.communicate wih VMs and Hyper-v host : use INTERNAL