AZ-120 Questions and Answers

https://github.com/MicrosoftDocs/azure-docs/issues/32537

https://azure.microsoft.com/en-us/blog/ vnet-peering-and-vpn-gateways/

To create a swap file in the directory that's defined by the ResourceDisk.MountPoint parameter, you can update the /etc/waagent.conf file by setting the following three parameters:

ResourceDisk.Format=y

ResourceDisk.EnableSwap=y

ResourceDisk.SwapSizeMB=xx

References:

https://support.microsoft.com/en-us/help/4010058/how-to-add-a-swap-file-in-linux-azure-virtual-machines

https://docs.microsoft.com/en-us/azure/load-balancer /load-balancer-standard-availability-zones

Table Description automatically generated

Step 1: Create and configure an enterprise application in the Azure AD tentant

To configure the integration of SAP Cloud Platform Identity Authentication into Azure AD, you need to add SAP Cloud Platform Identity Authentication from the gallery to your list of managed SaaS apps.

Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.

On the left navigation pane, select the Azure Active Directory service.

Navigate to Enterprise Applications and then select All Applications.

To add new application, select New application.

In the Add from the gallery section, type SAP Cloud Platform Identity Authentication in the search box.

Select SAP Cloud Platform Identity Authentication from results panel and then add the app. Wait a few seconds while the app is added to your tenant.

Graphical user interface, text, application Description automatically generated

Step 2: Download the single sign-on (SSO) metadata from the Azure AD tenant.

Download single sign-on metadata from Azure Active Directory.

Step 3: Create and configure a corporate identity provider.

Create corporate identity provider.

Step 4: Download the SAP Cloud Platform Identity Authentication Service tenant metadata.

Download Identity Authentication service tenant metadata.

Step 5: Upload the SAP Cloud Platform Identity Authentication Service tenant metadata to Azure AD tenant.

Upload Identity Authentication service tenant metadata to Azure Active Directory.

You have already uploaded the metadata file from Azure Active Directory to Identity Authentication service. It’s time to do it the other way round now and upload the metadata of Identity Authentication service to Azure Active Directory.

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.

Graphical user interface, application, table Description automatically generated

Box 1: User2

Graphical user interface, application, table Description automatically generated

Note:

Backup Contributor - This role has all permissions to create and manage backup except deleting Recovery Services vault and giving access to others. Imagine this role as admin of backup management who can do every backup management operation.

Box 2: User3

The User Access Administrator role lets you manage user access to Azure resources.

Box 1: Azure Site Recovery

Microsoft Azure Site Recovery (ASR) now supports SUSE Linux Enterprise Server 11 SP3/SP4 and SUSE Linux Enterprise Server 12 SP1/SP2/SP3. This is great for customers that are planning to migrate systems to Microsoft Azure or customers who need to have a business continuity strategy for their Azure deployments.

Azure Site Recovery enables SUSE customers to migrate their non-Azure virtual machines or physical servers to Microsoft Azure virtual machines.

Box 2: SAP Hana System replication

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.

E: The network latency across Availability Zones is not the same in all Azure regions. In some cases, you can deploy and run the SAP application layer across different zones because the network latency from one zone to the active DBMS VM is acceptable. But in some Azure regions, the latency between the active DBMS VM and the SAP application instance, when deployed in different zones, might not be acceptable for SAP business processes.

References:

https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/sap-ha-availability-zones

https://blogs.sap.com/2018/08/31/overview-of-backint-for-sap-hana-and-faq-for-3rd-party-backup-tool-support/

https://documentation.commvault.com/commvault/v11_sp16/article?p=114414.htm

Box 1: Yes

Box 2: Yes

The SAP Azure Enhanced Monitoring Extension allows for collecting diagnostic data including OS and Application performance counters from Azure VMs running SAP workloads.

Box 3: No

References:

http:// www.deployazure.com/compute/vir tual-machines/sap-azure-enhanced-monitoring-extension/

https://docs.microsoft.com/en-us/azure/virtual-machines/wor kloads/sap/azure-monitor-overview

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

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: 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

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

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: 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

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/

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

YES

YES

NO

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

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