Examkin

Soru

Zorluk: ZorData Lifecycle Management and Retention

A company is designing a data storage and retention strategy for two datasets stored in an Azure Storage account. The account must be designed to survive a primary datacenter outage and maintain regional disaster resilience. The datasets have the following requirements:

* Active Queries: These blobs are accessed frequently for the first 1010 days, followed by occasional access for the next 3535 days during which sub-second retrieval latency is required. The blobs must be deleted after a total of 4545 days.
* Audit Logs: These blobs are accessed occasionally for the first 3030 days during which sub-second retrieval latency is required. They must be retained for a total of 365365 days for compliance, after which they can be deleted. A retrieval latency of up to 1515 hours is acceptable after the initial 3030 days.

You need to select the storage account redundancy and lifecycle policy configuration that minimizes costs while meeting all requirements without incurring early deletion charges.

Which solution should you recommend?

  1. Configure the storage account with Geo-redundant storage (GRS). For Active Queries, transition to the Cool tier after 1010 days, and delete after 4545 days. For Audit Logs, transition to the Archive tier after 3030 days, and delete after 365365 days.Cevap
  2. B
    Configure the storage account with Locally redundant storage (LRS). For Active Queries, transition to the Cool tier after 1010 days, and delete after 4545 days. For Audit Logs, transition to the Archive tier after 3030 days, and delete after 365365 days.
  3. C
    Configure the storage account with Geo-redundant storage (GRS). For Active Queries, transition to the Archive tier after 1010 days, and delete after 4545 days. For Audit Logs, transition to the Cool tier after 3030 days, and delete after 365365 days.
  4. D
    Configure the storage account with Geo-redundant storage (GRS). For Active Queries, transition to the Cool tier after 1010 days, and delete after 4545 days. For Audit Logs, transition to the Archive tier immediately (after 00 days), and delete after 365365 days.

Cevap

Configure the storage account with Geo-redundant storage (GRS). For Active Queries, transition to the Cool tier after 1010 days, and delete after 4545 days. For Audit Logs, transition to the Archive tier after 3030 days, and delete after 365365 days.
The correct solution configures the storage account with Geo-redundant storage (GRS) to satisfy the regional resilience requirement, as Locally redundant storage (LRS) only replicates data within a single datacenter. For the Active Queries dataset, transitioning to the Cool tier after 1010 days and deleting after 4545 days keeps the data in the Cool tier for 3535 days, which exceeds the Cool tier's minimum retention period of 3030 days and thus avoids early deletion charges while maintaining the sub-second retrieval latency requirement. For the Audit Logs dataset, transitioning to the Archive tier after 3030 days and deleting after 365365 days keeps the data in the Archive tier for 335335 days, which exceeds the Archive tier's minimum retention period of 180180 days, minimizing costs while meeting the latency and retention requirements.

Adım Adım Çözüm

1
Determine the storage account redundancy configuration required for regional disaster resilience.
The storage account must be configured with Geo-redundant storage (GRS).
The requirements specify that the storage account must survive a primary datacenter outage and maintain regional disaster resilience. Locally redundant storage (LRS) only replicates data within a single datacenter and cannot survive a datacenter outage.
2
Determine the lifecycle policy for the Active Queries dataset based on retention and retrieval latency requirements.
Transition Active Queries to the Cool tier after 1010 days, and delete them after 4545 days.
Active Queries require sub-second retrieval latency between days 1111 and 4545. Moving them to the Archive tier would violate this requirement due to rehydration delays. Transitioning them to the Cool tier after 1010 days and deleting them after 4545 days means they spend 3535 days in the Cool tier. Since this is greater than the Cool tier's 3030-day minimum retention period, no early deletion charges are incurred.
3
Determine the lifecycle policy for the Audit Logs dataset based on retention and retrieval latency requirements.
Transition Audit Logs to the Archive tier after 3030 days, and delete them after 365365 days.
Audit Logs require sub-second retrieval latency for the first 3030 days. After 3030 days, a 1515-hour retrieval delay is acceptable, allowing them to be moved to the Archive tier to minimize costs. Since they will spend 335335 days in the Archive tier (365−30365 - 30) before deletion, this exceeds the Archive tier's 180180-day minimum retention period, avoiding early deletion charges.

Anahtar Kavram

Lifecycle management tier transitions and early deletion penalties
Bu soruyu puanla

Konular

Data Lifecycle Management and Retention

Bu konudan daha fazla soru