To meet the stringent SAP HANA storage Key Performance Indicators (KPIs) for throughput and I/O on Azure, it is necessary to aggregate the performance of multiple Azure Premium Storage disks. This is achieved by creating a striped volume using a software RAID, such as mdadm in Linux. RAID0 (striping) is the recommended configuration for both the /hana/data and /hana/log volumes. It combines the IOPS and throughput of all underlying disks without the performance overhead of parity calculations found in RAID5 or RAID6. The required data redundancy is provided by the underlying Azure Storage platform (Locally Redundant Storage - LRS), which maintains three copies of the data, making OS-level RAID for redundancy unnecessary.

A. RAID1: RAID1 (mirroring) provides redundancy but does not aggregate write performance, failing to meet the high throughput requirements for SAP HANA data and log volumes.

B. RAID5: RAID5 is explicitly not recommended for the write-intensive /hana/log volume due to the significant write penalty associated with parity calculations, which severely impacts performance and latency.

D. RAID6: RAID6 has an even higher write penalty than RAID5 because it calculates and writes two parity blocks, making it the least suitable option for high-performance database workloads like SAP HANA.

1. Microsoft Docs

"SAP HANA Azure virtual machine storage configurations"

Last updated: 01/29/2024.

Section: Linux LVM and mdadm: "For the SAP HANA data and log volumes

we don't recommend any RAID redundancy level. The reason is that Azure Premium Storage already provides a sufficient level of redundancy with three images of the disks... The main purpose of building a RAID volume is to stripe I/O against multiple Azure Premium disks." This statement directly supports using striping (RAID0) and advises against redundancy levels like RAID1

RAID5

and RAID6.

Section: Production recommended storage configuration: This section provides specific examples for different VM types

all of which use multiple disks striped together (RAID0) for /hana/data and /hana/log to achieve the required performance. For example

for an M32ts VM

it recommends "4 x P10" disks in a striped set for /hana/data.

Section: Considerations for the /hana/log volume: "For the /hana/log volume

the usage of RAID 5 is not supported." This explicitly disqualifies RAID5 as a correct answer.

Statement 1: Yes. Accelerated Networking uses Single Root I/O Virtualization (SR-IOV) to offload network processing from the VM’s CPU to the hardware NIC. This reduces the CPU overhead required for packet processing, thereby decreasing overall CPU usage.

Statement 2: No. One of the primary benefits of Accelerated Networking is the reduction of jitter and latency by bypassing the virtual switch and the host's "software" processing path. It provides a more consistent, deterministic network path.

Statement 3: No. This feature is restricted to specific supported VM sizes (typically those with 2 or more vCPUs) and requires specific OS versions (e.g., Windows Server 2012 R2+ or modern Linux distributions).

