Examkin

Question

Difficulty: HardConfigure Blob Storage Lifecycle and Replication

An administrator manages a General Purpose v2 (GPv2) storage account named storagelogsa in the East US region. The storage account is currently configured to use Locally Redundant Storage (LRS) and contains block blobs in a container named activitylogs.

A lifecycle management policy is applied to the storage account with a single rule:
- Filter: Blob prefix is activitylogs/archive/
- Action: Transition blobs to the Archive tier 30 days after modification.

Currently, the container contains:
- 500 blobs under activitylogs/raw/ (all modified 45 days ago, currently in the Hot tier)
- 200 blobs under activitylogs/archive/ (all modified 45 days ago, currently in the Archive tier)

You need to change the replication configuration of the storage account from LRS to Zone-Redundant Storage (ZRS) to ensure zonal availability. When you attempt to change the replication setting in the Azure portal, the option is unavailable.

Which of the following actions should you perform first to enable the replication configuration change?

  1. Rehydrate the 200 blobs in the activitylogs/archive/ path to the Hot or Cool tier.Answer
  2. B
    Assign the Storage Blob Data Contributor role to your user account at the container scope.
  3. C
    Temporarily delete the lifecycle management policy, and then wait 24 hours for the policy status to clear.
  4. D
    Perform a customer-managed failover by temporarily converting the storage account replication to Geo-Redundant Storage (GRS).

Answer

Rehydrate the 200 blobs in the activitylogs/archive/ path to the Hot or Cool tier.
The correct action is to rehydrate the archived blobs. Azure Storage replication conversions (such as moving from Locally Redundant Storage to Zone-Redundant Storage) are blocked if the storage account contains any blobs in the Archive tier. Rehydrating the blobs under the archived path to Hot or Cool tier satisfies this prerequisite.

Step-by-Step Solution

1
Analyze the current state of the blobs and lifecycle policy rules.
Identify that the 200 blobs under the prefix activitylogs/archive/ have been transitioned to the Archive tier because they were modified 45 days ago, which exceeds the 30-day threshold defined in the lifecycle policy.
Understanding the tier of the existing blobs is critical since replication changes have specific tier restrictions.
2
Evaluate the replication conversion requirements for Azure storage accounts.
Identify that Azure blocks changing the replication configuration (e.g., LRS to ZRS) of any storage account that contains blobs in the Archive tier.
Archived blobs are offline and must be rehydrated to an online tier (Hot or Cool) before metadata or configuration changes like replication conversion can be applied.
3
Select the correct remediation step.
Determine that the archived blobs must be rehydrated first to allow the replication change to proceed.
Rehydrating the blobs brings them back to an online tier, fulfilling the prerequisite for changing the storage account replication configuration.

Key Concept

Azure Storage replication changes are blocked if the storage account contains any blobs in the Archive tier. Before converting replication (such as LRS to ZRS), all archived blobs must be rehydrated to Hot or Cool.
Rate this question

Topics

Configure Blob Storage Lifecycle and Replication

More questions from this topic