You have two Azure virtual networks named VNet1 and VNet2. VNet1 contains an Azure virtual machine named VM1. VNet2 contains an Azure virtual machine\nnamed VM2.\nVM1 hosts a frontend application that connects to VM2 to retrieve data.\nUsers report that the frontend application is slower than usual.\nYou need to view the average round-trip time (RTT) of the packets from VM1 to VM2.\nWhich Azure Network Watcher feature should you use?\nA. IP flow verify\nB. Connection monitor\nC. NSG flow logs\nD. Connection troubleshoot\nCorrect Answer: B\nSection: (none)\nExplanation\nExplanation/Reference:\nExplanation:\nThe connection monitor capability monitors communication at a regular interval and informs you of reachability, latency, and network topology changes between\nthe VM and the endpoint\nIncorrect Answers:\nA: The IP flow verify capability enables you to specify a source and destination IPv4 address, port, protocol (TCP or UDP), and traffic direction (inbound or\noutbound). IP flow verify then tests the communication and informs you if the connection succeeds or fails. If the connection fails, IP flow verify tells you which\nsecurity rule allowed or denied the communication, so that you can resolve the problem.\nC: The NSG flow log capability allows you to log the source and destination IP address, port, protocol, and whether traffic was allowed or denied by an NSG.
\nD: The connection troubleshoot capability enables you to test a connection between a VM and another VM, an FQDN, a URI, or an IPv4 address. The test returns\nsimilar information returned when using the connection monitor capability, but tests the connection at a point in time, rather than monitoring it over time, as\nconnection monitor does.\nReference:\nhttps://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overview