Core Collections · interview question
Which boundary choice best fits sorting and grouping in a maintainable Python system?
Multiple choiceMediumchapter-3-curatedpremiumcore-collectionssorting-and-grouping
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 Core Collections
A free test with instant, explained results. No account needed.
More Core Collections questions
- A senior interviewer asks for one tradeoff behind sets. What is the strongest follow-up?
- Which explanation would best help the team align on tuples?
- Which option is the safer default when shipping code around lists?
- Which response shows the healthiest evidence-first mindset around sorting and grouping?
- What production risk should you worry about most if sorting and grouping is handled lazily?
- What production risk should you worry about most if sets is handled lazily?