DBMS for placements: interview questions by topic
DBMS questions are the theory behind the SQL you write in the same interview. Keys first — candidate, primary, foreign, and why a table can have many candidates but one primary. Then normalization, which is really a question about functional dependencies: which column determines which, and what goes wrong when a fact is stored twice. Transactions and ACID follow, with the follow-up that separates memorised from understood: what does each isolation level allow, and what does a lock actually protect?
Indexing comes up as 'why is this query slow' and 'when does an index make things worse'. The ER model and relational algebra appear in first rounds and university-style tests; SQL vs NoSQL and the CAP theorem appear when the interviewer has a system-design round in mind. Joins and views are asked here too, and they are answered on the SQL pages so nothing is said twice.
Each page below covers one topic: the questions that are asked, the answers with worked examples, and one question exactly as the diagnostic asks it. The diagnostic draws from every DBMS topic in the bank and names the ones to read first.
DBMS topics, one page each
10 of the 14 DBMS topics in the bank have a page so far; the diagnostic draws from all 14.
- Normalization interview questions
What each normal form requires, the anomalies it removes, partial and transitive dependencies, 3NF vs BCNF worked out, when to denormalize — answered.
- Transactions and ACID interview questions
ACID with examples, isolation levels and their anomalies, write-ahead logging, deadlocks, optimistic vs pessimistic locking — DBMS questions answered.
- Database indexing interview questions
What an index costs, clustered vs non-clustered, B-tree vs hash, the leftmost-prefix rule, covering indexes, why an index is ignored, selectivity.
- Keys in DBMS interview questions
Super, candidate, primary, alternate and foreign keys, primary key vs UNIQUE, composite and surrogate keys, candidate keys from FDs — answered.
- ER model and ER diagram interview questions
Entities, attributes and relationships, weak entities, cardinality and participation, mapping 1:N and M:N to tables, ISA hierarchies, ternary.
- SQL vs NoSQL interview questions
Relational vs NoSQL: schema, the four NoSQL families, scaling up vs out, transactions, embed vs reference, when NoSQL is the wrong choice.
- CAP theorem interview questions
What C, A and P mean, why partition tolerance is not optional, CP vs AP with examples, eventual consistency, what CAP does not say, PACELC.
- Relational algebra interview questions
Selection vs projection, the six basic operators, natural and theta joins, set difference, division for "all" queries, the SQL equivalents.
- Functional dependencies interview questions
What X → Y means, trivial FDs, Armstrong's axioms, attribute closure, checking an FD against data, canonical cover, lossless-join decomposition, 4NF.
- Concurrency control interview questions
Lost updates and dirty reads, serializability, shared vs exclusive locks, two-phase locking, deadlock prevention and detection, timestamp ordering, MVCC.
One question, exactly as the diagnostic asks it
From the DBMS bank — 67 questions across 14 topics. The answer is marked because this one is public; in a sitting you choose first, then see why each option is right or wrong.
A relation is said to be in First Normal Form (1NF) when which condition holds?
- 1Every non-key attribute is fully functionally dependent on the primary key
- 2Every determinant in the relation is a candidate key
- 3Every attribute contains only atomic (indivisible) values, with no repeating groups or multi-valued attributescorrect
- 4There are no transitive dependencies between non-key attributes
1NF requires atomic values in every cell, eliminating repeating groups or lists stored in a single field. The full-dependency option describes 2NF, the no-transitive-dependency option describes 3NF, and the determinant option describes BCNF, all of which are stronger, later normal forms.
Measure it
Reading the answers tells you what’s true. A diagnostic tells you what you get wrong.
10 DBMS questions across its topics, easy to hard, about fifteen minutes. You get a readiness figure with the arithmetic shown, the topics you missed named, and a practice set sized for today. Free: 1 diagnostic a month and 15 problems a day. No card.