Microsoft AZ-120 Planning and Administering Microsoft Azure for SAP Workloads Exam Practice Test

YES

YES

NO

Scenario: Increase the performance of SAP ECC applications by moving to SAP HANA.

References:

sap-hana/

The SAP Database Migration Option (DMO) with System Move option of SUM, used as part of the migration allows customer the options to perform the migration in a single step, from source system on-premises, or to the target system residing in Microsoft Azure, minimizing overall downtime.

References:

In a Hybrid-IT scenario, Active Directory from on-premises can be extended to serve as the

authentication mechanism through an Azure deployed domain controller (as well as potentially using the integrated DNS).

It is important to distinguish between traditional Active Directory Servers and Microsoft Azure Active Directory that provides only a subset of the traditional on-premises AD offering. This subset include Identity and Access Management, but does not have the full AD schema or services that many 3rd party application take advantage of. While Azure Active Directory IS a requirement to establish authentication for the Azure virtual machines in use, and it can synchronize users with customers’ on-premises AD, the two are explicitly different and customers will likely continue to require full Active Directory servers deployed in Microsoft Azure.

References:

Scenario: Upgrade and migrate SAP ECC to SAP Business Suite on HANA Enhancement Pack 8.

With the SAP LoadRunner application by Micro Focus, you can accelerate testing and development, reduce slowdowns and expenses, and gain a better understanding of performance issues. Validate software performance, virtualize your network, simulate workloads, benchmark production system performance, and optimize your deployment of SAP HANA software

References:

• A public internet user can reach the SAP Web-Dispatcher over port 443
• The SAP Web-Dispatcher can reach the SAP Application server over port 443
• The App Subnet accepts traffic on port 443 from 10.0.0.0/24
• The SAP Application server sends traffic on port 30015 to the SAP DB server
• The DB subnet accepts traffic on port 30015 from 10.0.1.0/24.
• Public Internet Access is blocked on both App Subnet and DB Subnet.

References:

Graphical user interface, text, application, email Description automatically generated

Box 1: Yes

The following is a quick checklist of storage configuration best practices for running your SQL Server on Azure VM:

• Place data, log, and tempdb files on separate drives.

Box 2: Yes

Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, greatly improving its networking performance. This high-performance path bypasses the host from the data path, which reduces latency, jitter, and CPU utilization for the most demanding network workloads on supported VM types.

Box 3: No

Note: The maximum transmission unit (MTU) is the largest size frame (packet), specified in bytes, that can be sent over a network interface. The MTU is a configurable setting. The default MTU used on Azure VMs, and the default setting on most network devices globally, is 1,500 bytes.

Graphical user interface, text Description automatically generated with medium confidence

Box 1: A proximity placement group

Azure offers proximity placement groups. Proximity placement groups can be used to force grouping of different VM types into a single Azure datacenter to optimize the network latency between these different VM types to the best possible. In the process of deploying the first VM into such a proximity placement group, the VM gets bound to a specific datacenter.

Note: SAP applications based on the SAP NetWeaver or SAP S/4HANA architecture are sensitive to network latency between the SAP application tier and the SAP database tier. This sensitivity is the result of most of the business logic running in the application layer. Because the SAP application layer runs the business logic, it issues queries to the database tier at a high frequency, at a rate of thousands or tens of thousands per second. In most cases, the nature of these queries is simple. They can often be run on the database tier in 500 microseconds or less.

Box 2: Enable Accelerated Networking

To further reduce network latency between Azure VMs, we recommend that you choose Azure Accelerated Networking. Use it when you deploy Azure VMs for an SAP workload, especially for the SAP application layer and the SAP DBMS layer.

Box 3: Network Performance Monitor

Network Performance Monitor (NPM) - a cloud-based network monitoring solution for cloud-only, on-premises, and hybrid networking environments.

Network Performance Monitor offers three broad capabilities:

• Performance Monitor: You can monitor network connectivity across cloud deployments and on-premises locations, multiple data centers, and branch offices and mission-critical multitier applications or microservices. With Performance Monitor, you can detect network issues before users complain.
• Service Connectivity Monitor
• ExpressRoute Monitor

