Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Normalization minimizes redundancy via 3NF; denormalization intentionally duplicates data for read performance. Normalized: Separate tables, no redundancy, complex JOINs. Denormalized: Flattened tables, redundant data, simpler queries. Use denormalization when: (1) Read-heavy...
This medium-level SQL question appears frequently in data engineering interviews at companies like McKinsey. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (join) will help you answer variations of this question confidently.
Break this problem into components. Identify the core trade-offs involved, then walk the interviewer through your reasoning step by step. Demonstrate awareness of edge cases and production considerations - this is what separates good answers from great ones.
Normalization minimizes redundancy via 3NF; denormalization intentionally duplicates data for read performance. Normalized: Separate tables, no redundancy, complex JOINs. Denormalized: Flattened tables, redundant data, simpler queries. Use denormalization when: (1) Read-heavy analytics—fewer JOINs, faster queries. (2) Star schema in data warehouses—facts + dimensions. (3) Caching/materialized views. (4) No strict consistency requirements. Trade-off: Update anomalies, storage cost. Best practice: Normalize OLTP; denormalize for analytics. Use incremental refresh for denormalized tables. Why it matters: Design choices compound at scale—wrong approach can cause 100× overhead. Scalability trade-offs: Profile before optimizing; validate on sample then full. Cost implications: Suboptimal choices multiply at billion-row scale.
Red Flag: Generic textbook answers. Pro-Move: 'At scale we measured X, implemented Y, achieved Z%—validated and iterated.'
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 SQL interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.