Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Microsoft
  5. AZ-120

Microsoft AZ-120 Exam
Planning and Administering Microsoft Azure for SAP Workloads (Page 14 )

Updated On: 9-Feb-2026
Page 14 of 84
PDF with 412 Questions

HOTSPOT (Drag and Drop is not supported)

You are designing the backup solution for an SAP database.

You have an Azure Storage account that is configured as shown in the following exhibit.



Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the graphic.

NOTE: Each correct selection is worth one point.

Hot Area:


  1. See Explanation for the Answer.

Answer(s): A

Explanation:



Box 1: standard solid-state drives (SSDs)
From the exhibit we see: Performance Standard

Standard SSD Managed Disks, a low-cost SSD offering, are optimized for test and entry-level production workloads requiring consistent latency.

Box 2: to another Azure region
From the exhibit we see: Replication: Geo-redundant storage (GRS)

Note: Geo-redundant storage (GRS) copies your data synchronously three times within a single physical location in the primary region using LRS. It then copies your data asynchronously to a single physical location in a secondary region that is hundreds of miles away from the primary region.



HOTSPOT (Drag and Drop is not supported)

You plan to implement a deployment of SAP NetWeaver on Azure. The deployment will be hosted on virtual machines that run Windows Server 2022.

You need to configure an authentication solution for the deployment. The solution must meet the following requirements:

Support single sign-on (SSO) and multi-factor authentication (MFA) for SAP NetWeaver applications.

Minimize administrative effort.

What should you include in the solution? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Hot Area:

  1. See Explanation for the Answer.

Answer(s): A

Explanation:



Box 1: Active Directory Domain Services (AD DS)
Join a domain (Windows only)
If your Azure deployment is connected to an on-premises Active Directory or DNS instance via an Azure site-to- site VPN connection or ExpressRoute (this is called cross-premises in Azure Virtual Machines planning and implementation for SAP NetWeaver), it is expected that the VM is joining an on-premises domain.

Box 2: Microsoft Entra ID
Microsoft Entra ID Single sign-on (SSO) integration with SAP NetWeaver When you integrate SAP NetWeaver with Microsoft Entra ID, you can:

Control in Microsoft Entra ID who has access to SAP NetWeaver. Enable your users to be automatically signed-in to SAP NetWeaver with their Microsoft Entra accounts.
Manage your accounts in one central location.

Note: Enable single sign-on for an enterprise application

Microsoft Entra ID has a gallery that contains thousands of pre-integrated applications that use SSO.


Reference:

https://learn.microsoft.com/en-us/azure/sap/workloads/deployment-guide

https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/add-application-portal-setup-sso



You have an on-premises SAP Enterprise Central Component (ECC) landscape that is hosted on servers that run Windows Server and uses an Oracle database.

You need to migrate the landscape to SAP S/4HANA on Azure virtual machines. The solution must minimize downtime.

What should you use?

  1. Azure Site Recovery
  2. Software Update Manager (SUM)
  3. Software Provisioning Manager (SWPM)
  4. Azure Migrate

Answer(s): B

Explanation:

Migration from SAP ERP On-Premise to SAP S/4HANA on Azure
Migration Procedure using DMO
The conversion of On-Premise SAP ERP6.0 into SAP S/4 HANA On Azure uses the one-step approach of using Database Migration Option (DMO) of SAP's Software Update Manager (SUM) tool.



