Data Access · interview question
Which move is the best default when row mapping becomes part of this workflow?
Multiple choiceHardchapter-11-curatedpremiumdata-accessrow-mapping
Answer and explanation
Correct answer
D. Translate raw rows into domain-oriented structures or DTOs so the rest of the code does not depend on tuple positions forever.
Why
Translate raw rows into domain-oriented structures or DTOs so the rest of the code does not depend on tuple positions forever. That is the stronger engineering move because candidates who talk about translation boundaries sound more deliberate and less accidental. Letting raw row tuples leak upward makes the service layer harder to read and easier to break.
Test yourself on Data Access
A free test with instant, explained results. No account needed.
More Data Access questions
- What assumption should be made explicit when working with transactions?
- Which response shows the healthiest evidence-first mindset around repository boundaries?
- What production risk should you worry about most if transactions is handled lazily?
- A senior interviewer asks for one tradeoff behind transactions. What is the strongest follow-up?
- What do interviewers usually hear as a strong signal when you discuss transactions well?
- What assumption should be made explicit when working with basic sqlite queries?