AZ-104 Implement and Manage Storage Practice Question
A company uses Azure Blob Storage for legal documents. The documents must not be modified or deleted for seven years after upload, even by administrators. What should you configure?
⚠ Common exam trap
Candidates often confuse soft delete or versioning with immutable storage, not realizing that only a time-based retention policy (WORM) provides the strict, administrator-proof immutability required for regulatory compliance.
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
✓
Immutable blob storage with a time-based retention policy
Immutable blob storage with a time-based retention policy (WORM – Write Once, Read Many) ensures that blobs cannot be modified or deleted for a specified retention period, even by administrators. This is the only Azure storage feature that provides legal hold or regulatory compliance for fixed records, such as legal documents that must remain unaltered for seven years.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Blob soft delete
Why it's wrong here
Blob soft delete provides a recovery safety net by preserving deleted blobs for a configurable period, but it does not block or prevent deletion in the first place. Even with soft delete enabled, a user with appropriate permissions can still overwrite or delete a blob, and the soft-deleted copy is not immutable—it is simply hidden and recoverable. As a result, it cannot guarantee that legal documents remain unaltered and undeleted for seven years; it only offers post-deletion recovery.
When this WOULD be correct
A company wants to recover blobs that are accidentally deleted or overwritten within a specified retention period, but does not require strict legal hold or administrator-proof immutability.
- ✓
Immutable blob storage with a time-based retention policy
Why this is correct
Immutable blob storage with a time-based retention policy enforces write-once-read-many (WORM) behavior: blobs cannot be modified or deleted until the retention period expires. For legal documents needing seven-year preservation, this policy provides a strict, compliance-ready guarantee because the retention clock starts when the policy is applied and continues regardless of user permissions. This is the only option that actually enforces immutability for the full required duration.
- ✗
Lifecycle management to move blobs to Archive
Why it's wrong here
Lifecycle management automates the movement of blobs to cooler tiers like Archive based on age or last-modified date, which is purely a cost-optimization mechanism. Moving a blob to the Archive tier does not lock the blob, nor does it prevent deletion or overwrite; an archived blob can be explicitly deleted at any time. This option reduces storage expenses but completely fails to provide any immutability or retention enforcement for legal documents.
When this WOULD be correct
A company wants to reduce storage costs by automatically moving blobs that have not been accessed for 30 days to the Cool tier, and blobs older than 90 days to the Archive tier. Lifecycle management would be the correct solution for this cost-optimization scenario.
- ✗
Blob versioning
Why it's wrong here
Blob versioning preserves historical versions of a blob whenever it is overwritten or deleted, but it does not prevent those operations from occurring on the current version. Without an immutable policy, an authorized user can still modify or delete the latest version, and while a deleted version is retained, the data remains mutable in practice. Versioning therefore aids recovery and auditing, but it does not satisfy a requirement for write-once, read-many protection over a fixed seven-year period.
When this WOULD be correct
An organization needs to recover from accidental deletion or overwrite of blobs, and wants to maintain a history of changes for auditing or rollback purposes, without requiring strict immutability. For example, a development team using Azure Blob Storage for application logs that may need to restore earlier versions.
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.
✓Immutable blob storage with a time-based retention policyCorrect answer▾
Why this is correct
Immutable blob storage with a time-based retention policy enforces write-once-read-many (WORM) behavior: blobs cannot be modified or deleted until the retention period expires. For legal documents needing seven-year preservation, this policy provides a strict, compliance-ready guarantee because the retention clock starts when the policy is applied and continues regardless of user permissions. This is the only option that actually enforces immutability for the full required duration.
✗Blob soft deleteWrong answer — click to see why▾
Why this is wrong here
Blob soft delete protects against accidental deletion but does not prevent modifications, and administrators can still delete blobs within the retention period if they have sufficient permissions.
★ When this WOULD be the correct answer
A company wants to recover blobs that are accidentally deleted or overwritten within a specified retention period, but does not require strict legal hold or administrator-proof immutability.
Why candidates choose this
Candidates may confuse soft delete with immutable storage, thinking it provides long-term protection against deletion, but they overlook that soft delete does not prevent modifications or administrator actions.
✗Lifecycle management to move blobs to ArchiveWrong answer — click to see why▾
Why this is wrong here
Lifecycle management moves blobs to different tiers or deletes them based on age, but it does not prevent modification or deletion by administrators. It cannot enforce a write-once, read-many (WORM) state required for legal hold or regulatory compliance.
★ When this WOULD be the correct answer
A company wants to reduce storage costs by automatically moving blobs that have not been accessed for 30 days to the Cool tier, and blobs older than 90 days to the Archive tier. Lifecycle management would be the correct solution for this cost-optimization scenario.
Why candidates choose this
Candidates may confuse lifecycle management with retention policies, thinking that moving blobs to Archive makes them immutable or that the policy itself prevents deletion, but Archive blobs can still be deleted by administrators.
✗Blob versioningWrong answer — click to see why▾
Why this is wrong here
Blob versioning preserves previous versions of blobs but does not prevent deletion or modification of the current version by administrators. It cannot enforce a legal hold or retention period that blocks all modifications and deletions.
★ When this WOULD be the correct answer
An organization needs to recover from accidental deletion or overwrite of blobs, and wants to maintain a history of changes for auditing or rollback purposes, without requiring strict immutability. For example, a development team using Azure Blob Storage for application logs that may need to restore earlier versions.
Why candidates choose this
Candidates may confuse versioning with immutability, thinking that preserving all versions inherently protects data from modification or deletion, not realizing that administrators can still delete the current version or entire storage account.
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
Managed Identities for Azure Resources
Key term
Policy
A policy is a set of rules or guidelines that defines how an organization manages, secures, and operates its IT systems and services.
Key term
Azure Storage
Azure Storage is Microsoft's cloud-based service for storing data like files, messages, and backups with high durability and scalability.
About these practice questions
This AZ-104 question is part of Courseiva's 1,049-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-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.