Service Design · interview question
A teammate submits shaky integration client shape code. Which review comment is the strongest?
Multiple choiceHardchapter-12-curatedpremiumservice-designintegration-client-shape
Answer and explanation
Correct answer
A. Make the rule clearer and easier to explain. Wrap the HTTP transport in a client that makes operations explicit and failures easier to reason about.
Why
The best review comment anchors the change to readability, correctness, and future maintenance. If every caller builds URLs and headers by hand, the integration logic fragments quickly.
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?