6.4Don't use Choice when Upsert already solves the problem

Bad:

Query Account
   ↓
Choice

exists?
  ↓ yes       ↓ no
Update       Create

when all you needed was:

Upsert

Choice is useful when business logic differs.

It's not automatically needed just because two outcomes exist.

Strong interview answer:

“I wouldn't introduce a Choice just to reproduce behavior already provided safely by an upsert. I'd use Choice when the downstream behavior genuinely depends on data or business state.”