Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You manage a virtual network named VNet1 that is hosted in the West US Azure region.
VNet1 hosts two virtual machines named VM1 and VM2 that run Windows Server.
You need to inspect all the network traffic from VM1 to VM2 for a period of three hours.
Solution: From Azure Network Watcher, you create a connection monitor.
Does this meet the goal?
A . Yes
B . No
Answer: B
Explanation:
Network Watcher Connection Monitor enables you to configure and track connection reachability, latency, and network topology changes. It helps reduce the amount of time to detect connectivity problems. The returned results can provide insights into whether a connectivity problem is due to a platform or a user configuration problem. This is not used in cases where we need to inspect for all the network traffic from one vm to another vm.
On the other hand Network Watcher packet capture allows you to create capture sessions to track traffic to and from a virtual machine. So in this scenario we need to use Network Watcher packet capture
References:
https://azure.microsoft.com/en-in/updates/general-availability-azure-network-watcher-connection-
monitor-in-all-public-
regions/#:~:text=Network%20Watcher%20Connection%20Monitor%20helps,or%20a%20user%20
configuration%20problem
https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-packet-capture-
manage-portal