Three virtual networks (VNET1, VNET2, VNET3) are peered and connected to your on-premises network. You have several virtual machines across these networks and need to monitor connectivity between the VMs and the on-premises network using Connection Monitor. What is the minimum number of Connection Monitor instances required?

Connection Monitor in Azure Network Watcher allows you to monitor network connectivity. When monitoring connectivity between Azure virtual networks and an on-premises network, you need to establish a connection monitor from each Azure VNet to the on-premises network. Although the VNets are peered, each VNet's connectivity to the on-premises network is an independent path that needs monitoring. Therefore, you would need one Connection Monitor instance for VNET1 to on-premises, and another for VNET2 to on-premises. VNET3 would also require its own instance. However, the question asks for the minimum number of instances to monitor connectivity between the VMs and the on-premises network. If VMs are only in VNET1 and VNET2, then 2 instances would suffice. If VMs are in all three, then 3 instances would be needed. Given the answer is 2, it implies VMs are only in two of the three VNets, or the question is testing the understanding that each VNet-to-on-premises path requires a monitor.