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...
This easy-level General/Other question appears frequently in data engineering interviews at companies like Altimetrik. While less common, it tests deeper understanding that distinguishes strong candidates.
Start by clearly defining the core concept being asked about. Interviewers want to see that you understand the fundamentals before diving into implementation details. Structure your answer with a definition, then explain the practical application with a concise example.
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. TRADE-OFF: Surrogate keys (auto-increment) when natural keys are composite or may change.
This answer is partially locked
Unlock the full expert answer with code examples and trade-offs
Practice real interviews with AI feedback, track progress, and get interview-ready faster.
Pro starts at $24/mo - cancel anytime
Get the most asked SQL questions with expert answers. Instant download.
No spam. Unsubscribe anytime.
Paste your answer and get instant AI feedback with a FAANG-level improved version.
Analyze My Answer β FreeAccording 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.