Examkin

Soru

Zorluk: OrtaData Lifecycle Management and Retention

You are designing a data retention strategy for database backup files stored in a General-purpose v2 (GPv2) Azure Blob storage account.

The backups must be managed according to the following requirements:
- For the first 14 days after creation, backups are frequently accessed for testing and must remain in the Hot tier.
- From day 15 to day 90, backups are rarely accessed but must be available with sub-second retrieval latency if a restore is needed.
- After 90 days, backups are only kept for compliance audits and can tolerate a retrieval time of up to 15 hours.
- All backups must be deleted exactly 365 days after creation.

Which lifecycle management policy ruleset minimizes storage costs without incurring early deletion charges or violating the latency requirements?

  1. Transition blobs to the Cool tier 14 days after creation, transition to the Archive tier 90 days after creation, and delete blobs 365 days after creation.Cevap
  2. B
    Transition blobs to the Archive tier 14 days after creation, and delete blobs 365 days after creation.
  3. C
    Transition blobs to the Cool tier 14 days after creation, transition to the Archive tier 30 days after creation, and delete blobs 365 days after creation.
  4. D
    Transition blobs to the Cool tier 14 days after creation, and keep them in the Cool tier until deleting them 365 days after creation.

Cevap

Transition blobs to the Cool tier 14 days after creation, transition to the Archive tier 90 days after creation, and delete blobs 365 days after creation.
The correct option transitions blobs to the Cool tier 14 days after creation, meeting the sub-second retrieval requirement for days 15 to 90. It then transitions them to the Archive tier 90 days after creation, minimizing storage costs for the remaining period since 15-hour latency is acceptable. Finally, it deletes them 365 days after creation. This ruleset avoids early deletion fees because the blobs spend 76 days in the Cool tier (exceeding the 30-day minimum) and 275 days in the Archive tier (exceeding the 180-day minimum).

Adım Adım Çözüm

1
Map the access requirements and latency tolerances to storage tiers for each period.
Days 1-14 require Hot tier; days 15-90 require sub-second latency (Cool tier); days 91-365 can tolerate 15 hours latency (Archive tier); day 366+ requires deletion.
This establishes the transition timeline based on access frequency and retrieval latency.
2
Verify if the proposed transitions satisfy the minimum retention periods of the respective tiers.
Cool tier duration: 90 - 14 = 76 days (minimum is 30). Archive tier duration: 365 - 90 = 275 days (minimum is 180). Both conditions are met.
Ensuring the minimum retention periods are met avoids incurring early deletion charges.
3
Identify the ruleset that matches the tier transitions and durations.
The correct lifecycle policy transitions blobs to Cool at day 14, Archive at day 90, and deletes at day 365.
This configuration satisfies all constraints at the lowest possible cost.

Anahtar Kavram

Azure Blob Storage Lifecycle Management Tiers and Retention Constraints
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Data Lifecycle Management and Retention

Bu konudan daha fazla soru