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

YES

YES

NO

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:

https://blogs.sap.com/2017/10/05/your-sap-on-azure-part-2-dmo-with-system-move/

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

References:

https://azure.microsoft.com/en-us/pricing/details/virtual-machines/rhel- sap-hana/

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:

https://www.suse.com/media/guide/sap_hana_on_azure_101.pdf

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:

https://www.sap.com/products/loadrunner.html

https://help.sap.com/viewer/f2ad7797884249eeb2e91dc26a991196/3.0.3.0/en-US

When you set up disaster recovery for on-premises VMware VMs, Site Recovery needs access to the vCenter

Server/vSphere host so that the Site Recovery process server can automatically discover VMs, and fail them

over as needed. By default the process server runs on the Site Recovery configuration server. Add an account

for the configuration server to connect to the vCenter Server/vSphere host.

References:

https://docs.microsoft .com/en-us/azure/site-recovery/vmware-azure-manage-vcenter

Box 1: Yes

The SAP Azure Enhanced Monitoring Extension builds on top of the Azure Diagnostic extension, which stores its data in an Azure Storage account that you specify.

Box 2: Yes

The Set-AzVMAEMExtension cmdlet updates the configuration of a virtual machine to enable or update the support for monitoring for SAP systems that are installed on the virtual machine. The cmdlet installs the Azure Enhanced Monitoring (AEM) extension that collects the performance data and makes it discoverable for the SAP system.

The -OSType specifies the OS. Either Windows or Linux.

Box 3: Yes

References:

https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostics-extension-overview

https://docs.microsoft.com/en-us/powershell/module/az.com pute/set-azvmaemextension

Box 1: Yes

Box 2: Yes

AAP application server to database server latency can be tested with ABAPMeter report /SSA/CAT.

Box 3: Yes

To analyze network issue or measure network metrics you can test the connection using SAP's NIPING program. You can use NIPING to analyze the network connection between any two machines running SAP software.

Box 1: No

Box 2: Yes

The minimum SAP HANA certified conditions for the different storage types are:

Azure Premium SSD - /hana/log is required to be cached with Azure Write Accelerator. The /hana/data volume could be placed on Premium SSD without Azure Write Accelerator or on Ultra disk

Box 3: Yes

References:

https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-vm-operations-storage

Graphical user interface, text, application Description automatically generated

Box 1: five minutes

Window Size is 5 minutes.

Box 2: admins action group will be emailed

The admins1 actiongroup will be executed.

Box 1: NO

Box 2: Yes

Box 3: Yes

Be aware that network traffic between two peered Azure virtual networks is subject to transfer costs. Huge data volume that consists of many terabytes is exchanged between the SAP application layer and the DBMS layer. You can accumulate substantial costs if the SAP application layer and DBMS layer are segregated between two peered Azure virtual networks.

References:

https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/dbms_guide_general

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.

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.

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

Get-AzDisk & Primium_LRS

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

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:

https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/sap-hana-cloud-platform- identity-authentication-tutorial

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:

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/p lan-connect-userprincipalname

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

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:

https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs

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:

https://docs.micros oft.com/en-us/azure/architecture/resiliency/recovery-loss-azure-region