Exam Bundle

Only the highest-ordered event row per customer is selected would demonstrate the separate action Use `ROW_NUMBER()` with `PARTITION BY customer_id` and deterministic order, which addresses “Per-customer latest event is needed while retaining the full winning row.” It does not verify the requirement “A raw events dataset must remove exact duplicate records without altering other fields” following Apply a full-record DISTINCT projection to the intended columns.

The output includes customers with null transaction values would demonstrate the separate action Use a LEFT JOIN from customers to transaction aggregates, which addresses “Customers with no transactions must remain in a customer enrichment result.” It does not verify the requirement “A raw events dataset must remove exact duplicate records without altering other fields” following Apply a full-record DISTINCT projection to the intended columns.

This signal belongs to the adjacent case “Records need to be ranked within each region without collapsing individual rows,” whose remedy is Use a ranking window with `PARTITION BY region`. The observed result for the present requirement is Identical duplicate rows collapse to one while distinct rows stay.

The alternative Refactor the logic into a reusable function or private intermediate dataset as supported has a distinct purpose—A pipeline needs a reused intermediate subquery with no persisted public table. It would not establish the required outcome (A Python pipeline definition should register a managed materialized view with declarative SQL); the necessary verification concerns The pipeline DAG contains the materialized view and its dataset is refreshed.

The alternative Use the Auto Loader `cloudFiles` streaming source in a pipeline dataset has a distinct purpose—A pipeline must ingest a stream from supported cloud files with Auto Loader. It would not establish the required outcome (A Python pipeline definition should register a managed materialized view with declarative SQL); the necessary verification concerns The pipeline DAG contains the materialized view and its dataset is refreshed.

Define the required target and AUTO CDC flow with `keys` and `sequence_by` belongs to the separate case “An AUTO CDC flow should be configured against a target with stable natural keys,” where A newer change event updates only the matching key according to sequence would be expected. That differs from the condition in this stem: “A Python pipeline definition should register a managed materialized view with declarative SQL.”

That observation is a valid indicator for “A pipeline must ingest a stream from supported cloud files with Auto Loader” when using Use the Auto Loader `cloudFiles` streaming source in a pipeline dataset. The scenario instead tests “A Python pipeline definition should register a managed materialized view with declarative SQL”; the relevant result is The pipeline DAG contains the materialized view and its dataset is refreshed.

The pipeline produces the correct downstream outputs without an unintended published table would demonstrate the separate action Refactor the logic into a reusable function or private intermediate dataset as supported, which addresses “A pipeline needs a reused intermediate subquery with no persisted public table.” It does not verify the requirement “A Python pipeline definition should register a managed materialized view with declarative SQL” following Use the supported pipelines Python decorator for a materialized view function.

This signal belongs to the adjacent case “An AUTO CDC flow should be configured against a target with stable natural keys,” whose remedy is Define the required target and AUTO CDC flow with `keys` and `sequence_by`. The observed result for the present requirement is The pipeline DAG contains the materialized view and its dataset is refreshed.

This action solves a different issue: “An AUTO CDC flow should be configured against a target with stable natural keys.” Its normal signal is A newer change event updates only the matching key according to sequence. Here the requested behavior is “A source needs an append-only streaming target defined in Python,” so that signal is not sufficient.

The alternative Refactor the logic into a reusable function or private intermediate dataset as supported has a distinct purpose—A pipeline needs a reused intermediate subquery with no persisted public table. It would not establish the required outcome (A source needs an append-only streaming target defined in Python); the necessary verification concerns The pipeline treats the target as a streaming table with incremental progress.

This action solves a different issue: “A Python pipeline definition should register a managed materialized view with declarative SQL.” Its normal signal is The pipeline DAG contains the materialized view and its dataset is refreshed. Here the requested behavior is “A source needs an append-only streaming target defined in Python,” so that signal is not sufficient.

The pipeline produces the correct downstream outputs without an unintended published table would demonstrate the separate action Refactor the logic into a reusable function or private intermediate dataset as supported, which addresses “A pipeline needs a reused intermediate subquery with no persisted public table.” It does not verify the requirement “A source needs an append-only streaming target defined in Python” following Use a supported `@dp.table`-style streaming table definition with the streaming DataFrame.

A newer change event updates only the matching key according to sequence would demonstrate the separate action Define the required target and AUTO CDC flow with `keys` and `sequence_by`, which addresses “An AUTO CDC flow should be configured against a target with stable natural keys.” It does not verify the requirement “A source needs an append-only streaming target defined in Python” following Use a supported `@dp.table`-style streaming table definition with the streaming DataFrame.

The pipeline DAG contains the materialized view and its dataset is refreshed pertains to a different control (Use the supported pipelines Python decorator for a materialized view function) and a different need (A Python pipeline definition should register a managed materialized view with declarative SQL). It cannot establish that Use a supported `@dp.table`-style streaming table definition with the streaming DataFrame met the stated goal.

This action solves a different issue: “An AUTO CDC flow should be configured against a target with stable natural keys.” Its normal signal is A newer change event updates only the matching key according to sequence. Here the requested behavior is “A pipeline must ingest a stream from supported cloud files with Auto Loader,” so that signal is not sufficient.

