Exam Bundle

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.

The alternative Define a streaming table over an append-only supported source has a distinct purpose—A streaming table should preserve append-only raw events rather than reaggregate the entire source. It would not establish the required outcome (A refreshed aggregate has nonincremental SQL operations over several inputs); the necessary verification concerns A pipeline refresh computes the correct report aggregates.

Use a materialized view with the desired declarative query is appropriate when “A daily dashboard needs a recomputed aggregate over upstream data”; it would be verified by The materialized view reflects the correct aggregate after its refresh. It does not directly satisfy “A refreshed aggregate has nonincremental SQL operations over several inputs,” whose relevant acceptance evidence is A pipeline refresh computes the correct report aggregates.

The alternative Use the supported pipelines Python decorator for a materialized view function has a distinct purpose—A Python pipeline definition should register a managed materialized view with declarative SQL. It would not establish the required outcome (A refreshed aggregate has nonincremental SQL operations over several inputs); the necessary verification concerns A pipeline refresh computes the correct report aggregates.

The materialized view reflects the correct aggregate after its refresh would demonstrate the separate action Use a materialized view with the desired declarative query, which addresses “A daily dashboard needs a recomputed aggregate over upstream data.” It does not verify the requirement “A refreshed aggregate has nonincremental SQL operations over several inputs” following Use a materialized view rather than forcing unsupported incremental stream semantics.

That observation is a valid indicator for “A Python pipeline definition should register a managed materialized view with declarative SQL” when using Use the supported pipelines Python decorator for a materialized view function. The scenario instead tests “A refreshed aggregate has nonincremental SQL operations over several inputs”; the relevant result is A pipeline refresh computes the correct report aggregates.

Queries return the current base-table values without a separate refresh job would demonstrate the separate action Create a view with the required projection when no persisted recomputation is needed, which addresses “A report consumer needs a read-only business presentation assembled from managed tables.” It does not verify the requirement “A refreshed aggregate has nonincremental SQL operations over several inputs” following Use a materialized view rather than forcing unsupported incremental stream semantics.

The alternative Use a streaming table reading from a supported incremental source has a distinct purpose—Every new event must be incrementally appended into a continuously maintained target. It would not establish the required outcome (A continuous ingestion target should read new records incrementally using file notifications); the necessary verification concerns The streaming table advances without rereading all existing files.

This action solves a different issue: “A query uses a nonaggregating stream and expects append-only emitted records.” Its normal signal is Only newly arrived input rows appear in the sink across triggers. Here the requested behavior is “A continuous ingestion target should read new records incrementally using file notifications,” so that signal is not sufficient.

The alternative Configure suitable pipeline updates and materialized view refresh has a distinct purpose—A materialized view is required to be refreshed by a pipeline schedule rather than on every source event. It would not establish the required outcome (A continuous ingestion target should read new records incrementally using file notifications); the necessary verification concerns The streaming table advances without rereading all existing files.

The pipeline runs without unsupported streaming operation failures would demonstrate the separate action Use a materialized view or redesign as a supported incremental transformation, which addresses “A stream source is being consumed with an operation that is unsupported incrementally.” It does not verify the requirement “A continuous ingestion target should read new records incrementally using file notifications” following Use a streaming table backed by the incremental ingestion stream.

This signal belongs to the adjacent case “A streaming Delta sink must accept new append rows and preserve committed offsets,” whose remedy is Use an append-compatible Delta streaming write with checkpointing. The observed result for the present requirement is The streaming table advances without rereading all existing files.

A pipeline refresh computes the correct report aggregates would demonstrate the separate action Use a materialized view rather than forcing unsupported incremental stream semantics, which addresses “A refreshed aggregate has nonincremental SQL operations over several inputs.” It does not verify the requirement “A continuous ingestion target should read new records incrementally using file notifications” following Use a streaming table backed by the incremental ingestion stream.

Use supported schema/type widening handling rather than forcing lossy casts is appropriate when “A source numeric type widens within supported compatibility boundaries”; it would be verified by New wide values are preserved without truncation in the accepted schema. It does not directly satisfy “A materialized view is required to be refreshed by a pipeline schedule rather than on every source event,” whose relevant acceptance evidence is The refreshed snapshot reflects data available by the update time.

Declare its streaming table or materialized view with a dependency on the source dataset is appropriate when “An intermediate dataset should automatically refresh when upstream dependencies change”; it would be verified by The pipeline dependency graph includes the upstream table and refreshes in order. It does not directly satisfy “A materialized view is required to be refreshed by a pipeline schedule rather than on every source event,” whose relevant acceptance evidence is The refreshed snapshot reflects data available by the update time.

