You have a deployment of SAP NetWeaver on Azure. You plan to implement Azure Monitor for SAP solutions to monitor the NetWeaver systems. You need to ensure that you can collect a complete array of…

Question

Options

• AFrom the SAP Management Console, create a system snapshot.
• BFrom the SAP GUI, unprotect the SAPControl web methods.
• CFrom the SAP Management Console, disable the SAPStartSRV service on each NetWeaver
• DFrom the SAP GUI, disable the wsdl11, wsdl11, and RFC services.

• B
  94% (16)
• C
  6% (1)

Explanation

Option B is correct because Azure Monitor for SAP solutions collects availability and performance data by querying SAPControl web methods - the built-in SAP monitoring API. By default, many of these web methods are "protected," meaning they require authentication that Azure Monitor cannot provide. Unprotecting them (via SAP GUI) allows the monitoring agent to call the full set of methods and retrieve a complete metrics payload.

Why the distractors are wrong:

• A (System snapshot): A snapshot captures a point-in-time state; it does nothing to enable ongoing, continuous metric collection by Azure Monitor.
• C (Disable SAPStartSRV): SAPStartSRV is the service that hosts the SAPControl web interface - disabling it would cut off Azure Monitor's ability to collect anything at all.
• D (Disable wsdl11/RFC services): Disabling services restricts access further; Azure Monitor needs more access to collect metrics, not less.

Memory tip: Think of it as unlocking a door - Azure Monitor knocks via SAPControl web methods, but if those methods are "protected" (locked), it can't get in. Your first step is always to unprotect = unlock, then monitoring can flow freely.

No community discussion yet for this question.