Without a transaction, partial writes can leave the database telling two incompatible stories at once.
Naming the pitfall early helps you design tests, reviews, and safer boundaries. Connect the idea to a realistic coding decision so recall is easier when solving similar questions.