Examkin

Soru

Zorluk: ZorData Lifecycle Management and Retention

An organization uses an Azure Data Lake Storage Gen2 (ADLS Gen2) account with hierarchical namespace enabled to store transaction logs. You need to configure a lifecycle management policy to meet the following requirements:
- The logs must support high-throughput, sub-second read and write access for the first 30 days after creation.
- From day 31 through day 180, logs are queried occasionally for auditing and must be available with sub-second retrieval latency.
- From day 181 through day 1,095 (3 years), the logs are kept strictly for regulatory compliance and are rarely accessed. A retrieval latency of up to 15 hours is acceptable.
- After 1,095 days, the logs can be safely deleted.
- Storage costs must be minimized.

Which two actions should you include in the lifecycle management policy?

  1. Transition the blobs to the Cool tier 30 days after creation.Cevap
  2. Transition the blobs to the Archive tier 180 days after creation.Cevap
  3. C
    Transition the blobs to the Archive tier 30 days after creation.
  4. D
    Transition the blobs to the Archive tier 30 days after creation, and delete the blobs 90 days after creation.
  5. E
    Transition the blobs to the Cool tier 180 days after creation, and transition the blobs to the Archive tier 1,095 days after creation.

Cevap

Transition the blobs to the Cool tier 30 days after creation, and transition the blobs to the Archive tier 180 days after creation.
Transitioning the blobs to the Cool tier 30 days after creation and transitioning them to the Archive tier 180 days after creation satisfies all latency and retention requirements at the lowest cost. The Cool tier preserves the required sub-second retrieval latency for auditing between days 31 and 180, while the Archive tier minimizes cost for the remaining compliance period where up to 15 hours of latency is acceptable.

Adım Adım Çözüm

1
Analyze the retrieval latency requirements for each phase.
Days 1 to 30 require the Hot tier (sub-second read/write). Days 31 to 180 require sub-second retrieval latency, meaning the data cannot be moved to the Archive tier yet. Days 181 to 1,095 allow up to 15 hours of latency, permitting the Archive tier.
Ensures the target storage tier for each lifecycle phase complies with access frequency and latency service level agreements.
2
Determine the cost-optimized transition schedule.
Transition to the Cool tier at day 30, which reduces storage costs while maintaining the required low latency. Transition to the Archive tier at day 180, which offers the lowest storage cost for the remainder of the compliance retention period.
Minimizes overall storage costs by moving the data to cooler tiers as soon as the latency requirements relax.
3
Validate the lifecycle policy against early deletion charges.
The blobs are kept in the Cool tier for 150 days (exceeding the 30-day minimum) and in the Archive tier for 915 days (exceeding the 180-day minimum) before deletion at day 1,095. No early deletion penalties are incurred.
Avoids unexpected billing overhead by ensuring the duration spent in each tier meets minimum retention constraints.

Anahtar Kavram

Data lifecycle management policies optimize storage costs by automatically transitioning blobs to cooler storage tiers or deleting them based on age, while aligning with retrieval latency and retention requirements.
Bu soruyu puanla

Konular

Data Lifecycle Management and Retention

Bu konudan daha fazla soru