Question 530
The lakehouse operations report for Oak River Energy describes this issue: A Delta target receives strings in an integer field through implicit coercion and downstream arithmetic becomes unreliable. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
A nonnumeric value triggers an explicit error or quarantine while valid integers persist correctly. The observation provides evidence that the proposed fix (Enforce declared column types and validate incoming casts before committing the write.) addressed the reported issue (A Delta target receives strings in an integer field through implicit coercion and downstream arithmetic becomes unreliable.) for Oak River Energy and its field operations and service infrastructure. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
A missing-key test row follows the configured reject or quarantine behavior and accepted rows have valid IDs. This is suitable evidence for another condition (An essential source identifier is nullable in the incoming schema and downstream joins lose records without warning.) after a different response (Define an explicit non-null validation rule or expectation for the identifier.). For Oak River Energy, it does not prove the required result: A nonnumeric value triggers an explicit error or quarantine while valid integers persist correctly.
A controlled duplicate-key input is detected and reconciled according to the expected data contract. This is suitable evidence for another condition (A customer identifier is supposed to be unique but repeated keys enter a reporting table unchecked.) after a different response (Validate key cardinality or deduplication rules before accepting the transformed dataset.). For Oak River Energy, it does not prove the required result: A nonnumeric value triggers an explicit error or quarantine while valid integers persist correctly.
The renamed-column test triggers the expected schema-contract alert rather than producing incomplete accepted rows. This is suitable evidence for another condition (A source renames a required column silently and the target pipeline drops it without identifying the breaking schema drift.) after a different response (Compare incoming and expected schemas and fail or quarantine incompatible changes explicitly.). For Oak River Energy, it does not prove the required result: A nonnumeric value triggers an explicit error or quarantine while valid integers persist correctly.