← Microsoft Certified: Azure for SAP Workloads Specialty
AZURE · objective · 22% of the exam
Design and implement high availability and disaster recovery (HADR) — Microsoft Certified: Azure for SAP Workloads Specialty
The official AZURE documentation our Design and implement high availability and disaster recovery (HADR) practice questions are cited to. Review the primary sources, then practise.
Official references for this objective
-
Microsoft — Active Geo-Replication - Azure SQL Database | Microsoft Learn
Forced failover immediately switches the geo-secondary to the primary role without waiting for synchronization with the primary. Any transactions committed on the primary but not
-
Microsoft — Backup and disaster recovery for managed disks on Azure VMs - Azure Virtual Machines | Microsoft Learn
Azure Disk Backup is a crash-consistent backup solution that takes point-in-time backup of a managed disk using incremental snapshots and supports multiple backups per day.
-
Microsoft — Configure a failover group - Azure SQL Managed Instance | Microsoft Learn
No public internet, gateways, or additional encryption is required in the communication between the peered virtual networks.
-
leave the default Latest processed (low RPO) setting for the recovery point. This option provides the lowest recovery point objective (RPO)
-
You should use ZRS when sharing a disk between multiple VMs. If you use LRS, the shared disk becomes a single point of failure for
-
The probe defines how Azure verifies which of the SQL Server instances currently owns the AG listener. Azure probes the service based on the IP
-
Microsoft — Create an Azure scale set that uses availability zones - Azure Virtual Machine Scale Sets | Microsoft Learn
When you expand the scale set to additional zones, the original instances are not migrated or changed.
-
Microsoft — Failover Groups Overview & Best Practices - Azure SQL Managed Instance | Microsoft Learn
Global virtual network peering (VNet peering) is the recommended way to establish connectivity between two instances in a failover group.