You plan to deploy an SAP production landscape in Azure during the next three years. The deployment will use on-demand capacity reservations.You need to minimize the costs of the planned deployment.What should you use?
Answer(s): B
For a production SAP landscape on Azure, you use Azure Reserved VM Instances (RIs) for on-demand capacity reservations to achieve cost savings while ensuring compute capacity is available. RIs are used with capacity reservations to apply a discount to the reserved capacity, but capacity reservations can also be used independently to guarantee compute capacity for your VMs without a long-term commitment.
https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-overview
HOTSPOT (Drag and Drop is not supported)You have an SAP production landscape in Azure. The landscape is in the West Europe Azure region. The landscape contains a Pacemaker cluster for SAP Central Services (SCS) that runs SUSE Linux Enterprise Server (SLES) and uses an Azure NetApp Files NFS volume for shared storage.You are designing a disaster recovery solution to ensure that SCS is available in the North Europe Azure region if the West Europe region become unavailable.You need to recommend a replication method for SCS virtual machines and the Azure NetApp Files volume.The solution must minimize administrative effort.What should you include in the recommendation? To answer, select the appropriate options in the answer area.NOTE: Each correct selection is worth one point.Hot Area:
Answer(s): A
Box 1: Azure Site RecoveryFor SCSAzure Site Recovery (ASR): Use ASR to replicate the SUSE virtual machines running the SAP Central Services (SCS) to the disaster recovery region. ASR replicates the VMs and their managed disks, so the virtual machines are ready for failover when needed.Incorrect:* Application groupsApplication Groups is not a standard term for a replication or high-availability solution for clustered SAP SCS in Azure. It is likely a misunderstanding of other technologies.* Shared disksShared disks are a native Azure feature for Windows clusters, but for Linux* Stretched clustersStretched clusters are not supported for this scenario due to the shared-disk requirement of the SAP cluster resources.Box 2: An application volume groupFor the volumeAn Azure NetApp Files application volume group (AVG) can be used to replicate shared storage for a SUSE Pacemaker cluster, and it's the recommended way for deploying SAP HANA volumes with low latency. An application volume group can also be used for SAP Central Services (SCS) volumes, including those used for shared storage in an SAP NetWeaver or S/4HANA system, to ensure high availability and proximity to your application VMs.
https://learn.microsoft.com/en-us/azure/sap/workloads/planning-supported-configurations https://learn.microsoft.com/en-us/azure/azure-netapp-files/application-volume-group-introduction
You have an Azure subscription that contains an Azure Synapse Analytics workspace named Synapse1.You have an SAP RISE managed workload.You need to implement a connector to copy data into an SAP HANA database by using a data pipeline createdin Synapse1.Which connector should you use?
Answer(s): D
Copy data from SAP HANA using Azure Data Factory or Synapse Analytics SAP HANA sinkCurrently, the SAP HANA connector is not supported as sink, while you can use generic ODBC connector with SAP HANA driver to write data into SAP HANA.Follow the Prerequisites to set up Self-hosted Integration Runtime and install SAP HANA ODBC driver first.Create an ODBC linked service to connect to your SAP HANA data store
https://learn.microsoft.com/en-us/azure/data-factory/connector-sap-hana
You have an Azure subscription that contains a virtual network named VNet1.You have an SAP RISE managed workload.You need to configure connectivity from VNet1 to the SAP Business Technology Platform (BTP).What should you include in the solution?
To connect an Azure Virtual Network to SAP BTP in a RISE managed workload, you can use a private connection like Azure Virtual Network (VNet) Peering, which connects your tenant to SAP's tenant through a private link. Alternatively, you can use a site-to-site VPN, though peering is preferred for performance. For direct connections to specific BTP services, Azure Private Link for SAP BTP can be used [A]. All these methods require coordination with SAP and require careful IP range planning and proper DNS peering.Method 3: Azure Private Link for SAP BTPHow it works: This allows specific SAP BTP services (like Cloud Foundry runtime) to connect privately to supported Azure native services through a private link connection, without the traffic traversing the public internet.When to use: Use this method when your Azure applications need to securely access specific BTP services that are exposed via this private link.Key steps:The SAP BTP environment must be configured to use the SAP Private Link Service.You will configure Azure Private Link to connect to the SAP Private Link Service.
https://learn.microsoft.com/en-us/azure/sap/workloads/rise-integration-network
You have an Azure subscription named Sub1 that is linked to a Microsoft Entra tenant named contoso.com.You have an on-premises deployment of SAP Landscape Management (LaMa).You need to ensure that the on-premises LaMa deployment is authorized to manage the SAP resources provisioned to Sub1.What should you create first?
A Microsoft Entra ID app registration is used as a component of an on-premises SAP Landscape Management (LaMa) integration to manage SAP resources, specifically by providing an on-premises provisioning agent that communicates with the SAP systems via a SCIM endpoint. The app registration is configured with a client secret and application ID that serve as credentials for the agent to authenticate and provision users and groups from Entra ID to the on-premises SAP systems.Note:App registration is a credential source: An app registration in Microsoft Entra ID provides the necessary credentials (application ID and client secret) for the on-premises provisioning agent to authenticate with Entra ID.On-premises provisioning agent: This agent is a component that connects on-premises applications to the Microsoft Entra provisioning service. It translates SCIM operations from Entra ID into actions for the on- premises systems, such as LDAP, SQL, or custom ECMA calls.SCIM protocol: The agent uses the SCIM 2.0 protocol to communicate with the target SAP application's SCIM endpoint, which is the standard for automating user provisioning.Management of SAP resources: By using this integration, SAP LaMa can manage SAP resources. This includes the automation of user and group provisioning into SAP systems, which is a key part of the overall management process.End-to-end solution: This integration enables a complete end-to-end solution for identity and access management, allowing LaMa to work with Microsoft Entra ID to manage the full lifecycle of users within SAP environments.Incorrect:[Not A, not B]An on-premises LaMa instance cannot directly use a managed identity from an Azure subscription for authentication because it does not have the necessary identity context.[Not D]The external identity provider is primarily for user authentication, enabling SSO into SAP applications.
https://learn.microsoft.com/en-us/entra/identity/app-provisioning/how-provisioning-works
Post your Comments and Discuss Microsoft AZ-120 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-120 content, but please register or login to continue.