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

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, a package import error appears only on the target compute; this choice would not establish the required python dependency triage decision.

Inspect effective grants on source, target and parent containers for the run-as principal. This diagnose action addresses a different case (job run permission debug), where the run-as principal lacks MODIFY on the target table. Unity Catalog authorization applies to the job execution identity. In the stated problem, a package import error appears only on the target compute; this choice would not establish the required python dependency triage decision.

Inspect executor stderr and driver logs near the failed stage. This diagnose action addresses a different case (cluster log diagnostics), where the notebook cell shows only a generic stage failure. Driver and executor logs often contain the exact import or JVM error. In the stated problem, a package import error appears only on the target compute; this choice would not establish the required python dependency triage decision.

Process an update and an insert and verify one correct current row per key. This validate 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.

Confirm rows with and without region codes both appear correctly. This validate action addresses a different case (conditional enrichment), where an unconditional inner join discards rows with missing region codes. A left join with explicit CASE logic preserves rows while enriching those that match. 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.

Inject an invalid record and confirm the update fails visibly. This validate action addresses a different case (expectation fail action), where the pipeline continues despite critical null records. Fail-on-violation expectations stop updates rather than silently filtering rows. 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.

Monitor state rows and dropped late-event counts. This monitor action addresses a different case (event-time watermarking), where old keys remain in state indefinitely without a lateness bound. Watermarks provide a lateness threshold for bounded stateful streaming operations. In the stated problem, the downstream write repeats non-idempotent side effects on retry; this choice would not establish the required job retry semantics decision.

Monitor condition outcomes and unexpected repair-task executions. This monitor action addresses a different case (conditional task branches), where both the normal and repair tasks run despite a branching requirement. Lakeflow Jobs condition tasks can route downstream execution based on a result. In the stated problem, the downstream write repeats non-idempotent side effects on retry; this choice would not establish the required job retry semantics decision.

Monitor entrypoint failures after runtime or package upgrades. This monitor 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, the downstream write repeats non-idempotent side effects on retry; this choice would not establish the required job retry semantics decision.

Use a left join plus a documented fallback label for unmatched keys. This design action addresses a different case (conditional enrichment), where an unconditional inner join discards rows with missing region codes. A left join with explicit CASE logic preserves rows while enriching those that match. In the stated problem, an order-level aggregation mistakenly treats the array as a single item; this choice would not establish the required array explosion decision.

Select appropriate salting or staged aggregation for a hot key. This design 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, an order-level aggregation mistakenly treats the array as a single item; this choice would not establish the required array explosion decision.

Define source deduplication plus an upsert merge contract. This design 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, an order-level aggregation mistakenly treats the array as a single item; this choice would not establish the required array explosion decision.

Use immutable surrogate dimension keys mapped from source business IDs. This design action addresses a different case (surrogate dimension keys), where joining facts directly on mutable business IDs links history incorrectly. Stable surrogate keys decouple dimensional identity from changing source identifiers. In the stated problem, joining facts directly to the membership table multiplies totals; this choice would not establish the required many-to-many bridge decision.

Plan an additive nullable dimension attribute with documented defaults. This design action addresses a different case (dimension evolution), where a destructive table recreation would invalidate downstream consumers. Additive schema evolution can preserve contracts when null defaults are acceptable. In the stated problem, joining facts directly to the membership table multiplies totals; this choice would not establish the required many-to-many bridge decision.

Create a gold aggregate keyed by day and product with documented measures. This design action addresses a different case (aggregate gold model), where interactive queries scan billions of detail rows for identical totals. A summarized gold table can serve a stable reporting grain efficiently. In the stated problem, joining facts directly to the membership table multiplies totals; this choice would not establish the required many-to-many bridge decision.

Compare deployed resource definitions against committed bundle configuration. This monitor action addresses a different case (bundle repository layout), where source files and deployment definitions are coupled to one developer workspace. A versioned Declarative Automation Bundle defines code and resource configurations separately from the target workspace. 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.

Alert on runtime upgrades that invalidate pinned wheel binaries. This monitor action addresses a different case (wheel abi compatibility), where the wheel works on a developer laptop but fails with a binary compatibility error. Compiled extensions must match the target runtime platform and Python ABI. 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.

Monitor divergence between tested package and deployed code version. This monitor 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.

