Microsoft Planning and Administering Microsoft Azure for SAP Workloads (AZ-120日本語版) - AZ-120日本語 Exam Practice Test

Explanation:
Box 1: Microsoft SQL Always on
For SQL Server instance
The Always On availability groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. Always On availability groups maximizes the availability of a set of user databases for an enterprise. An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together. An availability group supports a set of read- write primary databases and one to eight sets of corresponding secondary databases. Optionally, secondary databases can be made available for read-only access and/or some backup operations.
You can configure an Always On availability group replica for SQL Server on Azure virtual machines (VMs) in an Azure region that is remote to the primary replica. You can use this configuration for the purpose of disaster recovery (DR).
The local region in this article refer to the virtual machines and availability group already configured in the first region. The remote region is the new infrastructure Box 2: Azure Site Recovery For SAP Central Services SAP on Azure, Disaster recovery guidelines for SAP application For SAP systems running on virtual machines, you can use Azure Site Recovery to create a disaster recovery plan.
For SAP Central Services replicate VM using Azure Site Recovery.
Note: Following is the recommended disaster recovery approach for each component of an SAP system. Standalone non-NetWeaver SAP engines such as TREX and non-SAP applications aren't covered in this document.

Explanation:
Box 1: A proximity placement group
Azure offers proximity placement groups. Proximity placement groups can be used to force grouping of different VM types into a single Azure datacenter to optimize the network latency between these different VM types to the best possible. In the process of deploying the first VM into such a proximity placement group, the VM gets bound to a specific datacenter.
Note: SAP applications based on the SAP NetWeaver or SAP S/4HANA architecture are sensitive to network latency between the SAP application tier and the SAP database tier. This sensitivity is the result of most of the business logic running in the application layer. Because the SAP application layer runs the business logic, it issues queries to the database tier at a high frequency, at a rate of thousands or tens of thousands per second. In most cases, the nature of these queries is simple. They can often be run on the database tier in 500 microseconds or less.
Box 2: Enable Accelerated Networking
To further reduce network latency between Azure VMs, we recommend that you choose Azure Accelerated Networking. Use it when you deploy Azure VMs for an SAP workload, especially for the SAP application layer and the SAP DBMS layer.
Incorrect Answers:
Azure Write Accelerator is a functionality that is available for Azure M-Series VMs exclusively. 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: Network Performance Monitor
Network Performance Monitor (NPM) - a cloud-based network monitoring solution for cloud-only, on-premises, and hybrid networking environments.
Network Performance Monitor offers three broad capabilities:
Performance Monitor: You can monitor network connectivity across cloud deployments and on- premises locations, multiple data centers, and branch offices and mission-critical multitier applications or microservices. With Performance Monitor, you can detect network issues before users complain.
Service Connectivity Monitor
ExpressRoute Monitor
Note 2: Azure Monitor for SAP Solutions is an Azure-native monitoring product for anyone running their SAP landscapes on Azure. It works with both SAP on Azure Virtual Machines and SAP on Azure Large Instances.
Incorrect Answers:
Apache JMeter is a free and open source tool for performance testing of web applications.
SAP application server to database server latency can be tested with ABAPMeter report
/SSA/CAT. Latency between SAP application server and DBMS server can be tested using TCPPing (Ping is not an accurate tool on Azure) or the SAP ABAP report /SSA/CAT -> ABAPMeter - columns DB Access and E. DB Access.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/sap-proximity-placement-scenarios
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/dbms_guide_general
https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/sap-on-azure-general-update-march-2019/ba-p/377456

Explanation: Only visible for Actualtests4sure members. You can sign-up / login (it's free).

Explanation: Only visible for Actualtests4sure members. You can sign-up / login (it's free).

Explanation:
Box 1: the Azure Management API
If you are using Pacemaker with Azure fence agent in your high availability solution, then the VMs must have outbound connectivity to the Azure management API.
Note:
Depending on the location of the proxy, it may introduce additional latency in the calls from the Azure Fence Agent to the Azure Management API.
Box 2: Outbound only
Reference:
https://learn.microsoft.com/en-us/azure/sap/workloads/high-availability-guide-standard-load-balancer-outbound-connections

Explanation:
Box 1: Azure Monitor for SAP solutions
Monitoring
What is Azure Monitor for SAP solutions?
When you have critical SAP applications and business processes that rely on Azure resources, you might want to monitor those resources for availability, performance, and operation. Azure Monitor for SAP solutions is an Azure-native monitoring product for SAP landscapes that run on Azure.
It uses specific parts of the Azure Monitor infrastructure.
What can you monitor?
You can use Azure Monitor for SAP solutions to collect data from Azure infrastructure and databases in one central location. Then, you can visually correlate the data for faster troubleshooting.
To monitor components of an SAP landscape, add the corresponding provider. These components include Azure VMs, high-availability (HA) clusters, SAP HANA databases, and SAP NetWeaver.
What data is collected?
Data collection in Azure Monitor for SAP solutions depends on the providers that you configure.
The following data is collected for each provider.
*-> HA Pacemaker cluster data
Node, resource, and SBD status
Pacemaker location constraints
Quorum votes and ring status
* SAP HANA data
* Etc.
Box 2: A private endpoint
Connectivity
Use Azure Private Link to connect networks to Azure Monitor
With Azure Private Link, you can securely link Azure platform as a service (PaaS) resources to your virtual network by using private endpoints. Azure Monitor is a constellation of different interconnected services that work together to monitor your workloads. An Azure Monitor private link connects a private endpoint to a set of Azure Monitor resources to define the boundaries of your monitoring network. That set is called an Azure Monitor Private Link Scope (AMPLS).