Data Access · interview question
Which explanation would sound strongest in an interview when discussing repository boundaries?
Multiple choiceHardchapter-11-curatedpremiumdata-accessrepository-boundaries
Answer and explanation
Correct answer
C. Let repositories own query details while the service layer owns workflow and policy decisions. This separation-of-responsibility answer usually lands well in interviews because it sounds maintainable.
Why
Interviewers usually care less about keywords than about whether you can explain why the code is shaped the way it is.
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?