PRIMARY KEY: Unique identifier; one per table; NOT NULL; used for FKs. SECONDARY KEY: Non-primary unique (e.g., email, passport); can have multiple; supports lookups. WHY: PK enables referential integrity; secondary keys support alternate access paths. SCALABILITY: Index on PK is default; secondary keys need explicit indexes. COST: More indexes = slower writes, more storage; choose based on query patterns....
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 Altimetrik. 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 General/Other 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.