DRAG DROP
A software company has a Windows Server 2012 R2 server that has the Hyper-V role installed. The server
hosts a single virtual machine (VM) named VM1. VM1 has one virtual CPU, one virtual hard disk, and one
virtual network interface card (NIC) that is attached to an external network.
The company prepares to test its software in VM1. Before testing begins, VM1 must meet the following
requirements:
Availability of network bandwidth must be maximized.
VM network connectivity must be fault tolerant.
You need to configure the environment.
Which four 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:
Not sure about the proposed answer.
I am pretty sure that the New-NetSwitchTeam cmdlet is not in the answer :
“The network switch team is a team that is controlled by a Hyper-V extensible switch *forwarding* extension”
ref: http://technet.microsoft.com/en-us/library/jj553814.aspx
The order of the answer seems wrong… Setting up a host LBFO team after configuring VMs?
Do not confuse the kids
I think it is correct. Look here:
Example 3: Create a new team in a virtual machine
This set of commands allows teaming in virtual machines by using the AllowTeaming parameter of the Set-VMNetworkAdapter cmdlet and then creates a team named Team2 in the virtual machine specified by VMName. You must run the following command in the host (parent partition) with administrator permissions.
Windows PowerShell
PS C:\> Set-VMNetworkAdapter -VMName -AllowTeaming
PS C:\> New-NetLbfoTeam –Name Team2 –TeamMembers NIC1,NIC2
http://technet.microsoft.com/en-us/library/jj130847.aspx
You’re right. I thought that the New-NetLbfoTeam was for the host NICs.
The proposed answer is correct.
The answer is correct.
Set-VMNetworkAdapter
http://technet.microsoft.com/en-us/library/hh848457.aspx
AllowTeaming
Specifies whether the virtual network adapter can be teamed with other network adapters connected to the same virtual switch. The value can be On (allowed) or Off (disallowed).
New-NetLbfoTeam
http://technet.microsoft.com/en-us/library/jj130847.aspx
-The New-NetLbfoTeam cmdlet creates a new NIC team that consists of one or more network adapters. Teaming network adapters of different speeds is not supported. You can create a team with network adapters of different speeds, but the network traffic distribution algorithms do not take the speed of each network adapter into consideration when distributing traffic.
-When you create a team, you can specify additional properties such as TeamingMode and LoadBalancingAlgorithm.
-You need administrator privileges to use New-NetLbfoTeam.
New-NetSwitchTeam
http://technet.microsoft.com/en-us/library/jj553814.aspx
he New-NetSwitchTeam cmdlet creates a new switch team. A switch team must have a name for the team and must be created with one or more members, or network adapters.
The network switch team is a team that is controlled by a Hyper-V extensible switch forwarding extension. No other cmdlets can be used to manage a switch team and the NetSwitchTeam cmdlets must not be used to manage standard, or non-switch, network adapter teams.
If the option contains a step to add new switch, then new-netswitchteam is also valid.
You can create two external swtiches with two host nics, then it’s switch team.
Since the question listed only steps creating nic teaming, the answer should not include switch teaming.
The answer is correct. You may wonder how you associate VM with physical NIC, then what about other VMs for network. It’s for a SR-IOV network card which bypasses VM bus and directly send/receive IOs with VMs, yet it recognizes IOs for each VM communication. In this case, you associate VM’s NIC to the SR-IOV card and create NIC teaming in VM using New-NetLBFOTeam or through Server Manager.
I think the question seems easy, but yet can’t answer if SR-IOV nic is not mentioned because there’s no reason creating NIC teaming inside VM unless it’s switch team.
The answer is correct (A)
See this doc:
“Supported guest operating systems for guest clusters that use a shared virtual hard disk include Windows Server 2012 R2 and Windows Server 2012. To support Windows Server 2012 as a guest operating system, Windows Server 2012 R2 Integration Services must be installed within the guest (virtual machine).”
https://technet.microsoft.com/en-us/library/dn281956(v=ws.11).aspx
Very soon this website will be famous among all blogging and site-building people, due to it’s pleasant posts|