Service Design · interview question
Which judgment is strongest when choosing a data shape for repository boundaries?
Multiple choiceHardchapter-13-curatedpremiumservice-designrepository-boundaries
Answer and explanation
Correct answer
C. Pick the structure that matches the business meaning and the operations you need to perform repeatedly.
Why
The right shape makes the rest of the code simpler. The wrong shape forces awkward fixes everywhere else.
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?