Microsoft AZ-120 Practice Test Questions, Exam Dumps

Practice Exams:

View All

AZ-120 Microsoft Practice Test Questions and Exam Dumps

Question No 1:

You are performing a cloud migration of an SAP landscape to Microsoft Azure. In this deployment, the ASCS (ABAP SAP Central Services) instance is hosted in one Azure Availability Zone, while the SAP database server is located in a different Availability Zone to ensure high availability and fault tolerance. The ASCS/ERS (Enqueue Replication Server) configuration is implemented for redundancy and failover support.

During performance testing after the migration, you observe that application response times are slower in the Azure environment than they were on the previous on-premises infrastructure. This occurs despite having more powerful compute and memory configurations in Azure.

Your initial analysis indicates that Enqueue wait times have increased, which is contributing to the degraded performance.

Considering this scenario, which three factors could be contributing to the increased Enqueue wait times in this Azure-based SAP deployment?

Note: Each correct answer presents a complete and independent cause. Select three answers.

A. A missing Enqueue profile
B. Disk I/O delays during Enqueue backup operations
C. Misconfigured load balancer rules and health probes for Enqueue and ASCS
D. Active Enqueue replication
E. Network latency between the database server and the SAP application servers

Correct Answers:

C. Misconfigured load balancer rules and health check probes for Enqueue and ASCS
D. Active Enqueue replication
E. Network latency between the database server and the SAP application servers

Explanation:

In a high-availability SAP setup on Azure, increased Enqueue wait times can indicate bottlenecks in inter-component communication or incorrect configuration. Here are the likely causes:

1. Misconfigured Load Balancer Rules and Health Probes (Option C):
SAP ASCS uses TCP-based communication for lock management (Enqueue service). In Azure, load balancers (especially in active/passive setups) route traffic to ASCS. If health probes or rules are misconfigured, traffic may intermittently fail to reach the correct instance, causing delayed Enqueue processing and increased wait times.

2. Active Enqueue Replication (Option D):
While Enqueue Replication Server (ERS) ensures failover readiness, constant synchronization between the ASCS and ERS nodes introduces additional overhead. If replication is occurring too frequently or inefficiently across zones, it may delay Enqueue responses due to locking delays or race conditions.

3. Network Latency Across Zones (Option E):
Azure Availability Zones are physically separate data centers within a region. When ASCS and the database server reside in different zones, cross-zone communication introduces network latency. Since ASCS and the database interact frequently for transaction coordination, even slight delays can lead to noticeable performance degradation in Enqueue operations.

Other Options Explained:

A. Missing Enqueue profile: SAP will not start properly if the profile is missing; this is a configuration issue, not a performance-related cause.
B. Disk I/O during backup: Enqueue backups are periodic and not frequent enough to explain consistently increased wait times.

By understanding these root causes, administrators can optimize the placement and configuration of SAP components in Azure to restore expected performance levels.

Question No 2:

Your organization runs an on-premises SAP system hosted on AIX servers with IBM DB2 as the backend database. As part of a cloud modernization strategy, your team plans to migrate the SAP environment to Microsoft Azure. The target architecture on Azure will host the SAP workloads on Windows Server with Microsoft SQL Server as the underlying database.

Given that this migration involves a heterogeneous database platform switch—from IBM DB2 to Microsoft SQL Server—you need to choose the correct tool or process to extract (export) data from the current DB2 database and load (import) it into SQL Server while maintaining SAP compatibility and integrity.

Which tool or process should you use to handle the export from DB2 and import into SQL Server during this SAP migration?

A. R3load
B. Azure SQL Data Warehouse
C. SQL Server Management Studio (SSMS)
D. R3trans

Correct Answer: A. R3load

Explanation

When migrating an SAP system across different database platforms, such as from IBM DB2 to Microsoft SQL Server, you're performing a heterogeneous system copy. SAP provides specialized tools to ensure data integrity and consistency during such operations.

The recommended tool in this scenario is R3load, which is specifically designed for exporting and importing SAP data during system copies, especially in heterogeneous environments.

R3load works by reading the SAP kernel and dictionary structure to export data into platform-independent files. It then reimports this data into the new target database. It is commonly used in combination with the Migration Monitor (MIGMON) or the Software Provisioning Manager (SWPM) to streamline and automate the export/import process.

R3trans is used for transporting objects within the same SAP system and is not suitable for complete database migrations, especially across platforms.
SQL Server Management Studio (SSMS) is a great tool for managing SQL Server databases, but it's not suitable for structured SAP data migrations from non-SQL Server databases.
Azure SQL Data Warehouse (now called Azure Synapse Analytics) is used for big data analytics and is not appropriate for hosting transactional SAP workloads or for structured migrations like this.

Thus, R3load is the most appropriate and SAP-supported tool for performing this kind of database platform migration in an SAP environment.

Question No 3:

