Data Access · interview question
Which naming or modeling choice is strongest for repository boundaries?
Multiple choiceHardchapter-11-curatedpremiumdata-accessrepository-boundaries
class OrderRepository:
def by_id(self, order_id: str) -> tuple | None:
return connection.execute("SELECT id FROM orders WHERE id = ?", (order_id,)).fetchone()Answer and explanation
Correct answer
D. Use names and structures that describe the business fact directly instead of temporary implementation noise.
Why
Clear naming and modeling shorten debugging, review, and onboarding time.
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?