Note 2: Azure Monitor for SAP Solutions is an Azure-native monitoring product for anyone running their SAP landscapes on Azure. It works with both SAP on Azure Virtual Machines and SAP on Azure Large Instances.

We need upgrade to SAP NetWeaver 7.4 before the migration. Then Azure Site Recovery is used for the migration to Azure.

Box 1: No

You can't use an Azure Basic Load Balancer to create failover cluster solutions based on Windows Server Failover Clustering or Linux Pacemaker. Instead, you need to use the Azure Standard Load Balancer SKU.

Box 2: Yes

Azure Availability Zones is one of the high-availability features that Azure provides. Using Availability Zones improves the overall availability of SAP workloads on Azure.

The SAP application layer is deployed across one Azure availability set. For high availability of SAP Central Services, you can deploy two VMs in a separate availability set.

Box 3: Yes

You must use Azure Managed Disks when you deploy to Azure Availability Zones.

ST06 is a transaction code used for Operating System Monitor in SAP.

SAP transaction ST06 (Operating System Monitor) is classified in the Basis Component module under application component Operating System Monitors and runs Monitoring Operating System program RSHOST05 upon execution.

g-for-performance-and-scalability/

"For existing on-premises systems, you should reference system configuration and resource utilization data. The system utilization information is collected by the SAP OS Collector and can be reported via SAP transaction OS07N as well as the EarlyWatch Alert. "

The SAP HANA cockpit provides a single point of access to a range of SAP HANA administration and monitoring tasks. It is used to monitor and ensure the overall health of the system.

The HANA Monitoring dashboard also visualizes key HANA Metrics of SAP HANA system.

References:

tutorials.com/p/hana-monitoring-dashboard.html

Table Description automatically generated with low confidence

Box 1: 4

Scenario: the Azure Resource Manager template that will be used to provision the production application servers.

Ensure that each production application server has four 1-TB data disks.

Box 2: Standard_LRS

Scenario: Minimize costs whenever possible.

Box 3: contoso.onmicrosoft.com

The network contains an on-premises Active Directory domain named ad.contoso.com.

The Initial domain: The default domain (onmicrosoft.com) in the Azure AD Tenant. For example, contoso.onmicrosoft.com.

References:

lan-connect-userprincipalname

Box 1: Yes

Scenario: Technical requirements: Ensure that an application server can be restored from a backup created during the last five days within 15 minutes.

Instant Restore has 'The instance recovery snapshot(s) for 5 Day(s)'.

Box 2: No

Scenario: Ensure that all the production application servers can restore daily backups from the last 21 days.

The Retention of daily backup point is set to for 14 days only.

Box 3: Yes

Box 1: No

SAP HANA Replication consists of one primary node and at least one secondary node. Changes to the data on the primary node are replicated to the secondary node synchronously or asynchronously.

‎

Box 2: No

Since SPS11 SAP HANA system replication can be run in two different operation

modes:

delta_datashipping

logreplay

Box 3: Yes

AD connect, it's not mandatory to have AD FS, you can use Password HAsh Synch or Passthrough Authentication, but AD Connect is mandatory to synch you on-promises accounts to Azure AD

References:

identity-authentication-tutorial

ExpressRoute circuits are configured to allow you to burst up to two times the bandwidth limit you procured for no additional cost.

Scenario: It is estimated that during the migration, the bandwidth required between Azure and the New York office will be 1 Gbps. After the migration, a traffic burst of up to 3 Gbps will occur.

References:

Get-AzDisk & Primium_LRS

m/en-us/powershell/module/az.compute/get-azvmimage?view=azps-4.6.1 microsoft.com/en-us/powershell/module/az.compute/get-azdisk?view=azps-4.6.1

Scenario: Ensure that all the production databases can withstand the failure of an Azure region.

Note: Use Azure Site Recovery to replicate applications across regions. Azure Site Recovery replicates workloads running on physical and virtual machines from a primary site (either on-premises or in Azure) to a secondary location (in Azure). When an outage occurs at the customer's primary site, a failover can be triggered to quickly return the customer to an operational state. After the primary location is restored, customers can then fail back.

References:

oft.com/en-us/azure/architecture/resiliency/recovery-loss-azure-region