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

Monitor fact foreign-key consistency and changing dimension attributes. This monitor action addresses a different case (star schema analytics), where a denormalized mixed-grain table produces redundant attributes and expensive corrections. A star schema links a clear-grain fact to reusable dimensions for consistent analytics. In the stated problem, the same country appears under conflicting dimension keys across marts; this choice would not establish the required conformed dimensions decision.

Monitor orphaned foreign keys and repeated business identifiers. This monitor 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, the same country appears under conflicting dimension keys across marts; this choice would not establish the required conformed dimensions decision.

Monitor overlapping intervals and multiple current versions. This monitor action addresses a different case (scd type 2 effective dates), where a single current tier overwrites history in the dimension. SCD Type 2 stores effective start/end intervals for distinct historical dimension versions. In the stated problem, the same country appears under conflicting dimension keys across marts; this choice would not establish the required conformed dimensions decision.

Monitor uniqueness violations at the chosen grain. This monitor action addresses a different case (fact table grain), where summing revenue double-counts orders with multiple items. A dimensional fact must have one clearly documented row grain. In the stated problem, malformed source events contaminate metrics without an intermediate quality boundary; this choice would not establish the required medallion bronze silver gold decision.

Monitor aggregate freshness and reconciliation differences. This monitor 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, malformed source events contaminate metrics without an intermediate quality boundary; this choice would not establish the required medallion bronze silver gold decision.

Monitor overlapping intervals and multiple current versions. This monitor action addresses a different case (scd type 2 effective dates), where a single current tier overwrites history in the dimension. SCD Type 2 stores effective start/end intervals for distinct historical dimension versions. In the stated problem, malformed source events contaminate metrics without an intermediate quality boundary; this choice would not establish the required medallion bronze silver gold decision.

Restart on fresh compute and confirm the import error disappears. This validate 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, the only visible dashboard status is FAILED without a dataset name; this choice would not establish the required lakeflow event error classes decision.

Confirm job and pipeline IDs appear only in the intended workspace. This validate action addresses a different case (target-safe deployment), where the wrong workspace is selected because target is implicit. Explicit bundle target selection prevents accidental environment deployment. In the stated problem, the only visible dashboard status is FAILED without a dataset name; this choice would not establish the required lakeflow event error classes decision.

Confirm known-good logic and output metrics return without replay damage. This validate action addresses a different case (rollback deployment), where deployers have no record of the previous working configuration. Versioned bundle releases enable controlled rollback to a known commit. In the stated problem, the only visible dashboard status is FAILED without a dataset name; this choice would not establish the required lakeflow event error classes decision.

Verify expired subjects are inaccessible through approved retrieval paths. This validate action addresses a different case (retention purge), where expired records remain available in historical serving tables. Retention design must remove records and account for Delta time travel and obsolete files. In the stated problem, deleting a row from only the gold table leaves copies elsewhere; this choice would not establish the required data subject request decision.

Confirm reader cannot edit but approved maintainer can deploy. This validate action addresses a different case (workspace object acl), where the team needs read-only access for most users. Workspace object permissions can restrict who can edit or manage shared code. In the stated problem, deleting a row from only the gold table leaves copies elsewhere; this choice would not establish the required data subject request decision.

Query as privileged and standard readers and verify intended masked values. This validate action addresses a different case (column masking), where a raw SELECT on an approved table exposes plaintext email. Unity Catalog column masks can transform sensitive values at read time. In the stated problem, deleting a row from only the gold table leaves copies elsewhere; this choice would not establish the required data subject request decision.

Monitor dimension growth that may invalidate the broadcast assumption. This monitor 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, rows with null external IDs disappear from an inner join; this choice would not establish the required join with nullable keys decision.

Alert on failed expectations and blocked pipeline updates. This monitor 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, rows with null external IDs disappear from an inner join; this choice would not establish the required join with nullable keys decision.

