Planning and Administering Microsoft Azure for SAP Workloads (AZ-120) — Free Practice Questions
10 free sample questions from a bank of 324, with the correct answers and explanations. No signup required — start practising right now.
1You are migrating SAP to Azure. The ASCS application servers are in one Azure zone, and the SAP database server in in a different Azure zone. ASCS/ERS is
configured for high availability.
During performance testing, you discover increased response times in Azure, even though the Azure environment has better computer and memory configurations
than the on-premises environment.
During the initial analysis, you discover an increased wait time for Enqueue.
What are three possible causes of the increased wait time? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
a missing Enqueue profile
disk I/O during Enqueue backup operations
misconfigured load balancer rules and health check probes for Enqueue and ASCS
active Enqueue replication
network latency between the database server and the SAP application servers
Answer: B, D, E
The short version
BDE — Cross-zone Enqueue delay comes from I/O, replication, and network. Split ASCS and database across zones adds latency and overhead that directly inflates Enqueue wait time despite larger VMs.
Key concepts in this question
Enqueue service: central lock manager for SAP, highly sensitive to response time because every transaction waits on locks
Zone separation: places application and database in different fault domains, adding network round trips to lock and DB calls
Enqueue replication and backup I/O: extra writes and disk activity contend with lock processing
Load balancer probes: distribute traffic but do not themselves create Enqueue queueing when misconfigured in this pattern
Why BDE is correct
Disk I/O during backup stalls the Enqueue work process while it waits on storage, active replication doubles write work for high-availability sync, and cross-zone network latency stretches every DB and lock call. Together they explain why better CPU and memory still show slow response with high Enqueue waits. Microsoft and SAP guidance therefore co-locates ASCS with the database and isolates Enqueue performance factors first.
Why the others are wrong
A. a missing profile would prevent startup rather than cause gradual wait inflation under load
C. faulty LB rules affect connection distribution, not core Enqueue lock service time in this layout
AZ-120 exam tip
For Enqueue waits with split zones, remember I-R-N: I/O backup, Replication active, Network cross-zone latency.
2You have an on-premises SAP environment that uses AIX servers and IBM DB2 as the database platform.
You plan to migrate SAP to Azure. In Azure, the SAP workloads will use Windows Server and Microsoft SQL Server as the database platform.
What should you use to export from DB2 and import the data to SQL Server?
R3load
Azure SQL Data Warehouse
SQL Server Management Studio (SSMS)
R3trans
Answer: C
The short version
C — Use SSMS for heterogeneous DB2 to SQL Server move. SQL Server Management Studio provides export, import, and migration assistance suited to moving data into SQL Server on Azure.
Key concepts in this question
Heterogeneous migration: AIX plus DB2 to Windows plus SQL Server changes both OS and DBMS, requiring data-level export and import
SSMS tooling: hosts Import and Export Wizard and migration helpers for loading SQL Server targets
R3load and R3trans: SAP homogeneous and kernel tools for same-DB moves or transports, not cross-DBMS conversion
SQL Data Warehouse: an analytics target, not an export utility from DB2
Why C is correct
Moving from DB2 to SQL Server needs a SQL Server-side ingestion path that understands the target schema and bulk load. SSMS supplies that path for export files into SQL Server before SAP application import steps. That matches the settled key for this platform-shift scenario to Azure with SQL Server retained.
Why the others are wrong
A. serves homogeneous SAP copies within the same DBMS family, not DB2 to SQL Server conversion
B. is a data-warehouse service for analytics, not a DB2 extraction tool
D. moves transports and performs reloads within compatible environments, not cross-vendor migration
AZ-120 exam tip
Changing DBMS vendor toward SQL Server points to Microsoft ingestion tooling: think SSMS Import and Export when DB2 must land in SQL Server.
3Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You plan to migrate an SAP HANA instance to Azure.
You need to gather CPU metrics from the last 24 hours from the instance.
Solution: You query views from SAP HANA Studio.
Does this meet the goal?
Yes
No
Answer: B
The short version
B — Querying HANA Studio views alone does not meet the 24-hour goal. The task needs CPU metrics from the last 24 hours for Azure migration sizing, which demands retained history rather than a live snapshot. HANA Studio views show current system state, while daily trending needs persisted snapshots from DBA Cockpit or HANA cockpit monitoring. The bare Studio query therefore cannot prove coverage of the full window.
Key concepts in this question
HANA Studio views: Expose live threads, sessions, and host counters, useful for immediate diagnosis but not a daily archive.
History need: Sizing requires a full daily cycle to capture peaks and batch windows, not one point in time.
Cockpit stores: DBA Cockpit and HANA cockpit persist CPU and wait snapshots selectable by time window.
Migration impact: Missing overnight peaks would undersize the Azure target, so the method must provably span 24 hours.
Why B is correct
Querying Studio views without pointing at a history store returns current counters rather than a 24-hour CPU series. Overnight or batch peaks could be missed entirely, so the goal explicitly demanding the last 24 hours is unmet. A passing method would name the retained source or cockpit dashboard that holds timestamped samples, which this proposal omits.
Why the others are wrong
A. claims the bare query suffices, overstating live views as a historical source and ignoring the retention gap.
AZ-120 exam tip
Link 24-hour CPU history to cockpit retention, never to a live Studio snapshot alone.
4Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You plan to migrate an SAP HANA instance to Azure.
You need to gather CPU metrics from the last 24 hours from the instance.
Solution: You run SAP HANA Quick Sizer.
Does this meet the goal?
Yes
No
Answer: B
The short version
B — Quick Sizer cannot retrieve observed 24-hour CPU metrics. Quick Sizer estimates future HANA sizing from business inputs such as users, throughput, and data volume. It never reads host CPU counters from a running instance and has no access to the last day of telemetry. It serves planning, not observational measurement, so it cannot answer a gather-past-metrics goal.
Key concepts in this question
Quick Sizer role: Produces memory, CPU, and IOPS recommendations for a planned deployment from questionnaire data.
Observed versus modelled: This series asks for measured host CPU, fundamentally different from projected requirements.
True history sources: DBA Cockpit, HANA cockpit, and OS monitors retain timestamped CPU samples for such windows.
Series logic: Each row tests one solution alone, so a sizing calculator fails even though useful elsewhere.
Why B is correct
Running Quick Sizer yields a forward sizing report, never a query of source-host CPU over the last 24 hours. Because the goal requires observed metrics, an estimator outputting projected needs cannot satisfy it regardless of input care. The settled verdict follows the tool scope and rejects it for this task.
Why the others are wrong
A. claims Quick Sizer meets the goal, confusing capacity estimation with historical retrieval.
AZ-120 exam tip
Remember Quick Sizer equals future sizing, cockpit equals past performance.
5Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You plan to migrate an SAP HANA instance to Azure.
You need to gather CPU metrics from the last 24 hours from the instance.
Solution: You use DBA Cockpit from SAP GUI.
Does this meet the goal?
Yes
No
Answer: A
The short version
A — DBA Cockpit from SAP GUI covers the 24-hour CPU goal. DBA Cockpit aggregates database performance collectors and alert history for managed HANA systems. Its monitors retain CPU, memory, and wait snapshots filterable to the last 24 hours, directly answering the migration question. Cited cockpit dashboard references corroborate this as a documented history source.
Key concepts in this question
DBA Cockpit: Launched from SAP GUI, it surfaces workload snapshots and performance trends for ABAP and HANA.
Persistence: Background collectors store periodic CPU samples, enabling trend views beyond live values.
Cockpit parity: HANA cockpit offers similar dashboards, while this row tests the GUI DBA Cockpit path.
Sizing value: A full day of CPU supports Azure VM selection and validates fit for observed peaks.
Why A is correct
Using DBA Cockpit places the operator over the retained performance warehouse rather than a transient view. Opening CPU history and setting the window to the last 24 hours yields the samples needed for sizing, satisfying every element of the goal. That workflow plus the cited monitoring references makes the affirmative verdict well supported.
Why the others are wrong
B. claims failure, ignoring persisted collectors and contradicting the monitoring references showing CPU trending.
AZ-120 exam tip
Link DBA Cockpit plus 24 hours to Yes, and live-only queries to No.
6You have an SAP environment that is managed by using VMware vCenter.
You plan to migrate the SAP environment to Azure.
You need to gather information to identify which compute resources are required in Azure.
What should you use to gather the information?
Azure Migrate and SAP EarlyWatch Alert reports
Azure Site Recovery and SAP Quick Sizer
SAP Quick Sizer and SAP HANA system replication
Azure Site Recovery Deployment Planner and SAP HANA Cockpit
Answer: A
The short version
A — Combine Azure Migrate with EarlyWatch Alert. One shows current VMware utilization, the other shows SAP-specific load, together enabling right-sized Azure compute.
Key concepts in this question
Azure Migrate: discovers vCenter VMs and reports CPU, memory, disk, and network utilization for target sizing
EarlyWatch Alert: SAP report with dialog, background, and resource load essential for SAPS-based sizing
Site Recovery: replicates VMs for migration execution, not for initial assessment and sizing
Quick Sizer and HANA tools: scope narrow HANA or greenfield sizing, not full vCenter landscape discovery
Why A is correct
Sizing for Azure needs both infrastructure reality from vCenter and SAP workload truth from inside SAP. Azure Migrate gathers the former while EarlyWatch Alert provides hardware capacity and performance history for SAP. Microsoft migration methodology explicitly pairs them before choosing VM SKUs.
Why the others are wrong
B. executes replication but lacks SAP workload analysis for sizing decisions
C. covers HANA replication and quick estimates without vCenter utilization discovery
D. blends deployment planning with HANA Cockpit monitoring, missing full compute assessment
AZ-120 exam tip
Need to gather info to size from VMware plus SAP: answer is Azure Migrate plus EarlyWatch Alert, not a replication or HANA-only tool.
7You plan to migrate an SAP ERP Central Component (SAP ECC) production system to Azure.
You are reviewing the SAP EarlyWatch Alert report for the system.
You need to recommend sizes for the Azure virtual machines that will host the system.
Which two sections of the report should you review? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Hardware Capacity
Patch Levels under SAP Software Configuration
Hardware Configuration under Landscape
Database and ABAP Load Optimization
Data Volume Management
Answer: A, C
The short version
AC — Review capacity and landscape hardware sections. Those two EarlyWatch sections reveal utilization versus installed footprint for ECC sizing on Azure VMs.
Key concepts in this question
Hardware Capacity: CPU, memory, and SAPS consumption trends showing headroom or pressure
Landscape Hardware Configuration: installed hosts, cores, and layout defining what must be replaced in Azure
Patch levels: important for compliance but not for compute sizing math
Load optimization and volume management: tune ABAP and data growth, secondary to raw capacity needs
Why AC is correct
Right-sizing ECC VMs requires knowing both how much power is used and what hardware currently provides it. Capacity quantifies load while configuration inventories the source hosts to map to Azure SKUs. Together they let architects preserve performance without overprovisioning. That pair is the settled sizing source in EarlyWatch.
Why the others are wrong
B. tracks support-package currency, unrelated to VM core and memory math
D. guides SQL and ABAP tuning, not initial Azure host sizing
E. plans archiving and growth, not immediate production VM selection
AZ-120 exam tip
Sizing from EarlyWatch equals Capacity plus Configuration: usage plus installed hardware, never patches or ABAP tuning sections.
8You plan to migrate an SAP environment to Azure.
You need to recommend a solution to migrate the SAP application servers to Azure. The solution must minimize downtime and changes to the environments.
What should you include in the recommendation?
Azure Storage Explorer
Azure Import/Export service
AzCopy
Azure Site Recovery
Answer: D
The short version
D — Azure Site Recovery minimizes downtime for app servers. It replicates running VMs to Azure with orchestrated failover and little rebuild or reconfiguration.
Key concepts in this question
Site Recovery: agent-based replication of VMware or physical servers with recovery plans and test failover
Minimal change goal: lift-and-shift of SAP app servers preserves host identity and installed software
Storage tools: AzCopy, Storage Explorer, and Import-Export move files and blobs, not live server personalities
Downtime control: continuous replication shortens cutover to a brief failover window
Why D is correct
Migrating SAP application servers demands fidelity of OS, SAP binaries, and configuration with a short outage. Site Recovery replicates the whole server continuously and fails over in a coordinated way, avoiding manual rebuild. Microsoft positions it as the low-downtime path for SAP app tiers when database methods differ.
Why the others are wrong
A. browses storage accounts but does not replicate running servers
B. ships offline disks for bulk ingest, incurring long outage and manual rebuild
C. copies blobs and files efficiently yet leaves server OS and SAP stack to reinstall
AZ-120 exam tip
App servers with minimize downtime and changes equals Site Recovery: replicate the machine, not just the files.
9You plan to migrate an on-premises SAP development system to Azure.
Before the migration, you need to check the usage of the source system hardware, such as CPU, memory, network, etc.
Which transaction should you run from SAP GUI?
SM51
DB01
DB12
OS07N
Answer: D
The short version
D — Run OS07N to check OS-level hardware use. That SAP OS monitor shows CPU, memory, paging, and network at the host level before migration.
Key concepts in this question
OS07N: operating-system monitor in SAP GUI reporting host utilization history for sizing
SM51: lists application servers and status, not detailed host resource graphs
DB01 and DB12: focus on database performance and backup logs, not OS CPU and memory
Pre-migration check: needs host counters to pick Azure VM sizes and disks
Why D is correct
The question asks for source-system hardware usage like CPU, memory, and network before moving to Azure. OS07N is the transaction built to display exactly those OS collector counters from SAP. Using it gives the utilization baseline that Azure Migrate later complements. That direct mapping makes D the settled answer. This aligns with Microsoft SAP-on-Azure guidance that pairs utilization data with SAP workload truth for reliable sizing and performance.
Why the others are wrong
A. shows server instances and message types, not host CPU and memory history
B. analyzes exclusive DB wait situations, missing OS-level utilization
C. reviews backup and archiving status, not hardware consumption
AZ-120 exam tip
Hardware use from SAP GUI equals OS07N: OS monitor for CPU and memory, while SM51 lists servers and DB transactions stay in the database.
10Your company has an SAP environment that contains the following components:
✑ SAP systems based on SAP HANA and SAP Adaptive Server Enterprise (SAP ASE) that run on SUSE Linux Enterprise Server 12 (SLES 12)
✑ Multiple SAP applications
The company plans to migrate all the applications to Azure.
You need to get a comprehensive list of all the applications that are part of the SAP environment.
What should you use?
the SAP license information
the SAP Solution Manager
the data volume management report
the network inventory and locations
Answer: B
The short version
B — Use Solution Manager for full application inventory. It discovers managed SAP systems and their components centrally across HANA and ASE on SLES.
Key concepts in this question
Solution Manager: central lifecycle and monitoring hub with system landscape and application inventory
License info: proves entitlements but does not enumerate deployed apps and dependencies reliably
Volume management: reports data growth for archiving, not a catalog of applications
Network inventory: maps IPs and sites, not SAP product instances
Why B is correct
A heterogeneous SAP landscape with multiple apps on HANA and ASE needs a central registry that already tracks managed systems. Solution Manager maintains that landscape data and application list for operations and migration planning. That comprehensive role makes it the right source for all applications before moving to Azure.
Why the others are wrong
A. shows purchased rights, which may differ from what is actually installed and running
C. quantifies table growth for housekeeping, not application presence
D. documents connectivity locations, missing SAP product and version truth
AZ-120 exam tip
Need a complete SAP application list across the estate: pick Solution Manager landscape inventory over licenses, network maps, or data-volume reports.