Exam 70-740 topic 1 question 13 discussion

Answer is D. you run the command on the host server targeting the vm that is hosting the container. On the VM the container network is already set to transparent, so we need to make sure that the VM is on an external virtual switch/network.

D is correct because VM1 uses transparent mode network and therefore containers are connected to the same network as VM1 and spoofing must be configured on Server1. https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-networking

I agree, answer = D. For start, the containers will need transparency mode to bypass the host and communicate with the local DHCP server. Then each container requires a unique MAC address to be identified as separate devices on the network. Heres the tricky part - essentially answer A does the same thing, but the syntax is incorrect as there isn't a space between the VM name. Therefor running the cmd from server 1 as in answer D is correct.

Dutch 2005 Thanks for the reply, but why do we need to turn on "Mac Address Spoofing" when configuring the virtual machine network adapter to recieve TCP/IP configuration?

IMO, there's one thing that makes option A a wrong answer .. how you going to run "Set-VMNetworkAdapter" with the parameter -VMName on a VM? It doesn't make any sense, because you specify the -VMName on a host not a guest. Plus, hyper-v is the one who will block the multiple addresses if MacSpoofing is not set, so it only makes sense to run this command on the Hyper-v host, which is Server1.

Got this Q on exam

To use DHCP for IP assignment on a virtual container host enable MACAddressSpoofing If the container host is virtualized, and you wish to use DHCP for IP assignment, you must enable MACAddressSpoofing On The Virtual Machines Network Adapter . Otherwise, the Hyper-V host will block network traffic from the containers in the VM with multiple MAC addresses. You can enable MACAddressSpoofing with this PowerShell command: PS C:\> Get-VMNetworkAdapter -VMName ContainerHostVM | Set-VMNetworkAdapter -MacAddressSpoofing On

There is no VM running on VM1, so the command Get-VMNetworkAdapter on VM1 is pointless, and definitely not valid on VM1 itself! Also, the hostserver is most likely connected to an external NIC (for DHCP to work), so per VM on the hostserver one should set the MacAddressSpoofing. So D is the correct answer

Got this question in exam

Answer D: is correct because VM1 uses transparent mode network and therefore containers are connected to the same network as VM1 and spoofing must be configured on Server1. If transparent mode network was not the case (which by default is not) spoofing would have to be configured on both Server1 and VM1 because VM1 is a host for the containers, not only a guest on Server1.

PS C:> Get-VMNetworkAdapter -VMName ContainerHostVM | Set-VMNetworkAdapter -MacAddressSpoofing On The command needs to be run on the Hyper-V host.

Sorry this the correct link that contains Bonna's answer. https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/advanced

Updated Link: https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture

The Answer Should be A If the container host is virtualized, and you wish to use DHCP for IP assignment, you must enable MACAddressSpoofing on the virtual machines, not on the Servers, network adapter. Otherwise, the Hyper-V host will block network traffic from the containers in the VM with multiple MAC addresses. PS C:> Get-VMNetworkAdapter -VMName ContainerHostVM | Set-VMNetworkAdapter -MacAddressSpoofing On

Ans should be On VM1, runGet-VMNetworkAdapter-VMName VM1| Set-VMNetworkAdapter- MacAddressSpoofing On.

what is the answer

link not work