Quick Answer
The answer is to enable both blob versioning and blob soft delete. Blob versioning automatically preserves the state of a blob each time it is modified or overwritten, allowing you to restore any prior version directly. Blob soft delete acts as a safety net by retaining deleted or overwritten blobs for a configurable retention period, preventing permanent data loss and enabling recovery even after accidental removal. On the AZ-204 exam, this combination is frequently tested as a best practice for blob data protection, often in scenarios involving critical assets like product images where accidental overwrite must be prevented. A common trap is assuming versioning alone covers deletion—it does not; soft delete is required for that. Memory tip: think of versioning as your “time machine” for changes, and soft delete as your “trash can” with a recovery timer.
This AZ-204 practice question tests your understanding of develop for azure storage. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 Blob Storage workflow for product images must prevent accidental overwrite and support recovery of prior versions. Which two features should be enabled?
SFTP support
Why wrong: SFTP changes transfer protocol but does not preserve versions.
Blob soft delete
Soft delete helps recover deleted blobs and versions within the retention period.
Static website hosting
Why wrong: Static website hosting does not protect prior blob versions.
Blob versioning
Versioning keeps previous versions of blobs after writes or deletes.
Answer choices
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
Blob soft delete (B) protects against accidental deletion or overwrite by retaining deleted blobs for a configurable retention period, allowing recovery. Blob versioning (D) automatically maintains prior versions of a blob, enabling restoration of any previous state. Together, they provide comprehensive protection against overwrites and support version recovery.
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.
SFTP support
Why it's wrong here
SFTP changes transfer protocol but does not preserve versions.
Blob soft delete
Why this is correct
Soft delete helps recover deleted blobs and versions within the retention period.
Related concept
Read the scenario before looking for a memorised answer.
Static website hosting
Why it's wrong here
Static website hosting does not protect prior blob versions.
Blob versioning
Why this is correct
Versioning keeps previous versions of blobs after writes or deletes.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates may confuse SFTP support or static website hosting with data protection features, but neither provides versioning or soft-delete capabilities required for overwrite prevention and recovery.
Detailed technical explanation
Blob soft delete works by moving deleted blobs to a soft-deleted state, where they remain accessible via the List Blobs API with the `include=deleted` parameter until the retention period expires. Blob versioning creates a new version for each write operation (PutBlob, SetBlobProperties, etc.) and stores the previous version as an immutable snapshot, which can be promoted to the current version using the Copy Blob API. In practice, enabling both features ensures that even if a blob is overwritten, the prior version is preserved and can be restored without data loss.
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.
Develop for Azure storage — study guide chapter
Learn the concepts, then practise the questions
Develop for Azure storage practice questions
Targeted practice on this topic area only
All AZ-204 questions
997 questions across all exam domains
Microsoft Azure Developer Associate AZ-204 study guide
Full concept coverage aligned to exam objectives
AZ-204 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-204 questions linked to Develop Azure compute solutions.
Practise AZ-204 questions linked to Develop for Azure storage.
Practise AZ-204 questions linked to Implement Azure security.
Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.
Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.
Practise AZ-204 questions linked to AZ-204 fundamentals.
Practise AZ-204 questions linked to AZ-204 scenario.
Practise AZ-204 questions linked to AZ-204 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Develop for Azure storage — This question tests Develop for Azure storage — Read the scenario before looking for a memorised answer..
The correct answer is: Blob soft delete — Blob soft delete (B) protects against accidental deletion or overwrite by retaining deleted blobs for a configurable retention period, allowing recovery. Blob versioning (D) automatically maintains prior versions of a blob, enabling restoration of any previous state. Together, they provide comprehensive protection against overwrites and support version recovery.
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-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.
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.