You have an Azure subscription that contains a virtual network named VNET1, an SAP production landscape on Azure, and an SAP non-production landscape on Azure. Both landscapes connect to VNET1. Each…

Question

Options

• A1
• B2
• C3
• D6

• A
  75% (21)
• B
  7% (2)
• C
  4% (1)
• D
  14% (4)

Explanation

A single Azure Monitor for SAP Solutions (AMS) instance can monitor multiple SAP landscapes, multiple component types, and both production and non-production environments simultaneously. Because both landscapes are already connected to the same VNET1, one AMS instance has network visibility into all virtual machines - covering SAP HANA, SAP NetWeaver, and SQL Server across both environments without any additional instances.

Why the distractors are wrong:

• B (2) assumes you need one instance per landscape (prod/non-prod) - AMS has no such restriction
• C (3) assumes you need one per component type (HANA, NetWeaver, SQL Server) - AMS monitors all SAP components from a single instance
• D (6) combines both wrong assumptions (2 landscapes × 3 components) - the most expensive and most incorrect option

Memory tip: Think "one VNet, one monitor." AMS is scoped at the Azure Monitor resource level, not per-landscape or per-component. As long as all your SAP VMs share network connectivity (via VNET1 here), a single AMS instance covers everything. When a question says "minimize costs," always look for the single-instance answer first with AMS.

No community discussion yet for this question.