Azure Cosmos DB Table API for Dedicated Throughput
You are building an app named App1 that will store structured and unstructured data by using the Azure Table storage REST API. You need to recommend a solution that meets the following requirements: • Provides dedicated throughput and the fastest possible read and write times for the data • Minimizes storage costs What should you include in the recommendation?
Community Insight
The question tests knowledge of specialized NoSQL table storage versus general-purpose blob/file storage, with the trap being the assumption that 'Table Storage' implies only the legacy Azure Table Storage service rather than the modern Cosmos DB Table API.
This question evaluates the selection of Azure storage services for structured data requiring dedicated throughput and low latency. Azure Cosmos DB is identified as the correct solution due to its provisioned Request Units (RUs) that guarantee performance while maintaining cost efficiency compared to premium general-purpose accounts.
Candidates often select a standard or premium storage account (Option B or C), mistakenly believing that general-purpose storage provides better throughput or that the specific mention of 'Table storage REST API' refers exclusively to the legacy Azure Table Storage which does not offer dedicated throughput modes.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Azure Cosmos DB offers a Table API that is fully compatible with the Azure Table Storage REST API but provides significantly superior performance characteristics. By using a Cosmos DB database, you can enable 'dedicated throughput,' which means the database is provisioned with specific Request Units (RUs). This guarantees single-digit millisecond latencies for reads and writes, satisfying the requirement for the 'fastest possible read and write times.' It also minimizes costs by allowing you to pay only for the capacity you need, rather than reserving expensive premium storage tiers.Why the Other Options Are Wrong
A standard storage account (Option B) shares resources with other tenants and does not offer dedicated throughput or guaranteed low-latency SLAs for table operations. A premium storage account (Option C) is designed primarily for IOPS-intensive workloads like VM disks (page blobs) and does not support the Table API structure natively in a way that offers dedicated throughput scaling. Azure Cache for Redis (Option D) is an in-memory data store optimized for caching and session state, not for persistent structured data storage via the Table API, and it would incur significantly higher costs for large datasets.Community Comment Notes
The community consensus strongly supports Option A. As noted by user gpais, "Dedicated Throughput and Speed: Azure Cosmos DB for Table uses provisioned throughput measured in Request Units (RUs) to provide dedicated, guaranteed throughput." This aligns with the core differentiator of Cosmos DB over legacy storage solutions.Exam Strategy
When a question mentions 'Table Storage' alongside requirements for 'dedicated throughput' or 'millisecond latency', immediately consider Azure Cosmos DB's Table API. Legacy Azure Table Storage does not support dedicated throughput; only Cosmos DB does.
Frequently Asked Questions
Why isn't Azure Cache for Redis used for Table data?
Redis is an in-memory cache, not a persistent table storage solution. It lacks the Table API compatibility and is too expensive for bulk structured data storage.
Does 'Table storage REST API' mean only legacy storage?
No. While legacy Azure Table Storage exists, Cosmos DB's Table API is fully compatible with the same REST endpoints but adds features like dedicated throughput and global distribution.
Related Analysis
Practice All AZ-305 Questions
Access 95 questions with complete answers and detailed explanations.
View Full AZ-305 Practice Test →