Enable Soft Delete for Azure Data Lake Storage Gen2
Your organization uses Azure Data Lake Storage Gen2 for a data lake. You need to prevent accidental deletion of data by enabling a soft delete policy. Which configuration is required?
Quick Answer
The correct answer is to enable blob soft delete on the storage account. This configuration works because Azure Data Lake Storage Gen2 implements its soft delete capability through the underlying blob storage layer, meaning that enabling blob soft delete on the storage account automatically protects both blobs and the hierarchical namespace data from accidental deletion. On the Microsoft Azure Data Engineer Associate DP-203 exam, this question tests your understanding of how ADLS Gen2 inherits blob-level features, and a common trap is confusing soft delete with versioning or Azure Resource Manager locks—versioning keeps multiple snapshots but does not prevent deletion, while ARM locks only block resource-level changes, not data deletion. To remember this, think of the mnemonic "Blobs Back Up Data Lake"—since ADLS Gen2 is built on Blob Storage, enabling blob soft delete is the direct path to data protection.
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
✓
Enable blob soft delete on the storage account.
Azure Data Lake Storage Gen2 supports blob soft delete, which protects against accidental deletion by retaining deleted blobs for a specified retention period. Option A is incorrect because Azure Resource Manager locks prevent the deletion or modification of the storage account itself, not the data within it. Option B is incorrect because Azure Backup is designed for backing up VMs, SQL databases, and other workloads, not for managing soft delete of blobs. Option C is incorrect because blob versioning preserves previous versions of blobs, but it does not prevent deletion of the current version; soft delete is specifically for recovery from accidental deletion.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Apply an Azure Resource Manager lock.
Why it's wrong here
A Resource Manager lock prevents deletion of the storage account resource itself, not individual blobs or files within the data lake. It is tempting because it blocks accidental removal, but it is the right choice when protecting the account, container or resource group from being deleted, not for recovering deleted data.
- ✗
Configure Azure Backup for the storage account.
Why it's wrong here
Azure Backup protects workloads via recovery points and vaults; it does not implement the storage account's soft delete retention setting for blobs or Data Lake Gen2 files. It is tempting because it restores deleted data, but it is the right choice for VM, database or file-share backup, not for enabling soft delete on a data lake.
- ✗
Enable blob versioning.
Why it's wrong here
Blob versioning preserves previous versions of a modified blob; it does not retain a deleted blob for a recovery window. It is tempting because both features sit under Data Protection, but versioning is the correct choice when you need to recover overwritten content, whereas soft delete handles deletions.
- ✓
Enable blob soft delete on the storage account.
Why this is correct
Blob soft delete retains deleted blobs for a configurable retention period, letting you recover data removed accidentally. Enabling it at the storage account level protects all containers, satisfying the requirement to prevent accidental deletion in the Data Lake Storage Gen2 account.
Go deeper
Related to this question
About these practice questions
This DP-203 question is part of Courseiva's 509-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 →
Same concept, more angles
1 more way this is tested on DP-203
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your organization uses Azure Data Lake Storage Gen2 and needs to prevent accidental deletion of data by enabling soft delete. You also need to ensure that deleted blobs are recoverable for 30 days. What should you configure?
easy- A.Enable blob snapshots and set them to expire after 30 days.
- B.Use Azure Backup to create daily backups of the storage account.
- C.Enable container soft delete with a retention period of 30 days.
- ✓ D.Enable blob soft delete and set retention period to 30 days.
Why D: Blob soft delete enables recovery of deleted blobs within a specified retention period (30 days in this case). Option A is incorrect because blob snapshots are point-in-time copies that require manual management and do not provide automatic recovery of deleted blobs. Option B is incorrect because Azure Backup is designed for virtual machines and other Azure resources, not for blob-level recovery in Data Lake Storage Gen2. Option C is incorrect because container soft delete deletes entire containers, not individual blobs.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-203 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-203 exam.