Service Design · interview question
What is the clearest sign that code around dto mapping should be refactored?
Multiple choiceHardchapter-12-curatedpremiumservice-designdto-mapping
Answer and explanation
Correct answer
B. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Use boundary objects when the partner payload shape is not the shape the rest of your code wants to reason about.
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?