lifecycle policies move or delete eligible blobs based on configured conditions such as age. In this case, a team needs automatic deletion of old temporary blobs after a retention window. “Blob lifecycle management with an age-based tiering rule” would not satisfy that requirement; the supported action is “Blob lifecycle management deletion rules for eligible objects”. Lifecycle management evaluates blob age and policy filters to automate retention-related cleanup.

blob containers hold unstructured objects with account-level access and data protection controls. In this case, a team needs automatic deletion of old temporary blobs after a retention window. “Azure Blob Storage with a private container” would not satisfy that requirement; the supported action is “Blob lifecycle management deletion rules for eligible objects”. Lifecycle management evaluates blob age and policy filters to automate retention-related cleanup.

archive blobs are offline; regular reads require rehydration that is not instantaneous. In this case, a team needs automatic deletion of old temporary blobs after a retention window. “Rehydrate the archived blob to an online tier and wait for completion” would not satisfy that requirement; the supported action is “Blob lifecycle management deletion rules for eligible objects”. Lifecycle management evaluates blob age and policy filters to automate retention-related cleanup.

snapshots and versions retain earlier object states independent of a later update. In this case, a user overwrites an important blob and wants an earlier saved state. “A blob snapshot or version before destructive changes” would not satisfy that requirement; the supported action is “Blob versioning to retrieve an earlier version”. When enabled, versioning retains previous versions of modified blobs for recovery.

soft delete retains a deleted blob for a configured period before permanent removal. In this case, a user overwrites an important blob and wants an earlier saved state. “Blob soft delete with sufficient retention” would not satisfy that requirement; the supported action is “Blob versioning to retrieve an earlier version”. When enabled, versioning retains previous versions of modified blobs for recovery.

versioning improves recovery options while increasing stored data and potential costs. In this case, a user overwrites an important blob and wants an earlier saved state. “Each supported update can create a recoverable previous blob version” would not satisfy that requirement; the supported action is “Blob versioning to retrieve an earlier version”. When enabled, versioning retains previous versions of modified blobs for recovery.

Versioning helps with overwrites but does not by itself provide all desired deleted-object recovery behavior. In this case, a user accidentally deletes a blob in a container. “Blob versioning without deletion recovery retention” would not satisfy that requirement; the supported action is “Blob soft delete with sufficient retention”. Soft delete retains a deleted blob for a configured period before permanent removal.

File-share recovery protects a different storage service. In this case, a user accidentally deletes a blob in a container. “Azure Files share soft delete” would not satisfy that requirement; the supported action is “Blob soft delete with sufficient retention”. Soft delete retains a deleted blob for a configured period before permanent removal.

Lifecycle rules can remove older objects and are not a recovery mechanism. In this case, a user accidentally deletes a blob in a container. “A blob lifecycle deletion rule” would not satisfy that requirement; the supported action is “Blob soft delete with sufficient retention”. Soft delete retains a deleted blob for a configured period before permanent removal.

soft delete retains a deleted blob for a configured period before permanent removal. In this case, an administrator accidentally deletes an entire container holding important data. “Blob soft delete with sufficient retention” would not satisfy that requirement; the supported action is “Container soft delete on the storage account”. Container soft delete enables recovery of a recently deleted blob container within retention limits.

soft delete protects deleted content while versioning preserves earlier values after updates. In this case, an administrator accidentally deletes an entire container holding important data. “Enable blob soft delete and blob versioning as supported” would not satisfy that requirement; the supported action is “Container soft delete on the storage account”. Container soft delete enables recovery of a recently deleted blob container within retention limits.

data recovery must be checked alongside effective identity and file permissions. In this case, an administrator accidentally deletes an entire container holding important data. “Restored share-level authorization and file-system ACLs” would not satisfy that requirement; the supported action is “Container soft delete on the storage account”. Container soft delete enables recovery of a recently deleted blob container within retention limits.

when enabled, versioning retains previous versions of modified blobs for recovery. In this case, a compliance engineer must preserve a blob's current contents during accidental updates. “Blob versioning to retrieve an earlier version” would not satisfy that requirement; the supported action is “A blob snapshot or version before destructive changes”. Snapshots and versions retain earlier object states independent of a later update.

soft delete retains a deleted blob for a configured period before permanent removal. In this case, a compliance engineer must preserve a blob's current contents during accidental updates. “Blob soft delete with sufficient retention” would not satisfy that requirement; the supported action is “A blob snapshot or version before destructive changes”. Snapshots and versions retain earlier object states independent of a later update.

lifecycle policies can tier or remove previous versions according to supported conditions. In this case, a compliance engineer must preserve a blob's current contents during accidental updates. “Lifecycle rules targeting eligible previous blob versions” would not satisfy that requirement; the supported action is “A blob snapshot or version before destructive changes”. Snapshots and versions retain earlier object states independent of a later update.

versioning improves recovery options while increasing stored data and potential costs. In this case, a storage engineer needs to manage older blob versions and avoid uncontrolled long-term cost. “Each supported update can create a recoverable previous blob version” would not satisfy that requirement; the supported action is “Lifecycle rules targeting eligible previous blob versions”. Lifecycle policies can tier or remove previous versions according to supported conditions.

snapshots and versions retain earlier object states independent of a later update. In this case, a storage engineer needs to manage older blob versions and avoid uncontrolled long-term cost. “A blob snapshot or version before destructive changes” would not satisfy that requirement; the supported action is “Lifecycle rules targeting eligible previous blob versions”. Lifecycle policies can tier or remove previous versions according to supported conditions.

