Home › Forums › Azure › AZ-104 Microsoft Azure Administrator › Timed Mode Test 1, 5th question for Monitor and maintain Azure resources
-
Timed Mode Test 1, 5th question for Monitor and maintain Azure resources
JR-TutorialsDojo updated 3 months, 1 week ago
2 Members
·
4
Posts
-
Hi
Question reads:
Your organization currently has several virtual machines running in their Azure subscription.
You have been assigned to track and compare the latencies of the on-premises site with the latencies of the Azure application.
Which of the following options would satisfy this requirement?
– isn’t ‘packet capture’ also a correct option for this one? See:
Inspect and analyze packet capture files – Azure Network Watcher | Microsoft Learn
Quote:
‘Example uses of packet capture data include investigating network or application problems, detecting network misuse and intrusion attempts, and maintaining regulatory compliance.
In this article, you learn how to use a popular open-source tool to open a packet capture file that Network Watcher provided. You also learn how to calculate connection latency, ….‘
Thanks in advance for your thoughts.
-
Hello cornettoberlin,
Thanks for the feedback.
Could you please elaborate on why “packet capture” is considered correct?
From the explanation provided:
Packet Capture is incorrect because this will just help you capture all traffic on a VM in your virtual network. Unlike Connection Monitor, which allows you to track both on-premises and cloud infrastructure.
This seems to imply that Packet Capture is limited in scope and does not provide latency metrics or comparative insights between environments. I would appreciate your thoughts on how Packet Capture meets the scenario requirements or what specific capability makes it the preferred option.
Looking forward to your insights.
Best regards,
JR @ Tutorials Dojo -
Hello JR
Many thanks for swift and helpful response. While the link I sent says that packet capture can be used together with Wireshark to calculate network latency, I unfortunately overlooked the limitation (i.e. packet capture will just help you capture all traffic on a VM in your virtual network) that is stated in the explanation which you copied into your reply. In view of that, I now see that Connection Monitor makes perfect sense as the correct answer.
Thanks again and best regards
-
Happy to assist, rolandb. Let me know if you need any further clarification or support.
-
Log in to reply.