Pass Databricks Certified Data Engineer Professional Exam in First Attempt Guaranteed!

Confirm dashboard results refresh after source data updates. This validate action addresses a different case (materialized view choice), where each dashboard query recomputes the same expensive aggregation. A materialized view maintains a precomputed query result through refresh. In the stated problem, developers tune executor size without inspecting actual exchanges; this choice would not establish the required spark explain plans decision.

Confirm deployment reflects the reviewed configuration without extra changes. This validate action addresses a different case (databricks cli resource updates), where production configuration drifts from repository source definitions. Declarative deployment describes resources as reviewed version-controlled artifacts. In the stated problem, developers tune executor size without inspecting actual exchanges; this choice would not establish the required spark explain plans decision.

Replay a batch ID and confirm target rows are not duplicated. This validate action addresses a different case (streaming idempotent sink), where a retry of a completed batch produces duplicate sink rows. foreachBatch can execute a batch again and requires idempotent external writes for exactly-once effects. In the stated problem, developers tune executor size without inspecting actual exchanges; this choice would not establish the required spark explain plans decision.

Inspect source key uniqueness and merge match conditions. This diagnose action addresses a different case (cdc merge semantics), where the current INSERT-only target contains duplicate customer keys. A keyed Delta MERGE can update existing rows and insert new keys. In the stated problem, a plain dropDuplicates retains state without a practical bound for never-ending keys; this choice would not establish the required streaming dedup watermark decision.

Inspect join strategy and dimension size in the executed plan. This diagnose action addresses a different case (broadcast lookup table), where the join triggers a costly shuffle of the large fact dataset. Broadcasting an appropriately sized dimension can avoid a large shuffle join. In the stated problem, a plain dropDuplicates retains state without a practical bound for never-ending keys; this choice would not establish the required streaming dedup watermark decision.

Inspect per-key frequencies and Spark task duration distribution. This diagnose action addresses a different case (skewed group aggregation), where a single campaign dominates rows and one reduce task runs for minutes. A hot aggregation key causes skew despite ample parallelism. In the stated problem, a plain dropDuplicates retains state without a practical bound for never-ending keys; this choice would not establish the required streaming dedup watermark decision.

Use drop semantics only when invalid records may be excluded by policy. This design action addresses a different case (expectation drop action), where invalid rows currently reach downstream aggregates. A Lakeflow expectation configured to drop invalid rows filters violations from target output. In the stated problem, the pipeline continues despite critical null records; this choice would not establish the required expectation fail action decision.

Preserve unmatched facts with a left join when business rules require them. This design action addresses a different case (join with nullable keys), where rows with null external IDs disappear from an inner join. SQL null equality and join type determine whether unmatched rows survive. In the stated problem, the pipeline continues despite critical null records; this choice would not establish the required expectation fail action decision.

Choose a supported broadcast strategy for the small lookup dimension. This design action addresses a different case (broadcast lookup table), where the join triggers a costly shuffle of the large fact dataset. Broadcasting an appropriately sized dimension can avoid a large shuffle join. In the stated problem, the pipeline continues despite critical null records; this choice would not establish the required expectation fail action decision.

Deploy the wheel task with its documented entrypoint and parameters. This implement action addresses a different case (python task entrypoints), where the task exits before setting up its argument parser. A standard Python entrypoint and explicit arguments avoid notebook runtime assumptions. In the stated problem, code contains hard-coded region IDs and catalog names; this choice would not establish the required job parameters decision.

Include the unique tie-breaker in the supported sequence expression. This implement action addresses a different case (cdc duplicate sequence), where the processing order for tied source events is nondeterministic. A deterministic sequencing contract needs a unique ordered event position. In the stated problem, code contains hard-coded region IDs and catalog names; this choice would not establish the required job parameters decision.

Use the Databricks CLI to validate and deploy the bundle target. This implement action addresses a different case (databricks cli resource updates), where production configuration drifts from repository source definitions. Declarative deployment describes resources as reviewed version-controlled artifacts. In the stated problem, code contains hard-coded region IDs and catalog names; this choice would not establish the required job parameters decision.

Inspect duplicate file IDs and the ingestion checkpoint state. This diagnose action addresses a different case (retry-safe file loads), where a partially processed input file is loaded twice into Delta. Checkpointed incremental ingestion or stable event-level deduplication prevents repeated effects. In the stated problem, restarting with a fresh checkpoint replays previously ingested messages; this choice would not establish the required kafka offset durability decision.

Inspect inferred schemas and rescued or null fields in recently ingested rows. This diagnose action addresses a different case (nested json ingest), where the initial reader assumes one unchanging flat schema and loses new fields. Explicit schema management and rescued data handling protect evolving semi-structured ingestion. In the stated problem, restarting with a fresh checkpoint replays previously ingested messages; this choice would not establish the required kafka offset durability decision.

Inspect file media types and current input source format. This diagnose action addresses a different case (binary payload metadata), where a line-oriented text reader corrupts the raw binary payload. binaryFile input preserves raw file bytes and path metadata rather than decoding lines. In the stated problem, restarting with a fresh checkpoint replays previously ingested messages; this choice would not establish the required kafka offset durability decision.

Refactor business rules as pure DataFrame transform functions. This design action addresses a different case (transform composability), where business logic depends on notebook state and widgets. DataFrame.transform supports composable DataFrame-to-DataFrame functions. In the stated problem, a refactor broke a notebook-relative import in the deployed job; this choice would not establish the required python wheel packaging decision.

