Correct Answer: Use dedicated resource groups per SAP SID with consistent tags (e.g., Environment, SID, CostCenter, Owner) and Azure Cost Management budgets per resource group
SAP on Azure best practice: each SID (e.g., PRD, QAS, DEV) should have its own resource group containing all related resources (VMs, disks, NICs, NSGs). Apply consistent tags (SID,...
Correct Answer
Use dedicated resource groups per SAP SID with consistent tags (e.g., Environment, SID, CostCenter, Owner) and Azure Cost Management budgets per resource group
Why This Answer Is Correct
SAP on Azure best practice: each SID (e.g., PRD, QAS, DEV) should have its own resource group containing all related resources (VMs, disks, NICs, NSGs). Apply consistent tags (SID, Environment, CostCenter, Application) to enable cost filtering in Azure Cost Management + Billing. This enables chargeback per SID, access control per team, and lifecycle management (delete all SID resources by deleting the resource group). Mixing SIDs in one resource group creates governance and billing complexity.
This question evaluates your knowledge of High Availability — a core concept tested in Microsoft Certified: Azure for SAP Workloads Specialty (AZ-120). Understanding High Availability is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
You are configuring SAP HANA System Replication (HSR) across two different Azure Availability Zones in the same region. What replication mode should you use to ensure zero data loss while minimizing the impact on the primary node's performance?
You are designing the network topology for an SAP landscape on Azure. To ensure high availability of the SAP ASCS/SCS instance across two VMs in an availability set, what networking component is required to route traffic to the active node?
When configuring a SUSE Linux Enterprise Server (SLES) Pacemaker cluster for SAP ASCS High Availability in Azure, what resource is used to reliably fence (STONITH) a failed node?
You are migrating a legacy SAP ECC system running on Windows Server to Azure. You want to ensure the VMs automatically restart on healthy hardware if an underlying Azure host fails. What is this capability called?
Your organization uses Azure Active Directory (Entra ID) for authentication. You want to configure Single Sign-On (SSO) for your SAP Fiori launchpad. Which standard protocol is natively supported by both SAP Fiori (ABAP front-end) and Azure AD for this purpose?