Examkin

Question

Difficulty: MediumImplement Azure Blob Storage Lifecycle Management and Retention Policies

A company uses a Standard General Purpose v2 (GPv2) storage account to store temporary media processing files in a container named incoming-transcodes. You configure a lifecycle management policy to delete all blobs in this container 7 days after they are created. Some of these blobs are actively leased by processing worker roles, while others are accessed by external clients using Shared Access Signatures (SAS). Which of the following describes the execution behavior of the lifecycle management policy when it runs?

  1. A
    The lifecycle management policy only deletes the blobs if they are accessed via SAS tokens that explicitly include the delete permission scope.
  2. The lifecycle management policy executes and deletes the blobs regardless of active leases or the permissions of SAS tokens used to access the blobs.Answer
  3. C
    The lifecycle management policy fails to delete the blobs if they have active leases, as it cannot override the write lock of an active lease.
  4. D
    The lifecycle management policy bypasses the blobs if they are associated with case-sensitive metadata keys that contain uppercase letters.

Answer

The lifecycle management policy executes and deletes the blobs regardless of active leases or the permissions of SAS tokens used to access the blobs.
The correct answer states that the lifecycle management policy executes and deletes the blobs regardless of active leases or SAS permissions. Azure Blob Storage lifecycle management runs as a platform-level background process. While client applications must honor blob leases and SAS token permissions when performing operations on blobs, the lifecycle management service executes with administrative privileges and is not blocked by active leases or client-level access restrictions.

Step-by-Step Solution

1
Analyze the execution environment of Azure Blob Storage lifecycle management.
Identify that lifecycle management policies are service-level control plane operations defined directly on the storage account.
This establishes that the policy runs with native system privileges rather than under a specific user context or client session.
2
Evaluate the impact of active blob leases on lifecycle management execution.
Recall that active leases on blobs block client-side modifications/deletions but do not block service-level lifecycle management policies.
This determines that the leased blobs will still be successfully deleted when the rule runs.
3
Evaluate the impact of SAS tokens on lifecycle policy execution.
Recognize that lifecycle policies do not require client SAS permissions to execute.
Since the policy is defined at the account level and executes internally, SAS token permissions are irrelevant to the deletion process.

Key Concept

Azure Blob Storage Lifecycle Management Execution Mechanics
Estimated Time:1m 30s
Rate this question

Topics

Implement Azure Blob Storage Lifecycle Management and Retention Policies

More questions from this topic