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

Keep filter predicates aligned with the stored partition column. This design action addresses a different case (partition pruning), where a query wraps business_date in a transformation and reads many partitions. Direct predicates on partition keys can enable partition pruning. In the stated problem, the merge scans unrelated historical partitions; this choice would not establish the required predicate-limited merge decision.

Choose supported liquid clustering on commonly filtered device fields. This design action addresses a different case (liquid clustering cardinality), where partitioning by device would produce many tiny partitions. Liquid clustering organizes data by useful filter keys without high-cardinality partition directories. In the stated problem, the merge scans unrelated historical partitions; this choice would not establish the required predicate-limited merge 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, the merge scans unrelated historical partitions; this choice would not establish the required predicate-limited merge decision.

Monitor CI authentication failures and principal grants. This monitor action addresses a different case (api deployment authentication), where scheduled production deployment fails when the developer's token expires. Workload identity or service principal authentication decouples CI from employees. In the stated problem, the run-as principal lacks MODIFY on the target table; this choice would not establish the required job run permission debug decision.

Monitor duplicate delivery IDs and retry attempts. This monitor action addresses a different case (idempotent retry repair), where customers receive repeated notifications for the same batch. Task retries need idempotent side effects even when upstream work is reused. In the stated problem, the run-as principal lacks MODIFY on the target table; this choice would not establish the required job run permission debug decision.

Audit deployment target changes and cross-environment drift. This monitor 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 run-as principal lacks MODIFY on the target table; this choice would not establish the required job run permission debug 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, cost reports omit some job and workspace labels; this choice would not establish the required billing usage monitoring decision.

Monitor alert evaluations and delivery failures. This monitor 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, cost reports omit some job and workspace labels; this choice would not establish the required billing usage monitoring decision.

Alert on unusual sensitive-object access patterns. This monitor action addresses a different case (audit log review), where workspace notebook logs do not show the full audited account activity. System audit tables provide security-relevant account events subject to access controls. In the stated problem, cost reports omit some job and workspace labels; this choice would not establish the required billing usage monitoring 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, row-by-row Python invocation dominates stage runtime; this choice would not establish the required vectorized udf decision.

Apply watermark before supported stateful aggregation with matching event-time column. This implement 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, row-by-row Python invocation dominates stage runtime; this choice would not establish the required vectorized udf decision.

Configure the supported SCD Type 2 flow with keys and sequence. This implement 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, row-by-row Python invocation dominates stage runtime; this choice would not establish the required vectorized udf decision.

Run representative device filters and compare data skipping. This validate action addresses a different case (liquid clustering cardinality), where partitioning by device would produce many tiny partitions. Liquid clustering organizes data by useful filter keys without high-cardinality partition directories. In the stated problem, a query wraps business_date in a transformation and reads many partitions; this choice would not establish the required partition pruning decision.

Verify shuffle spill decreases without excessive scheduling overhead. This validate 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, a query wraps business_date in a transformation and reads many partitions; this choice would not establish the required partition pruning decision.

Compare results and max task time before and after. This validate 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, a query wraps business_date in a transformation and reads many partitions; this choice would not establish the required partition pruning decision.

Inspect the bundle manifest schema and validation result. This diagnose action addresses a different case (bundle validation), where an invalid resource key would be rejected only after production change. Bundle validation detects many configuration problems before deployment. In the stated problem, subsequent CI redeployment unexpectedly overwrites it; this choice would not establish the required unmanaged resource drift decision.

Inspect CI stages for tests, bundle validation and approvals. This diagnose 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, subsequent CI redeployment unexpectedly overwrites it; this choice would not establish the required unmanaged resource drift 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, subsequent CI redeployment unexpectedly overwrites it; this choice would not establish the required unmanaged resource drift decision.

Inspect event log messages, error class and dataset name around the failed update. This diagnose 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, scheduled updates are spaced several hours apart; this choice would not establish the required pipeline update cadence decision.

Inspect ingestion timestamps, pipeline refresh times and gold table commit times. This diagnose 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, scheduled updates are spaced several hours apart; this choice would not establish the required pipeline update cadence decision.

Inspect expectation metric counts in the event log. This diagnose action addresses a different case (expectation monitoring), where analysts confuse successful pipeline status with zero rejected records. Quality metric events reveal input and dropped records separately from update status. In the stated problem, scheduled updates are spaced several hours apart; this choice would not establish the required pipeline update cadence decision.

Audit unauthorized changes to workspace objects. This monitor 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, a broad SELECT still includes unstructured notes; this choice would not establish the required sensitive data suppression decision.

Audit row filter changes and unexpectedly broad query results. This monitor action addresses a different case (unity catalog row filter), where a shared table currently returns all regions to every reader. Unity Catalog row filters can restrict row visibility through governed policies. In the stated problem, a broad SELECT still includes unstructured notes; this choice would not establish the required sensitive data suppression decision.

Audit ownership changes and privilege grants. This monitor action addresses a different case (separation of duties), where all developers currently own production catalogs and can grant access. Separate deploy and governance roles reduce accidental privilege escalation. In the stated problem, a broad SELECT still includes unstructured notes; this choice would not establish the required sensitive data suppression decision.

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, summing revenue double-counts orders with multiple items; this choice would not establish the required fact table grain 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, summing revenue double-counts orders with multiple items; this choice would not establish the required fact table grain decision.

Model one order-line fact with product, store and date dimensions. This design 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.

Set explicit target overrides and deploy using the approved production target. This implement action addresses a different case (bundle target overrides), where development job arguments were deployed into the production target. Bundle targets can override environment-specific variables and resource settings. In the stated problem, an employee departure causes permissions failures during scheduled runs; this choice would not establish the required job run-as identity decision.

Define a streaming table reading the source through a supported streaming connector. This implement action addresses a different case (streaming table choice), where periodic full-refresh queries miss required incremental freshness. A streaming table tracks continuously arriving source data incrementally. In the stated problem, an employee departure causes permissions failures during scheduled runs; this choice would not establish the required job run-as identity decision.

Restore the approved checkpoint path in the query deployment. This implement action addresses a different case (streaming checkpoint identity), where a newly selected checkpoint location makes the stream reread historical input. Streaming checkpoint metadata records progress and state for restart continuity. In the stated problem, an employee departure causes permissions failures during scheduled runs; this choice would not establish the required job run-as identity decision.

Query as two regional users and confirm different allowed row sets. This validate action addresses a different case (unity catalog row filter), where a shared table currently returns all regions to every reader. Unity Catalog row filters can restrict row visibility through governed policies. In the stated problem, engineers propose a credential allowing access to all company buckets; this choice would not establish the required storage credential scope decision.

Confirm deployment works while a developer cannot grant themselves table access. This validate action addresses a different case (separation of duties), where all developers currently own production catalogs and can grant access. Separate deploy and governance roles reduce accidental privilege escalation. In the stated problem, engineers propose a credential allowing access to all company buckets; this choice would not establish the required storage credential scope 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, engineers propose a credential allowing access to all company buckets; this choice would not establish the required storage credential scope decision.