Question

Difficulty: MediumAzure Regions, Availability Zones, and Region Pairs

A logistics company is designing a disaster recovery model for its shipment tracking database in Azure. The database is currently hosted in the West US region. The disaster recovery solution must keep replicated data within the same geography for compliance, place the backup data at least 300 miles away to survive regional disasters, and ensure that Azure platform updates are performed sequentially rather than simultaneously across both locations. Which Azure architectural feature should the company use to meet these requirements?

  1. A
    Availability Zones
  2. Azure Region PairsAnswer
  3. C
    Availability Sets
  4. D
    Resource Groups

Answer

Azure Region Pairs
Azure Region Pairs automatically link two regions within the same geography (typically at least 300 miles apart). They ensure that data replication remains compliant with local residency rules, provide geographic separation to recover from regional disasters, and undergo sequential platform updates so that only one region in the pair is updated at a time, preventing simultaneous downtime.

Step-by-Step Solution

1
Analyze the requirements for physical separation and disaster recovery.
The requirement specifies a distance of at least 300 miles and protection against regional disasters, which points to a multi-region disaster recovery architecture rather than a high-availability single-region setup.
Distinguishing between local high availability and multi-region disaster recovery is the first step in selecting the correct Azure architecture component.
2
Evaluate the regulatory and platform maintenance constraints.
The solution must keep data within the same political geography and support sequential platform updates to avoid simultaneous downtime.
Azure Region Pairs are specifically configured to meet these constraints by pairing regions in the same geography and sequencing updates.
3
Select the Azure feature that matches all identified criteria.
Azure Region Pairs align with all requirements (geographic separation of 300+ miles, data residency compliance, and sequenced updates).
Comparing the features of Availability Zones, Availability Sets, and Resource Groups reveals that only Region Pairs satisfy the multi-region constraints.

Key Concept

Azure Region Pairs replication, data residency, and sequential update policies.
Rate this question