AZ-305 Design data storage solutions Practice Question
A company wants to store log data from multiple applications for up to 30 days for analysis. The data is append-only, and queries are infrequent but need to be fast when run. Which Azure data storage solution should you recommend?
⚠ Common exam trap
A common mix-up: candidates choose Azure Blob Storage (archive tier) for cost savings, overlooking the explicit requirement for fast query performance, which the archive tier cannot provide due to its multi-hour rehydration latency.
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 Log Analytics Workspace
Azure Log Analytics Workspace is the correct choice because it is purpose-built for ingesting, storing, and querying log data from multiple sources. It supports append-only log ingestion, retains data for up to 30 days in its interactive retention tier (configurable), and provides fast Kusto Query Language (KQL) queries for infrequent analysis. The workspace integrates natively with Azure Monitor and other services, making it ideal for centralized log analysis.
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 Log Analytics Workspace
Why this is correct
Log Analytics Workspace ingests append-only log data and retains it for a configurable period, here 30 days. Its Kusto query engine returns fast results on infrequent ad hoc queries, unlike blob storage, which suits archival rather than interactive analysis.
- ✗
Azure Table Storage
Why it's wrong here
Table Storage is a key-value store with no query engine, so it cannot deliver fast analytical queries over log data. It is tempting because it is inexpensive and schema-less for high-volume append writes, and would be correct for storing entity data retrieved by partition and row key.
- ✗
Azure Data Lake Storage Gen2
Why it's wrong here
Data Lake Storage Gen2 is a blob-based hierarchical namespace, not a query engine, so it provides no native fast query capability for infrequent analytical reads. It is tempting because it stores structured and unstructured data cheaply, and would suit a data lake feeding a separate analytics engine.
- ✗
Azure Blob Storage (archive tier)
Why it's wrong here
Archive tier stores blobs offline, so retrieval takes hours and cannot satisfy fast queries within the 30-day window. It is tempting because archive tier minimises storage cost for rarely accessed data, and would be correct for long-term retention where retrieval latency is irrelevant.
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.