Study guide
6.3 Storage Tier & Cost-Performance Trade-off 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
6.3 Storage Tier & Cost-Performance Trade-off Design
Key Takeaways Explain This Topic AI
Blob access tiers require minimum retention periods: Cool 30 days, Cold 90 days, and Archive 180 days on general-purpose v2 accounts; moving or deleting a blob early triggers a prorated early-deletion fee.
The Archive tier is offline and takes up to 15 hours to rehydrate to an online tier, and is only supported on LRS, GRS, and RA-GRS accounts (not ZRS, GZRS, or RA-GZRS).
LRS provides at least 11 nines durability within one datacenter; ZRS provides at least 12 nines across 3+ availability zones; GRS/GZRS provide at least 16 nines by adding an asynchronous copy in a paired region.
GRS and GZRS replicate to a Microsoft-paired region that may sit in a different jurisdiction, so data-residency requirements should be satisfied with LRS or ZRS instead.
Only RA-GRS and RA-GZRS provide continuous read access to the secondary region; plain GRS/GZRS require an account failover before any access to the secondary is possible.
Last updated: July 2026
Why Tier and Redundancy Decisions Matter on AZ-305
Every unstructured-data scenario on the exam eventually asks the same underlying question: how do we pay the least for the durability and access latency this workload actually needs? Two independent knobs answer that question: the blob's access tier (how often is it read?) and the storage account's redundancy configuration (how much regional or zone failure can we tolerate?). AZ-305 scenarios routinely combine both in a single question, so treat them as one design decision, not two.
Access Tiers: Hot, Cool, Cold, Archive
- Tier Minimum retention Latency (time to first byte) Storage cost Access/transaction cost
- Hot None Milliseconds Highest Lowest
- Cool 30 days Milliseconds Lower Higher
- Cold 90 days Milliseconds Lower still Higher still
- Archive 180 days Hours (rehydration required) Lowest Highest
Moving or deleting a blob before its minimum retention period has elapsed triggers a prorated early deletion fee . For example, a blob moved to the Cool tier and then deleted after 21 days is billed for the remaining 9 days (30 minus 21) of Cool-tier storage. An Archive-tier blob deleted after 45 days is billed for the remaining 135 days (180 minus 45) of Archive-tier storage — the fee always covers the gap between when the object was deleted and when the minimum retention period would have naturally elapsed.
Archive blobs are offline : they cannot be read or modified until rehydrated to Hot, Cool, or Cold. Rehydration can take up to 15 hours , with a choice between Standard and High rehydration priority (High costs more but completes faster). Lifecycle management policies automate these tier transitions with rules such as "move to Cool 30 days after last modification, move to Archive after 90 days" — this is the standard answer whenever a scenario wants automatic tiering without ongoing operational overhead .
Trap: the Archive tier is supported only on LRS, GRS, and RA-GRS accounts — not on ZRS, GZRS, or RA-GZRS. A scenario asking for zone-redundant archival storage in the same sentence is testing whether you catch this incompatibility; the correct response is to choose LRS or GRS for that workload, or to keep the data in Cold rather than Archive if zone redundancy is a hard requirement.
Redundancy: How Many Copies, and Where?
- Option Copies / scope Durability Protects against
- LRS (Locally Redundant) 3 copies, one physical datacenter At least 11 nines Drive, node, or rack failure only
ZRS (Zone-Redundant) 3+ copies across availability zones in one region At least 12 nines Datacenter/zone outage
GRS (Geo-Redundant) LRS in primary + asynchronous LRS copy in a paired region At least 16 nines Regional disaster (secondary not readable until failover)
GZRS (Geo-Zone-Redundant) ZRS in primary + asynchronous LRS copy in a paired region At least 16 nines Zone outage and regional disaster
RA-GRS / RA-GZRS GRS/GZRS + read access to the secondary Same as GRS/GZRS Adds continuous read availability during a primary-region outage
Two design rules the exam leans on hard:
Data-residency requirements override "more redundancy is always better." GRS and GZRS replicate to a Microsoft-paired region that can sit in a different jurisdiction. If regulation requires data to stay in-country, the correct answer is LRS or ZRS , not GRS "for extra safety" — defaulting to geo-redundant options for compliance-sensitive data is a classic AZ-305 trap answer.
A regional outage always requires an account failover to restore write access , even with GRS/GZRS. Only RA-GRS and RA-GZRS give you continuous read access without a failover, and even then writes remain unavailable in the primary region until the failover completes.
Changing Redundancy After the Fact
Redundancy is not always a one-time decision. Converting LRS to GRS is a self-service change in the Azure portal. Converting to or from ZRS , however, is a more involved migration (historically requiring a support request or a copy-based migration) because it changes how data is physically laid out across availability zones rather than simply adding an asynchronous replica. If a storage account already has blobs in the Archive tier , Microsoft recommends against changing its redundancy configuration at all, because every archived blob would first need to be rehydrated — a costly and slow operation — before the conversion could proceed. A newer smart tier capability can automatically move data between Hot, Cool, and Cold based on observed access patterns, which is a reasonable answer whenever a scenario wants tiering cost savings without hand-authoring lifecycle management rules, though it does not extend to the offline Archive tier.
Scenario Walkthrough
A hospital system stores 10 years of diagnostic imaging that is essentially never re-read after the first 6 months, but by law must never leave the country and must survive a full regional Azure outage.
Design: this is a deliberately trap-heavy combination. "Survive a full regional outage" argues for GRS or GZRS, but "must never leave the country" rules both out — the correct answer is ZRS (survives a datacenter/zone failure and satisfies the data-residency constraint) combined with a lifecycle management policy that tiers data to Cool at 30 days and Cold at 90 days — not Archive, since 6-month-old imaging may still need occasional retrieval at millisecond, not multi-hour, latency.
Key Takeaways Recap
Tier decisions trade storage cost against access cost and latency; redundancy decisions trade cost against blast-radius protection. The two most commonly tested traps in this pairing are the Archive-tier redundancy restriction (LRS/GRS/RA-GRS only) and the conflict between geo-replication and data-residency requirements, where LRS or ZRS is the correct answer despite GRS sounding "safer."