Study guide
9.4 Semi-Structured & Unstructured Data High Availability Design
Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Orientation
1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide
2 Chapter 2: Logging, Monitoring & Diagnostics Design
2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design
3 Chapter 3: Authentication & Authorization Design
3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design
4 Chapter 4: Governance, Compliance & Identity Governance Design
4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design
5 Chapter 5: Relational Data Storage Design
5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design
6 Chapter 6: Semi-Structured & Unstructured Data Storage Design
6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design
7 Chapter 7: Data Integration & Analytics Design
7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design
8 Chapter 8: Backup & Disaster Recovery Design
8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design
9 Chapter 9: High Availability Design
9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design
10 Chapter 10: Compute Solution Design
10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)
11 Chapter 11: Application Architecture Design
11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)
12 Chapter 12: Migration Design
12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)
13 Chapter 13: Network Solution Design
13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design
14 Chapter 14: Final Review, Exam Strategy & Career Path
14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path
9.4 Semi-Structured & Unstructured Data High Availability Design
Key Takeaways Explain This Topic AI
Azure Cosmos DB availability is driven by three independent choices: consistency level, zone redundancy, and single- vs. multi-region write topology — each affects your effective SLA and RPO.
Strong consistency requires 2+ regions for dynamic quorum but is incompatible with multi-region writes; only single-write-region accounts can use Strong consistency.
Per-partition automatic failover (PPAF) lets a single-write-region Cosmos DB account fail over individual partitions to a secondary region automatically, typically within about 3 minutes, without losing data at Strong consistency.
Azure Storage's four core redundancy tiers form a durability ladder: LRS (11 nines, single datacenter), ZRS (12 nines, 3+ zones), GRS (16 nines, +secondary region, async), GZRS (16 nines, zones + region).
Only RA-GRS and RA-GZRS grant read access to the secondary region without a failover; plain GRS/GZRS data in the secondary is invisible to applications until you trigger an account failover.
Last updated: July 2026
Why This Topic Matters
This is the last of the four high-availability sections in Domain 3, and it closes the loop with the non-relational services from Domain 2 (Cosmos DB, Blob Storage, Azure Files). AZ-305 pairs these services with scenario language like "must survive a region outage with no data loss" or "must remain writable in every region" — and the correct answer usually hinges on a subtle interaction (e.g., Strong consistency being incompatible with multi-region writes) that a candidate who only memorized service names will miss.
Cosmos DB: Zone Redundancy, Consistency, and Write Topology
Zone redundancy for Cosmos DB works like other Azure services — it replicates a region's data across Availability Zones with no impact on performance or latency and no application changes required . Microsoft recommends enabling it wherever supported, especially for single-region accounts, because it raises the account's availability SLA above the non-zone-redundant baseline.
Consistency level interacts directly with multi-region behavior. Cosmos DB offers five levels (Strong, Bounded Staleness, Session, Consistent Prefix, Eventual), but for HA design the critical rule is: Strong consistency is only available for single-write-region accounts , because it requires synchronous quorum writes across 2+ regions, and quorum cannot be maintained once multiple regions are simultaneously accepting writes.
Write topology is the core design fork:
Single-region writes, multi-region reads: one write region, any number of read regions. Supports Strong consistency. Failure recovery options include per-partition automatic failover (PPAF) — individual partitions fail over to a healthy region automatically, typically completing in about 3 minutes , with no data loss if the account uses Strong consistency — and service-managed failover , which is slower (can take an hour or more) and manual forced failover , which is the recommended way to restore availability quickly during a real outage.
Multi-region writes ("multi-master"): every configured region can accept writes. This gives the lowest write latency globally and the best write availability, but data is replicated asynchronously between regions, Strong consistency is not supported , and concurrent writes to the same item in different regions can conflict — Cosmos DB resolves these using a configurable conflict resolution policy , with a designated hub region acting as tie-breaker.
Topology Consistency support Failure recovery Best for
Single-region write, multi-region read All 5 levels, including Strong PPAF (~3 min, no data loss at Strong) or forced failover Workloads needing Strong consistency with global read scale
Multi-region write All except Strong Automatic SDK re-routing to healthy regions Globally distributed apps needing local low-latency writes everywhere
Azure Storage: The Redundancy Ladder
Unstructured and semi-structured object storage (Blob, Files, Tables, Queues, and managed disks where supported) shares a single redundancy model with four core SKUs:
SKU Replication Durability (per year) Read availability Survives zone loss? Survives region loss?
- LRS (Locally Redundant) 3 copies, 1 datacenter ≥99.999999999% (11 nines) ≥99.9% No No
- ZRS (Zone-Redundant) Synchronous, 3+ zones, 1 region ≥99.9999999999% (12 nines) ≥99.9% Yes No
GRS (Geo-Redundant) LRS in primary + async copy (LRS) in secondary region ≥99.99999999999999% (16 nines) ≥99.9% (secondary not readable) Yes (secondary intact) Yes, after failover
GZRS (Geo-Zone-Redundant) ZRS in primary + async copy (LRS) in secondary region ≥99.99999999999999% (16 nines) ≥99.9% (secondary not readable) Yes Yes, after failover
Appending RA- (Read-Access) to GRS or GZRS — RA-GRS or RA-GZRS — is what actually lets an application read from the secondary region during a primary-region outage, without waiting for a failover; that raises read availability to ≥99.99% . Plain GRS/GZRS replicate the data for durability, but the secondary copy stays invisible to your application until you trigger an account failover , which is a customer-initiated (or, for a severe outage, Microsoft-initiated) operation that promotes the secondary region to primary. Azure Files does not support RA-GRS/RA-GZRS at all — only GRS/GZRS without the read-access option.
Exam Scenarios
Scenario 1: A globally distributed IoT ingestion pipeline needs to accept writes with low latency in three regions simultaneously and can tolerate eventual conflict resolution. Design decision : Cosmos DB with multi-region writes enabled and a custom conflict resolution policy — Strong consistency is off the table by definition here.
Scenario 2: A financial ledger requires Strong consistency and must recover a failed write region automatically within minutes with zero data loss. Design decision : single-write-region Cosmos DB with Strong consistency and per-partition automatic failover (PPAF) enabled — roughly 3-minute recovery, no data loss.
Scenario 3: An application stores compliance documents in Blob Storage and must continue serving read traffic from a secondary region during a declared primary-region outage, without performing a failover. Trap : choosing plain GRS looks sufficient because it "replicates to another region," but GRS alone gives no read access to that data — only RA-GRS (or RA-GZRS) satisfies the "read without failover" requirement.
Takeaways
Strong consistency and multi-region writes are mutually exclusive in Cosmos DB — this is one of the highest-yield facts in the entire business-continuity domain.
PPAF gives single-write-region Cosmos DB accounts near-automatic, ~3-minute, no-data-loss recovery at Strong consistency — know it as the modern alternative to slower service-managed failover.
Recite the storage durability ladder by nines: LRS 11, ZRS 12, GRS/GZRS 16 — and remember durability (won't lose the data) is a different promise than availability (can read/write it right now).
"Read access to the secondary" always means RA-GRS or RA-GZRS , never plain GRS/GZRS — and Azure Files never gets the RA option at all.