Pick one SOLID principle, tell me the problem it was invented to solve, and tell me a case where following it made a codebase worse.
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.
A team has an architecture review checklist whose first item is "does this comply with SOLID?". Reviews have become arguments about whether a class has one responsibility, and the codebase has grown a large number of very small classes that are individually simple and collectively hard to follow.
What it is really testing
Whether the candidate can discuss the principles as *responses to problems* with trade-offs, rather than recite the acronym. Asking for a case where it made things worse is the discriminator: someone who has only read about SOLID cannot produce one, and someone who has applied it for years has several.