Examkin

Soru

Zorluk: OrtaData Lifecycle Management and Retention

A software developer is configuring lifecycle management rules for a General-purpose v2 (GPv2) Azure Blob Storage account that collects IoT telemetry data from manufacturing plants. The retention and access requirements are as follows:
- The telemetry data must support sub-second query response times for the first 30 days after upload.
- Between 31 and 180 days after upload, the data is rarely queried but must still be retrievable with sub-second latency.
- After 180 days, the data must be preserved for 7 years (2,555 days) to comply with industrial regulations. During this compliance period, a retrieval delay of up to 15 hours is acceptable.
- Storage costs must be minimized.

Which lifecycle management policy configuration should you recommend?

  1. Transition the blobs to the Cool tier 30 days after creation, transition to the Archive tier 180 days after creation, and delete the blobs 2,555 days after creation.Cevap
  2. B
    Transition the blobs to the Archive tier 30 days after creation, transition to the Cool tier 180 days after creation, and delete the blobs 2,555 days after creation.
  3. C
    Transition the blobs to the Archive tier 30 days after creation, and delete the blobs 2,555 days after creation.
  4. D
    Transition the blobs to the Archive tier 1 day after creation, transition to the Cool tier 30 days after creation, and delete the blobs 2,555 days after creation.

Cevap

Transition the blobs to the Cool tier 30 days after creation, transition to the Archive tier 180 days after creation, and delete the blobs 2,555 days after creation.
The correct configuration transitions the blobs to the Cool tier after 30 days to reduce storage costs while maintaining sub-second retrieval latency, transitions them to the Archive tier after 180 days when a retrieval delay of up to 15 hours is acceptable, and finally deletes them after 2,555 days to comply with the 7-year retention policy. This minimizes storage costs without violating any retrieval latency requirements.

Adım Adım Çözüm

1
Determine the storage tier required for the first 30 days.
Keep in the Hot tier (default) to support sub-second query analysis.
The initial 30 days require sub-second access for active analysis, which is provided by the Hot tier.
2
Select the storage tier for days 31 to 180.
Transition to the Cool tier 30 days after creation.
The Cool tier offers lower storage costs than the Hot tier while still providing the required sub-second retrieval latency for queries during this period of lower access frequency.
3
Select the storage tier and retention actions for data older than 180 days.
Transition to the Archive tier 180 days after creation, and delete after 2,555 days.
Since a retrieval delay of up to 15 hours is acceptable after 180 days, the data can be moved to the highly cost-effective Archive tier (which has a rehydration time of hours). It must be kept for the remainder of the 7 years (2,555 days) and then deleted to minimize ongoing costs.

Anahtar Kavram

Selecting appropriate storage tiers in Azure lifecycle management policies based on retrieval latency requirements and minimizing overall costs.
Bu soruyu puanla

Konular

Data Lifecycle Management and Retention

Bu konudan daha fazla soru