**Architectural Logic**: Pivoting (rows→columns) is a reshape operation with cardinality and performance implications. **SQL**: Aggregate + CASE: `SELECT product_id, MAX(CASE WHEN month='Jan' THEN sales END) AS jan_sales, ... FROM sales GROUP BY product_id`. Or PIVOT (SQL Server). **Spark**: `df.groupBy("product_id").pivot("month").agg(sum("sales"))`. **Why Cardinality Matters**: High cardinality in pivot column (e.g., pivot by user_id) causes column explosion—hundreds of columns, schema bloat....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Comcast. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.