You have a Windows Server 2012 R2 with the Hyper-V role installed. The host server hosts a virtual machine
(VM) named NYC-VM. The virtual switches for the host server are configured as follows:
NYC-VM must meet the following requirements:
communicate with all of the VMs on the same virtualization host server communicate with the virtualization host
server
must NOT communicate with VMs on different virtualization host servers
You need to configure the virtual switch for NYC-VM.
What should you do?
A.
On NYC-VM, enable virtual LAN identification.
B.
Run the Windows PowerShell command Connect-VMNetworkAdapter -VMName NYC- VM -SwitchName
INT.
C.
Connect NYC-VM to the EXT switch.
D.
Run the Windows PowerShell command Connect-VMNetworkAdapter -VMName NYC- VM -SwitchName
EXT.
Shouldn’t it be.. B.
Run the Windows PowerShell command Connect-VMNetworkAdapter -VMName NYC- VM -SwitchName
INT.
yes, i think B is correct. A is just to allow the use of a VLAN
Initially I was also inclined to go for B but after some investigation I ended up choosing answer A.
“Configuring virtual local area networks (VLANs)
On the management operating system, you will need to configure the virtual network to allow network traffic on the physical port. This is for the VLAN IDs that you want to use internally with virtual machines. Next, you configure the virtual machine to specify the virtual LAN that the virtual machine will use for all network communications.
There are two modes in which you can configure a VLAN: access mode and trunk mode. In access mode, the external port of the virtual network is restricted to a single VLAN ID in the UI. You can have multiple VLANs using WMI. Use access mode when the physical network adapter is connected to a port on the physical network switch that also is in access mode. To give a virtual machine external access on the virtual network that is in access mode, you must configure the virtual machine to use the same VLAN ID that is configured in the access mode of the virtual network. Trunk mode allows multiple VLAN IDs to share the connection between the physical network adapter and the physical network. To give virtual machines external access on the virtual network in multiple VLANs, you need to configure the port on the physical network to be in trunk mode. You will also need to know the specific VLANs that are used and all of the VLAN IDs used by the virtual machines that the virtual network supports.”
http://technet.microsoft.com/en-us/library/cc816585.aspx
http://www.serverwatch.com/server-tutorials/harnessing-the-power-of-hyper-v-network-virtual-switches.html
NYC-VM has to communicate. And reading the question i suppose that no switch is atteched to the VM. So we have to connect a switch to it. To only choise we have left is to connect it to a Internal Switch because of the requirements
(An Internal Virtual Network is similar to a Private Virtual Network in that it isn’t bound to any physical NIC. The Internal Virtual Network is an isolated virtual switch like the Private Virtual Network, but in the case of the Internal Virtual Network, the Host operating system has access to the guest virtual machines through the Internal Virtual Network virtual switch.)
Answer: B
B – as it needs to communicate both with the local VMs AND the host.
The answer is A. If the requirement states that you MUST be able to communicate with the Host Machine then you CANNOT use an Internal Network. So that means that choice B does not fufill the requirements and C and D allow for communication outside of the local machine. The only answer left is A.
If there was not the requirement to communicate with the Host then you would choose B.
How to Add and Configure Network Adapters for a Virtual Machine
http://technet.microsoft.com/en-us/library/bb740792.aspx
– Internal Network. Select this option for a virtual machine that you want to connect to an isolated internal network that enables communication only among virtual machines on the same host. Virtual machines attached to the internal virtual network cannot communicate with the host, with any other physical computers on the host’s LAN, or with the Internet.
– External Network . Select this option to specify that a virtual machine created by using this hardware profile will be connected to a physical network adapter on its host. Virtual machines attached to a physical network adapter can communicate with any physical or virtual computer that the host can communicate with and with any resources available on the intranet and over the Internet that the host computer can access.
I revoke my previous comment – the article I linked to was for VMM 2007. Things changed in VMM 2012.
The answer is B.
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.
Sure … B is absolutely correct!