Amazon
Avaya
Checkpoint
Cisco®
CompTIA
CrowdStrike
EC-Council
EXIN
Fortinet
Google
ISC
ISC2
ITIL®
Juniper
Microsoft
Okta
Palo Alto Networks
Salesforce
All Vendors
  1. Home
  2. Microsoft
  3. AZ-120

Microsoft AZ-120 Exam (page: 6)
Microsoft Planning and Administering Azure for SAP Workloads
Updated on: 25-Dec-2025

Viewing Page 6 of 53
AZ-120 PDF 412 Questions

HOTSPOT (Drag and Drop is not supported)

You have an Azure AD tenant named contoso.com that syncs to an Active Directory domain hosted on an Azure virtual machine.

You plan to deploy an SAP NetWeaver landscape on Azure that will use SUSE Linux Enterprise Server (SLES).

You need to recommend an authentication solution for the following scenarios. The solution must support Azure Multi-Factor Authentication (MFA):

Administrators sign in to SLES Azure virtual machines.

A user signs in to an SAP NetWeaver application.

What should you recommend for each scenario? 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: Azure Active Directory Domain Services (Azure AD DS)
Administrators sign in to SLES Azure virtual machines.

Join a SUSE Linux Enterprise virtual machine to an Azure Active Directory Domain Services managed domain. To let users sign in to virtual machines (VMs) in Azure using a single set of credentials, you can join VMs to an Azure Active Directory Domain Services (Azure AD DS) managed domain. When you join a VM to an Azure AD DS managed domain, user accounts and credentials from the domain can be used to sign in and manage servers. Group memberships from the managed domain are also applied to let you control access to files or services on the VM.

Box 2: Azure AD
A user signs in to an SAP NetWeaver application.

Azure Active Directory Single sign-on (SSO) integration with SAP NetWeaver When you integrate SAP NetWeaver with Azure AD, you can:

Control in Azure AD who has access to SAP NetWeaver.
Enable your users to be automatically signed-in to SAP NetWeaver with their Azure AD accounts. Manage your accounts in one central location - the Azure portal.



HOTSPOT (Drag and Drop is not supported)

You have an on-premises SAP NetWeaver deployment that runs SUSE Linux Enterprise Server (SLES). The deployment contains 200 GB of files used by application servers stored in an NFS share.

You plan to migrate the on-premises deployment to Azure.

You need to implement an NFS storage solution. The solution must meet the following requirements:

Ensure that only the application servers can access the storage.

Support NFS 4.1

Minimize costs.

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: Azure Files
To deploy the SAP NetWeaver application layer, you need shared directories like /sapmnt/SID and /usr/sap/ trans in the environment. Additionally, when deploying an HA SAP system, you need to protect and make highly available file systems like /sapmnt/SID and /usr/sap/SID/ASCS.

Now you can place these file systems on NFS on Azure Files. NFS on Azure Files is an HA storage solution. This solution offers synchronous Zone redundant storage (ZRS) and is suitable for SAP ASCS/ERS instances deployed across Availability Zones. You still need a Pacemaker cluster to protect single point of failure components like SAP Netweaver central services(ASCS/SCS).

Note: Azure Files offers fully managed file shares in the cloud that are accessible via the industry standard Server Message Block (SMB) protocol or Network File System (NFS) protocol. Both NFS and SMB protocols are supported on Azure virtual machines (VMs) running Linux.

Box 2: A private endpoint
Deploy Azure Files storage account and NFS shares
NFS on Azure Files, runs on top of Azure Files Premium storage.

It's recommended to access your Azure Storage account through an Azure Private Endpoint. Make sure to deploy the Azure Files storage account endpoint and the VMs, where you need to mount the NFS shares, in the same Azure VNet or peered Azure VNets.



You have an on-premises SAP NetWeaver landscape that contains an IBM DB2 database.

You need to migrate the database to a Microsoft SQL Server instance on an Azure virtual machine.

