SQL · interview question
Which boundary choice best fits schema thinking in a maintainable Python system?
Multiple choiceEasychapter-11-curatedpremiumsqlschema-thinking
Answer and explanation
Correct answer
D. Keep the concern close to the data or API boundary that owns it instead of scattering it across unrelated helpers.
Why
Responsibility should follow ownership. When the concern lives near the right boundary, the system is easier to test and explain.
Test yourself on SQL
A free test with instant, explained results. No account needed.
More SQL questions
- If you wrote a test around schema thinking, what should the test prove first?
- What do interviewers usually hear as a strong signal when you discuss schema thinking well?
- Which naming or modeling choice is strongest for schema thinking?
- What is the healthiest performance judgment around indexes and access patterns?
- Which option treats joins as an engineering policy decision instead of a syntax trick?
- A senior interviewer asks for one tradeoff behind joins. What is the strongest follow-up?