
Answer-first summary for fast verification
Answer: Create a delete lock for storage1.
The question requires preventing container deletion while allowing container creation in the storage account. Option B (Create a delete lock for storage1) is correct because Azure resource locks at the storage account level prevent deletion of the resource and its child resources (containers) while still permitting creation operations. The community discussion shows 100% consensus on B with upvoted comments confirming this is the correct approach. Option A (ReadOnly lock) would prevent both creation and deletion, which is too restrictive. Options C and D (container soft delete and blob soft delete) are data protection features that allow recovery after deletion but don't prevent the deletion action itself, so they don't meet the requirement.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You have an Azure Storage account named storage1. You need to configure it so that new containers can be created, but existing containers cannot be deleted.
What should you do?
A
Create a ReadOnly lock for storage1.
B
Create a delete lock for storage1.
C
Enable container soft delete.
D
Enable blob soft delete.
No comments yet.