Question 860
A left join loses unmatched orders after a WHERE filter references nullable columns from the right table. Which continuing control should the team adopt after recovery?
Explanation
Correct Answer
Test null and unmatched records when changing outer joins. This is the most directly relevant preventive control because a post-join WHERE predicate rejects null-extended outer-join rows. A concrete acceptance check is: Unmatched orders are preserved and matched orders satisfy the intended filter. To reduce recurrence: Test null and unmatched records when changing outer joins.
Incorrect Answers
Probabilistic model outputs are not a guarantee of policy-correct classification. Here the important technical distinction is that a post-join WHERE predicate rejects null-extended outer-join rows.
Window functions do not infer entity boundaries unless a partition is specified. The reported failure instead depends on this fact: a post-join WHERE predicate rejects null-extended outer-join rows.
Semi-structured values need type normalization before numerical aggregation. That consideration does not remove the current constraint: a post-join WHERE predicate rejects null-extended outer-join rows.