Which tool should you use?

  1. Data Migration Assistant
  2. SQL Server Migration Assistant (SSMA)
  3. Azure Migrate
  4. Azure Database Migration Service

Answer(s): B

Explanation:

IBM Db2 Azure Virtual Machines DBMS deployment for SAP workload You can migrate your user databases from IBM Db2 to SQL Server on Azure VM, by using the SQL Server Migration Assistant for Db2.



HOTSPOT (Drag and Drop is not supported)

You plan to migrate an SAP database from Oracle to Microsoft SQL Server by using the SQL Server Migration Assistant (SSMA).

You are configuring a Proof of Concept (PoC) for the database migration. You plan to perform the migration multiple times as part of the PoC.

You need to ensure that you can perform the migrations as quickly as possible. The solution must ensure that all Oracle schemas are migrated.

Which migration method and migration mode should you use? 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: Synchronization
In reference to step 7 below.
After you have converted Oracle schemas to SQL Server, you can load the resulting database objects into SQL Server. You can either have SSMA create the objects, or you can script the objects and run the scripts yourself.

Choosing Between Synchronization and Scripts
If you want to load the converted database objects into SQL Server without modification, you can have SSMA directly create or recreate the database objects. That method is quick and easy, but does not allow for customization of the Transact-SQL code that defines the SQL Server objects, other than stored procedures.

If you want to modify the Transact-SQL that is used to create objects, or if you want more control over objects creation, use SSMA to create scripts. You can then modify those scripts, create each object individually, and even use SQL Server Agent to schedule creating those objects.

Box 2: Default
The Default mode is recommended for most users. The Optimistic mode keeps more of the current Oracle syntax, and is easier to read. However, keeping current syntax might not be accurate. If the Oracle syntax must be converted to equivalent SQL Server syntax, the Full mode performs the most complete conversion, but the resulting code might be more difficult to read. In the Custom mode, you set the options.

Note: Recommended Migration Process (see step 7 below)
To successfully migrate objects and data from Oracle databases to SQL Server, Azure SQL Database, or Azure Synapse Analytics, use the following process:

Create a new SSMA project.

After you create the project, you can set project conversion, migration, and type mapping options. For information about project settings, see Setting Project Options (OracleToSQL). For information about how to customize data type mappings, see Mapping Oracle and SQL Server Data Types (OracleToSQL).

1. Create a new SSMA project.
2. Connect to the Oracle database server.
3. Connect to an instance of SQL Server.
4. Map Oracle database schemas to SQL Server database schemas.
5. Optionally, Create assessment reports to assess database objects for conversion and estimate the conversion time.
6. Convert Oracle database schemas into SQL Server schemas.
7. Load the converted database objects into SQL Server.
You can do this in one of the following ways:
Save a script and run it in SQL Server.
Synchronize the database objects.
8. Migrate data to SQL Server.
9. If necessary, update database applications.



You have an SAP landscape that is hosted on VMWare.

You plan to migrate an existing SAP landscape to Azure by using Azure Migrate.

You need to configure firewall rules to allow access to the Azure Migrate appliance management app.

To which port should you provide access?

  1. 3900
  2. 44368
  3. 44400
  4. 50014

Answer(s): B

Explanation:

Support matrix for VMware discovery
Prerequisites and support requirements for using the Azure Migrate: Discovery and assessment tool to discover and assess servers in a VMware environment for migration to Azure.
Port access requirements
Device: Azure Migrate Appliance
Inbound connections on TCP port 3389 to allow remote desktop connections to the appliance.
Inbound connections on port 44368 to remotely access the appliance management app by using the URL https://<appliance-ip-or-name>:44368.
Outbound connections on port 443 (HTTPS) to send discovery and performance metadata to Azure Migrate.



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.



Viewing Page 6 of 53



Share your comments for Microsoft AZ-120 exam with other users:

patricks 10/24/2023 6:02:00 AM

passed my az-120 certification exam today with 90% marks. studied using the dumps highly recommended to all.
Anonymous