Compare installed wheel versions with the CI release manifest. This monitor action addresses a different case (python wheel packaging), where a refactor broke a notebook-relative import in the deployed job. A properly packaged versioned wheel gives Python code stable import paths outside notebooks. In the stated problem, business logic depends on notebook state and widgets; this choice would not establish the required transform composability decision.

Detect unexpected package version changes in startup validation. This monitor action addresses a different case (library precedence), where a notebook-scoped installation overrides the expected cluster version. The runtime can resolve conflicting versions from different installation scopes. In the stated problem, business logic depends on notebook state and widgets; this choice would not establish the required transform composability decision.

Monitor overlapping effective intervals per business key. This monitor action addresses a different case (scd type 2 history), where overwrite-style updates destroy historical state needed for point-in-time reporting. SCD Type 2 records effective history instead of replacing the previous version. In the stated problem, business logic depends on notebook state and widgets; this choice would not establish the required transform composability decision.

Separate valid silver rows from a restricted quarantine table. This design 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, invalid rows currently reach downstream aggregates; this choice would not establish the required expectation drop action decision.

Choose fail semantics for non-negotiable constraints. This design action addresses a different case (expectation fail action), where the pipeline continues despite critical null records. Fail-on-violation expectations stop updates rather than silently filtering rows. In the stated problem, invalid rows currently reach downstream aggregates; this choice would not establish the required expectation drop action decision.

Define source deduplication plus an upsert merge contract. This design 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, invalid rows currently reach downstream aggregates; this choice would not establish the required expectation drop action decision.

Audit share membership changes against approvals. This monitor action addresses a different case (share catalog scope), where the recipient can discover unintended datasets. A Delta Sharing share should contain only explicitly approved assets. In the stated problem, engineers export the full source database into cloud object storage each hour; this choice would not establish the required federated connection decision.

Audit federation-specific grants and unexpected access. This monitor action addresses a different case (foreign catalog permission), where catalog discovery was mistaken for full table access. Unity Catalog usage and object privileges are still required for foreign data objects. In the stated problem, engineers export the full source database into cloud object storage each hour; this choice would not establish the required federated connection decision.

Monitor provider refresh and recipient visibility delays. This monitor action addresses a different case (shared table freshness), where consumers assume the share is a nightly static export. Delta Sharing exposes current authorized data as the provider updates the source. In the stated problem, engineers export the full source database into cloud object storage each hour; this choice would not establish the required federated connection decision.

Apply LEFT JOIN and CASE WHEN or COALESCE to the region output. This implement action addresses a different case (conditional enrichment), where an unconditional inner join discards rows with missing region codes. A left join with explicit CASE logic preserves rows while enriching those that match. In the stated problem, two events have the same event time and yield different surviving rows; this choice would not establish the required latest-per-key with ties decision.

Parse offset-aware timestamps and persist a consistent UTC representation. This implement action addresses a different case (timestamp timezone normalization), where events from different regions are ordered incorrectly in a UTC dashboard. Time-zone normalization is required before comparing timestamps from different sources. In the stated problem, two events have the same event time and yield different surviving rows; this choice would not establish the required latest-per-key with ties decision.

Query supported expectation metric records in the event log. This implement 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, two events have the same event time and yield different surviving rows; this choice would not establish the required latest-per-key with ties decision.

Use supported AQE with appropriate shuffle and join settings. This design action addresses a different case (adaptive execution), where static join strategy performs poorly at varying input volumes. Adaptive Query Execution can adjust supported shuffle partitions and join strategies at runtime. In the stated problem, executor memory pressure grows even though input rate is stable; this choice would not establish the required streaming state growth decision.

Schedule appropriate compaction or predictive optimization for the table. This design action addresses a different case (small file compaction), where read overhead grows because query plans open excessive small files. OPTIMIZE can compact compatible Delta files without changing logical table contents. In the stated problem, executor memory pressure grows even though input rate is stable; this choice would not establish the required streaming state growth decision.

Choose a partition count based on volume and executor capacity. This design action addresses a different case (shuffle partition count), where the current partition count is too low for data volume. Shuffle partition sizing affects memory pressure and task parallelism. In the stated problem, executor memory pressure grows even though input rate is stable; this choice would not establish the required streaming state growth decision.