Explain 1NF, 2NF, and 3NF with a student-marks example.
PICTURE THIS: DATABASE INDEX
Without indexScan every row
With indexJump to keys
CostWrites slower
Simple meaning
1NF: no repeating mark columns like mark1, mark2
WHY — SQL instead of guessing?
Why interviewers care about SQL:
SQL questions separate people
who only read docs from people who shipped.
Keep it short, concrete,
and tied to Backend work.
Stay structured
Name the idea, why it exists, then one short example.
Close cleanly
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 11NF: no repeating mark
columns like mark1, mark2
- 2Why it exists
each score is a row.
- 32NF: if the key
is (student_id, subject_id), student name must not hang off that composite key
- 4Give an example
move name to students.
- 53NF: city should not
be stored because it depends on pincode, not on the student key
- 6keep a pincode table
if that matters.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Say this line
“2NF: if the key is (student_id, subject_id), student name must not hang off that”
Break into beats
2NFifthekeyisstudent
Speaking order
2987408337471632900
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
1NF: no repeating mark columns like mark1, mark2 each score is a row.