Examkin

Soru

Zorluk: ZorConfigure Blob Storage Lifecycle and Replication

An organization has an Azure standard General Purpose v2 (GPv2) storage account named corpstoreupload in West US 2. The account currently uses Locally-redundant storage (LRS) and contains a blob container named invoices.

You need to meet the following requirements:
1. Provide read-only access to the data in a secondary region without waiting for a failover to be initiated if the primary region becomes unavailable.
2. Automatically move blobs in the invoices container to the Archive tier if they have not been modified for more than 90 days.
3. Automatically delete blobs in the invoices container if they have not been modified for more than 365 days.

Which of the following statements describe correct configurations or behaviors for this scenario? (Select TWO.)

  1. You can change the replication setting of the storage account directly from LRS to Read-access geo-redundant storage (RA-GRS) without data migration, but blobs transitioned to the Archive tier cannot be read from the secondary endpoint until they are rehydrated.Cevap
  2. You must configure a lifecycle management policy with a rule that filters by the prefix invoices/ and contains actions to transition blobs to the Archive tier after 90 days of modification, and to delete blobs after 365 days of modification.Cevap
  3. C
    To enable geo-redundancy, you must request a live migration from Microsoft Support to convert the storage account from LRS to Zone-redundant storage (ZRS) before you can change the replication to Read-access geo-zone-redundant storage (RA-GZRS), as LRS cannot be directly changed to geo-redundant replication.
  4. D
    To allow users to read the replicated blobs from the secondary endpoint, you only need to assign them the Reader role at the resource group level, as control plane roles automatically grant data-plane access to secondary endpoints.

Cevap

Converting the storage account directly from LRS to RA-GRS (where archived blobs must still be rehydrated to be read) and configuring a lifecycle policy rule with the prefix invoices/ to transition blobs to the Archive tier after 90 days and delete them after 365 days.
Changing replication from LRS to RA-GRS is a direct configuration update that does not require data migration. Archived blobs are offline and cannot be read from the primary or secondary endpoints until they are rehydrated. Additionally, Azure Lifecycle Management policies support prefix-filtered rules with multiple actions, allowing both a transition to the Archive tier after 90 days and deletion after 365 days in a single policy rule.

Adım Adım Çözüm

1
Analyze the replication requirement to provide read access to the secondary region without waiting for failover.
Determine that Read-Access Geo-Redundant Storage (RA-GRS) satisfies this requirement, and that a GPv2 storage account can be directly converted from LRS to RA-GRS without data migration.
RA-GRS replicates data to a secondary region and exposes a secondary read-only endpoint.
2
Analyze the lifecycle management requirement for the invoices container.
Create a lifecycle management rule using the prefix filter invoices/ with two actions: transition to Archive tier after 90 days since modification, and delete after 365 days since modification.
Lifecycle management rules allow targeting specific prefixes and executing multiple tiering/deletion actions sequentially.
3
Evaluate the behavior of archived blobs under RA-GRS replication.
Confirm that archived blobs are replicated to the secondary region but remain offline and unreadable at both endpoints until rehydrated.
The Archive tier is an offline tier, and rehydration is mandatory to access the blob data regardless of the replication setting.

Anahtar Kavram

Configuring storage replication from LRS to RA-GRS and implementing sequential lifecycle management policy rules.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Configure Blob Storage Lifecycle and Replication

Bu konudan daha fazla soru