When is a rich domain model worth the cost, and when is a transaction script the better design?
Answer it out loud before you open anything. The value of the flags below is in comparing them to what you actually said — including whether you named a cost, or only a principle.
The situation behind the question
A team is building an internal admin tool: twelve CRUD screens, a permissions check, and one screen that computes commission with about forty lines of rules that change quarterly. The tech lead wants entities, value objects, aggregates, repositories and domain services throughout.
What it is really testing
Whether the candidate can decide by *domain complexity* rather than by allegiance. The scenario is deliberately mixed: eleven screens do not need a domain model and one genuinely does, and the discriminating answer is the one that treats them differently.