Exam Bundle

This signal belongs to the adjacent case “A table schema must match exact expected field types and nullability,” whose remedy is Use `assertSchemaEqual` against the expected StructType. The observed result for the present requirement is The test verifies actual table reads, writes and expected persisted results.

Tests catch the invalid output for the negative fixtures pertains to a different control (Write focused parameterized unit cases covering null and duplicate inputs) and a different need (A business rule contains edge cases for nulls and duplicates). It cannot establish that Run an isolated integration test with controlled input and output tables met the stated goal.

The unit test detects differences in output records pertains to a different control (Use PySpark `assertDataFrameEqual` with explicit expected rows) and a different need (An expected DataFrame result should be compared to the actual full record content). It cannot establish that Run an isolated integration test with controlled input and output tables met the stated goal.

Use a carefully scoped `WHEN NOT MATCHED BY SOURCE THEN DELETE` clause belongs to the separate case “A full snapshot source is authoritative and the target should delete keys absent from it,” where Target rows absent from the authoritative snapshot are removed under the scope would be expected. That differs from the condition in this stem: “A source update must change only approved columns while preserving steward-maintained target annotations.”

Use `WHEN MATCHED AND <delete predicate> THEN DELETE` in MERGE belongs to the separate case “A deletion feed should remove matching target rows explicitly,” where Source-marked deletes remove only the intended target keys would be expected. That differs from the condition in this stem: “A source update must change only approved columns while preserving steward-maintained target annotations.”

The alternative Deduplicate to one deterministic source row per target key before MERGE has a distinct purpose—A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous. It would not establish the required outcome (A source update must change only approved columns while preserving steward-maintained target annotations); the necessary verification concerns The steward annotation stays unchanged while authorized source attributes update.

That observation is a valid indicator for “Only rows with a newer event version should replace an existing target record” when using Add an ordering/version predicate to the matched update condition. The scenario instead tests “A source update must change only approved columns while preserving steward-maintained target annotations”; the relevant result is The steward annotation stays unchanged while authorized source attributes update.

Target rows absent from the authoritative snapshot are removed under the scope pertains to a different control (Use a carefully scoped `WHEN NOT MATCHED BY SOURCE THEN DELETE` clause) and a different need (A full snapshot source is authoritative and the target should delete keys absent from it). It cannot establish that Use an explicit column assignment list in the MERGE matched update instead of updating all columns met the stated goal.

This signal belongs to the adjacent case “A deletion feed should remove matching target rows explicitly,” whose remedy is Use `WHEN MATCHED AND <delete predicate> THEN DELETE` in MERGE. The observed result for the present requirement is The steward annotation stays unchanged while authorized source attributes update.

This action solves a different issue: “A full snapshot source is authoritative and the target should delete keys absent from it.” Its normal signal is Target rows absent from the authoritative snapshot are removed under the scope. Here the requested behavior is “Only rows with a newer event version should replace an existing target record,” so that signal is not sufficient.

Use an explicit column assignment list in the MERGE matched update instead of updating all columns belongs to the separate case “A source update must change only approved columns while preserving steward-maintained target annotations,” where The steward annotation stays unchanged while authorized source attributes update would be expected. That differs from the condition in this stem: “Only rows with a newer event version should replace an existing target record.”

This action solves a different issue: “A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous.” Its normal signal is MERGE commits without multiple source rows matching the same target row. Here the requested behavior is “Only rows with a newer event version should replace an existing target record,” so that signal is not sufficient.

This signal belongs to the adjacent case “A full snapshot source is authoritative and the target should delete keys absent from it,” whose remedy is Use a carefully scoped `WHEN NOT MATCHED BY SOURCE THEN DELETE` clause. The observed result for the present requirement is An older event does not replace a newer target value.

This signal belongs to the adjacent case “A source update must change only approved columns while preserving steward-maintained target annotations,” whose remedy is Use an explicit column assignment list in the MERGE matched update instead of updating all columns. The observed result for the present requirement is An older event does not replace a newer target value.

MERGE commits without multiple source rows matching the same target row pertains to a different control (Deduplicate to one deterministic source row per target key before MERGE) and a different need (A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous). It cannot establish that Add an ordering/version predicate to the matched update condition met the stated goal.

This action solves a different issue: “Only rows with a newer event version should replace an existing target record.” Its normal signal is An older event does not replace a newer target value. Here the requested behavior is “A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous,” so that signal is not sufficient.

This action solves a different issue: “A full snapshot source is authoritative and the target should delete keys absent from it.” Its normal signal is Target rows absent from the authoritative snapshot are removed under the scope. Here the requested behavior is “A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous,” so that signal is not sufficient.

