Data Access · interview question
Which option describes the most likely pitfall around repository boundaries?
Multiple choiceHardchapter-11-curatedpremiumdata-accessrepository-boundaries
Answer and explanation
Correct answer
D. If business rules and SQL are tangled together, both testing and change impact get worse.
Why
If business rules and SQL are tangled together, both testing and change impact get worse. Calling out that risk matters because this separation-of-responsibility answer usually lands well in interviews because it sounds maintainable.
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?