Exam Bundle

The clone references existing data files instead of duplicating all initial storage pertains to a different control (Use supported Delta SHALLOW CLONE while accounting for source file retention dependencies) and a different need (An engineer wants a cheap metadata-oriented clone that shares source data files initially). It cannot establish that Inspect `DESCRIBE HISTORY` and compare affected versions met the stated goal.

This signal belongs to the adjacent case “Readers must not observe half-written updates during a multi-file table operation,” whose remedy is Use a Delta transaction-backed write or MERGE. The observed result for the present requirement is The history identifies the commit operation and version associated with the change.

That observation is a valid indicator for “A compliance copy requires an independent physical data copy of a Delta table” when using Use DEEP CLONE with supported target configuration. The scenario instead tests “A table's transaction history is important for diagnosing an accidental overwrite”; the relevant result is The history identifies the commit operation and version associated with the change.

This action solves a different issue: “An upstream contract change makes a required field disappear completely.” Its normal signal is The job fails with a missing-required-field signal before publishing incorrect output. Here the requested behavior is “New optional JSON fields should be captured without discarding previously known columns,” so that signal is not sufficient.

This action solves a different issue: “A strict fixed schema must reject unexpected incoming fields until a reviewed change.” Its normal signal is The pipeline fails for an added field instead of silently expanding schema. Here the requested behavior is “New optional JSON fields should be captured without discarding previously known columns,” so that signal is not sufficient.

Use supported schema/type widening handling rather than forcing lossy casts belongs to the separate case “A source numeric type widens within supported compatibility boundaries,” where New wide values are preserved without truncation in the accepted schema would be expected. That differs from the condition in this stem: “New optional JSON fields should be captured without discarding previously known columns.”

This signal belongs to the adjacent case “Unexpected fields should be retained for inspection but not added to the target schema,” whose remedy is Use Auto Loader `rescue` schema evolution mode with a rescued data column. The observed result for the present requirement is A restart after a new column update recognizes the evolved schema.

The job fails with a missing-required-field signal before publishing incorrect output would demonstrate the separate action Add explicit schema/field validation and route the invalid dataset to a controlled failure, which addresses “An upstream contract change makes a required field disappear completely.” It does not verify the requirement “New optional JSON fields should be captured without discarding previously known columns” following Configure appropriate Auto Loader schema evolution and persisted schema location.

That observation is a valid indicator for “A strict fixed schema must reject unexpected incoming fields until a reviewed change” when using Use a fail-on-new-columns schema evolution strategy. The scenario instead tests “New optional JSON fields should be captured without discarding previously known columns”; the relevant result is A restart after a new column update recognizes the evolved schema.

The alternative Use a fail-on-new-columns schema evolution strategy has a distinct purpose—A strict fixed schema must reject unexpected incoming fields until a reviewed change. It would not establish the required outcome (Unexpected fields should be retained for inspection but not added to the target schema); the necessary verification concerns New unexpected attributes appear in the rescued data payload.

This action solves a different issue: “An upstream contract change makes a required field disappear completely.” Its normal signal is The job fails with a missing-required-field signal before publishing incorrect output. Here the requested behavior is “Unexpected fields should be retained for inspection but not added to the target schema,” so that signal is not sufficient.

Use supported schema/type widening handling rather than forcing lossy casts belongs to the separate case “A source numeric type widens within supported compatibility boundaries,” where New wide values are preserved without truncation in the accepted schema would be expected. That differs from the condition in this stem: “Unexpected fields should be retained for inspection but not added to the target schema.”

The job fails with a missing-required-field signal before publishing incorrect output would demonstrate the separate action Add explicit schema/field validation and route the invalid dataset to a controlled failure, which addresses “An upstream contract change makes a required field disappear completely.” It does not verify the requirement “Unexpected fields should be retained for inspection but not added to the target schema” following Use Auto Loader `rescue` schema evolution mode with a rescued data column.

This signal belongs to the adjacent case “New optional JSON fields should be captured without discarding previously known columns,” whose remedy is Configure appropriate Auto Loader schema evolution and persisted schema location. The observed result for the present requirement is New unexpected attributes appear in the rescued data payload.

The pipeline fails for an added field instead of silently expanding schema pertains to a different control (Use a fail-on-new-columns schema evolution strategy) and a different need (A strict fixed schema must reject unexpected incoming fields until a reviewed change). It cannot establish that Use Auto Loader `rescue` schema evolution mode with a rescued data column met the stated goal.

Add explicit schema/field validation and route the invalid dataset to a controlled failure belongs to the separate case “An upstream contract change makes a required field disappear completely,” where The job fails with a missing-required-field signal before publishing incorrect output would be expected. That differs from the condition in this stem: “A strict fixed schema must reject unexpected incoming fields until a reviewed change.”

Use supported schema/type widening handling rather than forcing lossy casts belongs to the separate case “A source numeric type widens within supported compatibility boundaries,” where New wide values are preserved without truncation in the accepted schema would be expected. That differs from the condition in this stem: “A strict fixed schema must reject unexpected incoming fields until a reviewed change.”

