Examkin

Question

Difficulty: MediumConfigure Blob Storage Lifecycle and Replication

A company stores compliance archives in an Azure Blob Storage account named stlogscollector in the East US region. The storage account is configured for Read-access geo-redundant storage (RA-GRS) and has an active lifecycle management policy that transitions block blobs to the Archive tier after 30 days of inactivity. Due to a prolonged outage in the primary region, a customer-managed failover is successfully completed. What is the replication configuration and lifecycle policy status of the storage account immediately after the failover process finishes?

  1. A
    The replication type remains Read-access geo-redundant storage (RA-GRS), but the lifecycle management policy is paused until a failback operation is executed.
  2. B
    The replication type is upgraded to Geo-zone-redundant storage (GZRS), and the lifecycle management policy is permanently disabled.
  3. The replication type becomes Locally-redundant storage (LRS), and the lifecycle management policy continues to function normally.Answer
  4. D
    The replication type becomes Locally-redundant storage (LRS), but the lifecycle management policy is disabled until the administrator is assigned the Storage Blob Data Contributor role in the new primary region.

Answer

The replication type becomes Locally-redundant storage (LRS), and the lifecycle management policy continues to function normally.
The correct option explains that when a failover is initiated for a Geo-redundant storage (GRS) or Read-access geo-redundant storage (RA-GRS) account, the storage account replication type is automatically converted to Locally-redundant storage (LRS) in the new primary region. Additionally, lifecycle management policies are part of the storage account configuration and are preserved during failover, meaning they will continue to run normally in the new primary region.

Step-by-Step Solution

1
Determine the impact of a customer-managed failover on the replication configuration of the storage account.
The replication configuration changes from Read-access geo-redundant storage (RA-GRS) to Locally-redundant storage (LRS) in the new primary region.
When a failover is executed, the secondary region becomes the new primary, and geo-replication is terminated, forcing the replication type to LRS.
2
Evaluate the state of the existing lifecycle management policy following the failover.
The lifecycle management policy remains active and continues to execute in the new primary region.
Lifecycle policies are metadata and control plane configurations associated with the storage account itself, which are preserved and remain functional across regional failovers.
3
Verify whether administrator data-plane role assignments are required to resume lifecycle operations.
No role modifications are necessary because the lifecycle policy runs as a built-in service process.
Azure Storage executes lifecycle rules internally using system permissions, meaning user role changes have no effect on policy execution.

Key Concept

Storage account replication failover behavior and lifecycle policy persistence
Rate this question

Topics

Configure Blob Storage Lifecycle and Replication

More questions from this topic