AZ-120 Questions and Answers

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/

YES

YES

NO

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/

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

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

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

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

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

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

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

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

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

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