Hello, I ran across this practice exam question regarding multiple Hyper-V hosts connected to the "same network" attempting to get the test taker to state what VMs would be able to communicate based on the VLAN settings for each Virtual Switch or VM. I am not quite sure how to answer this one, primarily my confusion is around what happens when you create a vSwitch while specifying a VLAN ID here:
Then create a VM and specify a VLAN ID here:
I can't think of a time when you would ever do this in production.... I would assume that if you were going to enable VLAN tagging for Hyper-V hosts, you would simply leave the vSwitch in its default state without specifying a tag. The Hyper-v host physical network connection would then go to a "trunk" port on the switch where the native VLAN drops into your desired default network segment.
Then when you go to create VMs, you can specify a tag on the VM network adapter which would drop each VM into whatever network segment you needed them to be in.
I can't think of why you would EVER specify a VLAN tag for an entire vSwitch.. In my mind this would force every VM connected to the vSwitch to a particular network segment and further specifying a tag at the VM at that level would just break VM connectivity.
I mean wouldn't just setting the physical network port on the switch to "access mode" of the VLAN you want assigned to the virtual switch essentially accomplish the same thing?
Below is the question and details, hopefully you can help me clear this up!
You have two Hyper-V hosts named Server1 and Server2 that run Windows Server 2016. Server1 and Server2 connect to the same network. Server1 and Server2 have virutal switches configured as shown in the following table.
You have virtual machines configured as shown in the following table.
All of the virtual machines are configured to have IP addresses from the same network segment. The firewall on each of the virtual machines is configured to allow network connectivity. To which virutalmachines can you connect from VM1 and VM2?