What is the difference between 1NF and 2NF? ● 1NF (First Normal Form): Ensures that the table has atomic columns (no multi-valued or repeating groups) and each row has a unique identifier (Primary Key). ● 2NF (Second Normal Form): The table must be in 1NF and all non-key columns must depend on the entire primary key (i.e., there should be no partial dependencies). Example: ● A table with a composite primary key (e.g., StudentID, CourseID) where non-key
Answer: ttributes like CourseName only depend on CourseID would violate 2NF because CourseName is partially dependent on the composite key. You would separate this into two tables (one for Courses and one for Students).
What interviewers expect
- A clear definition tied to SQL in SQL & Databases projects
- Trade-offs (performance, maintainability, security, cost)
- When you would and would not use it in production
Real-world example
In a production SQL & Databases application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.
How to explain in the interview
- Define the concept in one or two sentences.
- Context — where it fits in SQL & Databases architecture.
- Example — a specific project, bug, or performance win.
- Trade-off — what you gain vs what you sacrifice.
Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.