Examkin

Soru

Zorluk: ZorData Lifecycle Management and Retention

A company is designing a data storage solution for a medical telemetry application. The application writes telemetry logs directly to an Azure Blob Storage General Purpose v2 (GPv2) account.

The logs must be managed according to the following requirements:
- For the first 3030 days after creation, logs must be immediately readable with sub-second latency to support real-time dashboards.
- Between day 3131 and day 9090, logs are rarely accessed but must remain online and readable within 1010 minutes for ad-hoc audit queries.
- After 9090 days, logs must be retained for compliance for a total of 33 years (1,0951,095 days) from creation. A retrieval latency of up to 1515 hours is acceptable for compliance queries.
- The lifecycle management strategy must minimize total storage costs.

You need to design a lifecycle management policy that meets these requirements while avoiding early deletion charges. Which lifecycle action sequence should you recommend?

  1. Transition blobs to the Cool tier after 3030 days, transition blobs to the Archive tier after 9090 days, and delete blobs after 1,0951,095 days.Cevap
  2. B
    Transition blobs to the Cold tier after 3030 days, transition blobs to the Archive tier after 9090 days, and delete blobs after 1,0951,095 days.
  3. C
    Transition blobs to the Archive tier after 3030 days, and delete blobs after 1,0951,095 days.
  4. D
    Transition blobs to the Cool tier after 3030 days, transition blobs to the Cold tier after 9090 days, and delete blobs after 1,0951,095 days.

Cevap

Transition blobs to the Cool tier after 3030 days, transition blobs to the Archive tier after 9090 days, and delete blobs after 1,0951,095 days.
The correct recommendation is to transition blobs to the Cool tier after 3030 days, then to the Archive tier after 9090 days, and delete them after 1,0951,095 days. The Cool tier satisfies the 1010-minute query latency constraint because it is an online tier. Since the blobs stay in the Cool tier for 6060 days (from day 3030 to day 9090), they exceed the Cool tier's 3030-day minimum retention period, preventing early deletion charges. Transitioning to the Archive tier at day 9090 minimizes cost for the long-term retention period, and because the blobs reside in Archive for 1,0051,005 days, they exceed the Archive tier's 180180-day minimum retention period, meaning no early deletion charges are applied when deleted at day 1,0951,095.

Adım Adım Çözüm

1
Analyze access latency constraints for each time window.
Day 00 to 3030 requires sub-second latency (Hot tier). Day 3131 to 9090 requires queries within 1010 minutes, requiring an online tier (Cool or Cold). Day 9191 to 10951095 allows up to 1515 hours latency, allowing the Archive tier.
Filter out tiers that cannot meet the performance SLAs of each phase.
2
Calculate the duration of the intermediate phase and evaluate early deletion penalties.
The intermediate phase lasts 6060 days (90−30=6090 - 30 = 60). The Cool tier has a 3030-day minimum retention, so 6060 days meets this threshold. The Cold tier has a 9090-day minimum retention, so transitioning after 6060 days would trigger a 3030-day early deletion penalty.
Choose the most cost-effective tier for the intermediate phase while avoiding extra fees.
3
Determine the long-term compliance storage tier and calculate its duration.
Moving to the Archive tier at day 9090 minimizes storage cost. The blobs spend 1,0051,005 days (1095−90=10051095 - 90 = 1005) in Archive. This exceeds the Archive 180180-day minimum retention threshold, ensuring no early deletion fee applies at the deletion point.
Verify that final deletion does not trigger compliance or retention penalties.

Anahtar Kavram

Azure Blob Storage Lifecycle Management Tiers and Minimum Retention Constraints
Bu soruyu puanla

Konular

Data Lifecycle Management and Retention

Bu konudan daha fazla soru