Question 730
The cloud operations team reviews the following risk: A developer accidentally deletes important blobs and discovers no soft-deleted recovery versions because blob soft delete is off. Which configuration change most directly resolves this problem?
Explanation
Correct Answer
The cause is: The storage account lacks blob soft delete retention to recover recently removed objects. The appropriate change is: Enable blob soft delete with an appropriate retention period and verify the restore process. Verify it with this outcome: A controlled deletion can be reversed within retention without rebuilding the entire account.
Incorrect Answers
This action concerns user delegation sas for blob storage, where Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. The reported incident instead involves The storage account lacks blob soft delete retention to recover recently removed objects.
This action concerns storage shared key authorization disable, where The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. The corrective response here is “Enable blob soft delete with an appropriate retention period and verify the restore process”; this alternative does not provide that response.
This action concerns storage customer managed key in key vault, where Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. The stem reports a developer accidentally deletes important blobs and discovers no soft-deleted recovery versions because blob soft delete is off; this control addresses a different failure condition.