Examkin

Question

Difficulty: MediumConfigure Blob Storage Lifecycle and Replication

You manage a standard General Purpose v2 (GPv2) storage account named `streports2026` in the North Europe region. The storage account is configured with Locally-Redundant Storage (LRS) and contains a container named `finance`.

You have the following requirements:
1. Replicate the storage account data to the West Europe region and ensure the data is immediately readable in the secondary region.
2. Automatically transition blobs in the `finance` container to the Cool tier 30 days after modification, and delete them after 365 days.

Which of the following actions should you perform? (Select TWO.)

  1. Change the replication configuration of the storage account from Locally-redundant storage (LRS) to Read-access geo-redundant storage (RA-GRS).Answer
  2. Create a lifecycle management policy rule that filters by the prefix finance/ and applies transition and deletion actions based on last modification time.Answer
  3. C
    Submit a support request to Microsoft to initiate a live migration of the storage account replication from Locally-redundant storage (LRS) to Read-access geo-redundant storage (RA-GRS).
  4. D
    Assign the Storage Blob Data Owner role to the storage account's system-assigned managed identity to authorize the execution of the lifecycle management policy.

Answer

The correct actions are to change the replication configuration of the storage account from Locally-redundant storage (LRS) to Read-access geo-redundant storage (RA-GRS), and to create a lifecycle management policy rule that filters by the prefix finance/ and applies transition and deletion actions based on last modification time.
To satisfy the replication requirement, the storage account's replication configuration must be changed from Locally-redundant storage (LRS) to Read-access geo-redundant storage (RA-GRS), which replicates the data to the paired region and makes it immediately readable. To satisfy the lifecycle requirement, a lifecycle management policy rule must be created that applies prefix filtering (specifying the container name 'finance/') and defines the transition and deletion actions based on the number of days since last modification.

Step-by-Step Solution

1
Change the storage account's replication setting from Locally-redundant storage (LRS) to Read-access geo-redundant storage (RA-GRS) via the Redundancy blade in the Azure Portal.
The storage account is configured to replicate data asynchronously to the paired region (West Europe) with read access enabled for the secondary endpoint.
This is a direct configuration update that satisfies the requirement for readable secondary geo-replication without requiring a support ticket.
2
Add a new rule in the Lifecycle Management blade of the storage account.
A rule is defined with a prefix filter matching the container path.
Lifecycle management rules require prefix filters (e.g., 'finance/') to target specific containers rather than the entire storage account.
3
Define the rule actions to transition blobs to the Cool tier 30 days after modification, and delete them 365 days after modification.
The lifecycle policy automatically processes the blobs in the 'finance' container according to the defined timeline.
This implements automated tiering and cleanup based on the last modified date to optimize storage costs.

Key Concept

Configuring Azure Blob Storage replication changes and setting up container-scoped lifecycle management policies.
Rate this question

Topics

Configure Blob Storage Lifecycle and Replication

More questions from this topic