Question

Difficulty: Very hardData Lifecycle Management and Retention

An enterprise is designing a data storage and lifecycle strategy for telemetry logs stored in Azure Data Lake Storage Gen2 (ADLS Gen2). The logs are stored as block blobs and must adhere to the following operational and compliance requirements:

* Operational Monitoring (Days 1–10): The logs are heavily queried with sub-second latency requirements.
* Batch Reconciliation (Days 11–90): The logs are read weekly for database reconciliation. Active, online access with low retrieval cost is required.
* Compliance Retention (Days 91–180): The logs are rarely accessed but must be retained. In the event of a regulatory audit, the logs must be readable within 3 hours. To minimize administrative overhead and avoid relying on High-Priority rehydration, the retrieval must use standard online access.
* Deletion (Day 180): Due to privacy regulations, the logs must be permanently deleted exactly 180 days after creation.

Which of the following JSON lifecycle policy configurations should you recommend to minimize storage and retrieval costs while avoiding early deletion charges?

  1. A
    {
    "actions": {
    "baseBlob": {
    "tierToCool": {
    "daysAfterModificationGreaterThan": 10
    },
    "tierToArchive": {
    "daysAfterModificationGreaterThan": 90
    },
    "delete": {
    "daysAfterModificationGreaterThan": 180
    }
    }
    }
    }
  2. B
    {
    "actions": {
    "baseBlob": {
    "tierToCold": {
    "daysAfterModificationGreaterThan": 10
    },
    "tierToArchive": {
    "daysAfterModificationGreaterThan": 90
    },
    "delete": {
    "daysAfterModificationGreaterThan": 180
    }
    }
    }
    }
  3. {
    "actions": {
    "baseBlob": {
    "tierToCool": {
    "daysAfterModificationGreaterThan": 10
    },
    "tierToCold": {
    "daysAfterModificationGreaterThan": 90
    },
    "delete": {
    "daysAfterModificationGreaterThan": 180
    }
    }
    }
    }
    Answer
  4. D
    {
    "actions": {
    "baseBlob": {
    "tierToArchive": {
    "daysAfterModificationGreaterThan": 10
    },
    "delete": {
    "daysAfterModificationGreaterThan": 180
    }
    }
    }
    }

Answer

The configuration that transitions the blobs to Cool on day 10, to Cold on day 90, and deletes them on day 180.
The configuration that transitions the blobs to Cool on day 10, to Cold on day 90, and deletes them on day 180 is correct because it aligns perfectly with the access requirements and minimum retention periods of each tier. Specifically: (1) The Cool tier transition occurs on day 10, meaning blobs spend 80 days in Cool (which exceeds the 30-day minimum retention period for the Cool tier). (2) The Cold tier transition occurs on day 90, meaning blobs spend 90 days in Cold (which exactly meets the 90-day minimum retention period for the Cold tier before they are deleted on day 180). (3) The Cold tier provides online access with millisecond retrieval times, satisfying the 3-hour retrieval SLA without relying on High-Priority Archive rehydration. (4) Keeping the data in Cool from day 10 to day 90 supports the active batch reconciliation with lower transaction and retrieval costs compared to the Cold tier.

Step-by-Step Solution

1
Analyze the query and retrieval latency requirements for each operational phase.
Operational monitoring (days 1-10) requires Hot tier. Batch reconciliation (days 11-90) requires low transaction retrieval costs with active online access, making Cool tier optimal. The audit phase (days 91-180) requires retrieval within 3 hours. Since Archive tier standard rehydration takes up to 15 hours and High-Priority is to be avoided, the data must remain in an online tier (Hot, Cool, or Cold).
Determines which tiers are technically viable for each phase of the lifecycle based on performance and SLA constraints.
2
Calculate the duration spent in each tier to verify minimum retention period compliance.
Cool tier minimum retention is 30 days; transitioning to Cool on day 10 and then to another tier on day 90 means the data spends 80 days in Cool, which is compliant. Cold tier minimum retention is 90 days; transitioning to Cold on day 90 and deleting on day 180 means the data spends exactly 90 days in Cold, which is compliant. Archive tier minimum retention is 180 days; transitioning to Archive on day 90 and deleting on day 180 means the data spends 90 days in Archive, which would violate the policy and incur early deletion charges.
Avoids early deletion fees, which are calculated based on the duration data stays in a specific billing tier.
3
Compare storage rates for the compliance phase (days 91-180).
Cold tier offers lower storage rates than Cool tier and meets the 3-hour retrieval SLA since it provides millisecond-level online access. Transitioning to Cold on day 90 is the most cost-effective approach.
Optimizes the total cost of ownership (TCO) while satisfying all system constraints.
4
Map the transitions to the correct JSON schema definitions under lifecycle management.
Configure 'tierToCool' for 10 days, 'tierToCold' for 90 days, and 'delete' for 180 days.
Translates the logical lifecycle plan into a valid Azure Resource Manager lifecycle policy action block.

Key Concept

Azure Storage Lifecycle Management tier transitions and minimum retention constraints
Rate this question