Study guide
6.2 Unstructured Data Storage 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.2 Unstructured Data Storage Design
Key Takeaways Explain This Topic AI
Blob Storage, Azure Files, and Data Lake Storage (ADLS) Gen2 are Azure's three unstructured-data services; ADLS Gen2 is not a separate service but Blob Storage with hierarchical namespace enabled.
Azure Files supports SMB (Windows, Linux, macOS) and NFS (Linux-only) protocols and is the default answer whenever an app needs to mount a drive letter or UNC path.
Azure Files does not support RA-GRS or RA-GZRS, so it has no continuously readable secondary region.
ADLS Gen2's hierarchical namespace enables POSIX-style ACLs at the file/directory level and Hadoop-compatible access via the ABFS driver used by Spark, Hive, and Synapse.
Azure File Sync caches an Azure file share on an on-premises Windows Server, the standard pattern for replacing an aging on-prem file server without losing local performance.
Last updated: July 2026
Why Unstructured Data Storage Decisions Matter on AZ-305
Not all data fits a document or table model. Video files, log archives, virtual machine disks, medical images, and lift-and-shift file shares are all unstructured data — bytes with no enforced internal schema. The "Recommend a solution for storing unstructured data" objective tests whether you can route a scenario to the right one of Azure's three unstructured storage services on the first read: Blob Storage , Azure Files , and Azure Data Lake Storage (ADLS) Gen2 .
Azure Blob Storage: The Default Object Store
Blob Storage stores unstructured data as objects (blobs) inside containers within a storage account. There are three blob types:
- Blob type Use case
- Block blobs Most common; large binary objects such as images, video, documents, and backups
- Append blobs Optimized for append-only operations, such as logging
- Page blobs Random read/write access; backs Azure managed and unmanaged disks (VM VHDs)
Blob Storage is accessed via REST calls or an SDK — it is not natively mountable as a network drive. That gap is exactly why Azure Files exists.
Azure Files: A Real File Share in the Cloud
Azure Files provides fully managed file shares accessed over SMB (Windows, Linux, and macOS clients) or NFS (Linux clients only), plus a REST API. Because it behaves like a traditional file server, it is the default choice whenever a scenario says the application or its users expect to mount a drive letter or a UNC path .
Tier Backing media Best for
Premium SSD, provisioned IOPS/throughput Latency-sensitive workloads — databases on file shares, high-transaction workloads
- Standard: Transaction Optimized HDD General-purpose transaction-heavy workloads
- Standard: Hot HDD Frequently accessed general-purpose file shares
- Standard: Cool HDD Infrequently accessed data, backup archives
Identity-based access uses Microsoft Entra Domain Services , on-premises Active Directory Domain Services (AD DS) , or Microsoft Entra Kerberos — a hybrid-identity design point revisited in Chapter 3's authorization coverage. Azure File Sync caches an Azure file share on an on-premises Windows Server so branch offices keep local read/write performance while the cloud share remains the source of truth — the standard answer for "replace an aging on-prem file server without losing local performance."
Trap: Azure Files does not support RA-GRS or RA-GZRS (there is no continuously readable secondary), and NFS shares are Linux-only — a requirement for Windows NFS clients should route you back to SMB, or to a different service entirely.
Azure Data Lake Storage Gen2: Analytics at Object-Storage Scale and Price
ADLS Gen2 is not a separate service — it is a set of capabilities layered on top of Blob Storage, unlocked by enabling hierarchical namespace (HNS) on the storage account. HNS turns a flat container of blobs into a true directory tree, which makes operations like renaming or deleting a folder a single atomic metadata operation instead of an expensive per-object enumeration across every blob sharing that name prefix.
Key ADLS Gen2 characteristics:
Hadoop-compatible access via the Azure Blob File System (ABFS) driver, used by Spark, Hive, and other HDFS-based frameworks — this is the answer whenever a scenario mentions Hadoop, Spark, Databricks, or Synapse Analytics reading raw files.
POSIX-style access control lists (ACLs) at the file and directory level, layered on top of Azure RBAC, giving finer-grained security than plain Blob Storage containers offer.
Massive scalability — no imposed limits on account size or file count; individual files can range from a few KB to hundreds of TB.
Inherits Blob Storage's tiering, lifecycle management, and redundancy options, because it is Blob Storage underneath — covered in the next section.
Choosing Between the Three
- Requirement in the scenario Choose
- "Mount a drive/share," "lift-and-shift file server," "SMB/NFS clients" Azure Files
- "Store images/video/backups," "REST/SDK access," "CDN origin" Blob Storage
"Hadoop/Spark/Databricks/Synapse," "data lake," "fine-grained file-level security for analytics" ADLS Gen2 (Blob Storage + hierarchical namespace)
Storage Account Types and Protocol Nuances
The service you get depends partly on the storage account type selected at creation:
Account type What it unlocks
General-purpose v2 ( StorageV2 ) Blob, Files, Queue, and Table in one account; supports hierarchical namespace for ADLS Gen2
Premium block blobs ( BlockBlobStorage ) SSD-backed block/append blobs for high-transaction, low-latency workloads
Premium file shares ( FileStorage ) SSD-backed Azure Files exclusively, for the Premium tier
A subtler exam trap: Blob Storage accounts with hierarchical namespace enabled can also expose data over the NFS 3.0 protocol directly (distinct from Azure Files' NFS support), which is useful for Linux-based big-data or HPC workloads that need POSIX file semantics against object storage without paying for a separate file-share service. Similarly, SFTP can be enabled directly on a Blob Storage account with hierarchical namespace, letting external partners upload files without provisioning a dedicated FTP server. Both NFS 3.0 and SFTP endpoints require hierarchical namespace to be enabled — another reason ADLS Gen2's HNS setting keeps reappearing across different unstructured-data requirements on the exam, not just analytics ones.
Scenario Walkthrough
A media company stores 500 TB of raw video assets that data scientists analyze with Databricks notebooks. They need directory-level access control so that only the analytics team can see the "raw" folder while marketing can browse only the "published" folder.
Design: a standard Blob Storage account with hierarchical namespace enabled (ADLS Gen2), because the workload needs both Hadoop-compatible (Databricks) access and folder-level POSIX ACLs — a plain Blob Storage container has no concept of folder-scoped permissions this granular; it can only apply access at the container or blob level.
Key Takeaways Recap
Blob Storage is the generic object store; Azure Files is for anything expecting a real file system over SMB or NFS; ADLS Gen2 is Blob Storage with hierarchical namespace turned on for big-data analytics and folder-level security. All three share the same underlying access-tier and redundancy model covered next in Section 6.3.