Question 572 of 881
AZ-204 Develop for Azure storage Practice Question
You are building a serverless application that needs to store user profile data. The data includes simple fields like name, email, and preferences. The data is frequently accessed by user ID. You need a schema-less, low-latency storage solution that is cost-effective for millions of small records. Which Azure Storage solution should you use?
⚠ Common exam trap
A common mix-up: candidates confuse Azure Table Storage with Azure Cosmos DB for Table API, but the question specifically asks for a cost-effective solution for millions of small records, and Azure Table Storage (part of Azure Storage account) is the cheaper, schema-less option without the premium features and higher cost of Cosmos DB.
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 Table Storage
Azure Table Storage is a NoSQL key-value store that is schema-less, making it ideal for storing user profile data with varying fields like name, email, and preferences. It offers low-latency access by user ID via the PartitionKey and RowKey, and it is cost-effective for millions of small records because you pay only for the storage consumed, with no minimum charge per record.
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 is primarily designed for storing large amounts of unstructured data, such as images, videos, documents, or log files. While it can store any type of data as a blob, it lacks native indexing or querying capabilities for structured key-value pairs. Storing user profiles here would require each profile to be a separate blob, necessitating custom serialization/deserialization and inefficient listing or filtering without an external indexing mechanism, making it unsuitable for direct key-value access.
- ✗
Azure Queue Storage
Why it's wrong here
Azure Queue Storage is specifically engineered for asynchronous message passing between decoupled application components, facilitating communication and workflow management. Its purpose is to temporarily store messages that are processed and then typically deleted, not to serve as a persistent data store for querying or retrieving user profiles on demand. It is designed for transient data in a message-oriented architecture, not for long-term, queryable data retention.
- ✓
Azure Table Storage
Why this is correct
Azure Table Storage is a NoSQL key-value store optimized for storing large amounts of structured, non-relational data with a flexible schema. It provides highly scalable and low-latency access to data, making it ideal for user profiles where a unique identifier, like a user ID, can serve as the RowKey or PartitionKey. This design allows for efficient retrieval of individual entities, perfectly aligning with the requirements for storing and quickly accessing user data in a serverless application.
- ✗
Azure File Storage
Why it's wrong here
Azure File Storage provides fully managed file shares in the cloud, accessible via the Server Message Block (SMB) protocol, primarily for 'lift-and-shift' scenarios or legacy applications requiring a file system interface. It is not optimized for programmatic, low-latency key-value lookups or structured data queries. Storing user profiles as individual files would introduce significant overhead for file system operations and parsing, making it inefficient for direct, high-performance data access in a serverless context.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This AZ-204 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-204 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.