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

Model Type 2 records with effective intervals and current-row flag. This design 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, a denormalized mixed-grain table produces redundant attributes and expensive corrections; this choice would not establish the required star schema analytics decision.

Choose one order-line grain for transaction detail metrics. This design 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, a denormalized mixed-grain table produces redundant attributes and expensive corrections; this choice would not establish the required star schema analytics decision.

Define a common country dimension with agreed identifiers and attributes. This design action addresses a different case (conformed dimensions), where the same country appears under conflicting dimension keys across marts. A conformed dimension provides common attribute definitions across fact models. In the stated problem, a denormalized mixed-grain table produces redundant attributes and expensive corrections; this choice would not establish the required star schema analytics 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, a recipient team copies files manually and loses timely updates; this choice would not establish the required d2d managed recipient 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, a recipient team copies files manually and loses timely updates; this choice would not establish the required d2d managed recipient decision.

Monitor recipient access and credential expiry. This monitor action addresses a different case (open protocol recipient), where the partner cannot use an internal Databricks-to-Databricks credential flow. Open Delta Sharing can support non-Databricks recipients using the sharing protocol. In the stated problem, a recipient team copies files manually and loses timely updates; this choice would not establish the required d2d managed recipient decision.

Correlate a known failed run to its constituent failed task. This validate 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, a manual UI report omits failed tasks and paginated runs; this choice would not establish the required jobs rest monitoring decision.

Remove one test unit and verify the alert condition is met. This validate action addresses a different case (sql alert threshold), where the current dashboard has no automated alert for missing units. SQL alerts can evaluate a query result against a configured threshold. In the stated problem, a manual UI report omits failed tasks and paginated runs; this choice would not establish the required jobs rest monitoring decision.

Compare total runtime and spend before and after. This validate action addresses a different case (compute utilization), where most provisioned resources sit idle between job runs. Compute metrics and usage history distinguish idle capacity from active work. In the stated problem, a manual UI report omits failed tasks and paginated runs; this choice would not establish the required jobs rest monitoring decision.

Alert on freshness lag rather than only job failure. This monitor action addresses a different case (end-to-end sla), where operators monitor compute uptime rather than data freshness. SLA monitoring should measure source event time to published table availability. In the stated problem, only personal email notifications are configured; this choice would not establish the required job webhook destination decision.

Monitor job failure rate and latency over time. This monitor 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, only personal email notifications are configured; this choice would not establish the required job webhook destination decision.

Monitor pipeline error and warning event rates. This monitor action addresses a different case (pipeline event log), where the Jobs status only reports a high-level failure. Lakeflow pipeline event logs include update-level errors and progress events. In the stated problem, only personal email notifications are configured; this choice would not establish the required job webhook destination 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, an operator proposes aggressive VACUUM retention during active long-running readers; this choice would not establish the required vacuum retention safety decision.

Choose a supported columnar Delta or Parquet layout for analytics. This design action addresses a different case (columnar compression), where row-oriented text storage increases scans and transfer volumes. Columnar formats and appropriate encoding improve analytical read efficiency. In the stated problem, an operator proposes aggressive VACUUM retention during active long-running readers; this choice would not establish the required vacuum retention safety decision.

Choose adaptive skew join handling or a justified hot-key strategy. This design action addresses a different case (skewed joins), where a single join partition spills heavily to disk. Adaptive skew handling or key salting can mitigate a hot join key. In the stated problem, an operator proposes aggressive VACUUM retention during active long-running readers; this choice would not establish the required vacuum retention safety decision.

Make writes idempotent before enabling retries. This design action addresses a different case (job retry semantics), where the downstream write repeats non-idempotent side effects on retry. Retries re-execute task logic; application code must protect repeated effects. In the stated problem, the row count doubles because the right side contains duplicate join keys; this choice would not establish the required sql join cardinality decision.

Model bronze as predecessor to both independent silver tasks. This design action addresses a different case (job task dag), where dependent tasks sometimes run before the bronze load finishes. Lakeflow Job task dependencies form a directed acyclic execution graph. In the stated problem, the row count doubles because the right side contains duplicate join keys; this choice would not establish the required sql join cardinality 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 row count doubles because the right side contains duplicate join keys; this choice would not establish the required sql join cardinality decision.

Create or update the approved location and grant only necessary privileges. This implement action addresses a different case (external location governance), where raw cloud permissions bypass central catalog governance. External locations map cloud paths to governed Unity Catalog storage credentials. In the stated problem, new data stewards cannot maintain its grants; this choice would not establish the required ownership reassignment decision.

Query supported lineage records or Catalog Explorer for dependencies. This implement action addresses a different case (lineage tracking), where investigators cannot tell which upstream transformation produced it. Unity Catalog lineage records relationships between governed data assets. In the stated problem, new data stewards cannot maintain its grants; this choice would not establish the required ownership reassignment decision.

Set the supported managed location and create tables under it. This implement action addresses a different case (managed storage ownership), where the data platform cannot apply consistent lifecycle governance. Managed locations centralize storage ownership for Unity Catalog managed assets. In the stated problem, new data stewards cannot maintain its grants; this choice would not establish the required ownership reassignment decision.

Ingest a mixed batch and reconcile passed and quarantined counts. This validate 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, implicit type coercion risks invalid numeric values being stored; this choice would not establish the required silver schema enforcement decision.

Append null IDs and confirm they are excluded while valid IDs remain. This validate 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, implicit type coercion risks invalid numeric values being stored; this choice would not establish the required silver schema enforcement 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, implicit type coercion risks invalid numeric values being stored; this choice would not establish the required silver schema enforcement decision.

Run OPTIMIZE or enable managed optimization where supported. This implement 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.

Add supported partition or clustering predicates to MERGE match conditions. This implement action addresses a different case (predicate-limited merge), where the merge scans unrelated historical partitions. Constraining merge matches to relevant partitions can reduce unnecessary target scanning. 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.

Configure supported min/max worker settings for the workload. This implement action addresses a different case (autoscaling right-size), where a fixed high-worker count wastes resources on quiet days. Supported autoscaling can adapt worker count within configured bounds. 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.

Validate distinct customer counts and allocated totals after bridge joins. This validate action addresses a different case (many-to-many bridge), where joining facts directly to the membership table multiplies totals. A bridge table models many-to-many relationships at an explicit membership grain. In the stated problem, summing revenue double-counts orders with multiple items; this choice would not establish the required fact table grain decision.

Reconcile gold totals and dashboard response time against direct fact queries. This validate 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, summing revenue double-counts orders with multiple items; this choice would not establish the required fact table grain decision.

Reconcile sample reports and verify dimensions join without duplication. This validate 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, summing revenue double-counts orders with multiple items; this choice would not establish the required fact table grain decision.

Enforce one active record per key with deterministic conflict rules. This design action addresses a different case (uniqueness quality rule), where an upstream replay creates multiple active versions. An explicit uniqueness check identifies duplicate business keys before serving data. 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.

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, rows with null external IDs disappear from an inner join; this choice would not establish the required join with nullable keys 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, rows with null external IDs disappear from an inner join; this choice would not establish the required join with nullable keys decision.