You have an Azure virtual machine named VM1 that has the Hyper-V server role installed.
On VM1, you create a nested virtual machine named VM2.
You need to ensure that VM2 can communicate with the virtual machines connected to the same virtual network as VM1.
What should you do first?
- Configure Router guard on the network adapter of VM2.
- Create a NAT switch on VM1.
- This answer is correct.
- Create an external switch on VM1.
- Enable MAC address spoofing on the network adapter of VM2.
- Create a NAT switch on VM1.
When operating in a public cloud environment where MAC address spoofing is impossible, you can allow connectivity from the virtual machines installed on a nested virtual machine that has the Hyper-V server role by using a NAT switch. An external switch fails to provide the intended functionality since it will result in traffic originating from multiple MAC addresses. MAC address spoofing must be implemented on the physical Hyper-V hosts, which is impossible in this scenario. The same applies to Router guard, however, this will not deliver the intended functionality either.