AZ-204 Develop for Azure storage Practice Question
You are developing a .NET Core application that stores session state data. The data is infrequently updated but must be read quickly for every user request. You need a serverless, globally distributed storage solution with low latency reads. Which Azure storage solution should you use?
⚠ Common exam trap
Many exam-takers choose Azure Redis Cache because of its reputation for low-latency caching, but they overlook the 'serverless' and 'globally distributed' requirements, which Redis Cache does not natively satisfy without manual configuration and provisioning, whereas Cosmos DB offers these features out of the box.
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 Cosmos DB with SQL API
Azure Cosmos DB with SQL API is the correct choice because it provides a globally distributed, serverless database service with single-digit millisecond read latency at any scale, making it ideal for infrequently updated session state that must be read quickly for every user request. Its multi-region replication ensures low-latency reads from any location, and the SQL API offers a familiar query interface for .NET Core applications.
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 Table Storage
Why it's wrong here
While Azure Table Storage is a cost-effective solution for storing large amounts of structured, non-relational data, it is not optimized for the low-latency, frequent read/write operations typical of session state. It lacks a strong latency Service Level Agreement (SLA) and does not offer built-in global distribution, requiring manual replication for multi-region scenarios. Its eventual consistency model can also be problematic for immediate session state updates, making it less suitable for interactive user sessions.
- ✓
Azure Cosmos DB with SQL API
Why this is correct
Azure Cosmos DB with the SQL API is an ideal choice for session state due to its guaranteed single-digit millisecond latency for both reads and writes, backed by comprehensive SLAs. It offers native global distribution with multi-region write capabilities, ensuring high availability and low latency for users worldwide without complex configuration. Furthermore, its serverless capacity model allows for automatic and cost-effective scaling based on demand, perfectly suiting dynamic session data requirements.
- ✗
Azure Redis Cache
Why it's wrong here
Azure Cache for Redis provides exceptionally low-latency, in-memory data access, making it highly performant for session state storage. However, it operates as a provisioned service, requiring users to select and pay for a specific cache tier, which can lead to inefficient resource utilization if not precisely matched to demand. While Redis can be globally distributed, this typically involves manual setup of geo-replication or multiple instances, adding significant operational complexity and configuration overhead compared to natively distributed solutions.
- ✗
Azure Blob Storage
Why it's wrong here
Azure Blob Storage is fundamentally designed for storing large, unstructured binary objects like media files, backups, or data lakes, prioritizing high throughput and cost-efficiency for these scenarios. It is not optimized for the small, frequent, and low-latency read/write operations that are crucial for effective session state management. Utilizing Blob Storage for session data would result in significantly higher access latencies and increased transaction costs, rendering it an inappropriate and inefficient choice for this use case.
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 |
Go deeper
Related to this question
About these practice questions
Courseiva writes every AZ-204 question from scratch — 881 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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-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.