Examkin

Soru

Zorluk: OrtaConfigure Blob Storage Lifecycle and Replication

An organization hosts application logs in an Azure Storage account named logdata99 located in the East US region. The storage account is configured as a standard General Purpose v2 (GPv2) account with Geo-redundant storage (GRS) replication. A lifecycle management policy is active on logdata99 to transition blobs in the applogs container to the Archive tier after 30 days of inactivity. Due to a primary region outage, an administrator initiates a customer-managed failover to the secondary region (East US 2). After the failover completes, how does the lifecycle management policy behave?

  1. A
    The lifecycle management policy is automatically deleted during the failover, as lifecycle policy definitions do not replicate to the secondary region.
  2. B
    The lifecycle management policy is paused until an administrator assigns the Storage Blob Data Contributor role to the lifecycle service principal in the new primary region.
  3. The lifecycle management policy remains active and will execute on the new primary endpoint in the secondary region.Cevap
  4. D
    The lifecycle management policy continues to execute, but it will only transition blobs to the Cool tier because the Archive tier is not supported on geo-replicated secondary endpoints.

Cevap

The lifecycle management policy remains active and will execute on the new primary endpoint in the secondary region.
The correct answer is that the lifecycle management policy remains active and will execute on the new primary endpoint in the secondary region. Lifecycle management policies are metadata-level configurations of the storage account. When a storage account is configured with GRS, this metadata replicates to the secondary region. While the policy only runs on the active primary endpoint, performing a failover changes the secondary region into the new primary region. Consequently, the lifecycle management rules will resume running on the new primary endpoint.

Adım Adım Çözüm

1
Analyze how lifecycle management policies are stored.
Lifecycle policies are stored as metadata configurations on the storage account.
This configuration is automatically replicated to the secondary region when GRS is enabled.
2
Determine where lifecycle management policies execute.
Lifecycle management policies execute only on the active primary endpoint of the storage account.
During normal operations, they run in the primary region; they do not run on the read-only secondary endpoint.
3
Evaluate the state of the storage account after customer-managed failover.
The secondary region (East US 2) becomes the new primary region, and the endpoint becomes writeable.
Since the lifecycle policy is replicated, it resumes execution on the new primary endpoint.

Anahtar Kavram

Lifecycle management policy replication and execution behavior during a storage account failover
Bu soruyu puanla

Konular

Configure Blob Storage Lifecycle and Replication

Bu konudan daha fazla soru