The alternative Configure appropriate Auto Loader schema evolution and persisted schema location has a distinct purpose—New optional JSON fields should be captured without discarding previously known columns. It would not establish the required outcome (A strict fixed schema must reject unexpected incoming fields until a reviewed change); the necessary verification concerns The pipeline fails for an added field instead of silently expanding schema.

That observation is a valid indicator for “A source numeric type widens within supported compatibility boundaries” when using Use supported schema/type widening handling rather than forcing lossy casts. The scenario instead tests “A strict fixed schema must reject unexpected incoming fields until a reviewed change”; the relevant result is The pipeline fails for an added field instead of silently expanding schema.

This signal belongs to the adjacent case “An upstream contract change makes a required field disappear completely,” whose remedy is Add explicit schema/field validation and route the invalid dataset to a controlled failure. The observed result for the present requirement is The pipeline fails for an added field instead of silently expanding schema.

That observation is a valid indicator for “Unexpected fields should be retained for inspection but not added to the target schema” when using Use Auto Loader `rescue` schema evolution mode with a rescued data column. The scenario instead tests “A strict fixed schema must reject unexpected incoming fields until a reviewed change”; the relevant result is The pipeline fails for an added field instead of silently expanding schema.

This action solves a different issue: “Unexpected fields should be retained for inspection but not added to the target schema.” Its normal signal is New unexpected attributes appear in the rescued data payload. Here the requested behavior is “A source numeric type widens within supported compatibility boundaries,” so that signal is not sufficient.

Use a fail-on-new-columns schema evolution strategy belongs to the separate case “A strict fixed schema must reject unexpected incoming fields until a reviewed change,” where The pipeline fails for an added field instead of silently expanding schema would be expected. That differs from the condition in this stem: “A source numeric type widens within supported compatibility boundaries.”

Configure appropriate Auto Loader schema evolution and persisted schema location belongs to the separate case “New optional JSON fields should be captured without discarding previously known columns,” where A restart after a new column update recognizes the evolved schema would be expected. That differs from the condition in this stem: “A source numeric type widens within supported compatibility boundaries.”

This signal belongs to the adjacent case “New optional JSON fields should be captured without discarding previously known columns,” whose remedy is Configure appropriate Auto Loader schema evolution and persisted schema location. The observed result for the present requirement is New wide values are preserved without truncation in the accepted schema.

The pipeline fails for an added field instead of silently expanding schema pertains to a different control (Use a fail-on-new-columns schema evolution strategy) and a different need (A strict fixed schema must reject unexpected incoming fields until a reviewed change). It cannot establish that Use supported schema/type widening handling rather than forcing lossy casts met the stated goal.

This signal belongs to the adjacent case “An upstream contract change makes a required field disappear completely,” whose remedy is Add explicit schema/field validation and route the invalid dataset to a controlled failure. The observed result for the present requirement is New wide values are preserved without truncation in the accepted schema.

Use a fail-on-new-columns schema evolution strategy is appropriate when “A strict fixed schema must reject unexpected incoming fields until a reviewed change”; it would be verified by The pipeline fails for an added field instead of silently expanding schema. It does not directly satisfy “An upstream contract change makes a required field disappear completely,” whose relevant acceptance evidence is The job fails with a missing-required-field signal before publishing incorrect output.

The alternative Use supported schema/type widening handling rather than forcing lossy casts has a distinct purpose—A source numeric type widens within supported compatibility boundaries. It would not establish the required outcome (An upstream contract change makes a required field disappear completely); the necessary verification concerns The job fails with a missing-required-field signal before publishing incorrect output.

The alternative Configure appropriate Auto Loader schema evolution and persisted schema location has a distinct purpose—New optional JSON fields should be captured without discarding previously known columns. It would not establish the required outcome (An upstream contract change makes a required field disappear completely); the necessary verification concerns The job fails with a missing-required-field signal before publishing incorrect output.

New unexpected attributes appear in the rescued data payload would demonstrate the separate action Use Auto Loader `rescue` schema evolution mode with a rescued data column, which addresses “Unexpected fields should be retained for inspection but not added to the target schema.” It does not verify the requirement “An upstream contract change makes a required field disappear completely” following Add explicit schema/field validation and route the invalid dataset to a controlled failure.

This signal belongs to the adjacent case “A source numeric type widens within supported compatibility boundaries,” whose remedy is Use supported schema/type widening handling rather than forcing lossy casts. The observed result for the present requirement is The job fails with a missing-required-field signal before publishing incorrect output.

A restart after a new column update recognizes the evolved schema pertains to a different control (Configure appropriate Auto Loader schema evolution and persisted schema location) and a different need (New optional JSON fields should be captured without discarding previously known columns). It cannot establish that Add explicit schema/field validation and route the invalid dataset to a controlled failure met the stated goal.