when enabled, versioning retains previous versions of modified blobs for recovery. In this case, a storage engineer needs to manage older blob versions and avoid uncontrolled long-term cost. “Blob versioning to retrieve an earlier version” would not satisfy that requirement; the supported action is “Lifecycle rules targeting eligible previous blob versions”. Lifecycle policies can tier or remove previous versions according to supported conditions.

when enabled, versioning retains previous versions of modified blobs for recovery. In this case, an app's blob has several past versions after many writes. “Blob versioning to retrieve an earlier version” would not satisfy that requirement; the supported action is “Each supported update can create a recoverable previous blob version”. Versioning improves recovery options while increasing stored data and potential costs.

lifecycle policies can tier or remove previous versions according to supported conditions. In this case, an app's blob has several past versions after many writes. “Lifecycle rules targeting eligible previous blob versions” would not satisfy that requirement; the supported action is “Each supported update can create a recoverable previous blob version”. Versioning improves recovery options while increasing stored data and potential costs.

soft delete protects deleted content while versioning preserves earlier values after updates. In this case, an app's blob has several past versions after many writes. “Enable blob soft delete and blob versioning as supported” would not satisfy that requirement; the supported action is “Each supported update can create a recoverable previous blob version”. Versioning improves recovery options while increasing stored data and potential costs.

File-share snapshots do not provide Blob overwrite/deletion recovery. In this case, an organization needs both recovery from deletion and recovery from overwrite. “Only enable Azure Files share snapshots” would not satisfy that requirement; the supported action is “Enable blob soft delete and blob versioning as supported”. Soft delete protects deleted content while versioning preserves earlier values after updates.

ARM locks are not a substitute for blob-level version history and soft delete. In this case, an organization needs both recovery from deletion and recovery from overwrite. “Only configure an Azure storage account resource lock” would not satisfy that requirement; the supported action is “Enable blob soft delete and blob versioning as supported”. Soft delete protects deleted content while versioning preserves earlier values after updates.

Archive changes access/storage tradeoffs but does not provide deleted/overwritten version recovery. In this case, an organization needs both recovery from deletion and recovery from overwrite. “Enable archive tier on every blob” would not satisfy that requirement; the supported action is “Enable blob soft delete and blob versioning as supported”. Soft delete protects deleted content while versioning preserves earlier values after updates.

versioning improves recovery options while increasing stored data and potential costs. In this case, a file share backup has been restored, but some user permissions are unexpectedly different. “Each supported update can create a recoverable previous blob version” would not satisfy that requirement; the supported action is “Restored share-level authorization and file-system ACLs”. Data recovery must be checked alongside effective identity and file permissions.

when enabled, versioning retains previous versions of modified blobs for recovery. In this case, a file share backup has been restored, but some user permissions are unexpectedly different. “Blob versioning to retrieve an earlier version” would not satisfy that requirement; the supported action is “Restored share-level authorization and file-system ACLs”. Data recovery must be checked alongside effective identity and file permissions.

container soft delete enables recovery of a recently deleted blob container within retention limits. In this case, a file share backup has been restored, but some user permissions are unexpectedly different. “Container soft delete on the storage account” would not satisfy that requirement; the supported action is “Restored share-level authorization and file-system ACLs”. Data recovery must be checked alongside effective identity and file permissions.

outputs publish selected deployment results to the caller after resource provisioning. In this case, an administrator must provision the same VNet configuration repeatedly across test environments. “A Bicep output or ARM template output expression” would not satisfy that requirement; the supported action is “Deploy a parameterized Bicep file defining the VNet”. Bicep defines desired Azure resources declaratively and accepts environment-specific parameter values.

variables and expressions compute names consistently without embedding separate environment-specific templates. In this case, an administrator must provision the same VNet configuration repeatedly across test environments. “A Bicep variable or expression derived from parameters” would not satisfy that requirement; the supported action is “Deploy a parameterized Bicep file defining the VNet”. Bicep defines desired Azure resources declaratively and accepts environment-specific parameter values.

parameters allow the same template definition to be reused with different input values. In this case, an administrator must provision the same VNet configuration repeatedly across test environments. “Replace the location literal with a deployment parameter” would not satisfy that requirement; the supported action is “Deploy a parameterized Bicep file defining the VNet”. Bicep defines desired Azure resources declaratively and accepts environment-specific parameter values.

a reusable template can derive or accept scope values rather than rely on embedded tenant-specific identifiers. In this case, a template uses a hard-coded location that differs between regions. “Use parameters and deployment context functions for required scope information” would not satisfy that requirement; the supported action is “Replace the location literal with a deployment parameter”. Parameters allow the same template definition to be reused with different input values.

parameterization separates environment choices from the shared declarative infrastructure definition. In this case, a template uses a hard-coded location that differs between regions. “Parameterize the SKU and pass its approved value at deployment” would not satisfy that requirement; the supported action is “Replace the location literal with a deployment parameter”. Parameters allow the same template definition to be reused with different input values.

the parameters block describes values supplied when a template is deployed. In this case, a template uses a hard-coded location that differs between regions. “The template's parameters section” would not satisfy that requirement; the supported action is “Replace the location literal with a deployment parameter”. Parameters allow the same template definition to be reused with different input values.