Service Design · interview question
Which option describes the most likely pitfall around repository boundaries?
Multiple choiceHardchapter-13-curatedpremiumservice-designrepository-boundaries
Answer and explanation
Correct answer
B. Leaking database detail into handlers or domain logic makes every change ripple farther than necessary.
Why
Leaking database detail into handlers or domain logic makes every change ripple farther than necessary. Calling out that risk matters because interviewers often hear this as a sign that you have worked in maintainable backend codebases.
Test yourself on Service Design
A free test with instant, explained results. No account needed.
More Service Design questions
- When is dependency injection being used in the wrong way?
- When is service layer being used in the wrong way?
- Which response shows the healthiest evidence-first mindset around dto mapping?
- Which option treats integration client shape as an engineering policy decision instead of a syntax trick?
- What is the clearest sign that code around integration client shape should be refactored?
- Another engineer will maintain this code later. What choice helps the most around service layer?