A retail company stores transaction logs in an Azure General Purpose v2 (GPv2) storage account. The storage account is configured with Read-access geo-redundant storage (RA-GRS), with East US as the primary region and West US as the secondary region. To comply with regulatory audit requirements, the company's IT team plans to perform a disaster recovery drill by initiating a customer-managed failover of the storage account to the secondary region. Which two outcomes will occur once the failover is complete? (Select two.)
- The storage account's redundancy configuration is converted to locally-redundant storage (LRS).Answer
- The primary connection endpoints for the blob, file, queue, and table services remain unchanged.Answer
- CThe storage account is automatically configured to replicate data back to the East US region as geo-redundant storage.
- DThe application can perform write operations to the secondary endpoint using the -secondary suffix during the failover process.
Answer
Once the customer-managed failover completes, the storage account's redundancy configuration is converted to locally-redundant storage (LRS), and the primary connection endpoints for the storage services remain unchanged.
When a customer-managed failover is initiated for an RA-GRS storage account, the secondary region becomes the new primary region, and the account type is automatically converted to LRS. Azure automatically updates the DNS settings so that the existing primary endpoints resolve to the new primary region, allowing applications using the primary connection strings to remain unchanged.
Step-by-Step Solution
Key Concept
Azure Storage customer-managed failover behavior and endpoint lifecycle.
Estimated Time:1m 30s