Exam 70-741 topic 1 question 28 discussion

I think is: New-VMSwitch and EnableEmbeddedTeaming # Create a vmSwitch with SET New-VMSwitch -Name SETswitch -NetAdapterName "SLOT 2","SLOT 3" -EnableEmbeddedTeaming $true

Answer Area -Name Production –NetAdapterName $true Add-NetLbfoTeamNic „NIC 1“, „NIC 2“ -EnableEmbeddedTeaming Add-VmNetworkAdapter -Enablelov Add-VmSwitch -EnablePacketDirect New-NetbfoTeam New-VmSwitch Answer: New-VmSwitch -EnableEmbeddedTeaming

Same as Q.141 on 70-740 dump

Question is not given properly. Correct Answers are: From 1st Slot: New VMSwitch cmdlet From 2nd Slot: -EnableEmbeddedTeaming

Microsoft Ref: New-VMSwitch -Name TeamedvSwitch -NetAdapterName "NIC 1","NIC 2" -EnableEmbeddedTeaming $true

Add-VMSwitch & EnableEmbeddedTeaming

New-VMSwitch & EnableEmbeddedTeaming

Migrate to VMWare. No serious enterprise uses Hyper-V, certainly not one that uses advanced infrastructure technologies.

If you guys look up each command, you'll see that none of these command contain the "-netAdapterName" parameter. So apparently none of these answers are correct... it should be "New-VmSwitch" that does contain the -netAdapterName parameter. https://docs.microsoft.com/en-us/powershell/module/hyper-v/new-vmswitch?view=win10-ps

New-VmSwitch -EnableEmbeddedTeaming

Sorry to be repeating myself 70-740 - Q 141- Answer New-VMSwitch & EnableEmbeddedTeaming

Correct answers Sellect New-VMSwitch & EnableEmbeddedTeaming

Add-VMSwitch -Name Production -NetAdapterName "NIC 1", "NIC 2" -EnableEmbeddedTeaming

NO its not Switch Embeded Teaming ... i think the question is scred up ... Because it states that the GUEST VM Musst be able to use RDMA. With Switch embeded teaming this is not Possible. With SED only the host itself could use the RDMA Capabilities So in my opinion you need to use ROOT-IO Virtualization wich in fact passes the real NIC hardware trhought to the VM. add-vmwitch - enableiov but you would create one vm-switch for nic1 and one extra vm-switch for nic2. So i think something is wrong with the question ... SEE: "With the release of Windows Server 1709 Windows Server supports RDMA in the guest" .. so not in Server 2016 https://techcommunity.microsoft.com/t5/Networking-Blog/The-Evolution-of-RDMA-in-Windows-now-extended-to-Hyper-V-Guests/ba-p/339699

Funny, all commands are wrong. Answer is: New-VMSwitch -Name Production -NetAdapterName "NIC 1","NIC 2" -EnableEmbeddedTeaming $true https://docs.microsoft.com/en-us/previous-versions/windows/server/mt403349(v=ws.12)#create-a-hyper-v-virtual-switch-with-set-and-rdma-vnics

i go with Dritter : Virtual Switches based on NIC-teaming are not RDMA capable. We have to create a Switch Embedded Teaming (SET) virtual Switch New-VMSwitch -Name SETswitch -NetAdapterName "SLOT 2","SLOT 3" -EnableEmbeddedTeaming $true

Spud1993 has it correct. New-VMSwitch -Name SETswitch -NetAdapterName "SLOT 2","SLOT 3" -EnableEmbeddedTeaming $true They should pull the question. none of the answers shown are correct.