Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Why storage class selection**: Cost vs. access frequency. At scale, wrong class = millions in waste. **Standard**: Low latency, frequent access. $0.023/GB/month. For hot data—active pipelines, real-time analytics. **Intelligent-Tiering**: Automatically moves objects between...
This easy-level Cloud/Tools question appears frequently in data engineering interviews at companies like Bitwise. While less common, it tests deeper understanding that distinguishes strong candidates.
Start by clearly defining the core concept being asked about. Interviewers want to see that you understand the fundamentals before diving into implementation details. Structure your answer with a definition, then explain the practical application with a concise example.
Why storage class selection: Cost vs. access frequency. At scale, wrong class = millions in waste. Standard: Low latency, frequent access. $0.023/GB/month. For hot data—active pipelines, real-time analytics. Intelligent-Tiering: Automatically moves objects between access tiers (frequent, infrequent, archive) based on access pattern. No retrieval fees. $0.0025/GB for monitoring + tier-specific storage. For unknown or fluctuating patterns—avoids manual lifecycle. Glacier: Archive—retrieval takes minutes (Expedited) to hours (Standard/Bulk). $0.004/GB (Glacier Flexible). Use for compliance, backups, cold data. Scalability: Lifecycle policies automate transitions; at 1 PB, manual class changes are impractical. Cost: Moving 100 TB from Standard to Glacier saves ~$1,900/month. Intelligent-Tiering adds monitoring cost but eliminates retrieval mistakes. Best practice: Lifecycle policies for time-based transition; Intelligent-Tiering for unsure patterns; Standard for pipeline intermediates.
Pro-Move: 'We use Intelligent-Tiering for our raw zone—access patterns vary by dataset; we avoided over-paying for Standard and retrieval fees from premature Glacier.' Red Flag: Putting all data in Glacier without understanding retrieval costs and latency—can block analytics and surprise on cost.
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.