AZ-204 Develop for Azure storage Practice Question
An application stores customer invoices in Azure Blob Storage. Deleted blobs must be recoverable for 14 days. What should be enabled? The design must avoid adding custom operational scripts.
⚠ Common exam trap
The trap here is that candidates might confuse soft delete with versioning or immutable storage, but soft delete is the only option that provides a configurable retention period for recovering deleted blobs without custom code.
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
✓
Blob soft delete with a 14-day retention period
Blob soft delete protects against accidental deletion by retaining deleted blobs for a specified retention period. Enabling it with a 14-day retention period allows recovery of deleted invoices within that window without custom scripts, meeting the requirement exactly.
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 with a 14-day retention period
Why this is correct
Blob soft delete retains deleted blobs for a specified retention period, letting them be restored natively without scripts. Setting 14 days matches the recoverability requirement exactly, satisfying the constraint that no custom operational tooling be introduced. Microsoft Entra ID permissions govern restore operations.
- ✗
Archive access tier
Why it's wrong here
Archive tier is a storage access tier controlling retrieval latency and cost for retained blobs; it does not retain deleted blobs. Soft delete retains deleted blobs for a configured retention period. Archive is tempting because it sounds like long-term retention, but it applies to live data, not deletions.
- ✗
Static website hosting
Why it's wrong here
Static website hosting serves blob content over HTTP from a container endpoint; it provides no deletion recovery. Soft delete retains deleted blobs for the retention window without scripts. Static hosting is tempting when blobs serve web content, but it addresses delivery, not recoverability.
- ✗
Immutable blob legal hold
Why it's wrong here
Legal hold preserves blobs indefinitely until explicitly cleared, so it cannot express a 14-day recoverable window. It is tempting because it does prevent deletion, but it targets litigation-driven retention rather than time-bound soft-delete recovery, which is what the scenario's 14-day requirement actually needs.
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 →
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.