You are currently managing an on-premises SAP landscape that runs on a virtualized infrastructure using VMware vCenter. Your organization has decided to transition this SAP environment to Microsoft Azure in order to take advantage of cloud scalability, flexibility, and cost-efficiency.

As part of the migration planning process, it is critical to understand the existing system’s compute utilization—including CPU, memory, and storage—so that you can accurately size equivalent or optimized resources in Azure.

Which tools should you use to collect accurate performance data from your current environment and estimate the appropriate compute sizing requirements in Azure?

A. Azure Migrate and SAP EarlyWatch Alert reports
B. Azure Site Recovery and SAP Quick Sizer
C. SAP Quick Sizer and SAP HANA system replication
D. Azure Site Recovery Deployment Planner and SAP HANA Cockpit

Correct Answer: A. Azure Migrate and SAP EarlyWatch Alert reports

Explanation:

Migrating SAP systems to Azure requires a deep understanding of your existing workload performance and utilization to ensure the cloud environment is properly sized and cost-effective. Two tools are particularly effective for gathering this information: Azure Migrate and SAP EarlyWatch Alert (EWA) reports.

Azure Migrate is a Microsoft tool designed to assess on-premises workloads—including virtual machines running on VMware or Hyper-V. It collects performance metrics like CPU usage, memory utilization, disk IOPS, and network throughput. This data helps determine the right-sized virtual machines in Azure to meet current performance needs while optimizing costs.

On the other hand, SAP EarlyWatch Alert is a service from SAP that provides detailed performance analysis of SAP systems. It gives historical trends and highlights potential performance bottlenecks, capacity planning concerns, and resource usage patterns specific to SAP applications, databases (including HANA), and infrastructure.

Combining Azure Migrate with SAP EWA reports offers both infrastructure-level and application-level insights. Azure Migrate ensures you gather precise compute metrics from the VMware environment, while EWA delivers SAP-specific context that’s crucial for right-sizing and planning.

Incorrect options:

B and D mention Azure Site Recovery tools, which are more focused on disaster recovery and migration execution than planning or sizing.
C suggests SAP Quick Sizer, which is typically used for sizing new SAP installations, not for assessing existing environments. HANA system replication is a high-availability solution, not a sizing tool.

Question No 4:

You are planning to migrate an existing SAP ERP Central Component (SAP ECC) production system to Microsoft Azure. As part of the migration preparation, you are analyzing the SAP EarlyWatch Alert (EWA) report for the system to determine the optimal Azure virtual machine (VM) sizes that will host your SAP workloads.

The EarlyWatch Alert report provides critical insights into the current performance, resource utilization, and configuration of the SAP system. Your goal is to use this data to accurately recommend the appropriate Azure VM sizes to ensure the system runs efficiently in the cloud environment.

Which two specific sections of the SAP EarlyWatch Alert report should you analyze to extract the necessary information for sizing the Azure virtual machines?

Choose TWO correct answers:

A. Hardware Capacity
B. Patch Levels under SAP Software Configuration
C. Hardware Configuration under Landscape
D. Database and ABAP Load Optimization
E. Data Volume Management

Correct Answers:

A. Hardware Capacity
C. Hardware Configuration under Landscape

Explanation:

When migrating SAP ECC systems to Azure, accurate VM sizing is critical to ensure that performance, scalability, and cost-efficiency targets are met. The SAP EarlyWatch Alert (EWA) report is a key tool for this task because it provides detailed insights into system behavior, resource usage, and performance.

1. Hardware Capacity:
This section outlines how much CPU, memory, and storage resources the current system is consuming. It provides peak and average usage statistics that are vital for selecting Azure VM sizes that can accommodate the SAP workload without over-provisioning. This ensures the Azure environment matches or exceeds the on-premises performance.

2. Hardware Configuration under Landscape:
This section details the physical or virtual setup of the current SAP system, including the number of CPUs, memory size, and storage configuration. Understanding the baseline infrastructure setup allows you to map the current hardware to equivalent Azure VMs, taking into account SAP's certification for supported VM types.

Why not the others?

B. Patch Levels under SAP Software Configuration: Relevant for security and maintenance, not for sizing.
D. Database and ABAP Load Optimization: Helps in performance tuning, not direct VM sizing.
E. Data Volume Management: Focuses on storage growth and housekeeping but doesn’t directly help size VMs.

By using the Hardware Capacity and Hardware Configuration sections, you can make data-driven decisions for sizing Azure VMs that align with SAP and Microsoft best practices for cloud deployments.

Question No 5:

You are an IT administrator responsible for managing the migration of your organization's SAP environment to Microsoft Azure. The current SAP application servers are hosted on-premises, and the business has strict requirements to ensure minimal downtime during the migration process. Additionally, the solution must require the least possible modifications to the existing server configurations to avoid reinstallation or significant reengineering.

Given these constraints, which Azure-native service should you recommend for migrating the SAP application servers to Azure while ensuring minimal disruption and configuration changes?

A. Azure Storage Explorer
B. Azure Import/Export service
C. AzCopy
D. Azure Site Recovery

