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

Load balancers. These are used to distribute traffic to virtual machines in the application-tier subnet. For high availability, use the built-in SAP Web Dispatcher, Azure Load Balancer, or network appliances, depending on the traffic type (such as HTTP or SAPGUI) or the required network services, such as Secure Sockets Layer (SSL) termination.

Reference: https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/sap/sap-netweaver

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

Box 1: Client IP

The standard load balancer allows stateful sessions to remain as there are no IP address changes with this method.

Box 2: Enabled

Make sure to enable Floating IP.

References:

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

Box 1: the same fault domain

Fault domains define the group of virtual machines that share a common power source and network switch. If a storage fault domain fails due to hardware or software failure, only the VM instance with disks on the storage fault domain fails.

Box 2: managed disks

Managed disks provide better reliability for Availability Sets by ensuring that the disks of VMs in an Availability Set are sufficiently isolated from each other to avoid single points of failure. It does this by automatically placing the disks in different storage fault domains (storage clusters) and aligning them with the VM fault domain.

References:

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/manage-availability

Step 1: Install the samba-winbind package

Install samba-winbind

Step 2: Add realm details to /etc/krb5.conf and /etc/samba/smb.conf

Edit files - best way to do this is to use yast on test machine and copy files from it

In following examples you need to replace EXAMPLE/EXAMPLE.COM/.example.com with your values/settings /etc/samba/smb.conf

[global]

workgroup = EXAMPLE

usershare allow guests = NO #disallow guests from sharing

idmap gid = 10000-20000

idmap uid = 10000-20000

kerberos method = secrets and keytab

realm = EXAMPLE.COM

security = ADS

template homedir = /home/%D/%U

template shell = /bin/bash

winbind offline logon = yes

winbind refresh tickets = yes

/etc/krb5.conf

[libdefaults]

default_realm = EXAMPLE.COM

clockskew = 300

[realms]

EXAMPLE.COM = {

kdc = PDC.EXAMPLE.COM

default_domain = EXAMPLE.COM

admin_server = PDC.EXAMPLE.COM

}

..

Step 3: Run net ads join -U administrator

Join the SLES 12 Server to the AD domain

References:

https://www.suse.com/support/kb/doc/?id=7018461

Box 1: No

You can't use an Azure Basic Load Balancer to create failover cluster solutions based on Windows Server Failover Clustering or Linux Pacemaker. Instead, you need to use the Azure Standard Load Balancer SKU.

Box 2: Yes

Azure Availability Zones is one of the high-availability features that Azure provides. Using Availability Zones improves the overall availability of SAP workloads on Azure. The SAP application layer is deployed across one Azure availability set. For high availability of SAP Central Services, you can deploy two VMs in a separate availability set.

Box 3: Yes

You must use Azure Managed Disks when you deploy to Azure Availability Zones.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/sap-ha-availability-zones

Box 1: No

Azure Availability Zones are physically separate locations within an Azure region protecting customers’ applications and data from datacenter-level failures. It is good for applications that require low-latency synchronous replication with protection from datacenter-level failures.

Box 2: Yes

AAP application server to database server latency can be tested with ABAPMeter report /SSA/CAT.

Box 3: Yes

To analyze network issue or measure network metrics you can test the connection using SAP's NIPING program. You can use NIPING to analyze the network connection between any two machines running SAP software.

Reference:

https://azure.microsoft.com/sv-se/blog/azure-availability-zones-expand-with-new-services-and-to-new-regions-in-europe-and-united-states/

https://azure.microsoft.com/en-us/blog/sap-on-azure-architecture-designing-for-performance-and-scalability/

https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=360974069

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.

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

When you set up disaster recovery for on-premises VMware VMs, Site Recovery needs access to the vCenter Server/vSphere host so that the Site Recovery process server can automatically discover VMs, and fail them over as needed. By default the process server runs on the Site Recovery configuration server. Add an account for the configuration server to connect to the vCenter Server/vSphere host.

Reference: https://docs.microsoft.com/en-us/azure/site-recovery/vmware-azure-manage-vcenter