Your on-premises network contains a Microsoft SQL server named DCSQL1. You have an Azure subscription that contains an SAP production landscape and a SQL server named AZSQL1. The SAP landscape uses…

Question

Options

• Athe Azure VM extension for SAP solutions
• Bthe Network Watcher extension
• Cthe Azure Diagnostics extension
• Dthe Log Analytics agent

• A
  3% (1)
• B
  87% (27)
• C
  3% (1)
• D
  6% (2)

Explanation

Option B is correct because Connection Monitor (part of Azure Network Watcher) requires the Network Watcher extension to be installed on Azure VMs to act as a monitoring endpoint. Since AZSQL1 is an Azure VM, it needs this extension so Connection Monitor can measure round-trip latency between it and DCSQL1 (which would use the Log Analytics agent or a standalone MMA as the on-premises endpoint).

Why the others are wrong:

• A (Azure VM extension for SAP) - This collects SAP-specific performance metrics for Azure Monitor, not network latency between endpoints.
• C (Azure Diagnostics extension) - This collects OS-level diagnostics (logs, metrics) from VMs and sends them to Azure Storage or Event Hubs; it has no role in network path monitoring.
• D (Log Analytics agent) - This is actually what you'd install on the on-premises machine (DCSQL1) to register it as a Connection Monitor endpoint, not on the Azure VM side.

Memory tip: Think of it this way - Network Watcher = network monitoring tool, so its extension is what enables a VM to participate in network monitoring. The name tells you the purpose. If the question asks about an Azure VM in a Connection Monitor scenario, the answer will almost always be the Network Watcher extension.

No community discussion yet for this question.