The alternative Create a view with the required projection when no persisted recomputation is needed has a distinct purpose—A report consumer needs a read-only business presentation assembled from managed tables. It would not establish the required outcome (A materialized view is required to be refreshed by a pipeline schedule rather than on every source event); the necessary verification concerns The refreshed snapshot reflects data available by the update time.

A pipeline update advances the streaming table while retaining its checkpointed progress pertains to a different control (Use a streaming table reading from a supported incremental source) and a different need (Every new event must be incrementally appended into a continuously maintained target). It cannot establish that Configure suitable pipeline updates and materialized view refresh met the stated goal.

The pipeline DAG contains the materialized view and its dataset is refreshed would demonstrate the separate action Use the supported pipelines Python decorator for a materialized view function, which addresses “A Python pipeline definition should register a managed materialized view with declarative SQL.” It does not verify the requirement “A materialized view is required to be refreshed by a pipeline schedule rather than on every source event” following Configure suitable pipeline updates and materialized view refresh.

New rows appear while previous committed rows remain present pertains to a different control (Define a streaming table over an append-only supported source) and a different need (A streaming table should preserve append-only raw events rather than reaggregate the entire source). It cannot establish that Configure suitable pipeline updates and materialized view refresh met the stated goal.

This action solves a different issue: “A target needs append-only ingestion rather than destructive daily replacement.” Its normal signal is A second update adds new source rows without replacing prior accepted rows. Here the requested behavior is “A streaming table should preserve append-only raw events rather than reaggregate the entire source,” so that signal is not sufficient.

Create a view with the required projection when no persisted recomputation is needed is appropriate when “A report consumer needs a read-only business presentation assembled from managed tables”; it would be verified by Queries return the current base-table values without a separate refresh job. It does not directly satisfy “A streaming table should preserve append-only raw events rather than reaggregate the entire source,” whose relevant acceptance evidence is New rows appear while previous committed rows remain present.

Use an append-compatible Delta streaming write with checkpointing belongs to the separate case “A streaming Delta sink must accept new append rows and preserve committed offsets,” where New records accumulate exactly once at supported sink boundaries after restart would be expected. That differs from the condition in this stem: “A streaming table should preserve append-only raw events rather than reaggregate the entire source.”

That observation is a valid indicator for “A target needs append-only ingestion rather than destructive daily replacement” when using Read the incremental source into a streaming table instead of overwriting a static table. The scenario instead tests “A streaming table should preserve append-only raw events rather than reaggregate the entire source”; the relevant result is New rows appear while previous committed rows remain present.

That observation is a valid indicator for “A streaming Delta sink must accept new append rows and preserve committed offsets” when using Use an append-compatible Delta streaming write with checkpointing. The scenario instead tests “A streaming table should preserve append-only raw events rather than reaggregate the entire source”; the relevant result is New rows appear while previous committed rows remain present.

Queries return the current base-table values without a separate refresh job would demonstrate the separate action Create a view with the required projection when no persisted recomputation is needed, which addresses “A report consumer needs a read-only business presentation assembled from managed tables.” It does not verify the requirement “A streaming table should preserve append-only raw events rather than reaggregate the entire source” following Define a streaming table over an append-only supported source.

This action solves a different issue: “A materialized view is required to be refreshed by a pipeline schedule rather than on every source event.” Its normal signal is The refreshed snapshot reflects data available by the update time. Here the requested behavior is “A report consumer needs a read-only business presentation assembled from managed tables,” so that signal is not sufficient.

Use the supported pipelines Python decorator for a materialized view function belongs to the separate case “A Python pipeline definition should register a managed materialized view with declarative SQL,” where The pipeline DAG contains the materialized view and its dataset is refreshed would be expected. That differs from the condition in this stem: “A report consumer needs a read-only business presentation assembled from managed tables.”

This action solves a different issue: “A pipeline reads real managed tables and the team needs to validate end-to-end behavior.” Its normal signal is The test verifies actual table reads, writes and expected persisted results. Here the requested behavior is “A report consumer needs a read-only business presentation assembled from managed tables,” so that signal is not sufficient.

That observation is a valid indicator for “A pipeline reads real managed tables and the team needs to validate end-to-end behavior” when using Run an isolated integration test with controlled input and output tables. The scenario instead tests “A report consumer needs a read-only business presentation assembled from managed tables”; the relevant result is Queries return the current base-table values without a separate refresh job.

The deployed target has its expected resource names without editing shared production defaults pertains to a different control (Use a target-specific override for the job resources in the bundle) and a different need (An environment needs a controlled version of the same notebook job with separate resource names). It cannot establish that Create a view with the required projection when no persisted recomputation is needed met the stated goal.

New rows appear while previous committed rows remain present pertains to a different control (Define a streaming table over an append-only supported source) and a different need (A streaming table should preserve append-only raw events rather than reaggregate the entire source). It cannot establish that Create a view with the required projection when no persisted recomputation is needed met the stated goal.