What is the change tracker?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
It watches loaded entities for property changes and builds INSERT/UPDATE/DELETE on SaveChanges.
WHY — EF Core instead of guessing?
Why interviewers care about EF Core:
people who only read docs from people who shipped.
and tied to .NET work.
Name the idea, why it exists, then one short example.
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:
- 1It watches loaded entities
for property changes and builds INSERT/UPDATE/DELETE on SaveChanges.
- 2Why it exists
Detached graphs need explicit state.
- 3Too many tracked entities
hurt memory.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
It watches loaded entities for property changes and builds INSERT/UPDATE/DELETE on SaveChanges. Detached graphs need explicit state.