You need to ensure that the NLB feature can distribute …

Your network contains five servers that run Windows Server 2012.
You install the Hyper-V server role on the servers.
You create an external virtual network switch on each server.
You plan to deploy five virtual machines to each Hyper-V server.
Each virtual machine will have a virtual network adapter that is connected to the external virtual network switch and that has a VLAN identifier of 1.
Each virtual machine will run Windows Server 2012.
All of the virtual machines will run the identical web application.
You plan to install the Network Load Balancing (NLB) feature on each virtual machine and join each virtual machine to an NLB cluster.
The cluster will be configured to use unicast only.
You need to ensure that the NLB feature can distribute connections across all of the virtual machines.
What should you do?

Your network contains five servers that run Windows Server 2012.
You install the Hyper-V server role on the servers.
You create an external virtual network switch on each server.
You plan to deploy five virtual machines to each Hyper-V server.
Each virtual machine will have a virtual network adapter that is connected to the external virtual network switch and that has a VLAN identifier of 1.
Each virtual machine will run Windows Server 2012.
All of the virtual machines will run the identical web application.
You plan to install the Network Load Balancing (NLB) feature on each virtual machine and join each virtual machine to an NLB cluster.
The cluster will be configured to use unicast only.
You need to ensure that the NLB feature can distribute connections across all of the virtual machines.
What should you do?

A.
From the properties of each virtual machine, add a second virtual network adapter.
Connect the new virtual network adapters to the external virtual network switch.
Configure the new virtual network adapters to use a VLAN identifier of 2.

B.
On each Hyper-V server, create a new private virtual network switch.
From the properties of each virtual machine, add a second virtual network adapter.
Connect the new virtual network adapters to the new private virtual network switches.

C.
On each Hyper-V server, create a new external virtual network switch.
From the properties of each virtual machine, add a second virtual network adapter.
Connect the new virtual network adapters to the new external virtual network switches.

D.
From the properties of each virtual machine, enable MAC address spoofing for the existing virtual network adapter.

Explanation:
MAC spoofing
The changing of the assigned MAC address may allow the bypassing of access control lists on servers or routers, either hiding a computer on a network or allowing
it to impersonate another network device.
A user may wish to legitimately spoof the MAC address of a previous hardware device in order to reacquire connectivity after hardware failure.

http://blogs.technet.com/b/jhoward/archive/2009/05/21/new-in-hyper-v-windows-server-2008-r2-part-2-macspoofing.aspx



Leave a Reply 0

Your email address will not be published. Required fields are marked *