Instiq
Chapter 5 · Plan and Configure High Availability and Disaster Recovery·v2.0.0·Updated 6/3/2026·~9 min

What's changed: Deepened DP-300 Chapter 5 (ja figures; comparison tables/scenarios/FAQ/traps/deep paragraphs in all sections)

5.2High Availability and Disaster Recovery Strategies

Key points

Understand Azure SQL zone redundancy (in-region HA), active geo-replication and failover groups (cross-region DR), and Always On availability groups (VM). Design to RPO/RTO requirements.

High availability (HA) addresses in-region failures; disaster recovery (DR) addresses whole-region failures. Azure SQL provides mechanisms for both.

5.2.1HA and DR mechanisms

Diagram showing in-region HA via zone redundancy (replicas across availability zones) and Business Critical built-in replicas, and cross-region DR via active geo-replication (readable secondary in another region) and failover groups (group of DBs with automatic failover, switch without changing the connection string), plus Always On availability groups on VM.
HA and DR mechanisms
  • Zone redundancy: place replicas across availability zones within a region to tolerate zone failure (HA).
  • Active geo-replication: create a readable replica in another region (DR, read scale).
  • Failover group: group DBs for automatic failover, switching without changing the connection string (DR).
  • Always On availability groups: HA/DR for SQL on VM (self-configured).
Exam point

Common on DP-300: in-region HA = zone redundancy, cross-region DR = active geo-replication/failover groups, automatic switch without changing connection string = failover group, VM HA/DR = Always On availability groups. Tighter RPO/RTO → combine zone redundancy + geo.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.