You have an Azure subscription that contains an Azure Monitor for SAP solutions resource and a virtual machine named VM1. VM1 runs SUSE Enterprise Linux (SLES) and hosts an SAP NetWeaver application…

Question

Options

• AOn VM1, install the Prometheus node exporter.
• BFrom the Azure portal, add the Azure Monitor for SAP solutions NetWeaver provider.
• CFrom the Azure portal, add the Azure Monitor for SAP solutions OS (Linux) provider.
• DOn VM1, install the Telegraf agent.

• A
  88% (43)
• B
  2% (1)
• C
  4% (2)
• D
  6% (3)

Explanation

Installing the Prometheus node exporter on VM1 must come first because the Azure Monitor for SAP solutions OS (Linux) provider works by scraping metrics exposed by the node exporter running on the VM - without it, the provider has nothing to collect from, making it a prerequisite before any portal configuration.

Option B (NetWeaver provider) is wrong because that provider targets SAP application-layer metrics (ABAP work processes, message server, etc.), not OS-level CPU/memory/network data.

Option C (OS Linux provider) is the next step after A, not the first - adding the provider in the portal only works once the node exporter is already running and exposing metrics on the VM.

Option D (Telegraf) is a red herring - Telegraf is used with Azure Monitor for different scenarios (like writing to Azure Monitor Metrics), but Azure Monitor for SAP solutions specifically relies on Prometheus node exporter for Linux OS metrics.

Memory tip: Think of it as "install the reporter, then register the listener" - the node exporter reports metrics on the VM, and the Azure portal provider is what listens. You can't register a listener for something that isn't reporting yet.

No community discussion yet for this question.