A wicker-ferry ticket scan is deleted while blob soft delete retention is 14 days, so the object remains recoverable and billable during that window. How should the developer contrast this with a lifecycle delete action?
Select an answer to reveal the explanation.
Short Explanation
Soft delete is the recycle bin; lifecycle delete is the scheduled shredder for old inventory. With soft delete on, a lifecycle delete still lands in the bin first—it does not skip retention and wipe early.
Full Explanation
Soft delete and lifecycle delete solve different problems. Soft-delete retention keeps accidentally deleted blobs recoverable (and billable) for a configured window—here 14 days for the wicker-ferry ticket scan—so administrators can undelete. Lifecycle delete removes blobs that match age/prefix/tag filters as a governance/cost control. When soft delete is enabled, a lifecycle delete generally soft-deletes first: the object leaves the active namespace but remains recoverable until soft-delete retention expires, rather than skipping soft delete entirely. Contrasting the two: soft delete protects against mistakes; lifecycle delete schedules removal by rule—and with soft delete on, scheduled deletes still enter the soft-deleted state before final purge.
Lifecycle delete immediately purging soft-deleted blobs and shortening retention to zero fails as an overstatement; soft-delete retention continues to govern recoverability after deletes, including those initiated by lifecycle, subject to how protection features interact—lifecycle does not simply zero out retention.
Treating soft delete and lifecycle delete as identical because both only change access tiers fails: neither feature is “only tiering.” Soft delete is recovery after delete; lifecycle performs tier and delete actions.
Claiming lifecycle delete cannot run if soft delete is enabled fails because the features coexist; soft delete does not disable lifecycle evaluation.
Exam caveat: during soft-delete retention, capacity charges continue for deleted blobs—budget for “recycle bin” storage after bulk lifecycle deletes. Operational check: enable soft delete, let a lifecycle rule delete a test blob, list with include-deleted, confirm recoverability within retention, and document when permanent purge occurs.