AZ-305 Design data storage solutions Practice Question
Which TWO Azure services can be used to store unstructured data such as documents, images, and videos?
⚠ Common exam trap
Candidates often confuse Azure Files (a file share service) with unstructured storage, but Azure Files is for structured file sharing with SMB/NFS, not for object storage of documents, images, and videos.
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 Blob Storage
Azure Blob Storage is designed for storing massive amounts of unstructured data, such as documents, images, and videos, as objects (blobs) in a flat namespace. It supports three types of blobs (block, append, and page) and provides REST APIs for access, making it ideal for scalable, cost-effective storage of binary and text data.
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 this is correct
Azure Blob Storage is Microsoft's object storage solution, specifically engineered to store and serve massive amounts of unstructured data—such as images, videos, documents, logs, and backup files—at global scale. It exposes REST-based HTTP(S) endpoints, supports lifecycle management across hot/cool/archive access tiers, and provides cost-effective redundancy options. Because each object is addressed by a unique URL and stored without a required schema, Blob Storage is the canonical service for unstructured data in Azure.
- ✗
Azure Files
Why it's wrong here
Azure Files provides fully managed file shares in the cloud that speak the industry-standard SMB and NFS protocols, allowing resources to be mounted as network drives on Windows, Linux, and macOS machines. Although the underlying file data may be arbitrary bytes, the service imposes a hierarchical, directory-based structure optimized for shared file access in lift-and-shift or hybrid scenarios. It is not designed to be a general-purpose, schema-independent object store for massive unstructured repositories—it remains fundamentally a network file share.
- ✗
Azure SQL Database
Why it's wrong here
Azure SQL Database is a relational database engine that enforces a fixed schema on write, organizing all data into tables, rows, and columns with primary and foreign key constraints. Even though it technically supports BLOB data types for binary content, storing large volumes of unstructured data there would incur substantial overhead in query planning, indexing, and transaction logging, which are all designed for structured, ACID-compliant workloads. Relational engines are purpose-built for normalized structured data, not for hosting unstructured content like media libraries or data lakes.
- ✓
Azure Data Lake Storage Gen2
Why this is correct
Azure Data Lake Storage Gen2 is built directly on top of Azure Blob Storage, combining the object-store scalability and low-cost design of Blob with a hierarchical file system and POSIX permissions. It is optimized for big-data analytics, enabling petabyte-scale ingestion of unstructured and semi-structured files such as JSON, Parquet, CSV, images, and video, while preserving directory-level operations and role-based access controls. As a superset of Blob Storage, it absolutely qualifies as a service for storing unstructured data, particularly for analytics pipelines.
- ✗
Azure Cosmos DB
Why it's wrong here
Azure Cosmos DB is a multi-model NoSQL database that handles schema-agnostic data in the form of JSON documents, key-value pairs, column-family tables, and graphs, but it is not an object store for raw binary files. Its flexibility lies in accommodating evolving document schemas and supporting rich queries on indexable fields, not in storing or serving unstructured blobs at massive scale. Storing large binaries or free-form data in Cosmos DB would be a misuse—object storage like Azure Blob is the appropriate choice for truly unstructured content.
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
This AZ-305 question is part of Courseiva's 795-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.