74. Why should a requirement distinguish missing information from a value of zero?
EasyData & validation
Technical
Show model answer
Zero is a known value under the field's definition; missing can mean unknown, not collected, not applicable or failed retrieval. Converting all blanks to zero can distort totals, rates and decisions while hiding an information-quality problem that should remain visible to users.
I'd agree valid states and calculation and display handling with owners. Defaults need justification, not silent removal of uncertainty merely to make a chart or formula work.
What interviewers listen for
- Distinguish value from information state
- Define calculation and display handling
- Avoid silent uncertainty removal