Examkin

Question

Difficulty: EasyImplement Azure Blob Storage Lifecycle Management and Retention Policies

You are implementing an Azure Blob Storage lifecycle management policy for a Standard General Purpose v2 (GPv2) storage account to automate data tiering. Which two of the following statements are correct regarding the configuration and execution of these policies? (Select two.)

  1. The lifecycle management policy is executed by the Azure Storage service once every 24 hours.Answer
  2. The policy actions, such as tierToCool and delete, are valid operations applied to the baseBlob type.Answer
  3. C
    To allow the policy to execute, you must generate a Shared Access Signature (SAS) token with delete permissions and bind it to the policy.
  4. D
    If a target blob is locked with an active lease, the lifecycle policy automatically acquires the lease ID to perform the delete action.

Answer

The lifecycle management policy is executed by the Azure Storage service once every 24 hours, and the policy actions, such as tierToCool and delete, are valid operations applied to the baseBlob type.
The lifecycle management policy is executed by the Azure Storage platform once every 24 hours. Furthermore, actions such as tierToCool, tierToArchive, and delete are standard, valid operations that can be defined under the baseBlob node of the policy rule schema.

Step-by-Step Solution

1
Analyze the execution schedule of Azure Blob Storage lifecycle management policies.
Confirm that lifecycle management runs once daily (every 24 hours) automatically.
This is a platform-managed background process that runs on a daily cycle.
2
Identify valid actions for base blobs (baseBlob) in the policy rules.
Verify that tierToCool, tierToArchive, and delete are supported actions.
The lifecycle rule schema defines these actions for baseBlob to manage the data lifecycle.
3
Evaluate the security and execution requirements of the policy.
Note that native platform policies do not require custom SAS tokens and respect active blob leases.
Security is handled natively by Azure, and active leases block policy executions to prevent accidental data modification or deletion.

Key Concept

Azure Blob Storage Lifecycle Management execution rules and action schema on Standard GPv2 storage accounts.
Rate this question

Topics

Implement Azure Blob Storage Lifecycle Management and Retention Policies

More questions from this topic