Fig. 1 One-step conversion from SAP ERP to SAP S/4 HANA using DMO to Azure Benefits of using DMO approach compared to the classical export/import method are:
No export of the source database to the file system
No transport of source database export files to Azure
SAP S/4 HANA conversion `On-the-fly' over the WAN MPLS connection using the DMO of Software Update
Manager
Ability to leverage the flexibility of Azure by running the conversion on a very powerful system Reduced business downtime by leveraging the above benefits
Prerequisites / System Requirement
To use the DMO approach to migrate to Azure, your on-premise SAP ERP system should fulfil following requirements
SAP ERP system running on a non-HANA database (like Oracle/DB2) It should be Unicode system
It should be running on SAP Netweaver Application server for ABAP component only (No Dual stack system supported)



DRAG DROP (Drag and Drop is not supported)

You have a bill of materials (BOM) that describes SAP deployments.

You plan to automate the implementation of an SAP S4/HANA deployment to Azure by using the SAP deployment automation framework on Azure.

You need to generate the SAP application templates for the planned implementation and update the BOM.

In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.

Select and Place:

  1. See Explanation for the Answer.

Answer(s): A

Explanation:



Step 1: Generate an ABAP Central Services (ASCS) parameter file Generate SAP Application templates for automation
The SAP on Azure Deployment Automation Framework uses a Bill of Materials (BOM) to define the SAP Application. Before you can deploy a system using a custom BOM, you need to also create the templates for the ini-files used in the unattended SAP installation.

Generate ASCS parameter file

Step 2: Install the SAP HANA and SAP Central Services (CSC) instances

Step 3: Load the database content

Load database content

Make sure the following settings are in place on the VM before you begin:

Install and configure your HANA and SCS instances. These instances must be online before you complete the database content load. (Step 2)

The <sid>adm user you created when you generated the unattended installation file for ASCS must be a member of the sapinst group.

The user identifier for <sid>adm must match the value of hdblcm. This example uses 2000.

The SWPM needs access to /sapmnt/<SID>/global/. To configure permissions, run chown <sid>adm:sapsys / sapmnt/<SID>/global.

Step 4: Generate and combine the parameter files of the application servers Generate database load template

Generate PAS parameter file
Generate an unattended installation parameter file for use with PAS.

Generate additional application servers parameter file
Generate an unattended installation parameter file for use with AAS.

Combine parameter files
You can combine your parameter files, which all end with inifile.params, into one file for the installation process.

Create combination file
To create a file that combines all your parameters:

1. If you haven't already, download each parameter file you created (ASCS, PAS, and AAS). You need these files on the computer or VM from which you're working.

2. Make a backup of each parameter file.

3. Create a new combination file. Name this file for the SAP product that you're using. For example, S4HANA_2020_ISS_v001.inifile.params.

4. Open the ASCS parameter file (scs.inifile.params) in an editor.

5. Copy the header of the ASCS parameter file into the combination file. For example:

######################################################################################### ################################
# #
# Installation service 'SAP S/4HANA Server 2020 > SAP HANA Database > Installation #
# > Application Server ABAP > Distributed System > ASCS Instance', product id 'NW_ABAP_ASCS:S4HANA2020.CORE.HDB.ABAP' #
# #
######################################################################################### #########

6. For each inifile.params file you have, copy the product identifier line from the header. Then, copy the product identifiers into the header of your combination.

Step 5: Add the templates to the BOM.
7. Open your bom.yml file in an editor.

8. Copy the sections for product_ids into your combination file.

9. For each inifile.params file you have, copy the product identifier from the header into the appropriate part of product_ids. For example, copy your ASCS to scs:

product_ids:
scs: "NW_ABAP_ASCS:S4HANA2020.CORE.HDB.ABAP"
db: ""
pas: ""
aas: ""
web: ""

10. Remove any lines that you commented out or left blank.

11. Save your combination file.



You have an on-premises SAP AnyDB deployment hosted on an operating system that is NOT supported in Azure.

You need to migrate the deployment to Azure by performing a replatform and migration to SAP HANA. The solution must meet the following requirements:

Minimize administrative effort.

Minimize downtime.

What should you use?

  1. Azure Migrate
  2. Azure Database Migration Service
  3. SAP Software Provisioning Manager
  4. SAP Software Update Manager

Answer(s): D

Explanation:

Migrate an SAP platform to Azure
DMO: DMO uses one tool to upgrade an SAP workload and a database migration to the SAP HANA database, and this process is often called a one-step migration. The SAP Software Update Manager tool creates a shadow repository for the current database while creating a target database simultaneously. It eventually copies the shadow repository and switches the SAP database connection to the target database. This approach is commonly used when the following data points are observed in the migration plan:
The current OS or DBMS isn't supported in Azure, requiring an upgrade or replatform.
*-> There's a plan to upgrade to SAP S/4HANA during migration.
Note: Software Update Manager
The Software Update Manager (SUM) can be used for several scenarios or use cases.
Database Migration
A database migration transfers the SAP system from one database type to another. The Software Update Manager offers the Database Migration Option (DMO), which is the combination of the SAP software update with the database migration.
DMO was initially a procedure to migrate to an SAP HANA database only. At this time, only the combination of upgrade and migration was possible, since typically the source system was not yet on a software level that is
supported by SAP HANA database. Now, DMO allows for migration to other database types than SAP HANA database (see respective SAP note for details and restrictions) and DMO can be used for a pure migration, without changing the SAP software level: DMO without System Change. In addition, it is possible to change not only the database (host), but also the Application Server: DMO with System Move.
Incorrect:
* Azure Migrate
Azure Migrate features tools that can migrate most platforms and workloads, but SAP workloads require different tools and processes to replicate and deploy their assets. Once the core platform is deployed, standard processes and tools help dependent workloads to resume and finish migrating.
Note: Azure Migrate is a Microsoft service that helps an enterprise assess how its on-premises workloads will perform, and how much they will cost to host, in the Azure public cloud.
An enterprise can use Azure Migrate to discover information about the VMware VMs running within its own data center, including CPU and memory usage, as well as performance history.
* Azure Database Migration Service
Azure Database Migration Service enables seamless migrations from multiple database sources to Azure Data platforms with minimal downtime. The service uses the Data Migration Assistant to generate assessment reports that provide recommendations to guide you through the changes required before performing a migration. When you're ready to begin the migration process, Azure Database Migration Service performs all the required steps.
* SAP Software Provisioning Manager
Software Provisioning Manager offers the execution of many system provisioning tasks and covers a broad range of platforms and products, both on the ABAP and the Java technology.
Classical migration: The SAP Software Provisioning Manager is a software logistics tool for database migrations. Classical migration uses a homogeneous or heterogenous system copy approach, sometimes called a two-step migration. This approach is commonly used when the following observations surface in the migration plan:
The operating systems (OS) and DBMS are compatible with Azure.
There aren't other requirements to upgrade or replatform the OS or DBMS systems.






Post your Comments and Discuss Microsoft AZ-120 exam prep with other Community members:

Join the AZ-120 Discussion