You have a General Purpose v2 (GPv2) storage account named `storagedata` in the East US region. The storage account is configured with Geo-Redundant Storage (GRS). A lifecycle management policy is active on the account, which automatically transitions block blobs in a container named `logs` to the Archive tier 30 days after they are created.
Due to a disaster in the primary region, you initiate a customer-managed failover for the storage account.
What is the state of the storage account replication and the archived blobs after the failover completes?
- The storage account replication changes to Locally Redundant Storage (LRS). The archived blobs remain in the Archive tier and must be rehydrated to an online tier before they can be read.Cevap
- BThe storage account replication changes to Locally Redundant Storage (LRS). The archived blobs are automatically rehydrated to the Hot tier to ensure availability.
- CThe storage account replication remains Geo-Redundant Storage (GRS). Users with the Storage Blob Data Reader role can read the archived blobs directly without rehydration.
- DThe storage account replication changes to Read-Access Geo-Redundant Storage (RA-GRS). The archived blobs are moved to the Cold tier to reduce storage costs.
Cevap
The storage account replication changes to Locally Redundant Storage (LRS). The archived blobs remain in the Archive tier and must be rehydrated to an online tier before they can be read.
When a customer-managed failover is initiated for a Geo-Redundant Storage (GRS) account, the secondary region becomes the new primary region, and the replication configuration changes to Locally Redundant Storage (LRS). Archived blobs are failed over successfully but remain in the Archive tier. They must be rehydrated to an online tier (Hot or Cool) before their data can be accessed.
Adım Adım Çözüm
Anahtar Kavram
Storage Account Failover and Lifecycle Tier Behavior