Examkin

Question

Difficulty: HardConfigure Blob Storage Lifecycle and Replication

An administrator is configuring a standard General Purpose v2 (GPv2) storage account named `mystorage` that currently uses locally-redundant storage (LRS). The administrator needs to configure blob lifecycle management rules and plan for replication upgrades.

Which two configurations are valid or represent correct behaviors for this storage account?

  1. The replication configuration can be converted from LRS to Geo-Redundant Storage (GRS) directly in the Azure portal without downtime.Answer
  2. A lifecycle management policy can be configured to filter blobs using blob index tags to transition them to the Archive tier.Answer
  3. C
    The replication configuration can be converted from LRS to Zone-Redundant Storage (ZRS) directly from the Azure portal configuration blade.
  4. D
    Assigning the storage account Owner role at the resource group level allows administrators to read archived blobs directly without performing a rehydration action.

Answer

The replication configuration can be converted from LRS to Geo-Redundant Storage (GRS) directly in the Azure portal without downtime, and a lifecycle management policy can be configured to filter blobs using blob index tags to transition them to the Archive tier.
The correct configurations are converting from LRS to Geo-Redundant Storage (GRS) directly in the Azure portal without downtime, and using blob index tags in a lifecycle management policy to filter blobs transitioning to the Archive tier. Converting standard GPv2 storage accounts from LRS to GRS is fully supported online, and blob index tags provide granular criteria filtering for lifecycle actions.

Step-by-Step Solution

1
Determine valid replication migration paths.
LRS to GRS conversion can be done online without downtime directly in the portal. However, LRS to ZRS is not direct and requires requesting a live migration from Microsoft Support or performing manual data copy.
Azure allows upgrading standard GPv2 storage accounts from LRS to GRS seamlessly, but converting to ZRS has zone-specific migration requirements.
2
Analyze lifecycle policy capabilities and filtering.
Lifecycle policies support transitioning blobs to Cool, Cold, Archive, or deleting them. Filtering can be done via prefix matches or blob index tags.
Blob index tags allow granular lifecycle rule execution based on key-value attributes associated with the blobs.
3
Review data access and rehydration requirements.
Blobs in the Archive tier are offline and cannot be read directly regardless of the RBAC permissions held by the user; they must first be rehydrated.
Archive tier is an offline tier designed for archival data, and direct read operations are blocked at the storage account data plane.

Key Concept

Blob Storage Lifecycle Policies and Replication Settings
Estimated Time:2m 0s
Rate this question

Topics

Configure Blob Storage Lifecycle and Replication

More questions from this topic