Move resource definitions into bundle YAML with review gates. This design action addresses a different case (databricks cli resource updates), where production configuration drifts from repository source definitions. Declarative deployment describes resources as reviewed version-controlled artifacts. In the stated problem, a refactor broke a notebook-relative import in the deployed job; this choice would not establish the required python wheel packaging decision.

Create an importable command-line entrypoint with explicit validated arguments. This design action addresses a different case (python task entrypoints), where the task exits before setting up its argument parser. A standard Python entrypoint and explicit arguments avoid notebook runtime assumptions. In the stated problem, a refactor broke a notebook-relative import in the deployed job; this choice would not establish the required python wheel packaging decision.

Inspect Query Profile operators for scan volume and pruning. This diagnose action addresses a different case (query profile scans), where operators assume the query is always CPU-bound. Query Profile identifies scan, pruning and shuffle behavior for SQL workloads. In the stated problem, operators monitor compute uptime rather than data freshness; this choice would not establish the required end-to-end sla decision.

Inspect run status, task IDs and time windows in supported jobs system tables. This diagnose action addresses a different case (job operational history), where operators only see the most recent run in the Jobs UI. Jobs system records support historical analysis of runs and tasks. In the stated problem, operators monitor compute uptime rather than data freshness; this choice would not establish the required end-to-end sla decision.

Inspect current notification settings and run failure statuses. This diagnose action addresses a different case (job email notification), where operators manually check the run page every morning. Lakeflow Jobs support status-triggered notifications for run outcomes. In the stated problem, operators monitor compute uptime rather than data freshness; this choice would not establish the required end-to-end sla decision.

Create separate dashboards for rejected data and failed pipeline updates. This design action addresses a different case (quality metric interpretation), where analysts misread a quality count as the number of pipeline task failures. Expectation metrics describe data rows and must be interpreted separately from orchestration status. In the stated problem, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records decision.

Define a reviewable additive-column evolution policy. This design action addresses a different case (controlled schema evolution), where the silver writer rejects every new record after the upstream schema change. Schema evolution must be reviewed rather than enabling unrestricted acceptance for every column. In the stated problem, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records decision.

Specify canonical typed silver columns and an invalid-value quarantine rule. This design action addresses a different case (silver schema enforcement), where implicit type coercion risks invalid numeric values being stored. Schema validation and explicit casts make type conversion failures observable. In the stated problem, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records decision.

Inspect malformed timestamps and pipeline data-quality rules. This diagnose action addresses a different case (quarantine bad records), where dropping invalid rows silently hides upstream quality failures. Quarantine preserves invalid events separately while allowing valid records through. In the stated problem, an upstream replay creates multiple active versions; this choice would not establish the required uniqueness quality rule decision.

Inspect row-level expectation metrics alongside pipeline event types. This diagnose action addresses a different case (quality metric interpretation), where analysts misread a quality count as the number of pipeline task failures. Expectation metrics describe data rows and must be interpreted separately from orchestration status. In the stated problem, an upstream replay creates multiple active versions; this choice would not establish the required uniqueness quality rule decision.

Compare source and target schemas before changing the writer. This diagnose action addresses a different case (controlled schema evolution), where the silver writer rejects every new record after the upstream schema change. Schema evolution must be reviewed rather than enabling unrestricted acceptance for every column. In the stated problem, an upstream replay creates multiple active versions; this choice would not establish the required uniqueness quality rule decision.

Inspect Python version, wheel tags and package resolution logs. This diagnose action addresses a different case (python dependency triage), where a package import error appears only on the target compute. Runtime-specific wheel compatibility and pinning must be tested in CI. In the stated problem, an invalid resource key would be rejected only after production change; this choice would not establish the required bundle validation decision.

Inspect the failing record schema under restricted access. This diagnose action addresses a different case (pipeline debug sampling), where re-running a huge source in development is slow and risky. A minimal reproducible input isolates the failure without modifying production data. In the stated problem, an invalid resource key would be rejected only after production change; this choice would not establish the required bundle validation decision.

Inspect pipeline event log update IDs and error messages. This diagnose action addresses a different case (lakeflow event error classes), where the only visible dashboard status is FAILED without a dataset name. Pipeline event logs identify failing update and dataset messages. In the stated problem, an invalid resource key would be rejected only after production change; this choice would not establish the required bundle validation decision.

Monitor expectation-drop counts and upstream correction rates. This monitor action addresses a different case (expectation drop action), where invalid rows currently reach downstream aggregates. A Lakeflow expectation configured to drop invalid rows filters violations from target output. In the stated problem, events from different regions are ordered incorrectly in a UTC dashboard; this choice would not establish the required timestamp timezone normalization decision.

Monitor tied timestamps and nondeterministic upstream sequence values. This monitor action addresses a different case (latest-per-key with ties), where two events have the same event time and yield different surviving rows. A deterministic tie-breaker is required in a per-key window ranking. In the stated problem, events from different regions are ordered incorrectly in a UTC dashboard; this choice would not establish the required timestamp timezone normalization decision.

Monitor null-key rate and unmatched dimension lookups. This monitor action addresses a different case (join with nullable keys), where rows with null external IDs disappear from an inner join. SQL null equality and join type determine whether unmatched rows survive. In the stated problem, events from different regions are ordered incorrectly in a UTC dashboard; this choice would not establish the required timestamp timezone normalization decision.