Inspecting Network Traffic between VM1 and VM2
Question
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 Performance Monitor, you create a Data Collector Set (DCS).
Does this meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.B
You should use Azure Network Watcher.
https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overviewNo, creating a Data Collector Set (DCS) in Performance Monitor is not the correct solution to meet the goal of inspecting all the network traffic from VM1 to VM2 for a period of three hours.
Performance Monitor is a tool that is used to monitor system performance and resource usage on Windows machines. It collects and displays system statistics, such as CPU usage, memory usage, and disk usage. It does not provide the ability to capture and inspect network traffic.
To inspect network traffic between VM1 and VM2, you would need to use a network capture tool, such as Wireshark, on one or both of the virtual machines. Wireshark is a free and open-source network protocol analyzer that allows you to capture and inspect network traffic in real-time.
To capture network traffic using Wireshark, you would need to:
- Install Wireshark on one or both of the virtual machines.
- Start a capture session in Wireshark, selecting the network interface that is used to communicate between VM1 and VM2.
- Allow the capture session to run for the desired three-hour period.
- Stop the capture session and analyze the captured traffic.
It's important to note that capturing network traffic can generate a large amount of data, so you may need to filter the capture results to focus on the traffic between VM1 and VM2.
In summary, the solution of creating a Data Collector Set in Performance Monitor does not meet the goal of inspecting network traffic between VM1 and VM2 for a period of three hours. A network capture tool, such as Wireshark, would be more appropriate for this task.
