Data Access · interview question
Which option treats repository boundaries as an engineering policy decision instead of a syntax trick?
Multiple choiceHardchapter-11-curatedpremiumdata-accessrepository-boundaries
Answer and explanation
Correct answer
D. Use it to make the operational rule explicit, observable, and maintainable under real workload conditions.
Why
Senior answers focus on ownership, reliability, and maintainability rather than only API recall.
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?