Monitor invalid timezone offsets and parsing errors. This monitor 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, rows with null external IDs disappear from an inner join; this choice would not establish the required join with nullable keys decision.

Submit a known broken transformation and confirm deployment is blocked. This validate action addresses a different case (ci quality gates), where the deployment pipeline only checks YAML syntax. CI must run transformation tests and controlled integration checks before deployment. In the stated problem, the notebook cell shows only a generic stage failure; this choice would not establish the required cluster log diagnostics decision.

Run the pipeline and confirm the previous error class does not recur. This validate 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, the notebook cell shows only a generic stage failure; this choice would not establish the required cluster log diagnostics decision.

Confirm job and pipeline IDs appear only in the intended workspace. This validate action addresses a different case (target-safe deployment), where the wrong workspace is selected because target is implicit. Explicit bundle target selection prevents accidental environment deployment. In the stated problem, the notebook cell shows only a generic stage failure; this choice would not establish the required cluster log diagnostics decision.

Apply USE CATALOG, USE SCHEMA and table SELECT to the consumer group. This implement action addresses a different case (catalog privilege inheritance), where the team lacks USE CATALOG and USE SCHEMA on the parent containers. Unity Catalog object access generally requires relevant parent usage privileges. In the stated problem, teams grant SELECT merely to expose object listings; this choice would not establish the required browse metadata privilege decision.

Apply approved tags to the catalog objects or columns. This implement action addresses a different case (governed tags), where naming conventions alone are inconsistent across teams. Governed tags can classify assets for discovery and policy workflows. In the stated problem, teams grant SELECT merely to expose object listings; this choice would not establish the required browse metadata privilege decision.

Grant SELECT on the schema with requisite parent usage. This implement action addresses a different case (schema-level grant inheritance), where analysts must repeatedly request identical SELECT grants for each table. Unity Catalog schema-level privileges can apply to existing and future child objects. In the stated problem, teams grant SELECT merely to expose object listings; this choice would not establish the required browse metadata privilege decision.

Create a representative safe sample and separate test pipeline. This design 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, the scheduler launches a full rebuild instead of rerunning the affected date; this choice would not establish the required override run parameters decision.

Define a controlled change-management path for resource configuration. This design action addresses a different case (unmanaged resource drift), where subsequent CI redeployment unexpectedly overwrites it. Declarative source of truth should include intentional job-resource changes. In the stated problem, the scheduler launches a full rebuild instead of rerunning the affected date; this choice would not establish the required override run parameters decision.

Use a repair run for recoverable task failures rather than blindly rerunning all tasks. This design action addresses a different case (repair failed tasks), where operators rerun the entire job and duplicate completed side effects. Repair runs can rerun failed or selected tasks while preserving successful predecessor work under supported semantics. In the stated problem, the scheduler launches a full rebuild instead of rerunning the affected date; this choice would not establish the required override run parameters decision.

Use transactional merge or a committed batch-ID deduplication design. This design 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, the downstream write repeats non-idempotent side effects on retry; this choice would not establish the required job retry semantics decision.

Normalize the right side to its intended grain before joining. This design action addresses a different case (sql join cardinality), where the row count doubles because the right side contains duplicate join keys. A many-to-many join expands cardinality unless the right grain is established. 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.

Branch downstream tasks using an If/else condition before divergent paths. This design 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.

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, an upstream replay creates multiple active versions; this choice would not establish the required uniqueness quality rule decision.

Rank events by business key, event time and a deterministic tie-breaker. This design 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, an upstream replay creates multiple active versions; this choice would not establish the required uniqueness quality rule 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, an upstream replay creates multiple active versions; this choice would not establish the required uniqueness quality rule 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, partners risk losing access or using a leaked long-lived credential; this choice would not establish the required sharing credential rotation 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, partners risk losing access or using a leaked long-lived credential; this choice would not establish the required sharing credential rotation 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, partners risk losing access or using a leaked long-lived credential; this choice would not establish the required sharing credential rotation decision.