Question 360
An Azure Storage account had Blob soft delete enabled for 14 days but container soft delete was disabled when a production blob container was deleted yesterday. The team has no Azure Backup recovery point or independent copy. An engineer proposes enabling container soft delete today to recover yesterday's deleted container. What is the correct technical assessment?
Explanation
Correct Answer
Blob soft delete protects individual blobs, snapshots and versions, but not deletion of the container containing them. Container soft delete is a separate setting that must have been enabled before container deletion; enabling it later cannot retroactively protect the already-deleted container. With no other recovery copy, Azure Storage has no supported in-account undelete for this specific container loss.
Incorrect Answers
Undelete Blob works on soft-deleted blob objects inside a retained container; it does not restore the container namespace deleted without container soft delete. The premise that Blob soft delete automatically covers containers is false.
Container soft delete starts protecting container deletions only after it is enabled. The 14-day Blob soft-delete retention does not apply as a container retention window, so enabling container protection today does not revive the deletion from yesterday.
Blob versioning retains prior versions of supported blob content; it is not a container soft-delete mechanism, and turning it on after deletion cannot manufacture a version of a missing container.