Microsoft Azure Documentation: "Create a Windows VM with accelerated networking," Section: Benefits, Paragraph 2 & 4. (https://learn.microsoft.com/en-us/azure/virtual-network/create-vm-accelerated-networking-powershell)

Microsoft Azure Documentation: "SAP on Azure: SAP Netweaver on Azure VMs - Accelerated Networking," Section: Performance Recommendations. (https://learn.microsoft.com/en-us/azure/sap/workloads/deployment-guide#accelerated-networking)

Microsoft Azure Documentation: "Accelerated Networking - Limitations and Constraints," Section: Supported VM instances. (https://learn.microsoft.com/en-us/azure/virtual-network/accelerated-networking-overview#limitations-and-constraints)

The most effective method to minimize costs for non-production environments like development and quality assurance is to shut them down during periods of inactivity, such as nights and weekends. Azure Automation runbooks provide a robust and schedulable mechanism to automatically stop (deallocate) and start Azure virtual machines. When a VM is deallocated, Azure stops billing for compute resources (CPU, memory), resulting in significant cost savings. This approach directly addresses the requirement by ensuring the SAP landscapes are only running and incurring costs when they are actively being used.

B. The stopsap command stops the SAP application services running within the OS but does not deallocate the Azure VM, so compute costs continue to accrue.

C. Azure App Service is a Platform-as-a-Service (PaaS) offering and is not used to host the core components of an SAP NetWeaver or S/4HANA environment.

D. Azure Virtual Machine Scale Sets are designed for automatic scaling of identical VMs based on performance metrics, not for scheduled shutdowns of entire landscapes.

1. Microsoft Learn

"Start/Stop VMs v2 overview": This document describes a feature built on Azure Automation specifically for cost optimization. It states

"The Start/Stop VMs v2 feature starts or stops enabled Azure VMs on a schedule. It helps optimize costs for users who want to stop VMs when not in use and then start them when they're needed." This directly supports using automation for the described scenario.

2. Microsoft Docs

"Azure Virtual Machines planning and implementation for SAP NetWeaver"

Section: "General Azure VM deployment": This guide

while not explicitly detailing automation

establishes the foundation that SAP landscapes run on IaaS VMs. The principle of deallocating IaaS VMs to save costs is a fundamental Azure best practice. The document notes

"For non-production systems

you can reduce costs by shutting down the SAP systems and deallocating the VMs." Azure Automation is the primary tool to schedule this deallocation.

3. Microsoft Docs

"Virtual machine states and billing status": This document clarifies that billing for compute resources stops only when a VM is in the Stopped (deallocated) state. This confirms why simply running stopsap (Option B)

which leaves the VM in a Running state

does not save on compute costs

whereas using an automation runbook to deallocate the VM (Option A) does.

The Azure Standard support plan is designed for production workloads and provides 24/7 technical support. For critical business impact incidents (Severity A), it guarantees an initial response time of less than one hour. This meets the primary technical requirement. Among the plans that satisfy this response time (Standard, Professional Direct, and Premier), the Standard plan is the most cost-effective, thereby fulfilling the "minimize costs" requirement.

A. Professional Direct: While this plan also offers a response time of less than one hour for critical incidents, it is more expensive than the Standard plan and thus does not meet the cost minimization requirement.

C. Basic: The Basic support plan is included with all Azure subscriptions but does not offer technical support for production environments or a guaranteed response time for critical incidents.

D. Premier: The Premier (now part of Unified Support) plan offers a much faster response time (e.g., <15 minutes) but is the most expensive option, violating the requirement to minimize costs.

---

1. Microsoft Azure Official Documentation

"Support Plans": This document provides a direct comparison of the features

including response times and target use cases

for all Azure support plans.

Reference: Under the "Compare support plans" table

in the "Technical support" section

the row for "Initial response time" for "Critical business impact (Severity A)" explicitly states "< 1 hour" for both Standard and Professional Direct plans. The cost hierarchy is also evident from the pricing details on the same page.

Source: Microsoft Azure. (n.d.). Azure Support Plans. Retrieved from https://azure.microsoft.com/en-us/support/plans/

2. Microsoft Azure Official Documentation

"How to create an Azure support request": This document details the process of creating a support request and defines the severity levels

confirming that "Severity A" is for critical business impact.

Reference: The section "Severity levels" defines Severity A as "Critical Impact - Production system down". The ability to select this severity is tied to the support plan level.

Source: Microsoft Azure. (2023

October 24). How to create an Azure support request. Retrieved from https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request#severity-levels

The SAP Software Update Manager (SUM) with its Database Migration Option (DMO) feature is the designated SAP tool for this scenario. It combines a system update, conversion, or upgrade with a database migration (e.g., from AnyDB to SAP HANA) into a single, highly optimized procedure. The "DMO with System Move" capability specifically supports migrating to a different infrastructure, such as from on-premises to Azure. This one-step approach significantly minimizes downtime and administrative effort compared to a traditional two-step export/import migration using other tools.

A. SAP Software Provisioning Manager: SWPM is used for new installations or classic two-step migrations (export/import). This method typically involves more downtime and administrative steps than the integrated SUM with DMO process.

C. Azure Migrate: Azure Migrate is an infrastructure migration service for moving VMs and servers to Azure. It does not perform the application-specific database replatforming from SAP AnyDB to SAP HANA.

D. Azure Database Migration Service: This service is for migrating non-SAP databases (like SQL Server, Oracle) to Azure PaaS database offerings. It does not support the application-aware migration required for SAP systems to HANA.

1. Microsoft Docs

Azure Architecture Center

"SAP S/4HANA in Linux on Azure": This document outlines migration strategies. Under the "Migration to S/4HANA" section

it states

"For migrations from an existing SAP ERP system to S/4HANA

the SAP Software Update Manager (SUM) tool is the officially supported and recommended tool. It offers a path that combines the software update and the database migration to SAP HANA (if applicable) in one tool." This confirms SUM as the primary tool for combined updates and HANA migration.

2. Microsoft Docs

Azure Virtual Machines

"SAP workload on Azure: planning and deployment checklist": In the "Migration phase" section

this guide discusses migration methodologies. It explicitly lists "Using SAP Software Update Manager (SUM) with Database Migration Option (DMO)" as a key method for migrating to Azure

highlighting its efficiency for combining tasks.

3. SAP Help Portal

"Database Migration Option (DMO) of Software Update Manager 2.0 SP17": The official SAP documentation describes the tool's purpose: "The Database Migration Option (DMO) of Software Update Manager (SUM) is the process for migration to a different database... DMO can be used to migrate to SAP HANA database... The DMO procedure combines the database migration with the software update." This directly supports its use for minimizing downtime by combining steps.

SAP Central Services (SCS): The SCS layer is a critical but relatively lightweight component of the SAP application layer. It does not require high memory-to-vCPU ratios like a database. D-Series (specifically the Ds-series) VMs are officially supported for SAP production application servers and Central Services, providing a balanced and cost-effective compute solution.

SAP HANA: HANA is an in-memory database requiring high memory performance and strict SAP certification. The M-Series is specifically designed and certified for large-scale, memory-intensive workloads like SAP HANA, offering the necessary RAM and vCPU throughput required for production support.

Microsoft Learn: Use Azure to host and run SAP workload scenarios - SAP workload on Azure: supportable VMs. (Sections: "Application server" and "Database server").

SAP Note 1928533: SAP Applications on Azure: Supported Products and Azure VM types. This note lists certified VM series for SAP production.

SAP Note 2316233: SAP HANA on Microsoft Azure Support Indicators. (Details M-series certification for HANA production).

Microsoft Architecture Guide: SAP NetWeaver on Azure Virtual Machines - Architecture Reference.

Microsoft Azure Documentation: Azure Virtual Machines for SAP HANA - M-series Specifications.

When attaching data disks to an Azure Linux VM for an SAP workload, a stable naming convention is required for automation, as device names like /dev/sdc can change upon reboot. Azure provides a set of stable symbolic links under the /dev/disk/azure/ directory. Specifically, data disks are organized by SCSI controller and LUN. The path /dev/disk/azure/scsi1/ contains symbolic links named lun0, lun1, lun2, etc., which correspond directly to the LUN specified in the ARM template. Running the ls /dev/disk/azure/scsi1 command lists these links, allowing a direct correlation between the LUN and the underlying kernel device name (e.g., sdc), which is the goal of the question.

A. ls /dev/disk/azure/root: This path is a symbolic link to the operating system (OS) disk, not the attached data disks.

C. tree /dev/disk/azure/root: This command also targets the OS disk path. It is used for viewing a directory tree, which is not the intended use for this specific path.

D. tree /dev/disk/azure/resource: This path is a symbolic link to the temporary resource disk, not the persistent data disks used for SAP files.

1. Microsoft Learn

"Configure LVM on a Linux VM in Azure": This document demonstrates using the /dev/disk/azure/scsi1/ path to identify disks by their LUN. Under the "Identify the data disks" section

it shows the command ls -l /dev/disk/azure/scsi1/ and its output

which clearly maps lun0

lun1

etc.

to their corresponding /dev/sd device names.

2. Microsoft Learn

"Azure Virtual Machines storage configuration for SAP NetWeaver": In the "Linux" section

this guide states

"On Linux

the Azure platform creates friendly names in the directory /dev/disk/azure. For your automation scripts

use the devices in the /dev/disk/azure directory." This confirms the recommended practice for SAP workloads is to use this stable path for disk identification.

3. Microsoft Learn

"Troubleshoot Linux VM device name changes": This article explains the problem of non-persistent device names and recommends using persistent naming conventions. It mentions that the Azure Linux Agent creates symbolic links under /dev/disk/azure based on the SCSI address (including LUN) of the disks

reinforcing the reliability of this path for correlation.

Azure AD Connect is the primary Microsoft tool for integrating on-premises Active Directory with Azure AD (now Microsoft Entra ID). It facilitates identity synchronization and configures the chosen authentication method, which could be Password Hash Synchronization, Pass-through Authentication, or Federation with AD FS. To use on-premises identities to administer Azure resources, the foundational step is to synchronize them to Azure AD. Azure AD Connect is the tool that accomplishes this. AD FS is only one of several authentication options and is itself often configured through Azure AD Connect, making Azure AD Connect the more fundamental and initial component to implement.

A. No change is needed: AD FS is an optional federation service, not a mandatory first step. The primary tool for establishing hybrid identity is Azure AD Connect.

C. Azure AD join: This process is for registering devices directly with Azure AD. It is unrelated to synchronizing user identities from on-premises AD for resource administration.

D. Enterprise State Roaming: This feature synchronizes user settings and application data across Windows devices. It is not a foundational component for identity management or resource administration.

---

1. Microsoft Learn

Azure Active Directory Documentation. "What is Azure AD Connect?". This document introduces Azure AD Connect as the tool to integrate on-premises directories with Azure AD. It states

"Azure AD Connect is the Microsoft tool designed to meet and accomplish your hybrid identity goals." It lists "Federation integration" as one of its features

showing that AD FS is a component managed by Azure AD Connect

not a prerequisite for it.

Reference: https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/whatis-azure-ad-connect

Introduction section.

2. Microsoft Learn

Azure Active Directory Documentation. "Choose the right authentication method for your Azure Active Directory hybrid identity solution". This document compares the different authentication methods. It presents a flowchart where the decision to use Federation (like AD FS) comes after the initial decision to synchronize with Azure AD

a process managed by Azure AD Connect. This confirms that Azure AD Connect is the starting point.

Reference: https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/choose-ad-authn

"Authentication methods" section and diagram.

3. Microsoft Learn

Azure Active Directory Documentation. "What is federation with Azure AD?". This document explains that federation is an option for authentication and explicitly states

"You can configure federation with AD FS by using Azure AD Connect with only a few clicks." This reinforces that Azure AD Connect is the tool used to implement the solution.

Reference: https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/whatis-fed

"Federation with Azure AD" section.

For the SAP ERP system, the goal is a simultaneous migration (Oracle to HANA) and a platform shift (On-premises to Azure). The SUM DMO with System Update is the standard tool for "One-Step" migrations, allowing you to upgrade the SAP application version and migrate the database to SAP HANA in a single downtime window.

For the SAP NetWeaver 7.3 Portal, the SUM DMO tool is primarily designed for ABAP stacks. Java stacks (like most portals) or older NetWeaver versions typically require a Heterogeneous System Copy using the Software Provisioning Manager (SWPM). This process exports the source database and imports it into the target HANA database on Azure, effectively handling the change in OS/DB architecture.

SAP Support Portal, SAP Note 2377305: "Case 3: Migration of an SAP system to SAP HANA using DMO." This confirms DMO is the tool for combining upgrade and migration for ABAP-based systems like ERP.

SAP Help Portal - Software Update Manager (SUM) 2.0: Section "Database Migration Option (DMO) of SUM" specifies that DMO is the preferred method for migrating to SAP HANA while performing a release upgrade.

Microsoft Azure Documentation: "SAP NetWeaver on Azure Virtual Machines (VMs) planning and implementation." This documentation outlines using SWPM for heterogeneous copies when moving non-ABAP or specific Java-based Portal components to Azure.

SAP NetWeaver Guide: "System Copy Guide: SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on UNIX/Oracle," detailing the use of Software Provisioning Manager (SWPM) for heterogeneous system copies.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Microsoft_AZ-120_Dumps/page_31_img_1.jpg?