Microsoft AZ-120 Practice Test - Questions Answers, Page 10

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.

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

Secondary indexes for very large tables can be removed from the STR file and built ONLINE with scripts after the main portion of the import has finished and post processing tasks such as configuring STMS are occurring.

References: https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/very-large-database-migration-to-azure-8211-recommendations/ba-p/368146

If a customer runs non-SAP systems, the only way of Sizing the required Hardware for SAP HANA is the Quick-Sizer tool. HANA-based Cloud Quick Sizer: Please use this version, if the product that you want to size shall run in the Cloud; e.g. SAP S/4HANA Cloud and SAP Data Warehouse Cloud.

Reference: https://www.sap.com/about/benchmark/sizing.html#quick-sizer

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. Incorrect Answers:

A: Transaction code SM51 is to display list of active application servers that have registered in the SAP message server. B: DB01 is a transaction code used for Analyze Exclusive Lockwaits in SAP.

C: Transaction code DB12 is to collects and presents information that is necessary to monitor database backups.

Reference: https://saptransactions.com/codes/ST06/

For the load balancers of the failover clusters of SAP Central Services and the DBMS layer, you need to use the Standard SKU Azure Load Balancer. The Basic Load Balancer won't work across zones.

Note:

The DBMS also is a single point of contact in an SAP system. You need to protect it by using a high-availability solution. The following figure shows a SQL Server AlwaysOn high-availability solution in Azure, with Windows Server Failover Clustering and the Azure internal load balancer.

Incorrect Answers:

C: Azure Virtual WAN is a networking service that brings many networking, security, and routing functionalities together to provide a single operational interface.

D: Application Proxy is recommended for giving remote users access to internal resources. Application Proxy replaces the need for a VPN or reverse proxy for these remote access use cases.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/sap-high-availability-architecture-scenarios

Step 1: Create a proximity placement group

A proximity placement group is a logical grouping of Azure resources within the same Azure data center in order to reduce latency.

Step 2: Create an Availability Set

Create an availability set that references the Azure proximity group.

By adding the availability sets to proximity placement groups, the network latencies are considerably reduced, thereby improving the overall performance.

Step 3: Deploy SQL Server on Azure Virtual machines

Step 4: Deploy the application tier in the Azure virtual machines

Deploy the application layer VMs by referencing the availability set and the proximity placement group.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/sap-proximity-placement-scenarios

If you want to move an existing deployed system from another relational database management system (RDBMS) to HANA. SAP provides reports to run on your existing SAP system. If the database is moved to HANA, these reports check the data and calculate memory requirements for the HANA instance.

/SDF/HDB_SIZING is a standard Executable ABAP Report available within your SAP system (depending on your version and release level).

ABAP code listing snippet for SAP ABAP Report /SDF/HDB_SIZING

*&-------------------------------*

*& Report /SDF/HDB_SIZING // ZNEWHDB_SIZE

*&

*&-------------------------------*

*& Estimates the memory requirement in HANA of non-HANA databases * *& When run on HANA, size the database using real memory consumption *& values.

*&-------------------------------*

*

*

REPORT /SDF/HDB_SIZING LINE-SIZE 101 LINE-COUNT 90 NO STANDARD PAGE HEADING.

DATA: l_version TYPE c LENGTH 6 VALUE '54'. "54.2 TYPES: ty_para(2) TYPE n, ty_top(3) TYPE n.

TYPE-POOLS: abap.

DATA: tabname TYPE tabname, subrc TYPE sy-subrc, p_prf TYPE abap_bool,

....See full code listing within your SAP system using transactions such as SE80 and SE38

Incorrect Answers:

A: When you're starting an implementation from scratch, SAP Quick Sizer will calculate memory requirements of the implementation of SAP software on top of HANA.

Reference: https://www.se80.co.uk/sapreports/-/-fs-/-fs-sdf-fs-hdb_sizing.htm https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-sizing

In the Azure Security Center regulatory compliance blade, you can get an overview of key portions of your compliance posture with respect to a set of supported standards. Currently supported standards are Azure CIS, PCI DSS 3.2, ISO 27001, and SOC TSP.

Reference:

https://azure.microsoft.com/en-us/blog/regulatory-compliance-dashboard-in-azure-security-center-now-available/

Box 1: Ev3 series M Azure virtual machines

The Ev3 series pricing is starting from $58.40 /per month.

The E-series Azure VMs are optimized for heavy in-memory applications such as SAP HANA. These VMs are configured with high memory-to-core ratios, which makes them well-suited for memoryintensive enterprise applications, large relational database servers, in-memory analytics workloads etc.

The Ev3-series VMs range from 2 to 64 vCPUs and 16-432 GiB of RAM, respectively.

Example workloads include SAP HANA (e.g., E64s v3, E20ds v4, E32ds v4, E48ds v4, E64ds v4), SAP S/4 HANA application layer, SAP NetWeaver application layer, and more broadly memory-intensive enterprise applications, large relational database servers, data warehousing workloads, business intelligence applications, in-memory analytics workloads, and additional business-critical applications, including systems that process financial transactions of various nature... Incorrect Answers:

On price: The M-series family pricing is starting from $1,121.65 /per month.

Note: The M-series family of Azure virtual machines are memory optimized and are ideal for heavy in-memory workloads such as SAP HANA. The M-Series offer up to 4 TB of RAM on a single VM. In addition, these VMs offer a virtual CPU count of up to 128 vCPUs on a single VM to enable high performance parallel processing.

Example workloads include SAP HANA, SAP S/4 HANA, SQL Hekaton and other large in-memory business critical workloads requiring massive parallel compute power.

Box 2: Hana on Azure (Large Instances)

The storage used in HANA Large Instances has a file size limitation. The size limitation is 16 TB per file.

Reference:

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

https://azure.microsoft.com/en-us/pricing/details/virtual-machines/series/