Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Azure Region Pairs for In-Country Disaster Recovery
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An enterprise is planning a disaster recovery and backup strategy for critical business data hosted in Microsoft Azure. The organization must ensure that backup data replicates hundreds of miles away to protect against major geographic disasters, while strictly keeping all data within the same national boundary to meet legal data residency and compliance requirements.
Which Azure architectural component satisfies these requirements?
Explanations
Resource groups
Resource groups
What Resource Groups Are
A resource group is a logical container in Azure used to deploy, manage, organize, and monitor related Azure resources as a single unit.
Why It Doesn't Meet the Requirement
Resource groups are administrative and management boundaries, not physical or geographical architectures. They do not replicate data across hundreds of miles, nor do they manage disaster recovery failovers between geographic locations.
Key Characteristics and Limitations
- Logical Organization: Used for life-cycle management, access control (RBAC), and tagging.
- No Redundancy Capability: A resource group itself does not provide data replication or backup capabilities.
- Location-Specific Metadata: While a resource group has a location where its metadata is stored, it can contain resources deployed across various regions.
This Answer Would Be Correct If
The company needed a way to manage, organize, and apply access controls to a collection of cloud resources as a single administrative unit.
Additional Context
Resources contained within a single resource group can be provisioned in different paired regions, but the resource group itself does not perform data replication or failover.
Region pairs
Region pairs
What Region Pairs Are
An Azure region pair consists of two regions within the same geographic boundary (such as the same country or geopolitical jurisdiction) that are situated hundreds of miles apart. Microsoft links these pairs directly to enable high availability, automatic geo-redundant data replication, and streamlined disaster recovery coordination.
How It Meets the Requirements
- Geographic Distance: Paired regions are typically separated by at least 300 miles (hundreds of miles), ensuring that large-scale disasters such as severe weather, power grid failures, or regional outages do not affect both regions simultaneously.
- Data Residency and Compliance: Azure pairs regions residing within the same geopolitical and regulatory boundary (with rare exceptions like Brazil South), ensuring that replicated data stays compliant with local tax, legal, and data governance laws.
Key Advantages and Capabilities
- Sequential System Updates: Azure rolls out platform updates to only one region in a pair at a time to minimize downtime and prevent update-related outages across both locations.
- Physical Isolation: Datacenters in paired regions operate on independent power, cooling, and network infrastructure.
- Recovery Prioritization: In the event of a broad multi-region outage, Azure prioritizes the recovery of at least one region from each pair to guarantee service restoration.
- Native Platform Replication: Built-in storage tiers, such as Geo-Redundant Storage (GRS) and Geo-Zone-Redundant Storage (GZRS), automatically replicate data across the paired region.
Why This Is Optimal
Region pairs directly solve the challenge of achieving cross-region disaster recovery without violating data sovereignty or compliance laws, providing an automated and synchronized failover architecture.
Availability Zones
Availability Zones
What Availability Zones Are
Availability Zones are physically separate datacenters located within the same Azure region. Each zone has its own independent power, cooling, and networking infrastructure to protect applications from localized datacenter failures.
Why It Doesn't Meet the Requirement
Availability Zones are typically separated by only several kilometers (up to approximately 100 kilometers) within the same metropolitan region. While they provide resilience against single datacenter failures, they do not provide protection against broad, regional catastrophes (like major natural disasters or regional power grid collapses) that require multi-hundred-mile geographic separation.
Key Characteristics and Limitations
- Intra-region Focus: Confined to a single geographic region rather than spanning hundreds of miles.
- Low Latency: Optimized for low-latency synchronization between datacenters within the same metropolitan boundary.
- Zonal and Zone-Redundant Support: Protects against hardware, power, or localized network failures within a single region.
This Answer Would Be Correct If
The organization needed high availability across distinct datacenters with low latency within a single metropolitan region.
Additional Context
Availability Zones and region pairs complement each other; architectures often combine Availability Zones for high availability within a region and region pairs for disaster recovery across regions.
Sovereign regions
Sovereign regions
What Sovereign Regions Are
Sovereign regions (also known as dedicated cloud environments) are physically and logically isolated instances of Azure created specifically to meet stringent security, sovereignty, and regulatory requirements. Examples include Azure Government (for US government entities) and Azure China 21Vianet.
Why It Doesn't Meet the Requirement
Sovereign regions represent separate physical and logical cloud instances rather than an architectural pairing mechanism for geo-replication and disaster recovery. Standard commercial enterprises operating within public Azure regions cannot simply rely on sovereign regions to pair standard workloads for cross-region disaster recovery.
Key Characteristics and Limitations
- Isolated Clouds: Completely separated from standard public Azure datacenters.
- Specific Access Controls: Require specialized agreements and screening to provision workloads.
- Compliance Focus: Designed for specific government or sovereign jurisdictional standards rather than general multi-region pairing.
This Answer Would Be Correct If
The scenario involved a government agency requiring a dedicated cloud instance with specialized compliance controls separated entirely from public Azure infrastructure.
Additional Context
Sovereign clouds maintain their own distinct region pairs within their isolated boundaries, but the term itself does not define the paired replication mechanism.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Regional Pairs Data Residency
Describe Azure regions, region pairs, and sovereign regions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Government
Describe Azure regions, region pairs, and sovereign regions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Regions
Describe Azure regions, region pairs, and sovereign regions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Site Recovery
Describe Azure regions, region pairs, and sovereign regions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Locally Redundant Storage
Describe redundancy options
IntermediateAZ-204 Developing Solutions for Microsoft Azure Exam
Azure Blob System Properties vs User-Defined Metadata
Set and retrieve properties and metadata
Last updated Validated