DRAG DROP (Drag and Drop is not supported)You have an Azure subscription that is linked to a Microsoft Entra tenant. The subscription contains a virtual machine named VM1.You install SAP Landscape Management (LaMa) on VM1.You need to ensure that you can use SAP LaMa to manage the deployment of SAP workloads to Azure virtual machines. The solution must minimize administrative effort.Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.Select and Place:
Answer(s): A
Step 1: From the Azure portal, create an app registration.Set up the SAP LaMa connector for AzureThe connector for Azure uses the Azure Resource Manager API to manage your Azure resources. SAP LaMa can use a service principal or a managed identity to authenticate against this API. If your SAP LaMa instance is running on an Azure VM, we recommend using a managed identity.Use a service principal to get access to the Azure APIFollow these steps to create a service principal for the SAP LaMa connector for Azure:1. Go to the Azure portal.2. Open the Azure Active Directory pane.3. Select App registrations. (Step 1)4. Select New registration. (Step 1)5. Enter a name, and then select Register. (Step 1)6. Select the new app, and then on the Settings tab, select Certificates & secrets.7. Create a new client secret, enter a description for a new key, select when the secret should expire, and then select Save.8. Write down the value. You'll use it as the password for the service principal.9. Write down the application ID. You'll use it as the username of the service principal.By default, the service principal doesn't have permissions to access your Azure resources. Assign the Contributor role to the service principal at resource group scope for all resource groups that contain SAP systems that SAP LaMa should manage.Step 2: From Azure portal, enable a system-assigned managed identity for VM1.Use a managed identity to get access to the Azure APITo be able to use a managed identity, your SAP LaMa instance has to run on an Azure VM that has a system- assigned or user-assigned identity.Configure managed identities for Azure resources on a VM using the Azure portal Enable system-assigned managed identity on an existing VMTo enable system-assigned managed identity on a VM that was originally provisioned without it, your account needs the Virtual Machine Contributor role assignment. No other Azure AD directory role assignments are required.1. Sign in to the Azure portal using an account associated with the Azure subscription that contains the VM.2. Navigate to the desired Virtual Machine and select Identity.3. Under System assigned, Status, select On and then click Save:Incorrect:* From Azure portal, create a user-assigned managed identity. The managed identity needs to be assigned to the Virtual Machine.Step 3: From the Azure Portal, assign the Contributor role to the managed identity for the subscription. By default, the managed identity doesn't have permissions to access your Azure resources. Assign the Contributor role to the VM identity at resource group scope for all resource groups that contain SAP systems that SAP LaMa should manage.Incorrect:* From the SAP Landscape management, create an SAP LaMa connector.SAP LaMa connector for AzureMany customers use SAP Landscape Management (LaMa) to operate and monitor their SAP landscape. Since version 3.0 SP05, SAP LaMa includes a connector to Azure by default. You can use this connector to deallocate and start virtual machines (VMs), copy and relocate managed disks, and delete managed disks. With these basic operations, you can relocate, copy, clone, and refresh SAP systems by using SAP LaMa.
https://learn.microsoft.com/en-us/azure/sap/workloads/lama-installation https://learn.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/qs-configure- portal-windows-vm
DRAG DROP (Drag and Drop is not supported)You plan to deploy an SAP production landscape on Azure. The landscape will use SAP HANA databases that run on Azure virtual machines.Each HANA virtual machine will contain the following three premium data disks:SharedDataLogYou need to configure caching on the data disks. The solution must meet the following requirements:Maximize data throughput.Minimize potential data loss.Which caching configuration should you use for each disk? To answer, drag the appropriate caching configurations to the correct disks. Each caching configuration may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.NOTE: Each correct selection is worth one point.Select and Place:
Box 1: No CachingSAP HANA Azure virtual machine Premium SSD storage configurations/hana/data - None or read cachingBox 2: Write AcceleratorSolutions with premium storage and Azure Write Accelerator for Azure M-Series virtual machines Azure Write Accelerator is a functionality that is available for Azure M-Series VMs exclusively in combination with Azure premium storage. As the name states, the purpose of the functionality is to improve I/O latency of writes against the Azure premium storage. For SAP HANA, Write Accelerator is supposed to be used against the /hana/log volume only. Therefore, the /hana/data and /hana/log are separate volumes with Azure Write Accelerator supporting the /hana/log volume only.Box 3: Read cachehana/shared - read caching
https://learn.microsoft.com/en-us/azure/sap/workloads/hana-vm-premium-ssd-v1
DRAG DROP (Drag and Drop is not supported)You have an Azure subscription that contains a D-series virtual machine named SQL1.You plan to deploy an SAP landscape on Azure that will have Microsoft SQL Server installed.You install a SQL server on SQL1 and place databases and logs on separate disks.You need to configure caching for the disks.Which type of cache should you configure for each disk? To answer, drag the appropriate cache types to the correct disks. Each cache type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.NOTE: Each correct selection is worth one point.Select and Place:
Box 1: Read-OnlyReadOnly caching is highly beneficial for SQL Server data files that are stored on Premium Storage. ReadOnly caching brings low read latency, high read IOPS, and throughput as, reads are performed from cache, which is within the VM memory and local SSD. These reads are much faster than reads from data disk, which is from Azure Blob storage. Premium storage does not count the reads served from cache towards the disk IOPS and throughput. Therefore, your applicable is able to achieve higher total IOPS and throughput.Box 2: NoneNone cache configuration should be used for the disks hosting SQL Server Log file as the log file is written sequentially and does not benefit from ReadOnly caching.Incorrect:* Read/WriteReadWrite caching should not be used to host SQL Server files as SQL Server does not support data consistency with the ReadWrite cache. Writes waste capacity of the ReadOnly blob cache and latencies slightly increase if writes go through ReadOnly blob cache layers.* Write AcceleratorEnable Write AcceleratorWrite Acceleration is a disk feature that is only available for the M-Series Virtual Machines (VMs).
https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/storage-configuration
HOTSPOT (Drag and Drop is not supported)You have an Azure virtual machine named VM1 that hosts an SAP application server.You need to implement snoozing for VM1. The solution must meet the following requirements:Minimize compute costs for VM1.Gracefully terminate the SAP application.What should you do? To answer, select the appropriate options in the answer area.NOTE: Each correct selection is worth one point.Hot Area:
Box 1: sapcontrol.exeOn VM1, run:Automatic snoozing of SAP systems on azureAutomatic snoozing can be implemented to SAP systems running on Microsoft Azure to reduce IaaS costs and manage the monthly spend to maintain cost-effective IaaS on Microsoft Azure Public Cloud which has been a peak interest for enterprise grade, mid-size companies . Snoozing helps to reduce infrastructure costs by eliminating resource utilization when systems are not required for business operations.Snoozing ProcedureThere are different ways to address snoozing process on Azure. We will talk few scenarios here.Scenario 1: Using Azure AutomationWe must create Powershell functions to start and stop sap instances. These functions can be created in different ways. Below is the very simple example using sapcontrol.exe to start and stop sap instances. Alternatively, sapcontrol web service calls can also be used to complete this task. Below are the sample powershell functions to stop /start all sap instances installed on Virtual systems with Windows operating system.Sample script to STOP SAP Instances in Virtual MachineBox 2: az vm deallocateFrom Azure Cloud Shell, run:How Azure VM Billing WorksWhen Microsoft Azure Virtual Machines (VMs) are running they are billed on a "per hour" basis. You will only pay for the number of hours your VM is running after you create it. If you leave the VM running all month long, this means you pay for the entire month. But, if you stop and deallocate the VM, then you will only be billed for the time the VM is actually running.The reason you are only billed for the time when the VM is running, and not when it's deallocated, is because when it's running is the only time actual compute hardware in the datacenter is dedicated to your VM. When the VM is deallocated, then Microsoft Azure releases the hardware reservation for your VM so it can be used by some other Azure resource that needs it.Note: Scenario 1: Using Azure AutomationThis scenario explains how to leverage native Azure automation to schedule automatic SAP system startup / shutdown when needed. Azure provides runbooks gallery with sample scripts to start or shutdown virtual machines on demand. These scripts will not handle applications like SAP running inside those virtual machines. If at all graceful shutdown of SAP application is required in any organization, that has to be handled separately in Microsoft Azure automation run book. There is a requirement to create a power shell / shell script depending on operating system and initiate execution of shell script using Virtual machine custom extension.
https://community.sap.com/t5/technology-blogs-by-members/automatic-snoozing-of-sap-systems-on-azure/ba- p/13415507https://build5nines.com/properly-shutdown-azure-vm-to-save-money
HOTSPOT (Drag and Drop is not supported)You plan to implement a deployment of SAP NetWeaver on Azure. The deployment will be hosted on virtual machines that run a custom Windows Server 2022 Datacenter image.You need to configure the virtual machines to support Secure Boot.What should you do? To answer, select the appropriate options in the answer area.NOTE: Each correct selection is worth one point.Hot Area:
Box 1: Setting the Security type to Trusted launch virtual machines Enable Secure Boot by;Trusted launch is a way to improve the security of generation 2 VMs. Trusted launch protects against advanced and persistent attack techniques by combining infrastructure technologies like vTPM and secure boot.Note: Deploy a trusted launch VM (see step 8 below)Create a virtual machine with trusted launch enabled. Choose an option below:1. Sign in to the Azure portal.2. Search for Virtual Machines.3. Under Services, select Virtual machines.4. In the Virtual machines page, select Add, and then select Virtual machine.5. Under Project details, make sure the correct subscription is selected.6. Under Resource group, select Create new and type a name for your resource group or select an existing resource group from the dropdown.7. Under Instance details, type a name for the virtual machine name and choose a region that supports trusted launch.8. For Security type select Trusted launch virtual machines. This will make three more options appear - Secure boot, vTPM, and Integrity Monitoring. Select the appropriate options for your deployment.9. Etc.Box 2: VHDUser virtual disk format:Trusted launch VM supported imagesFor the following image sources, the security type on the image definition should be set to TrustedLaunchsupported:Gen2 OS Disk VHDGen2 Managed ImageGen2 Gallery Image Version
https://learn.microsoft.com/en-us/azure/virtual-machines/trusted-launch-portal
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.