Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Azure Regional Pairs Keep Data in the Same Geography
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.
A financial services organization is planning to deploy a mission-critical workload to Azure. The architecture requires multi-region disaster recovery and geo-redundant data replication to ensure business continuity in the event of a regional disaster.
Due to strict financial regulations and government compliance mandates, customer data must remain within the same national and legal jurisdiction at all times.
Which architectural feature of Azure ensures that automated cross-region replication meets these data residency and compliance requirements?
Explanations
Single-zone deployment within a single Azure datacenter
Single-zone deployment within a single Azure datacenter
What Single-Zone Deployment Is
A single-zone deployment runs an entire workload and its associated data inside one standalone datacenter within a specific Azure region. It does not use secondary datacenters, Availability Zones, or secondary regions for redundant infrastructure.
Why It Doesn't Meet the Requirement
While deploying inside a single zone keeps data in the local region and prevents cross-border data transfer, it completely fails to fulfill the scenario's critical requirement for multi-region disaster recovery and automated geo-replication. If the single datacenter suffers a power loss, flood, or hardware failure, the entire workload will experience downtime and potential data loss.
Key Characteristics and Limitations
- Single Point of Failure: Entire infrastructure is susceptible to facility-level disruptions.
- No Multi-Region Resiliency: Fails to provide business continuity during catastrophic regional events.
- Low Implementation Complexity: Simple to configure but offers the lowest availability tier for enterprise systems.
This Answer Would Be Correct If
The organization required the simplest, lowest-cost deployment model and had no requirements for high availability, failover, or disaster recovery.
Additional Context
High availability and compliance must be balanced. Selecting regional pairs within the same country provides both disaster recovery and data residency without sacrificing reliability.
Cross-subscription resource group migration
Cross-subscription resource group migration
What Cross-Subscription Resource Group Migration Is
Resource migration across subscriptions allows administrators to move existing Azure resources, such as virtual machines, storage accounts, and virtual networks, from one Azure subscription to another within the same tenant using Azure Resource Manager.
Why It Doesn't Meet the Requirement
Moving resources across subscriptions is an administrative and governance operation; it is not a disaster recovery or data redundancy mechanism. It does not replicate data across physical regions, nor does it address continuous automated failover or automated compliance controls for data residency.
Key Characteristics and Limitations
- Management Boundary Operation: Changes ownership, billing allocation, and governance scopes of resources.
- No Active Replication: Does not perform real-time data synchronization between separate geographic locations.
- Manual or Scripted Process: Executed on demand rather than functioning as an automated disaster recovery solution.
This Answer Would Be Correct If
The company needed to transfer ownership of an existing workload from a development subscription to a dedicated production subscription for billing purposes.
Additional Context
Subscriptions serve as containers for billing and access control, whereas regions, availability zones, and regional pairs define the physical and geographic boundaries of deployed infrastructure.
Azure regional pairs located within the same geographic boundary
Azure regional pairs located within the same geographic boundary
What Azure Regional Pairs Are
Azure regional pairs consist of two distinct Azure regions within the same broader geographic area that are connected through Microsoft's dedicated high-speed network. Microsoft intentionally designs region pairs to enable seamless disaster recovery, automated cross-region replication (such as Geo-Redundant Storage (GRS)), and coordinated platform maintenance while maintaining geographic isolation between datacenters.
How It Meets the Data Residency Requirement
With the exception of Brazil South (which pairs with South Central US), Azure regional pairs are permanently situated within the same geographic and political boundary (such as within the United States, Europe, Canada, or Australia). This intentional design guarantees that when data is asynchronously replicated across regions for business continuity, it never crosses national borders, directly fulfilling data residency, tax compliance, and law enforcement jurisdiction mandates.
Key Advantages and Capabilities
- Data Residency Compliance: Guarantees that data at rest and in transit between paired regions stays within defined legal borders.
- Disaster Isolation: Paired regions are typically separated by at least 300 miles to prevent simultaneous impact from localized natural disasters or power outages.
- Sequential Updates: Azure rolls out planned platform updates sequentially across pairs, ensuring only one region is updated at a time.
- Priority Recovery: In the event of a broad multi-region outage, Azure prioritizes at least one region in each pair for rapid restoration.
Why This Is Optimal
Utilizing regional pairs allows organizations to achieve high availability and disaster recovery without violating strict data privacy and residency laws. It gives businesses enterprise-grade reliability while maintaining full compliance with local regulatory frameworks.
Global dynamic traffic distribution across international regions
Global dynamic traffic distribution across international regions
What Global Dynamic Traffic Distribution Does
Global dynamic traffic distribution uses services like Azure Traffic Manager or Azure Front Door to route user requests across different Azure regions around the world. These services optimize application performance and latency by sending users to the closest available endpoint based on real-time routing algorithms.
Why It Doesn't Meet the Requirement
Distributing traffic across international regions directly violates data residency and jurisdictional constraints. If an application or its database routes requests or synchronizes customer records across international borders, the organization becomes subject to foreign data privacy laws and fails local regulatory compliance rules requiring all data to remain within a specific national jurisdiction.
Key Characteristics and Limitations
- Worldwide Routing: Designed to direct traffic to endpoints across global geographies rather than confining operations to a single country.
- No Inherent Data Residency Controls: Traffic routing tools do not enforce physical storage location boundaries on their own.
- Latency Focused: Primary goal is reducing user latency and offering global failover rather than adhering to jurisdictional containment.
This Answer Would Be Correct If
The organization wanted to route international customers to the nearest regional endpoint across the globe without any restrictions on cross-border data transfer.
Additional Context
Global traffic routing solutions can be configured with geographic routing profiles, but they do not replace the underlying storage boundary provided by paired regions located within the same geography.
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 Site Recovery
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 Region Pairs
Describe Azure regions, region pairs, and sovereign regions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure VM Stopped Deallocated Disk Billing
Describe factors that can affect costs in Azure
AdvancedAZ-104 Microsoft Azure Administrator Exam
Availability Zones High Availability
Deploy virtual machines to availability zones and availability sets
Last updated Validated