Data Cleanup · interview question
What assumption should be made explicit when working with normalization pipelines?
Multiple choiceMediumchapter-4-curatedpremiumdata-cleanupnormalization-pipelines
Answer and explanation
Correct answer
B. The expected data shape, boundary rule, or invariant that the rest of the code depends on staying true.
Why
Once assumptions are explicit, bugs are easier to detect and test cases are easier to design.
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?