Examkin

Question

Difficulty: MediumConfigure Blob Storage Lifecycle and Replication

An administrator manages a standard General Purpose v2 (GPv2) storage account named stbackup2026 in the East US region. The storage account currently uses Locally Redundant Storage (LRS). To meet new corporate policies, the administrator must ensure the storage account is protected against regional outages. Additionally, any logs stored in a container named 'temp-logs' must be automatically deleted 30 days after they are created. Which two actions should the administrator perform to meet these requirements?

  1. Change the replication configuration of the storage account from Locally Redundant Storage (LRS) to Geo-Redundant Storage (GRS).Answer
  2. Create a lifecycle management policy with a rule that filters by the 'temp-logs' prefix and deletes blobs 30 days after creation.Answer
  3. C
    Initiate a customer-managed account failover to convert the storage account from Locally Redundant Storage (LRS) to Geo-Redundant Storage (GRS).
  4. D
    Assign the Storage Blob Data Owner role at the storage account scope to the system-assigned managed identity of the lifecycle management policy.

Answer

The administrator should change the replication configuration of the storage account to Geo-Redundant Storage (GRS) and configure a lifecycle management policy with a rule that targets the 'temp-logs' container to delete blobs 30 days after creation.
To satisfy the requirements, the administrator needs to change the replication type of the storage account to a geo-redundant option (such as Geo-Redundant Storage) to protect against regional outages, and configure a native lifecycle management rule with a prefix filter matching the specific container name to automatically delete the blobs 30 days after creation.

Step-by-Step Solution

1
Navigate to the storage account configuration settings in the Azure portal or use Azure CLI/PowerShell, and change the replication from Locally Redundant Storage (LRS) to Geo-Redundant Storage (GRS).
The storage account data is replicated asynchronously to the paired secondary region, meeting the protection requirement against regional outages.
GRS provides regional disaster recovery protection by keeping three copies of data in the primary region and three copies in the secondary region.
2
Navigate to the lifecycle management blade under data management, add a new rule targeting blob creation time, set the action to delete the blob 30 days after creation, and apply a prefix filter matching the 'temp-logs' container name.
A native lifecycle policy is established to automatically clean up the log files without administrative overhead.
Lifecycle management provides automated, rule-based deletion and tiering transitions, and the prefix filter limits the rule scope to the designated container.

Key Concept

Azure Storage replication conversion paths and Blob lifecycle management policy rules.
Estimated Time:1m 30s
Rate this question

Topics

Configure Blob Storage Lifecycle and Replication

More questions from this topic