Use an explicit column assignment list in the MERGE matched update instead of updating all columns belongs to the separate case “A source update must change only approved columns while preserving steward-maintained target annotations,” where The steward annotation stays unchanged while authorized source attributes update would be expected. That differs from the condition in this stem: “A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous.”

That observation is a valid indicator for “Only rows with a newer event version should replace an existing target record” when using Add an ordering/version predicate to the matched update condition. The scenario instead tests “A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous”; the relevant result is MERGE commits without multiple source rows matching the same target row.

The steward annotation stays unchanged while authorized source attributes update pertains to a different control (Use an explicit column assignment list in the MERGE matched update instead of updating all columns) and a different need (A source update must change only approved columns while preserving steward-maintained target annotations). It cannot establish that Deduplicate to one deterministic source row per target key before MERGE met the stated goal.

Target rows absent from the authoritative snapshot are removed under the scope would demonstrate the separate action Use a carefully scoped `WHEN NOT MATCHED BY SOURCE THEN DELETE` clause, which addresses “A full snapshot source is authoritative and the target should delete keys absent from it.” It does not verify the requirement “A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous” following Deduplicate to one deterministic source row per target key before MERGE.

This action solves a different issue: “A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous.” Its normal signal is MERGE commits without multiple source rows matching the same target row. Here the requested behavior is “A deletion feed should remove matching target rows explicitly,” so that signal is not sufficient.

The alternative Add an ordering/version predicate to the matched update condition has a distinct purpose—Only rows with a newer event version should replace an existing target record. It would not establish the required outcome (A deletion feed should remove matching target rows explicitly); the necessary verification concerns Source-marked deletes remove only the intended target keys.

This action solves a different issue: “A source update must change only approved columns while preserving steward-maintained target annotations.” Its normal signal is The steward annotation stays unchanged while authorized source attributes update. Here the requested behavior is “A deletion feed should remove matching target rows explicitly,” so that signal is not sufficient.

That observation is a valid indicator for “A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous” when using Deduplicate to one deterministic source row per target key before MERGE. The scenario instead tests “A deletion feed should remove matching target rows explicitly”; the relevant result is Source-marked deletes remove only the intended target keys.

This signal belongs to the adjacent case “A full snapshot source is authoritative and the target should delete keys absent from it,” whose remedy is Use a carefully scoped `WHEN NOT MATCHED BY SOURCE THEN DELETE` clause. The observed result for the present requirement is Source-marked deletes remove only the intended target keys.

That observation is a valid indicator for “A source update must change only approved columns while preserving steward-maintained target annotations” when using Use an explicit column assignment list in the MERGE matched update instead of updating all columns. The scenario instead tests “A deletion feed should remove matching target rows explicitly”; the relevant result is Source-marked deletes remove only the intended target keys.

The alternative Add an ordering/version predicate to the matched update condition has a distinct purpose—Only rows with a newer event version should replace an existing target record. It would not establish the required outcome (A full snapshot source is authoritative and the target should delete keys absent from it); the necessary verification concerns Target rows absent from the authoritative snapshot are removed under the scope.

This action solves a different issue: “A source batch contains duplicate rows matching one target key and MERGE becomes ambiguous.” Its normal signal is MERGE commits without multiple source rows matching the same target row. Here the requested behavior is “A full snapshot source is authoritative and the target should delete keys absent from it,” so that signal is not sufficient.

This action solves a different issue: “A source update must change only approved columns while preserving steward-maintained target annotations.” Its normal signal is The steward annotation stays unchanged while authorized source attributes update. Here the requested behavior is “A full snapshot source is authoritative and the target should delete keys absent from it,” so that signal is not sufficient.

An older event does not replace a newer target value pertains to a different control (Add an ordering/version predicate to the matched update condition) and a different need (Only rows with a newer event version should replace an existing target record). It cannot establish that Use a carefully scoped `WHEN NOT MATCHED BY SOURCE THEN DELETE` clause met the stated goal.

The steward annotation stays unchanged while authorized source attributes update would demonstrate the separate action Use an explicit column assignment list in the MERGE matched update instead of updating all columns, which addresses “A source update must change only approved columns while preserving steward-maintained target annotations.” It does not verify the requirement “A full snapshot source is authoritative and the target should delete keys absent from it” following Use a carefully scoped `WHEN NOT MATCHED BY SOURCE THEN DELETE` clause.

Source-marked deletes remove only the intended target keys pertains to a different control (Use `WHEN MATCHED AND <delete predicate> THEN DELETE` in MERGE) and a different need (A deletion feed should remove matching target rows explicitly). It cannot establish that Use a carefully scoped `WHEN NOT MATCHED BY SOURCE THEN DELETE` clause met the stated goal.