AZ-104 Implement and Manage Storage Practice Question
An application team plans to store block blobs for application logs, lifecycle them to cooler tiers over time, and use Azure Monitor diagnostic exports from several Azure resources into the same storage account. They also want access tier controls and general-purpose features in one place. Which storage account type should the administrator create?
⚠ Common exam trap
Test-takers frequently assume any blob-specific account (like BlobStorage or BlockBlobStorage) is sufficient for diagnostic exports, but Azure Monitor requires a general-purpose v2 account to properly create the necessary containers and support lifecycle management policies.
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
✓
StorageV2 general-purpose account, because it supports blobs, tiering, and broad Azure integrations.
A StorageV2 general-purpose account (B) is the correct choice because it supports block blobs, lifecycle management policies for tiering to cool, cold, and archive tiers, and integrates seamlessly with Azure Monitor diagnostic exports. Unlike specialized accounts, StorageV2 provides a unified platform for blobs, files, queues, and tables, meeting the team's need for access tier controls and general-purpose features in one place.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
BlobStorage account, because it is optimized for storing only unstructured blobs.
Why it's wrong here
A legacy BlobStorage account is a specialized account type that can only store block blobs and append blobs, with no support for files, queues, tables, or any premium performance tier. While it does offer blob access tiers and lifecycle management, it is now considered obsolete because StorageV2 provides all its features plus complete service coverage and better integration. Choosing BlobStorage would unnecessarily restrict the application team to a narrowly scoped account without any added benefit over the modern general-purpose v2 option.
When this WOULD be correct
A question that asks for a storage account optimized solely for storing unstructured blob data (e.g., for a simple backup or archive solution) with no need for Azure Monitor integration or lifecycle management would make BlobStorage the correct answer.
- ✓
StorageV2 general-purpose account, because it supports blobs, tiering, and broad Azure integrations.
Why this is correct
A general-purpose v2 (StorageV2) account is the recommended Azure Storage account for blob-centric workloads because it consolidates blob, file, queue, table, and disk services under one account. It natively supports the hot, cool, and archive blob access tiers along with lifecycle management policies, enabling cost-effective tiering of application logs. StorageV2 also integrates directly with Azure Monitor for metrics and diagnostic settings, making it the ideal choice for application teams that need broad Azure service interoperability.
- ✗
FileStorage account, because it supports any Azure diagnostic data format and access tiers.
Why it's wrong here
A FileStorage account is intended exclusively for premium Azure Files workloads, delivering SMB and NFS file shares with high IOPS, not for storing blobs or diagnostic data. It does not support blob access tiers (hot/cool/archive) and cannot ingest the wide variety of Azure Monitor diagnostic formats that are designed for blob or general-purpose storage. The claim that FileStorage accepts any Azure diagnostic data format is factually incorrect; it is optimized for file shares, not for log-centric storage scenarios.
When this WOULD be correct
If the question required storing file shares for applications using SMB protocol, with premium performance and no need for blob storage or lifecycle management, a FileStorage account would be correct.
- ✗
BlockBlobStorage account, because it is required whenever logs are exported from Azure Monitor.
Why it's wrong here
A BlockBlobStorage account is a premium-performance account designed for low-latency, high-throughput block blob workloads, not for general application logging. It is absolutely not required for exporting logs from Azure Monitor; diagnostic settings can send logs to any general-purpose v2 or legacy BlobStorage account. This option misrepresents a deployment requirement, and BlockBlobStorage also lacks the flexible access tiers and lifecycle management found in StorageV2, making it a poor fit for typical log storage.
When this WOULD be correct
A scenario where an application requires maximum performance for block blob storage with low latency, such as for high-throughput logging or analytics workloads, and does not need Azure Monitor diagnostics or lifecycle management.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.
✓StorageV2 general-purpose account, because it supports blobs, tiering, and broad Azure integrations.Correct answer▾
Why this is correct
A general-purpose v2 (StorageV2) account is the recommended Azure Storage account for blob-centric workloads because it consolidates blob, file, queue, table, and disk services under one account. It natively supports the hot, cool, and archive blob access tiers along with lifecycle management policies, enabling cost-effective tiering of application logs. StorageV2 also integrates directly with Azure Monitor for metrics and diagnostic settings, making it the ideal choice for application teams that need broad Azure service interoperability.
✗BlobStorage account, because it is optimized for storing only unstructured blobs.Wrong answer — click to see why▾
Why this is wrong here
BlobStorage accounts do not support Azure Monitor diagnostic exports or lifecycle management policies, which are required for the scenario.
★ When this WOULD be the correct answer
A question that asks for a storage account optimized solely for storing unstructured blob data (e.g., for a simple backup or archive solution) with no need for Azure Monitor integration or lifecycle management would make BlobStorage the correct answer.
Why candidates choose this
Candidates may think BlobStorage is sufficient because the primary data type is blobs, overlooking the need for broader Azure integrations and lifecycle management features that only StorageV2 provides.
✗FileStorage account, because it supports any Azure diagnostic data format and access tiers.Wrong answer — click to see why▾
Why this is wrong here
FileStorage accounts are optimized for SMB file shares, not block blobs, and do not support Azure Monitor diagnostic exports or access tier controls for blobs.
★ When this WOULD be the correct answer
If the question required storing file shares for applications using SMB protocol, with premium performance and no need for blob storage or lifecycle management, a FileStorage account would be correct.
Why candidates choose this
Candidates may confuse FileStorage with general-purpose storage, assuming it supports any data format and tiering, or misremember that Azure Monitor exports can go to file shares.
✗BlockBlobStorage account, because it is required whenever logs are exported from Azure Monitor.Wrong answer — click to see why▾
Why this is wrong here
BlockBlobStorage accounts do not support Azure Monitor diagnostic exports or lifecycle management policies, and they lack general-purpose features like tables and queues.
★ When this WOULD be the correct answer
A scenario where an application requires maximum performance for block blob storage with low latency, such as for high-throughput logging or analytics workloads, and does not need Azure Monitor diagnostics or lifecycle management.
Why candidates choose this
Candidates may think that block blobs for logs require a BlockBlobStorage account, overlooking that StorageV2 accounts also support block blobs and provide the necessary additional features.
Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
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
Learn chapter
Privileged Identity Management (PIM)
Key term
Storage account
A cloud storage account is a container that holds a set of cloud storage services and their data, providing a unique namespace and access policies for storing and managing unstructured data.
Key term
Azure Monitor
Azure Monitor is a cloud service that collects, analyzes, and acts on telemetry data from your Azure and on-premises resources to help you understand performance and availability.
About these practice questions
One of 1,049 original AZ-104 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-104 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-104 exam.