Examkin

Question

Difficulty: MediumData Lifecycle Management and Retention

An enterprise is designing a data lifecycle management policy for a General-purpose v2 (GPv2) Azure Blob storage account that stores daily transactional logs. The storage strategy must meet the following requirements:
- Logs are frequently accessed and modified during the first 3030 days after creation.
- Between 3131 and 9090 days, logs are accessed occasionally but must remain available for immediate, sub-second retrieval.
- After 9090 days, logs are rarely accessed, and a retrieval latency of up to 1515 hours is acceptable.
- Logs must be retained for a total of 365365 days and then deleted to minimize costs.
- The lifecycle policy must minimize costs without violating any access or latency requirements.

Which two actions should you configure in the lifecycle management policy? (Select TWO.)

  1. Transition blobs to the cool tier 3030 days after creation.Answer
  2. Transition blobs to the archive tier 9090 days after creation.Answer
  3. C
    Transition blobs to the archive tier 3030 days after creation.
  4. D
    Transition blobs to the archive tier 300300 days after creation.

Answer

To meet the requirements, the lifecycle policy must transition the blobs to the cool tier 3030 days after creation, and transition the blobs to the archive tier 9090 days after creation.
The correct lifecycle policy actions are transitioning blobs to the cool tier after 3030 days and transitioning blobs to the archive tier after 9090 days. Transitioning to the cool tier at day 3030 optimizes costs when the data is no longer accessed frequently, but still allows immediate sub-second access for the next 6060 days. Transitioning to the archive tier at day 9090 is optimal because the data is rarely accessed, and the 1515-hour rehydration latency matches the enterprise's allowed retrieval time. Since the blobs stay in the archive tier for 275275 days (from day 9090 to day 365365), they exceed the 180180-day minimum archive storage duration, avoiding any early deletion penalties.

Step-by-Step Solution

1
Analyze access patterns and latency requirements for the first phase (00-9090 days).
Identify that data must be in the Hot tier for the first 3030 days to support frequent access, and must transition to the Cool tier at 3030 days to support occasional access with sub-second retrieval latency until day 9090.
Data in the Archive tier cannot be retrieved in sub-seconds, so transitioning to Archive at day 3030 is ruled out.
2
Analyze access patterns, latency requirements, and minimum retention constraints for the second phase (9090-365365 days).
Identify that data can transition to the Archive tier at day 9090 because it is rarely accessed and the 1515-hour rehydration latency is acceptable. The data will remain in the Archive tier for 275275 days before deletion at day 365365.
Transitioning to Archive at day 9090 satisfies the 180180-day minimum retention threshold for the Archive tier, avoiding early deletion penalties. Transitioning at day 300300 would violate this threshold.

Key Concept

Azure Storage lifecycle management allows automating transitions between Hot, Cool, and Archive tiers based on file age to optimize costs while respecting latency and retrieval constraints, including minimum retention periods.
Estimated Time:2m 0s
Rate this question

Topics

Data Lifecycle Management and Retention

More questions from this topic