Service Design · interview question
Another engineer will maintain this code later. What choice helps the most around integration client shape?
Multiple choiceHardchapter-12-curatedpremiumservice-designintegration-client-shape
Answer and explanation
Correct answer
C. Make the rule obvious in names, flow, and boundaries so the next reader does not have to reverse-engineer your intent.
Why
Maintainability comes from explicit intent. This kind of wrapper discussion often lands well in interviews because it balances abstraction with practicality.
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?