Explain Azure Blob Storage access tiers.
Assesses fundamental understanding of Microsoft Azure conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Blob Storage offers tiers that trade storage cost against access cost and latency.
- Hot: frequent access, highest storage cost, lowest access cost.
- Cool: infrequent access, minimum 30-day storage, lower storage cost, higher access cost.
- Cold: rarely accessed, minimum 90 days, lower still.
- Archive: offline, minimum 180 days, lowest storage cost, hours to rehydrate before reading.
Set a tier at upload or move blobs later with lifecycle management policies.
{
"rules": [{
"name": "archive-old",
"type": "Lifecycle",
"definition": {
"filters": {"blobTypes": ["blockBlob"], "prefixMatch": ["logs/"]},
"actions": {"baseBlob": {
"tierToCool": {"daysAfterModificationGreaterThan": 30},
"tierToArchive": {"daysAfterModificationGreaterThan": 180}
}}
}
}]
}
Early deletion before the minimum age incurs charges, so model the access pattern before choosing a tier.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.