What anomalies occur with concurrent transactions, and how do isolation levels protect against them? Give an example where Read Committed would let you down.
~4 min by voice
How to approach it
The interviewer wants to see whether you understand the real concurrency anomalies and not just the table from the standard: lost update and write skew, the dependence on the DBMS, and whether you can fix races precisely (locks, atomic UPDATEs, constraints) rather than just "setting Serializable".
The interviewer will ask this question and listen. Think out loud and ask for a hint if you need one. When you're done, pause or tap “That's my answer”. In about a minute, your score and the points you covered show up here.