Examkin

Soru

Zorluk: ZorData Lifecycle Management and Retention

A company is designing a data storage solution on Azure Blob Storage to store monthly application transaction logs. The logs are stored in a General-purpose v2 storage account. The lifecycle requirements for the logs are as follows:
- For the first 4545 days after creation, logs are actively queried by an analytical application requiring sub-second retrieval latency.
- From day 4646 to day 180180, logs are rarely accessed, but when they are, they must be retrieved within 55 minutes.
- From day 181181 to day 365365, logs are only stored for compliance preparation. Retrieval latency of up to 1515 hours is acceptable.
- After 365365 days, the logs must be deleted permanently.

To minimize storage and retrieval costs, which of the following lifecycle management rule configurations should you recommend?

  1. Transition blobs to the Cold tier after 4545 days, transition to the Archive tier after 180180 days, and delete the blobs after 365365 days.Cevap
  2. B
    Transition blobs to the Archive tier after 4545 days, and delete the blobs after 365365 days.
  3. C
    Transition blobs to the Cool tier after 4545 days, transition to the Archive tier after 300300 days, and delete the blobs after 365365 days.
  4. D
    Transition blobs to the Cold tier after 4545 days, transition to the Archive tier after 9090 days, and delete the blobs after 365365 days.

Cevap

Transition blobs to the Cold tier after 4545 days, transition to the Archive tier after 180180 days, and delete the blobs after 365365 days.
Transitioning blobs to the Cold tier after 4545 days satisfies the 55-minute retrieval requirement since the Cold tier offers sub-second retrieval latency, and it is more cost-effective than the Cool tier. The blobs remain in the Cold tier for 135135 days (from day 4646 to 180180), which is greater than the Cold tier's 9090-day minimum retention period, avoiding any early deletion penalties. Transitioning to the Archive tier after 180180 days is acceptable because the 1515-hour retrieval latency matches the Archive tier's standard rehydration speed. The blobs reside in the Archive tier for 185185 days (from day 181181 to 365365), which exceeds the Archive tier's 180180-day minimum retention period, avoiding early deletion penalties upon final deletion on day 366366.

Adım Adım Çözüm

1
Analyze retrieval latency requirements for each period to map compatible Azure Blob Storage tiers.
Days 11 to 4545 require sub-second latency (Hot tier). Days 4646 to 180180 require under 55 minutes (Hot, Cool, or Cold tiers are valid; Archive is invalid due to hours-long rehydration latency). Days 181181 to 365365 allow up to 1515 hours (Archive tier is valid).
Mapping latency limits guarantees that performance requirements are satisfied in every phase.
2
Determine the most cost-effective tier for the second phase (days 4646 to 180180) and check minimum retention limits.
Cold tier is selected because it has lower storage costs than Cool tier and meets the sub-second retrieval latency requirement. The logs remain in the Cold tier for 135135 days (from day 4646 to 180180). This exceeds the Cold tier minimum retention period of 9090 days, ensuring no early deletion or transition penalties are incurred.
Optimizing cost in intermediate tiers requires comparing storage rates and matching duration with minimum retention policies.
3
Evaluate the timing for the Archive tier transition and subsequent deletion.
Logs are transitioned to Archive on day 180180 and deleted after day 365365. The duration in the Archive tier is 185185 days (from day 181181 to 365365). This exceeds the Archive tier minimum retention period of 180180 days, avoiding any early deletion penalties.
Ensuring the data spends at least 180180 days in the Archive tier before deletion prevents early deletion charges.

Anahtar Kavram

Data Lifecycle Management and Retention
Bu soruyu puanla

Konular

Data Lifecycle Management and Retention

Bu konudan daha fazla soru