The alternative Refactor the logic into a reusable function or private intermediate dataset as supported has a distinct purpose—A pipeline needs a reused intermediate subquery with no persisted public table. It would not establish the required outcome (A pipeline must ingest a stream from supported cloud files with Auto Loader); the necessary verification concerns The pipeline discovers new files and commits them without a daily full scan.

Use the supported pipelines Python decorator for a materialized view function is appropriate when “A Python pipeline definition should register a managed materialized view with declarative SQL”; it would be verified by The pipeline DAG contains the materialized view and its dataset is refreshed. It does not directly satisfy “A pipeline must ingest a stream from supported cloud files with Auto Loader,” whose relevant acceptance evidence is The pipeline discovers new files and commits them without a daily full scan.

The pipeline produces the correct downstream outputs without an unintended published table pertains to a different control (Refactor the logic into a reusable function or private intermediate dataset as supported) and a different need (A pipeline needs a reused intermediate subquery with no persisted public table). It cannot establish that Use the Auto Loader `cloudFiles` streaming source in a pipeline dataset met the stated goal.

The pipeline treats the target as a streaming table with incremental progress would demonstrate the separate action Use a supported `@dp.table`-style streaming table definition with the streaming DataFrame, which addresses “A source needs an append-only streaming target defined in Python.” It does not verify the requirement “A pipeline must ingest a stream from supported cloud files with Auto Loader” following Use the Auto Loader `cloudFiles` streaming source in a pipeline dataset.

This signal belongs to the adjacent case “An AUTO CDC flow should be configured against a target with stable natural keys,” whose remedy is Define the required target and AUTO CDC flow with `keys` and `sequence_by`. The observed result for the present requirement is The pipeline discovers new files and commits them without a daily full scan.

Refactor the logic into a reusable function or private intermediate dataset as supported belongs to the separate case “A pipeline needs a reused intermediate subquery with no persisted public table,” where The pipeline produces the correct downstream outputs without an unintended published table would be expected. That differs from the condition in this stem: “An AUTO CDC flow should be configured against a target with stable natural keys.”

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: “An AUTO CDC flow should be configured against a target with stable natural keys.”

Use a supported `@dp.table`-style streaming table definition with the streaming DataFrame is appropriate when “A source needs an append-only streaming target defined in Python”; it would be verified by The pipeline treats the target as a streaming table with incremental progress. It does not directly satisfy “An AUTO CDC flow should be configured against a target with stable natural keys,” whose relevant acceptance evidence is A newer change event updates only the matching key according to sequence.

The pipeline produces the correct downstream outputs without an unintended published table pertains to a different control (Refactor the logic into a reusable function or private intermediate dataset as supported) and a different need (A pipeline needs a reused intermediate subquery with no persisted public table). It cannot establish that Define the required target and AUTO CDC flow with `keys` and `sequence_by` met the stated goal.

The pipeline treats the target as a streaming table with incremental progress pertains to a different control (Use a supported `@dp.table`-style streaming table definition with the streaming DataFrame) and a different need (A source needs an append-only streaming target defined in Python). It cannot establish that Define the required target and AUTO CDC flow with `keys` and `sequence_by` met the stated goal.

That observation is a valid indicator for “A pipeline must ingest a stream from supported cloud files with Auto Loader” when using Use the Auto Loader `cloudFiles` streaming source in a pipeline dataset. The scenario instead tests “An AUTO CDC flow should be configured against a target with stable natural keys”; the relevant result is A newer change event updates only the matching key according to sequence.

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 pipeline needs a reused intermediate subquery with no persisted public table.”

Define the required target and AUTO CDC flow with `keys` and `sequence_by` belongs to the separate case “An AUTO CDC flow should be configured against a target with stable natural keys,” where A newer change event updates only the matching key according to sequence would be expected. That differs from the condition in this stem: “A pipeline needs a reused intermediate subquery with no persisted public table.”

The alternative Use a supported `@dp.table`-style streaming table definition with the streaming DataFrame has a distinct purpose—A source needs an append-only streaming target defined in Python. It would not establish the required outcome (A pipeline needs a reused intermediate subquery with no persisted public table); the necessary verification concerns The pipeline produces the correct downstream outputs without an unintended published table.

The pipeline discovers new files and commits them without a daily full scan pertains to a different control (Use the Auto Loader `cloudFiles` streaming source in a pipeline dataset) and a different need (A pipeline must ingest a stream from supported cloud files with Auto Loader). It cannot establish that Refactor the logic into a reusable function or private intermediate dataset as supported met the stated goal.

A newer change event updates only the matching key according to sequence would demonstrate the separate action Define the required target and AUTO CDC flow with `keys` and `sequence_by`, which addresses “An AUTO CDC flow should be configured against a target with stable natural keys.” It does not verify the requirement “A pipeline needs a reused intermediate subquery with no persisted public table” following Refactor the logic into a reusable function or private intermediate dataset as supported.

The pipeline DAG contains the materialized view and its dataset is refreshed pertains to a different control (Use the supported pipelines Python decorator for a materialized view function) and a different need (A Python pipeline definition should register a managed materialized view with declarative SQL). It cannot establish that Refactor the logic into a reusable function or private intermediate dataset as supported met the stated goal.