Describe considerations for working with non-relational data on Azure →easyMultiple ChoiceObjective-mapped
DP-900 Practice Question: Describe considerations for working with non-relational data on Azure
A media company stores user profile images in Azure Blob Storage. Regulators require that the images cannot be deleted or overwritten for a period of 90 days after upload. Which Azure Blob Storage feature should the company enable to meet this requirement?
⚠ Common exam trap
Watch out — candidates often confuse soft delete (which only recovers deleted blobs) with immutable storage (which prevents both deletion and overwrite during the retention period), leading them to choose soft delete when the requirement explicitly prohibits overwrites as well.
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
✓
B: Immutable storage with a time-based retention policy
Immutable storage with a time-based retention policy (also known as WORM – Write Once, Read Many) prevents blobs from being deleted or overwritten for a specified retention interval. By setting a 90-day policy, the company ensures that user profile images remain unmodifiable and undeletable during that period, directly satisfying the regulatory requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A: Soft delete
Why it's wrong here
When blob soft delete is enabled, deleted blobs are retained in a hidden soft-deleted state for a configurable retention interval, during which they can be recovered by an authorized caller. However, the delete operation still succeeds, and the blob is placed in a state that is not readable until restored; after the retention window expires, the blob is permanently purged. It also does not block overwrites, since a new upload with the same name replaces the current version unless blob versioning is separately enabled. Therefore soft delete only offers a recovery window against accidental data loss, not active prevention of deletion or modification.
- ✓
B: Immutable storage with a time-based retention policy
Why this is correct
Immutable storage with a time-based retention policy places a blob container into a write-once-read-many (WORM) state in which blobs cannot be modified or deleted by any user for the configured retention interval. Once the policy is enforced, even account administrators or privileged role holders cannot alter or remove the blobs; they can only extend the retention period, not shorten or remove it. This directly satisfies the requirement to prevent both deletion and overwriting of profile images, making it a compliant solution for legal or regulatory data protection.
- ✗
C: Access tiers (Hot, Cool, Archive)
Why it's wrong here
Blob access tiers (Hot, Cool, Cold, and Archive) are designed to match storage costs to how frequently data is accessed, with Archive offering the lowest cost in exchange for high rehydration latency and a higher access penalty. Tiers are purely a performance and cost classification, and a blob in any tier is still subject to normal delete and overwrite operations. Its metadata and lease state are unaffected by tier, so it provides zero protection against data modification or deletion. The requirement for immutability is entirely outside the scope of what access tiers address.
- ✗
D: Lifecycle management rules
Why it's wrong here
Lifecycle management uses rules to automatically transition blobs from Hot to Cool or Archive based on age or modify dates, and can also execute deletion jobs when blobs reach a configured expiration threshold. Because these rules are administrative automation that can physically remove blobs, implementing them would actually increase the risk of losing profile images, not reduce it. No lifecycle rule can set a WORM lock, disable user deletion permissions, or prevent overwrites. Therefore it is not a mechanism for protecting data from deletion or modification; it is a mechanism for automating data expiration.
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
This DP-900 question is part of Courseiva's 820-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 DP-900 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 DP-900 exam.