Exam AZ-802 Topic 1 Question 142 Discussion

Explanation:
On Server1, you can create additional private and internal virtual switches only. Server1 can access network shares on virtual machines that are connected to VSwitch2 or VSwitch3 only.
Hyper-V supports three virtual switch types: External (bound to a physical network adapter, optionally shared with the management OS), Internal (connects VMs to each other and to the management OS, with no physical adapter binding), and Private (connects VMs to each other only, with no management OS or external connectivity). A single physical network adapter can be bound to only one External virtual switch at a time (absent NIC teaming); because Server1 has only one NIC and it is already bound to VSwitch3 as an External switch, no additional External switch can be created without adding another physical adapter -- but Internal and Private switches, which never bind to a physical NIC, can still be created freely. This means Server1 can create additional private and internal virtual switches only, not additional external switches. For host-to-VM connectivity, the management operating system can communicate with VMs on an Internal switch (VSwitch2) and, because the management OS shares the adapter via the Microsoft Hyper-V Network Adapter, with VMs on the External switch (VSwitch3) as well; the management OS has no network path to VMs on a Private switch (VSwitch1), since Private switches by design isolate VM traffic from the host. Consequently, Server1 can access network shares hosted on VMs connected to VSwitch2 or VSwitch3 only -- not VSwitch1, and not all three switches as the source exhibit ' s highlighting suggested.