Correct Answer: D. Azure Site Recovery

Explanation:

When migrating SAP application servers to Azure with minimal downtime and configuration changes, Azure Site Recovery (ASR) is the most suitable solution. ASR is a disaster recovery and migration service that replicates on-premises workloads—including physical servers and virtual machines—to Azure. It enables seamless failover to Azure in the event of a planned migration or unplanned outage.

SAP environments are typically mission-critical, and any downtime can significantly impact business operations. Azure Site Recovery minimizes downtime by allowing for real-time replication of workloads. Once replication is complete, a failover to Azure can be performed during a pre-scheduled maintenance window, minimizing impact to users.

Moreover, ASR does not require extensive changes to the existing server configurations. The application servers are migrated “as-is,” preserving the current OS, applications, and settings. This makes it ideal for migrating complex SAP workloads without the need to rebuild or reconfigure the systems.

The other options are not suitable for this type of migration:

Azure Storage Explorer is a tool for managing storage accounts but not for server migration.
Azure Import/Export service is intended for large data transfers using physical disks—not live server migrations.
AzCopy is a command-line utility to copy data to and from Azure Storage, useful for data transfer but not full server migration.

Thus, Azure Site Recovery offers a low-downtime, low-disruption path to migrating SAP application servers to Azure.

Would you like a similar breakdown for migrating SAP HANA databases?

Question No 6:

You are preparing to migrate an on-premises SAP development system to Microsoft Azure as part of your organization's cloud transformation strategy. A key part of the pre-migration analysis involves gathering performance and usage statistics from the current system to size the virtual machines (VMs) and other infrastructure components correctly in Azure.

To do this effectively, you must assess how the current system utilizes key hardware resources, such as CPU usage, memory consumption, network load, and other operating system-level performance metrics.From the SAP GUI,

Which transaction code should you use to perform this detailed analysis of the operating system resource utilization?

Select one correct answer.

A. SM51
B. DB01
C. DB12
D. OS07N

Correct Answer: D. OS07N

Explanation:

Before migrating an SAP system to Azure, it is essential to understand the current workload characteristics to determine the correct size and type of Azure virtual machines, storage, and networking resources. This ensures cost-effective and performance-optimized deployment in the cloud.

The OS07N transaction code in SAP is used to monitor operating system-level statistics directly from the SAP GUI. It provides a real-time and historical overview of various performance metrics, including:

CPU usage (by user, system, and idle time)
Memory utilization
Disk usage
Network load
Swap space and paging activity

This data is collected from the underlying OS agents (SAP Host Agent) and helps system administrators make informed decisions when planning system migrations.

Here's why the other options are incorrect:

A. SM51: Displays information about application servers in the SAP system but does not provide detailed OS-level metrics.
B. DB01: Used to analyze database table locks; it is relevant for performance tuning but not for OS-level resource usage.
C. DB12: Used to monitor database backups and their history—not related to CPU or memory usage.

In contrast, OS07N is the go-to transaction for capturing and reviewing system resource utilization over time, making it the best choice for migration planning.

Using OS07N, you can gather a performance baseline of your current system, which is essential when right-sizing your Azure infrastructure to avoid over-provisioning or performance bottlenecks.

Question No 7:

Your organization is preparing to migrate its existing SAP landscape to Microsoft Azure. The current on-premises SAP environment includes:

SAP systems that use both SAP HANA and SAP Adaptive Server Enterprise (SAP ASE) as databases.
All systems are hosted on SUSE Linux Enterprise Server 12 (SLES 12).
The environment contains multiple SAP applications across different business units.

As part of the initial assessment and planning phase of the migration, your task is to gather a comprehensive and accurate list of all SAP applications currently in use across the environment. This inventory will be used to evaluate migration readiness and design the architecture in Azure.

Which tool should you use to identify and inventory all the SAP applications in the environment?

A. The SAP license information
B. The SAP Solution Manager
C. The data volume management report
D. The network inventory and locations

Correct Answer: B. The SAP Solution Manager

Explanation

SAP Solution Manager is the correct tool to use when you need a comprehensive and system-integrated view of all SAP components and applications within an environment. It is SAP’s centralized application lifecycle management (ALM) platform and provides detailed visibility into the technical and functional landscape of an SAP deployment.

Solution Manager includes features such as Landscape Management Database (LMDB) and System Landscape Directory (SLD), which help track all installed SAP applications, instances, database platforms, versions, patch levels, and interdependencies. These features are essential during migration planning to ensure a complete and accurate inventory of systems and applications.

Other options are not suitable for this task:

A. SAP license information may list licensed products but not actual installed or used applications.
C. Data volume management report is focused on database usage and space management, not application inventory.
D. Network inventory and locations pertain to infrastructure assets, not SAP application discovery.

By using SAP Solution Manager, migration teams can reduce risks, avoid missing components during the move, and plan the Azure architecture more effectively.