Examkin

Soru

Zorluk: Çok zorImplement Azure Blob Storage Lifecycle Management and Retention Policies

An organization uses a Standard General Purpose v2 (GPv2) storage account to store compliance reports in a container. A lifecycle management policy is active with a rule that transitions all blobs in the container to the Archive tier 30 days after they are last modified. The lifecycle management policy executes once every 24 hours.

You need to rehydrate an archived blob named `reports/2025_audit.pdf` to the Hot tier to perform a 5-day audit analysis. You must ensure that the lifecycle management policy does not transition the blob back to the Archive tier during the 5-day analysis period.

Which sequence of actions should you perform? To answer, arrange the actions in the correct order.

  1. 1Call the Set Blob Tier API (or use the Azure portal/CLI) to set the tier of the blob to Hot.
  2. 2Monitor the blob's properties and wait until the rehydration status shows that the transition to the Hot tier is complete.
  3. 3Perform a metadata write operation (such as setting a custom metadata key-value pair) on the rehydrated blob.
  4. 4Begin the 5-day audit analysis and perform the required read operations on the blob.

Cevap

To safely rehydrate the blob and prevent it from being immediately re-archived, first initiate the rehydration by setting the blob's tier to Hot. Next, wait for the rehydration process to complete and the blob's status to transition to Hot. Then, perform a metadata write operation to update the Last-Modified timestamp. Finally, begin the 5-day audit analysis and perform the required read operations.
The correct order requires first initiating the rehydration of the blob to the Hot tier because it is currently offline and metadata writes are blocked. Once rehydration completes, you must perform a metadata write operation (such as setting dummy metadata properties) to update the Last-Modified timestamp. Since the lifecycle management policy evaluates the last-modified time and runs once every 24 hours, updating the metadata resets the lifecycle clock and prevents the policy from re-archiving the blob during the 5-day audit analysis.

Adım Adım Çözüm

1
Call Set Blob Tier to transition the blob to the Hot tier.
The blob status changes to rehydrate-pending-to-hot.
The blob must be rehydrated from the Archive tier before its data can be read or its metadata updated.
2
Monitor the blob properties and wait for the tier to transition to Hot.
The blob tier becomes Hot and the pending status clears.
You must wait for the blob to be online in the Hot tier before any metadata write operations can be performed.
3
Update the blob's metadata or properties.
The blob's Last-Modified timestamp is updated to the current date and time.
Changing a blob's tier via Set Blob Tier does not update its Last-Modified time. Because the policy archives blobs older than 30 days and runs every 24 hours, the policy would archive the blob again on its next execution unless the Last-Modified timestamp is refreshed.
4
Perform the required read operations for the 5-day audit analysis.
The audit analysis is completed while the blob remains in the Hot tier.
The updated Last-Modified timestamp ensures the lifecycle policy will not archive the blob for another 30 days.

Anahtar Kavram

Rehydrating blobs from the Archive tier and preventing immediate re-archiving by updating the Last-Modified timestamp via metadata modifications.
Bu soruyu puanla

Konular

Implement Azure Blob Storage Lifecycle Management and Retention Policies

Bu konudan daha fazla soru