Service Design · interview question
Which move is the best default when dependency injection becomes part of this workflow?
Multiple choiceMediumchapter-13-curatedpremiumservice-designdependency-injection
Answer and explanation
Correct answer
A. Inject repositories and services at boundary seams so tests and reasoning stay local and explicit.
Why
Inject repositories and services at boundary seams so tests and reasoning stay local and explicit. That is the stronger engineering move because candidates who speak clearly about seams and ownership sound more maintainable. Global hidden dependencies make route behavior harder to predict and harder to override in tests.
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?