Data Access · interview question
Which move is the best default when repository boundaries becomes part of this workflow?
Multiple choiceHardchapter-11-curatedpremiumdata-accessrepository-boundaries
Answer and explanation
Correct answer
B. Let repositories own query details while the service layer owns workflow and policy decisions.
Why
Let repositories own query details while the service layer owns workflow and policy decisions. That is the stronger engineering move because this separation-of-responsibility answer usually lands well in interviews because it sounds maintainable. If business rules and SQL are tangled together, both testing and change impact get worse.
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?