Study guide
6.4 Unstructured Data Protection & Durability 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.4 Unstructured Data Protection & Durability Design
Key Takeaways Explain This Topic AI
Blob soft delete keeps deleted or overwritten blobs, snapshots, or versions recoverable for a configurable 1-365 day retention period via the Undelete Blob operation.
Soft delete does not protect against container deletion (needs container soft delete) or storage account deletion (needs a resource lock).
Blob versioning automatically creates an immutable previous version on every overwrite and is the prerequisite for point-in-time restore of block blobs.
Immutable (WORM) storage offers time-based retention (1 day to 146,000 days) or legal hold policies that block modification/deletion by anyone, including the account owner, and support SEC Rule 17a-4(f), FINRA Rule 4511, and CFTC Rule 1.31(d) compliance.
Immutability policies are incompatible with point-in-time restore, so regulatory-grade tamper protection and full historical rollback cannot be combined on the same data.
Last updated: July 2026
Why Protection and Durability Design Matters on AZ-305
Redundancy (Section 6.3) protects against hardware and datacenter failure — it does nothing to protect against a user or attacker deleting or encrypting your data on purpose . The "Recommend a data solution for protection and durability" objective tests a different, narrower layer of defense: soft delete , versioning , and immutable (WORM) storage — each aimed at a specific failure mode, and frequently combined in ransomware-resilience and regulatory-compliance scenarios.
Blob Soft Delete: Undo for Accidental Deletes and Overwrites
Soft delete keeps a deleted or overwritten blob, snapshot, or version recoverable for a configurable retention period of 1 to 365 days . During that window, the Undelete Blob operation restores it; after the window expires, it is permanently gone.
What soft delete protects against: an application bug or a person accidentally deleting or overwriting a blob.
What it does not protect against: deletion of the container itself (enable container soft delete separately) or deletion of the storage account (only a resource lock on the account prevents that).
Blob Versioning: An Automatic History, Not Just an Undo Button
Blob versioning , when enabled, automatically creates a new immutable previous version every time a blob is overwritten — with no application code changes required. Combined with soft delete, deleting the "current" version simply promotes the most recent previous version to current, rather than losing the data outright.
Versioning is also the prerequisite for point-in-time restore for block blobs, which lets an administrator roll an entire container (or a prefix within it) back to its exact state at any point within the retention window — the strongest answer to "recover from a ransomware attack that corrupted thousands of blobs at once."
Immutable Storage: WORM for Regulatory Compliance
Immutable storage (Write Once, Read Many — WORM ) is the strongest protection tier: while an immutability policy is active, data cannot be modified or deleted by anyone , including the storage account owner. There are two policy types:
Policy type Behavior Use when
Time-based retention Locks data for a fixed interval (1 day to 146,000 days, or roughly 400 years) A known regulatory retention period, e.g. "retain trade records for 7 years"
Legal hold Locks data until a named tag is explicitly cleared The retention period is unknown in advance — active litigation or an investigation
Both can be scoped at container level (one policy applies to the whole container, and is supported on ADLS Gen2/hierarchical-namespace accounts) or version level (per-account, per-container, or per-blob-version granularity — requires versioning, and is not yet supported on hierarchical-namespace/ADLS Gen2 accounts ).
A time-based retention policy starts unlocked (for testing only) and must be locked to be compliant with regulations such as SEC Rule 17a-4(f) , FINRA Rule 4511 , and CFTC Rule 1.31(d) — all commonly named in financial-services AZ-305 scenarios. Once locked, the retention period can only be extended , never shortened, and a locked container can only be deleted once it is empty.
Trap: immutability policies are incompatible with point-in-time restore . You cannot combine "roll back to any moment" recovery with "nobody can ever modify this data" compliance on the same data, because point-in-time restore is itself a form of modification.
Tracking Immutability at Scale
For accounts with many containers and blobs, Azure Storage blob inventory generates a daily report listing every blob, snapshot, and version along with whether it currently has an immutability policy applied. This is the standard answer whenever a scenario asks how to prove, for audit purposes, which objects are actually protected — manually enumerating containers does not scale, and the inventory report is purpose-built for that governance need. A related nuance: version-level immutability policies specifically are not compatible with blob inventory on the same account, so an architect choosing version-level WORM for granular per-blob retention needs a different auditing approach, typically the policy's own audit log (which records up to seven time-based retention commands per container, including user ID, command type, and timestamps).
Building a Layered Protection Strategy
A defense-in-depth answer for "protect blob data end-to-end" typically stacks:
Soft delete + container soft delete — undo accidental application-level mistakes.
Versioning — automatic history and the basis for point-in-time restore.
Immutable storage (locked time-based retention) — regulatory-grade tamper protection for records that must never change.
Resource lock on the storage account — the only control that stops the account itself from being deleted.
Azure Backup for blobs (operational or vaulted) — an additional layer outside the storage account itself, useful when the requirement extends to protecting against the loss of the account or subscription, not just individual objects.
Scenario Walkthrough
A broker-dealer must retain trade confirmation records for 7 years in a state that satisfies SEC 17a-4(f), while also protecting the storage account from accidental deletion by an over-privileged administrator.
Design: enable blob soft delete for day-to-day protection, then apply a container-level, locked, time-based retention policy set to a 7-year (2,555-day) retention interval for the compliance requirement, and add a resource lock (CanNotDelete) on the storage account so the account itself cannot be removed regardless of a user's RBAC permissions.
Key Takeaways Recap
Soft delete undoes mistakes, versioning gives you an automatic rollback history, and immutable storage is the only layer that survives a malicious or over-privileged administrator. Pick the layer — or combination of layers — that matches the actual threat named in the scenario, not just "more protection is always better."