AZ-305 Design data storage solutions Practice Question
A company is building a big data analytics platform that will process structured, semi-structured, and unstructured data using Azure Synapse Analytics and other tools. They need a storage layer that supports hierarchical namespaces and fine-grained access control at the directory level. Which Azure storage solution should they use?
⚠ Common exam trap
Test-takers frequently confuse Azure Blob Storage with ADLS Gen2, assuming blob storage supports hierarchical namespaces natively, but it requires explicit enabling of the hierarchical namespace feature, which is only available in ADLS Gen2 accounts.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure Data Lake Storage Gen2
Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct choice because it combines Azure Blob Storage with a hierarchical namespace, enabling directory-level access control lists (ACLs) and POSIX-compliant permissions. This is essential for the big data analytics platform described, as it must support structured, semi-structured, and unstructured data with fine-grained access control at the directory level, which Azure Synapse Analytics can directly query via ABFS (Azure Blob File System) driver.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Azure Blob Storage
Why it's wrong here
Azure Blob Storage offers a flat namespace in which all files are stored as blobs within containers, lacking a true directory hierarchy. This absence of a hierarchical namespace makes directory-level operations like rename, delete, or move inefficient because they require enumerating and updating individual blobs, and access control is limited to container-level or blob-level ACLs rather than fine-grained directory-scoped permissions. Consequently, while Blob Storage can store data, it does not meet the metadata and security requirements essential for a big data analytics platform.
- ✓
Azure Data Lake Storage Gen2
Why this is correct
Azure Data Lake Storage Gen2 is the correct choice because it combines the scalability and cost-effectiveness of Blob Storage with a hierarchical namespace that organizes data into directories, enabling efficient atomic operations and fast path-based access. It also supports POSIX-compliant ACLs at both file and directory levels, allowing fine-grained security that matches the needs of multi-tenant analytics workloads. Its native integration with Hadoop, Spark, Databricks, and Azure Synapse makes it the optimal storage layer for big data analytics, as it provides high throughput and parallel processing capabilities.
- ✗
Azure Files
Why it's wrong here
Azure Files delivers SMB and NFS file shares primarily for lifting and shifting on-premises file servers or sharing files among virtual machines, with a design centered around latency-sensitive, interactive workloads. It does not provide a hierarchical namespace with analytical semantics (like directory rename as a single operation) nor the high-throughput parallel data access patterns required by analytics engines. Using Azure Files for big data pipelines would incur capacity and performance limits, and its protocol overhead makes it ill-suited for petabyte-scale analytical processing.
- ✗
Azure Cosmos DB
Why it's wrong here
Azure Cosmos DB is a globally distributed, multi-model NoSQL database optimized for transactional, low-latency workloads with predictable performance, not for storing and analyzing huge volumes of raw or semi-structured data for batch analytics. It lacks a hierarchical storage namespace and its access model is read-based via CRUD operations or SQL queries, whereas big data analytics requires in-place, columnar or data lake–style scanning across datasets. Additionally, its cost model charges per request unit, making scanning massive datasets prohibitively expensive compared to a data lake storage purpose-built for analytical queries.
Visual reference
Quick reference
Azure Blob Storage Tier Comparison
| Tier | Storage Cost | Retrieval Cost | Latency | Use Case |
|---|---|---|---|---|
| Hot | Highest | Lowest | Immediate | Active data, frequent reads |
| Cool | Lower | Higher | Immediate | Data accessed < once / month |
| Cold | Lower still | Higher | Immediate | Data accessed < once / quarter |
| Archive | Lowest | Highest + rehydration delay | Hours | Long-term compliance retention |
Go deeper
Related to this question
About these practice questions
One of 795 original AZ-305 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-305 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-305 exam.