Question

Difficulty: Very hardAzure Regions, Availability Zones, and Region Pairs

A company is designing a disaster recovery solution for an application hosted in the East US region. To protect the application from a region-wide disaster while complying with data residency regulations, the company plans to replicate its database to East US 2, stating that East US 2 is the default Azure region pair for East US and that Azure automatically performs synchronous replication across paired regions to guarantee zero data loss. Is the company's statement regarding this disaster recovery design true or false?

Answer: Answer

Answer

The statement is false because East US is paired with West US, not East US 2, and cross-region replication between paired regions is asynchronous, which does not guarantee zero data loss.
The correct evaluation of this statement is false because the default region pair for East US is West US, and cross-region replication is asynchronous to prevent latency issues over large physical distances.

Step-by-Step Solution

1
Identify the default region pair for East US.
The default region pair for East US is West US.
Azure region pairs are pre-defined by Microsoft. East US is paired with West US, while East US 2 is paired with Central US.
2
Analyze the replication mechanism between Azure region pairs.
Replication between paired regions is asynchronous.
Paired regions are separated by a physical distance of at least 300 miles. Synchronous replication over this distance would introduce high network latency, so Azure uses asynchronous replication for cross-region data transfer.
3
Evaluate the statement's validity based on these findings.
The proposed architecture is incorrect.
Since the wrong region pair is identified and synchronous replication is incorrectly assumed, the statement is false.

Key Concept

Azure Region Pairs and cross-region replication characteristics
Rate this question