Azure Table Storage for Log Data
You need to store billions of small log entries (each ~200 bytes) written in chronological order from multiple producers. The logs are read sequentially in bulk once per day. You need to maximize write throughput and minimize storage costs. Which Azure Storage solution should you choose?
⚠ Common exam trap
A common mix-up: candidates confuse Append Blob with Block Blob, assuming high block count can achieve similar append performance, but Block Blob requires explicit block management and cannot guarantee atomic append operations, making Append Blob the only correct choice for this workload.
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
✓
Append Blob in Blob Storage
Append Blob in Blob Storage is optimized for append operations, making it ideal for writing small log entries in chronological order from multiple producers. It provides high write throughput because each append operation is atomic and can be performed concurrently, and it minimizes storage costs by storing data in a cost-effective blob tier without the overhead of indexing or metadata management required by other solutions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Append Blob in Blob Storage
Why this is correct
Append Blobs are specifically designed for append operations, making them ideal for logging scenarios where new data is continuously added to the end of a blob. Each 200-byte log entry can be atomically appended, ensuring data integrity and high write throughput for billions of sequential entries. This specialized blob type efficiently handles the scale and frequency of small, incremental writes without incurring significant overhead, providing a cost-effective and performant solution for continuous logging.
- ✗
Block Blob in Blob Storage with high block count
Why it's wrong here
Block blobs with a high block count incur significant per-block metadata overhead and commit latency, making them unsuitable for billions of tiny, high-frequency writes; the correct solution, Append Blob, appends each log entry atomically without block management overhead. This option tempts because block blobs are designed for parallel uploads of large files, where high block count improves throughput for a single large object, not for many small sequential writes.
- ✗
Azure Data Lake Storage Gen2 with hierarchical namespace
Why it's wrong here
While Azure Data Lake Storage Gen2 leverages Blob Storage, its primary optimization is for big data analytics workloads, including hierarchical namespace capabilities for file and folder management. It is not specifically engineered for the extreme high-throughput ingestion of billions of small, sequential append-only log entries to a single file. Using ADLS Gen2 for this specific logging pattern might introduce unnecessary complexity or cost compared to directly utilizing an Append Blob, which is purpose-built for such a task.
- ✗
Azure Files with SMB protocol
Why it's wrong here
Azure Files provides fully managed file shares accessible via SMB or NFS protocols, designed for general-purpose file storage and sharing across virtual machines or on-premises environments. It is not optimized for the specific workload of billions of high-frequency, small append operations to a single log file. The performance characteristics and cost model of Azure Files are not suited for this extreme scale of sequential logging, making it an inefficient choice compared to specialized blob types.
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 883 original AZ-204 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 →
Same concept, more angles
1 more way this is tested on AZ-204
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You need to store billions of small telemetry data entries (each ~100 bytes) from IoT devices. The data is written once and rarely updated. You need to run analytical queries on the last 30 days of data daily. The queries scan large ranges of data by timestamp and require sub-second response times. You need the lowest storage cost while meeting query latency requirements. Which Azure Storage solution should you use?
hard- ✓ A.Azure Blob Storage with hot access tier and Data Lake Storage Gen2.
- B.Azure Table Storage with a timestamp partition key.
- C.Azure Cosmos DB with SQL API and automatic indexing.
- D.Azure Blob Storage with cool access tier and Azure Data Lake Storage Gen2.
Why A: Azure Blob Storage with the hot access tier is suitable for data that is accessed frequently (daily queries on the last 30 days), providing lower transaction costs compared to the cool tier for active data. Azure Data Lake Storage Gen2, built on Blob Storage, enables hierarchical namespace and POSIX-like access, allowing efficient analytical queries on large timestamp-ranged data with sub-second response times via partitioning and parallel processing, meeting the performance and scalability requirements at a cost-effective price point for the storage of billions of small entries.
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.