Examkin

Question

Difficulty: MediumImplement Azure Blob Storage Lifecycle Management and Retention Policies

You are configuring a lifecycle management policy for a Standard General Purpose v2 (GPv2) storage account to automate data tiering for diagnostic logs. The logs are stored as block blobs.

You define the following JSON policy rule:

{
"rules": [
{
"enabled": true,
"name": "ArchiveAndCleanupLogs",
"type": "Lifecycle",
"definition": {
"actions": {
"baseBlob": {
"tierToArchive": {
"daysAfterModificationGreaterThan": 30
},
"delete": {
"daysAfterModificationGreaterThan": 90
}
}
},
"filters": {
"blobTypes": [
"blockBlob"
],
"prefixMatch": [
"logs/daily"
],
"blobIndexMatch": [
{
"name": "environment",
"op": "==",
"value": "production"
}
]
}
}
}
]
}

Which two of the following statements regarding the behavior, configuration, and execution of this policy are correct?

  1. Blobs with the tag key 'Environment' (with a capital 'E') set to 'production' will not be transitioned or deleted by this rule because blob index tag names and values are case-sensitive.Answer
  2. B
    If a matching blob has an active lease, you must add a leaseId property inside the delete action block of the JSON policy to allow the platform to delete the leased blob.
  3. The Azure storage platform executes the lifecycle management policy once every 2424 hours to evaluate the blobs and execute the defined actions.Answer
  4. D
    To authorize the execution of the lifecycle rules, you must append a Shared Access Signature (SAS) token with write and delete permissions to the prefixMatch container path.

Answer

The correct statements are that blobs with the tag key 'Environment' set to 'production' will not be transitioned or deleted because blob index tag names and values are case-sensitive, and that the Azure storage platform executes the lifecycle management policy once every 2424 hours.
The correct statements describe the case-sensitivity of blob index tags, which prevents mismatching casings like 'Environment' from being processed, and the platform's execution schedule of once every 2424 hours for lifecycle policies.

Step-by-Step Solution

1
Analyze the case-sensitivity of the blobIndexMatch filter defined in the policy.
The filter specifies a tag name of 'environment' and a value of 'production'.
Because blob index tags are case-sensitive in Azure Blob Storage lifecycle management, blobs with the tag 'Environment' (capital 'E') will not match this filter and will not be processed by this rule.
2
Evaluate the execution frequency of the Azure Blob Storage lifecycle management policies.
The platform runs these policies automatically once per day.
This is a platform-level constraint where policy rules are evaluated on a 2424-hour execution schedule.
3
Analyze the distractors regarding active leases and SAS tokens.
Lifecycle policies do not accept a leaseId parameter in the action schema and do not use SAS tokens for authentication.
Leased blobs will fail to delete during the lifecycle execution run without breaking the lease first, and the policy execution is a built-in platform mechanism requiring no SAS credentials.

Key Concept

Azure Blob Storage Lifecycle Management policy rules, tag case-sensitivity, and execution schedule on Standard GPv2 accounts.
Estimated Time:1m 30s
Rate this question

Topics

Implement Azure Blob Storage Lifecycle Management and Retention Policies

More questions from this topic