Memory · interview question
Which boundary choice best fits tracing allocations in a maintainable Python system?
Multiple choiceMediumchapter-16-curatedpremiummemorytracing-allocations
Answer and explanation
Correct answer
B. 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 Memory
A free test with instant, explained results. No account needed.
More Memory questions
- What is the healthiest performance judgment around tracing allocations?
- When is tracing allocations being used in the wrong way?
- What does a strong engineer do when reasoning through tracing allocations code?
- If tracing allocations fails in production, what handling philosophy is strongest?
- What assumption should be made explicit when working with tracing allocations?
- Another engineer will maintain this code later. What choice helps the most around tracing allocations?