Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Architectural Logic**: Join choice directly impacts query cost, data correctness, and downstream semantics. INNER keeps only matching rows—ideal when referential integrity is enforced and you want to exclude orphans; minimizes shuffle and output size. LEFT preserves all from A...
Red Flag: Using FULL OUTER without articulating the business case—it signals lack of schema understanding. Pro-Move: Say 'I prefer LEFT when the right side is optional; I validate expected NULL counts in CI to catch schema drift.'
This medium-level SQL question appears frequently in data engineering interviews at companies like Impetus, Tech Mahindra. 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.
Architectural Logic: Join choice directly impacts query cost, data correctness, and downstream semantics. INNER keeps only matching rows—ideal when referential integrity is enforced and you want to exclude orphans; minimizes shuffle and output size. LEFT preserves all from A with optional B—use when B is a "dimension" that may not exist (e.g., optional user attributes); RIGHT is mirror of LEFT; FULL OUTER preserves both sides—expensive due to bilateral NULL expansion. Why: INNER is cheapest (smallest result, best predicate pushdown). LEFT/RIGHT force outer-side preservation, increasing rows. FULL OUTER doubles NULL handling and is rare in production. Scalability: INNER scales best; LEFT/RIGHT scale with outer table size; FULL OUTER is O(|A|+|B|). Cost: At petabyte scale, a misguided FULL OUTER can 10x bytes processed vs INNER. Example: A(1,2,3), B(2,3,4)—INNER: 2,3. LEFT: 1(null), 2, 3. RIGHT: 2, 3, 4(null). FULL: 1(null), 2, 3, 4(null).
Red Flag: Using FULL OUTER without articulating the business case—it signals lack of schema understanding. Pro-Move: Say 'I prefer LEFT when the right side is optional; I validate expected NULL counts in CI to catch schema drift.'
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 2 companies. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.