Explanation
Azure Policy enables you to set policies to conform to the GDPR. Azure Policy is generally available today at no additional cost to Azure customers. You can use Azure Policy to define and enforce policies that help your cloud environment become compliant with internal policies as well as external regulations.
Azure Policy is deeply integrated into Azure Resource Manager and applies across all resources in Azure.
Individual policies can be grouped into initiatives to quickly implement multiple rules. You can also use Azure Policy in a wide range of compliance scenarios, such as ensuring that your data is encrypted or remains in a specific region as part of GDPR compliance. Microsoft is the only hyperscale cloud provider to offer this level of policy integration built in to the platform for no additional charge.
References:
https://azure.microsoft.com/de-de/blog/new-capabilities-to-enable-robust-gdpr-compliance/

see the explanation for below image:
Explanation
Answer selected as in image below.
Graphical user interface, text, application, email Description automatically generated

Explanation

Box 1: No
Box 2: Yes
The 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 disk Box 3: Yes References:
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-vm-operations-storage

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/

The Azure network functionality used is:
Azure virtual networks are connected to the ExpressRoute circuit that connects to your on-premises network assets.
An ExpressRoute circuit that connects on-premises to Azure should have a minimum bandwidth of 1 Gbps or higher. This minimal bandwidth allows adequate bandwidth for the transfer of data between on-premises systems and systems that run on VMs. It also allows adequate bandwidth for connection to Azure systems from on-premises users.
All SAP systems in Azure are set up in virtual networks to communicate with each other.
References:
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-network-architecture

Explanation

Step 1: Create a virtual network…
We recommended that for test failover, you choose a network that’s isolated from the production recovery site network specific in the Compute and Network settings for each VM. By default, when you create an Azure virtual network, it is isolated from other networks. The test network should mimic your production network:
The test network should have same number of subnets as your production network. Subnets should have the same names.
The test network should use the same IP address range.
Step 2: Add a public IP address…
Because Site Recovery does not replicate the cloud witness, we recommend that you deploy the cloud witness in the disaster recovery region.
Step 3: Shut down production virtual machines
Make sure that the primary VM is shut down when you run the test failover. Otherwise there will be two VMs with the same identity, running in the same network at the same time. This can lead to unexpected consequences.
Step 4: Select Test failover from the Recovery Plans blade
References:
https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-test-failover-to-azure

Explanation
Box 1: NO
Box 2: Yes
Box 3: Yes
Be aware that network traffic between two peered Azure virtual networks is subject to transfer costs. Huge data volume that consists of many terabytes is exchanged between the SAP application layer and the DBMS layer. You can accumulate substantial costs if the SAP application layer and DBMS layer are segregated between two peered Azure virtual networks.
References:
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/dbms_guide_general

You set up alerts on Azure VPN Gateway metrics. Azure Monitor provides the ability to set up alerts for Azure resources. You can set up alerts for virtual network gateways of the “VPN” type.
Metric: AverageBandwidth: Average combined bandwidth utilization of all site-to-site connections on the gateway.
Reference:
https://docs.microsoft.com/bs-latn-ba/azure/vpn-gateway/vpn-gateway-howto-setup-alerts-virtual-network-gatew

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.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/sap-high-availability-architecture-scenarios

Explanation
YES
YES
NO

Explanation:
Scenario: Ensure that all the production databases can withstand the failure of an Azure region.
References:
https://docs.microsoft.com/en-us/powershell/module/az.compute/get-azvmimage

Explanation

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.
Reference:
https://blogs.sap.com/2017/10/05/your-sap-on-azure-part-2-dmo-with-system-move/ Migrate SAP Workloads to Azure Testlet 2 Case Study This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Overview
Contoso, Ltd. is a manufacturing company that has 15,000 employees.
The company uses SAP for sales and manufacturing.
Contoso has sales offices in New York and London and manufacturing facilities in Boston and Seattle.
Existing Environment
Active Directory
The network contains an on-premises Active Directory domain named ad.contoso.com. User email addresses use a domain name of contoso.com.
SAP Environment
The current SAP environment contains the following components:
* SAP Solution Manager
* SAP ERP Central Component (SAP ECC)
* SAP Supply Chain Management (SAP SCM)
* SAP application servers that run Windows Server 2008 R2
* SAP HANA database servers that run SUSE Linux Enterprise Server 12 (SLES 12) Problem Statements Contoso identifies the following issues in its current environment:
* The SAP HANA environment lacks adequate resources.
* The Windows servers are nearing the end of support.
* The datacenters are at maximum capacity.
Requirements
Planned Changes
Contoso identifies the following planned changes:
* Deploy Azure Virtual WAN.
* Migrate the application servers to Windows Server 2016.
* Deploy ExpressRoute connections to all of the offices and manufacturing facilities.
* Deploy SAP landscapes to Azure for development, quality assurance, and production.
All resources for the production landscape will be in a resource group named SAPProduction.
Business goals
Contoso identifies the following business goals:
* Minimize costs whenever possible.
* Migrate SAP to Azure without causing downtime.
* Ensure that all SAP deployments to Azure are supported by SAP.
* Ensure that all the production databases can withstand the failure of an Azure region.
* Ensure that all the production application servers can restore daily backups from the last 21 days.
Technical Requirements
Contoso identifies the following technical requirements:
* Inspect all web queries.
* Deploy an SAP HANA cluster to two datacenters.
* Minimize the bandwidth used for database synchronization.
* Use Active Directory accounts to administer Azure resources.
* Ensure that each production application server has four 1-TB data disks.
* Ensure that an application server can be restored from a backup created during the last five days within 15 minutes.
* Implement an approval process to ensure that an SAP administrator is notified before another administrator attempts to make changes to the Azure virtual machines that host SAP.
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.
Proposed Backup Policy
An Azure administrator proposes the backup policy shown in the following exhibit.

Azure Resource Manager Template
An Azure administrator provides you with the Azure Resource Manager template that will be used to provision the production application servers.

Explanation
The Azure Desired State Configuration (DSC) VM Extension is updated as-needed to support enhancements and new capabilities delivered by Azure, Windows Server, and the Windows Management Framework (WMF) that includes Windows PowerShell.
References:
https://docs.microsoft.com/en-us/powershell/scripting/dsc/getting-started/azuredscexthistory

Explanation
Simplify cloud migration by using Site Recovery to migrate your SAP deployment to Azure.
Reference:
https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-sap