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 11 )

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

HOTSPOT (Drag and Drop is not supported)

You have an on-premises SAP ERP Central Component (SAP ECC) deployment on servers that run Windows Server 2016 and have Microsoft SQL Server 2016 installed.

You plan to migrate the deployment to Azure.

You need to identify which migration method and migration option to use. The solution must minimize downtime of the SAP ECC deployment.

What should you identify? 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: SAP Database Migration Option with System Move
In 2013, SAP introduced new procedure called Database Migration Option (part of Software Update Manager), which can help you during the migration to HANA database. It combines Unicode conversion, system update and database migration into a single step which extremely simplified the overall process.



Until SUM SP20, DMO had one disadvantage it didn't allow you to change your Primary Application Server host. If you wanted to move the instance to the new server you had to perform the whole operation as two-step activity:

1. Execute DMO
2. Use Homogeneous system copy to move the system

Software Update Manager is constantly developed and with every new support package SAP is releasing new features (did you know it can send you e-mails?). One of the newest ones is the possibility to move the system to the new server during single DMO execution. But that's not all. We don't even have to update any system component so we focus on the migration process only, which makes it perfect for system migration to cloud platforms.

Incorrect:
* Classical migration: The SAP Software Provisioning Manager is used specifically as a software logistics tool for database migrations. Classical migration uses a heterogenous system copy approach and is 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.

Box 2: Parallel export/import
DATA TRANSFER MODES
Finally, it took around two hours of processing and SUM stopped at HOSTCHANGE_MOVE phase. This is the moment when we start the synchronization of our two systems. We can choose one out of two synchronization options:

Serial mode: when we want to wait until all exports files are created and then move entire content at once.

Parallel mode: when we want to enable the online synchronization. In this scenario, the import and export jobs are running in parallel. The job dmo2sapcloud.sh is running in the background and sending files from the source to the target host.

As there is no need to wait for the complete file export, the parallel mode can be a huge advantage of the System Move process.



You have an on-premises SAP NetWeaver deployment that uses Windows Server 2016 and Microsoft SQL Server 2016.

You need to migrate the deployment to an Azure virtual machine that runs Windows Server 2016 and has Microsoft SQL Server 2019 installed.

Which migration method should you use?

  1. lift-and-shift
  2. Azure Migrate
  3. classical SAP Database Migration Option (DMO)
  4. heterogeneous SAP classical migration

Answer(s): A

Explanation:

Rehost: Often referred to as "lift and shift" migration, this no-code option lets you migrate your existing applications to Azure quickly. Each application is migrated as is, which provides the benefits of the cloud without the risks or costs of making code changes.



DRAG DROP (Drag and Drop is not supported)

You have an on-premises SAP NetWeaver-based ABAP deployment hosted on servers that run Windows Server or Linux.

You plan to migrate the deployment to Azure.

What will invalidate the existing NetWeaver ABAP licenses for each operating system once the servers are migrated to Azure? To answer, drag the appropriate actions to the correct operating systems. Each action may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.

NOTE: Each correct selection is worth one point.

Select and Place:


  1. See Explanation for the Answer.

Answer(s): A

Explanation:



Box 1: Deleting the Azure virtual machine and recreating a new virtual machine that uses the same disks Box 2: Changing the hostname assigned to the operating system Windows Server:
SAP Hardware Key Input Parameters in an On-Premises Environment In the physical and virtual environments , the SAP hardware key is using the following input parameters:
On Windows
Windows Computer SID (Secure ID)
(local) hostname

On Linux:

The MAC address of the first valid network card

It is important to mention that any change of HW key input parameters will cause an existing valid SAP license to become invalid.

For example, a valid license will become invalid if you change Windows local host name, or you do a sysprep (which will generate new Windows computer SID) where your SAP ASCS/SCS instance is running. Similarly, the same will happen on Linux if you exchange the network card, or you change the order of multiple network cards.

Incorrect:
* Deallocating the Azure virtual machine

Box 3: Replacing the primary NIC

Linux:

Note: Role of an SAP Hardware (HW) Key
Every SAP NetWeaver ABAP or Java system needs a valid SAP license. Customers will generate an SAP license on SAP Service Marketplace, by providing different input values like the SAP product name, SAP SID, DBMS and last but not least, an SAP Hardware (HW) key.

SAP Hardware Key Input Parameters in an Azure Cloud

For the SAP systems in Azure, input parameters used for calculation of the hardware key is changed in the following way:

On Windows

Windows Computer SID
(local) hostname
Azure VM Unique ID

On Linux:

Azure VM Unique ID

On Windows, we got a new input parameter (Azure VM Unique ID), in addition to two existing ones e.g.
Windows Computer SID and hostname.

On Linux, the first valid NIC MAC address is replaced with Azure VM Unique ID.



You have an Azure subscription that contains two SAP HANA on Azure (Large Instances) deployments named HLI1 and HLI2. HLI1 is deployed to the East US Azure region. HLI2 is deployed to the West US 2 Azure region.

You need to minimize network latency for inter-region communication between HLI1 and HLI2.

