Data Access · interview question
What is the clearest sign that code around repository boundaries should be refactored?
Multiple choiceHardchapter-11-curatedpremiumdata-accessrepository-boundaries
Answer and explanation
Correct answer
A. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Let repositories own query details while the service layer owns workflow and policy decisions.
Test yourself on Data Access
A free test with instant, explained results. No account needed.
More Data Access questions
- What assumption should be made explicit when working with transactions?
- Which response shows the healthiest evidence-first mindset around repository boundaries?
- What production risk should you worry about most if transactions is handled lazily?
- A senior interviewer asks for one tradeoff behind transactions. What is the strongest follow-up?
- What do interviewers usually hear as a strong signal when you discuss transactions well?
- What assumption should be made explicit when working with basic sqlite queries?