Use indexes when: high selectivity (many distinct values), frequent filters/joins, read-heavy workload. Avoid when: low cardinality (e.g., gender), small tables (full scan is cheap), write-heavy (index maintenance cost), columns rarely in WHERE. Over-indexing causes slow writes and storage bloat. Rule of thumb: index columns in WHERE, JOIN ON, ORDER BY. Monitor with pg_stat_user_indexes (Postgres) or sys.dm_db_index_usage_stats (SQL Server). Drop unused indexes....
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 NAB. 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.