What is cohesion, and how do you tell a cohesive module from a folder full of related files?
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 codebase is organised as controllers/, services/, repositories/ and models/. Adding a field to a customer profile touches one file in each, plus a validator and a serializer. The team describes the structure as "well separated".
What it is really testing
Whether the candidate can tell structural tidiness from actual cohesion. Grouping files by technical kind produces folders that look organised and modules that are not cohesive at all: nothing in services/ changes for the same reason as anything else in services/.