HOTSPOT (Drag and Drop is not supported)You are deploying an SAP environment across Azure Availability Zones. The environment has the following components:ASCS/ERS instances that use a failover clusterSAP application servers across the Azure Availability ZonesDatabase high availability by using a native database solutionFor each of the following statements, select Yes if the statement is true. Otherwise, select No.NOTE: Each correct selection is worth one point.Hot Area:
Answer(s): A
Box 1: NoAzure Availability Zones are physically separate locations within an Azure region protecting customers' applications and data from datacenter-level failures. It is good for applications that require low-latency synchronous replication with protection from datacenter-level failures.Box 2: YesAAP application server to database server latency can be tested with ABAPMeter report /SSA/CAT.Box 3: YesTo 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.
You deploy an SAP environment on Azure.You need to validate the load distribution to the application servers.What should you use?
Answer(s): D
Load balancers. These are used to distribute traffic to virtual machines in the application-tier subnet. For high availability, use the built-in SAP Web Dispatcher, Azure Load Balancer, or network appliances, depending on the traffic type (such as HTTP or SAPGUI) or the required network services, such as Secure Sockets Layer (SSL) termination.
HOTSPOT (Drag and Drop is not supported)You plan to deploy a highly available ASCS instance to SUSE Linux Enterprise Server (SLES) virtual machines in Azure.You are configuring an internal Azure Standard Load Balancer for the ASCS instance.How should you configure the internal Standard Load Balancer? To answer, select the appropriate options in the answer area.NOTE: Each correct selection is worth one point.Hot Area:
Box 1: Client IPThe standard load balancer allows stateful sessions to remain as there are no IP address changes with this method.Box 2: EnabledMake sure to enable Floating IP.
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.You deploy SAP HANA on Azure (Large Instances).You need to back up the SAP HANA database to Azure.Solution: You create a Recovery Services vault and a backup policy.Does this meet the goal?
Backup architectureThe backup process begins by creating a Recovery services vault in Azure. This vault will be used to store the backups and recovery points created over time.The Azure VM running SAP HANA server is registered with the vault, and the databases to be backed-up are discovered. To enable the Azure Backup service to discover databases, a preregistration script must be run on the HANA server as a root user.This script creates AZUREWLBACKUPHANAUSER DB user and a corresponding key with the same name in hdbuserstore. Refer to the setting up permissions section to understand more about what the script does.Azure Backup Service now installs the Azure Backup Plugin for HANA on the registered SAP HANA server.The AZUREWLBACKUPHANAUSER DB user created by the preregistration script is used by the Azure Backup Plugin for HANA to perform all backup and restore operations. If you attempt to configure backup for SAP HANA DBs without running this script, you might receive the following error:UserErrorHanaScriptNotRun.To configure backup on the databases that are discovered, choose the required backup policy and enable backups.Once the backup is configured, Azure Backup service sets up the Backint parameters at the DATABASE level on the protected SAP HANA server.The Azure Backup Plugin for HANA maintains all the backup schedules and policy details. It triggers the scheduled backups and communicates with the HANA Backup Engine through the Backint APIs.The HANA Backup Engine returns a Backint stream with the data to be backed up.All the scheduled backups and on-demand backups (triggered from the Azure portal) that are either full or differential are initiated by the Azure Backup Plugin for HANA. However, log backups are managed and triggered by HANA Backup Engineitself.
https://docs.microsoft.com/en-us/azure/backup/sap-hana-db-about https://docs.microsoft.com/en-us/azure/backup/backup-azure-sap-hana-database#configure-backup
HOTSPOT (Drag and Drop is not supported)For each of the following statements, select Yes if the statement is true. Otherwise, select No.NOTE: Each correct selection is worth one point.Hot Area:
Box 1: NoBox 2: YesThe 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 diskBox 3: Yes
Post your Comments and Discuss Microsoft AZ-120 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-120 content, but please register or login to continue.