The correct answer is to lock the immutability policy after validation is complete. Locking the policy enforces retention settings by making the configuration irrevocable, meaning no user—including administrators—can modify or delete the retention rules once locked. This mechanism, often referred to as a legal hold or time-based retention policy, is essential for compliance with regulations like SEC 17a-4 or FINRA, as it ensures data cannot be altered or overwritten during the specified period. On the AZ-104 exam, this concept tests your understanding of Azure Blob Storage data protection and governance, often appearing in scenarios where you must prevent unauthorized changes to retention policies after validation. A common trap is confusing locking with simply setting the policy; remember that locking is a separate, final step that makes the policy immutable. Memory tip: think of it as “set it, validate it, lock it”—the lock is the permanent seal that enforces compliance.
AZ-104 Implement and Manage Storage Practice Question
This AZ-104 practice question tests your understanding of implement and manage storage. 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.
Exhibit
Container properties:
Container name: auditlogs
Immutable storage: enabled
Immutability policy mode: Unlocked
Retention period: 30 days
Allow protected append writes: Yes
Compliance note: the retention period has been tested and approved, and the organization wants the setting to be fixed so it cannot be shortened later.
Based on the exhibit, what should the administrator do to prevent anyone from changing the retention settings after validation?
Container properties:
Container name: auditlogs
Immutable storage: enabled
Immutability policy mode: Unlocked
Retention period: 30 days
Allow protected append writes: Yes
Compliance note: the retention period has been tested and approved, and the organization wants the setting to be fixed so it cannot be shortened later.
A
Lock the immutability policy after validation is complete.
An unlocked immutability policy allows authorized changes during setup and testing. Once the retention period is validated, locking the policy prevents shortening or weakening retention settings later, which is exactly what the compliance note requires.
B
Move the container to the Cool access tier to preserve the retention period.
Why wrong: Access tier changes affect storage cost and retrieval behavior, not immutability enforcement. They do not prevent someone from changing the retention configuration.
C
Create a blob snapshot every day so the retention settings cannot be edited.
Why wrong: Snapshots help preserve data versions, but they do not lock or protect the container's retention policy settings. The exhibit asks about preventing policy changes, not about copying data.
D
Enable container public access so the audit logs are easier to verify.
Why wrong: Public access weakens security and does not help with immutability. It would expose the logs unnecessarily and still would not lock the retention settings.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Lock the immutability policy after validation is complete.
Option A is correct because locking the immutability policy (also known as a legal hold or time-based retention policy) prevents any user—including administrators—from modifying or deleting the policy. Once locked, the retention settings become irrevocable, ensuring that data cannot be altered or overwritten during the specified retention period. This is a critical step for compliance with regulations such as SEC 17a-4 or FINRA.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Lock the immutability policy after validation is complete.
Why this is correct
An unlocked immutability policy allows authorized changes during setup and testing. Once the retention period is validated, locking the policy prevents shortening or weakening retention settings later, which is exactly what the compliance note requires.
Related concept
Read the scenario before looking for a memorised answer.
✗
Move the container to the Cool access tier to preserve the retention period.
Why it's wrong here
Access tier changes affect storage cost and retrieval behavior, not immutability enforcement. They do not prevent someone from changing the retention configuration.
✗
Create a blob snapshot every day so the retention settings cannot be edited.
Why it's wrong here
Snapshots help preserve data versions, but they do not lock or protect the container's retention policy settings. The exhibit asks about preventing policy changes, not about copying data.
✗
Enable container public access so the audit logs are easier to verify.
Why it's wrong here
Public access weakens security and does not help with immutability. It would expose the logs unnecessarily and still would not lock the retention settings.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse 'locking' a policy with other storage management actions like changing access tiers or creating snapshots, mistakenly believing those actions can enforce immutability when only a locked policy provides the required legal protection.
Detailed technical explanation
How to think about this question
Under the hood, Azure Blob Storage immutability policies are enforced at the container level using a WORM (Write Once, Read Many) model. When a policy is locked, Azure applies a policy-level lock that prevents any changes to the retention interval or deletion of the policy, even by the subscription owner. This is implemented via the Azure Resource Manager with a special 'immutabilityPolicyState' property set to 'Locked'. In a real-world scenario, a financial institution must lock the policy after validating the retention period to meet regulatory audit requirements; otherwise, an administrator could inadvertently or maliciously shorten the retention window.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
Implement and Manage Storage — This question tests Implement and Manage Storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Lock the immutability policy after validation is complete. — Option A is correct because locking the immutability policy (also known as a legal hold or time-based retention policy) prevents any user—including administrators—from modifying or deleting the policy. Once locked, the retention settings become irrevocable, ensuring that data cannot be altered or overwritten during the specified retention period. This is a critical step for compliance with regulations such as SEC 17a-4 or FINRA.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
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 →
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.
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.
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.