What should you implement?

  1. a NAT gateway
  2. IP routing tables
  3. ExpressRoute FastPath
  4. ExpressRoute Global Reach

Answer(s): D

Explanation:

ExpressRoute Global Reach SAP HANA on Azure (Large Instances) for inter-region communication With ExpressRoute Global Reach, you can link ExpressRoute circuits together to make a private network between your on-premises networks.
Use case
ExpressRoute Global Reach is designed to complement your service provider's WAN implementation and connect your branch offices across the world. For example, if your service provider primarily operates in the United States and has linked all of your branches in the U.S., but the service provider doesn't operate in Japan and Hong Kong Special Administrative Region, with ExpressRoute Global Reach you can work with a local service provider and Microsoft to connect your branches there to the ones in the U.S. using ExpressRoute and
our global network.
Note: If SAP HANA on Azure (Large Instances) is deployed in multiple Azure regions, a separate tenant is deployed in the HANA Large Instance stamp. You can run both under the same Azure subscription provided these instances are part of the same SAP landscape.
Incorrect:
Not C: FastPath is designed to improve the data path performance between your on-premises network and your virtual network. When enabled, FastPath sends network traffic directly to virtual machines in the virtual network, bypassing the gateway.



HOTSPOT (Drag and Drop is not supported)

You have an on-premises SAP landscape that uses DB2 databases and contains an SAP Financial Accounting (SAP FIN) deployment. The deployment contains a file share that stores 50 GB of bitmap files.

You plan to migrate the on-premises SAP landscape to SAP HANA on Azure and store the images on Azure Files shares. The solution must meet the following requirements:

Minimize costs.

Minimize downtime.

Minimize administrative effort.

You need to recommend a migration solution.

What should you recommend using to migrate the databases and to check the images? 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: SAP Database Option (DMO) with System Move

Database Migration Option (DMO)
DMO of Software Update Manager (SUM) in a nutshell

SUM does not only offer to update software components, but can also execute a database migration (for ABAP based systems)
DMO is the combination of software update with the database migration To only migrate the database (without software update), the approach "DMO without system update" can be used
The standard DMO is an inplace-procedure, as it keeps the Application Server level unchanged, only changes the database (host)
To combine the database migration with a move of the system to a different environment, "DMO with system move" can be used
Specifically for the conversion to SAP S/4HANA, DMOVE2S4 can be used as alternative for "DMO with system move"
DMO allows an easy reset of the procedure at any point in time DMO allows migration to SAP HANA DB, and (depending on scenario) to other database types as well SUM 1.0 (for target systems based on SAP BASIS 7.40 and lower) allows to execute a Unicode conversion as part of the migration

Incorrect:
* 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.

* Data Migration Assistant (DMA)
The Data Migration Assistant (DMA) helps you upgrade to a modern data platform by detecting compatibility issues that can impact database functionality in your new version of SQL Server or Azure SQL Database.

Note: With Microsoft Azure, you can migrate your existing SAP application running on IBM Db2 for Linux, UNIX, and Windows (LUW) to Azure virtual machines. With SAP on IBM Db2 for LUW, administrators and developers

can still use the same development and administration tools, which are available on-premises.

Box 2: AzCopy
The size of the files, 50 GB, makes it suitable for AzCopy rather than for Databox.

Use AzCopy from a Windows or Linux command line to easily copy data to and from Blob Storage, Azure File Storage, and Azure Table Storage with optimal performance. AzCopy supports concurrency and parallelism, and the ability to resume copy operations when interrupted. You can also use AzCopy to copy data from AWS to Azure. For programmatic access, the Microsoft Azure Storage Data Movement Library is the core framework that powers AzCopy. It's provided as a .NET Core library.

Incorrect:
* Azure Migrate
The Azure Migrate: Discovery and assessment tool discovers and assesses on-premises VMware VMs, Hyper- V VMs, and physical servers for migration to Azure. Here's what the tool does: Azure readiness: Assesses whether on-premises servers, SQL Servers and web apps are ready for migration to Azure.

* Azure Data Box
The Microsoft Azure Data Box cloud solution lets you send terabytes of data into and out of Azure in a quick, inexpensive, and reliable way. The secure data transfer is accelerated by shipping you a proprietary Data Box storage device. Each storage device has a maximum usable storage capacity of 80 TB and is transported to your datacenter through a regional carrier. The device has a rugged casing to protect and secure data during the transit.

You can order the Data Box device via the Azure portal to import or export data from Azure. Once the device is received, you can quickly set it up using the local web UI. Depending on whether you will import or export data, copy the data from your servers to the device or from the device to your servers, and ship the device back to Azure. If importing data to Azure, in the Azure datacenter, your data is automatically uploaded from the device to Azure. The entire process is tracked end-to-end by the Data Box service in the Azure portal.

Use cases
Data Box is ideally suited to transfer data sizes larger than 40 TBs in scenarios with no to limited network connectivity. The data movement can be one-time, periodic, or an initial bulk data transfer followed by periodic transfers.






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

Join the AZ-120 Discussion