Soru

Zorluk: OrtaImplement Azure Blob Storage Lifecycle Management and Retention Policies

You have an Azure subscription with a Standard General Purpose v2 (GPv2) storage account named `medicalrecordsstore`. The container named `patients` contains the following block blobs:

* `patients/recordA.json`: Modified 120120 days ago. Tag: `ArchiveStatus` = `Ready`. No active lease.
* `patients/recordB.json`: Modified 110110 days ago. Tag: `archivestatus` = `Ready`. No active lease.
* `patients/recordC.json`: Modified 105105 days ago. Tag: `ArchiveStatus` = `Ready`. Has an active lease.

You implement the following lifecycle management policy:

{
"rules": [
{
"enabled": true,
"name": "archiveRule",
"type": "Lifecycle",
"definition": {
"actions": {
"baseBlob": {
"tierToArchive": {
"daysAfterModificationGreaterThan": 100
}
}
},
"filters": {
"blobTypes": ["blockBlob"],
"prefixMatch": ["patients/"],
"blobIndexMatch": [
{
"name": "ArchiveStatus",
"op": "==",
"value": "Ready"
}
]
}
}
}
]
}

After the policy runs, which blobs will be successfully transitioned to the Archive tier?

  1. Only patients/recordA.json and patients/recordC.jsonCevap
  2. B
    patients/recordA.json, patients/recordB.json, and patients/recordC.json
  3. C
    Only patients/recordA.json
  4. D
    None of the blobs

Cevap

Only patients/recordA.json and patients/recordC.json will be transitioned to the Archive tier.
Only patients/recordA.json and patients/recordC.json are transitioned because they both exceed the 100100-day modification age limit and possess the exact case-sensitive tag key 'ArchiveStatus' with the value 'Ready'. The active lease on patients/recordC.json does not prevent the built-in lifecycle management service from modifying the blob tier.

Adım Adım Çözüm

1
Evaluate the modification time constraint.
All three blobs (recordA.json modified 120120 days ago, recordB.json modified 110110 days ago, and recordC.json modified 105105 days ago) exceed the threshold of 100100 days since last modification.
The actions.baseBlob.tierToArchive.daysAfterModificationGreaterThan filter specifies a duration of 100100 days.
2
Apply the blob index tag filter rules.
Only recordA.json and recordC.json match the filter key 'ArchiveStatus' with value 'Ready'.
Blob index tag filters are case-sensitive. The blob recordB.json has the tag key 'archivestatus' in lowercase, which fails to match the rule's uppercase key 'ArchiveStatus'.
3
Evaluate lease status constraints on the matching blobs.
Both recordA.json and recordC.json are successfully transitioned.
Azure Blob Storage lifecycle management policy actions are execution-exempt from client-side blob leases. An active lease on recordC.json does not block the platform from performing the tier transition.

Anahtar Kavram

Azure Blob Storage lifecycle management policy execution constraints, index tag case-sensitivity, and lease interaction.
Tahmini Süre:1m 30s
Bu soruyu puanla