Data Cleanup · interview question
Which boundary choice best fits normalization pipelines in a maintainable Python system?
Multiple choiceMediumchapter-4-curatedpremiumdata-cleanupnormalization-pipelines
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 Data Cleanup
A free test with instant, explained results. No account needed.
More Data Cleanup questions
- A teammate submits shaky safe output writes code. Which review comment is the strongest?
- When is safe output writes being used in the wrong way?
- What is the clearest sign that code around safe output writes should be refactored?
- You cannot rewrite everything today. What is the best incremental improvement around normalization pipelines?
- Which move is the best default when normalization pipelines becomes part of this workflow?
- Which option describes the most likely pitfall around normalization pipelines?