Quick Answer
The answer is immutable blob storage with a time-based retention policy, which enforces a WORM (Write Once, Read Many) model to prevent any modification or deletion of data for a fixed duration. This is correct because the policy locks blobs at the storage level, ensuring that even account administrators or privileged users cannot alter or remove the evidence during the seven-year legal hold period, directly satisfying compliance requirements for preserving legal evidence. On the AZ-500 exam, this scenario tests your understanding of data protection controls under Azure Storage security, often appearing as a distractor against legal hold (which applies to individual blobs without a fixed time limit) or soft delete (which allows recovery but not immutable locking). A common trap is confusing time-based retention with legal hold—remember that time-based retention sets a countdown clock for all blobs in a container, while legal hold is indefinite and per-blob. Memory tip: think “WORM locks the clock” for time-based retention, ensuring data stays frozen for exactly seven years.
This AZ-500 practice question tests your understanding of secure compute, storage, and databases. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A storage account contains legal evidence that must not be modified or deleted for seven years. Which feature should be configured?
Soft delete only
Why wrong: This does not meet the stated requirement as directly as the correct option.
Lifecycle management to archive tier
Why wrong: This does not meet the stated requirement as directly as the correct option.
Customer-managed keys
Why wrong: This does not meet the stated requirement as directly as the correct option.
Immutable blob storage with a time-based retention policy
Correct for the stated requirement.
Answer choices
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) is the correct choice because it enforces a strict seven-year retention period during which blobs cannot be modified or deleted, even by account administrators. This is achieved through a policy that locks the data at the storage level, ensuring compliance with legal hold requirements for evidence preservation.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Soft delete only
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
Lifecycle management to archive tier
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
Customer-managed keys
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
Immutable blob storage with a time-based retention policy
Why this is correct
Correct for the stated requirement.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates often confuse soft delete (which only protects against accidental deletion for a short period) with immutable storage (which enforces a hard, non-negotiable retention lock against both modification and deletion for a specified duration).
Detailed technical explanation
Immutable storage uses a WORM model enforced by a time-based retention policy that sets a minimum retention interval (e.g., 7 years) on a container or storage account; once the policy is locked, it cannot be shortened or removed, and any attempt to delete or overwrite blobs is rejected with an HTTP 409 (Conflict) error. Under the hood, Azure Blob Storage maintains a metadata timestamp for each blob that tracks the retention expiration, and the storage service enforces the policy at the API level, even bypassing privileged operations like storage account deletion. In a real-world scenario, this is critical for eDiscovery or regulatory compliance (e.g., SEC Rule 17a-4) where data must be preserved in its original form for a defined period.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Secure compute, storage, and databases — study guide chapter
Learn the concepts, then practise the questions
Secure compute, storage, and databases practice questions
Targeted practice on this topic area only
All AZ-500 questions
1,000 questions across all exam domains
Microsoft Azure Security Engineer Associate AZ-500 study guide
Full concept coverage aligned to exam objectives
AZ-500 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise AZ-500 questions linked to Secure identity and access.
Practise AZ-500 questions linked to Secure compute, storage, and databases.
Practise AZ-500 questions linked to Secure Azure using Microsoft Defender for Cloud and Microsoft Sentinel.
Practise AZ-500 questions linked to Manage identity and access.
Practise AZ-500 questions linked to Secure networking.
Practise AZ-500 questions linked to AZ-500 fundamentals.
Practise AZ-500 questions linked to AZ-500 scenario.
Practise AZ-500 questions linked to AZ-500 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Secure compute, storage, and databases — This question tests Secure compute, storage, and databases — Read the scenario before looking for a memorised answer..
The correct answer is: Immutable blob storage with a time-based retention policy — Immutable blob storage with a time-based retention policy (WORM – Write Once, Read Many) is the correct choice because it enforces a strict seven-year retention period during which blobs cannot be modified or deleted, even by account administrators. This is achieved through a policy that locks the data at the storage level, ensuring compliance with legal hold requirements for evidence preservation.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This AZ-500 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-500 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.