Service Design · interview question
Which move is the best default when dto mapping becomes part of this workflow?
Multiple choiceHardchapter-12-curatedpremiumservice-designdto-mapping
Answer and explanation
Correct answer
D. Use boundary objects when the partner payload shape is not the shape the rest of your code wants to reason about.
Why
Use boundary objects when the partner payload shape is not the shape the rest of your code wants to reason about. That is the stronger engineering move because candidates who understand translation layers usually explain integrations more clearly. Skipping DTOs can make the service layer speak in partner-specific language forever.
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?