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

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, the current partition count is too low for data volume; this choice would not establish the required shuffle partition count 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, the current partition count is too low for data volume; this choice would not establish the required shuffle partition count decision.

Enable or tune adaptive features without disabling correctness checks. This implement 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, the current partition count is too low for data volume; this choice would not establish the required shuffle partition count decision.

Compare scanned files before and after on the same date predicate. This validate action addresses a different case (data skipping statistics), where file-level statistics are missing for the filter column. Delta data skipping uses collected column statistics to eliminate files. In the stated problem, the merge scans unrelated historical partitions; this choice would not establish the required predicate-limited merge 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, the merge scans unrelated historical partitions; this choice would not establish the required predicate-limited merge decision.

Compare file count and query result checksums before and after. This validate 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, the merge scans unrelated historical partitions; this choice would not establish the required predicate-limited merge decision.

Deploy the previous approved bundle revision with correct target. This implement 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, a package import error appears only on the target compute; this choice would not establish the required python dependency triage decision.

Correct the missing dependency or incompatible runtime package. This implement 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.

Run databricks bundle validate for the intended target in CI. This implement 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, a package import error appears only on the target compute; this choice would not establish the required python dependency triage decision.

Compare run results, startup latency and billed usage. This validate action addresses a different case (serverless job fit), where provisioning overhead exceeds useful task execution time. Supported serverless jobs can reduce infrastructure management and startup overhead. 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.

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, an operator proposes aggressive VACUUM retention during active long-running readers; this choice would not establish the required vacuum retention safety decision.

Confirm maintenance activity occurs on appropriate tables without duplicate jobs. This validate action addresses a different case (predictive optimization), where operators run blanket manual OPTIMIZE jobs regardless of table use. Predictive optimization can automate supported managed-table maintenance based on workload signals. 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.

Query the export view and confirm prohibited fields are absent. This validate action addresses a different case (sensitive data suppression), where a broad SELECT still includes unstructured notes. Column suppression and data minimization prevent unnecessary sensitive-field release. In the stated problem, a shared table currently returns all regions to every reader; this choice would not establish the required unity catalog row filter 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, a shared table currently returns all regions to every reader; this choice would not establish the required unity catalog row filter 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, a shared table currently returns all regions to every reader; this choice would not establish the required unity catalog row filter decision.

Inspect the streaming table definition and expectation violation counts. This diagnose 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, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records 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, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records decision.

Inspect existing expectation rules and failed-update event details. This diagnose 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, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records 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, a package import error appears only on the target compute; this choice would not establish the required python dependency triage 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, a package import error appears only on the target compute; this choice would not establish the required python dependency triage 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, a package import error appears only on the target compute; this choice would not establish the required python dependency triage decision.

Query supported billing system tables and join approved usage metadata. This implement action addresses a different case (billing usage monitoring), where cost reports omit some job and workspace labels. Databricks system billing tables can expose usage records for cost attribution. In the stated problem, the current dashboard has no automated alert for missing units; this choice would not establish the required sql alert threshold decision.

Set the supported job notification destination for failed runs. This implement 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, the current dashboard has no automated alert for missing units; this choice would not establish the required sql alert threshold decision.

Configure pipeline update scheduling based on the freshness requirement. This implement action addresses a different case (pipeline update cadence), where scheduled updates are spaced several hours apart. Pipeline update frequency determines available end-to-end freshness. In the stated problem, the current dashboard has no automated alert for missing units; this choice would not establish the required sql alert threshold decision.

Observe silver tasks start after bronze succeeds and run concurrently where eligible. This validate 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, engineers assume an intermediate filter executed before any action; this choice would not establish the required spark lazy evaluation decision.

Simulate passing and failing checks and verify only the intended path runs. This validate 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, engineers assume an intermediate filter executed before any action; this choice would not establish the required spark lazy evaluation decision.

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, engineers assume an intermediate filter executed before any action; this choice would not establish the required spark lazy evaluation decision.

Assign a dedicated production service principal with only required grants. This design action addresses a different case (service principal access), where the individual's credentials create unnecessary privilege and lifecycle risk. Production automation should use least-privilege service principals for stable identity. In the stated problem, a broad SELECT still includes unstructured notes; this choice would not establish the required sensitive data suppression decision.

Apply a governed column mask while preserving needed analytic access. This design 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, a broad SELECT still includes unstructured notes; this choice would not establish the required sensitive data suppression decision.

Use a row filter keyed to approved region mapping. This design 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.

Create a share, authorize the recipient and attach the approved tables. This implement action addresses a different case (d2d managed recipient), where a recipient team copies files manually and loses timely updates. Databricks-to-Databricks Delta Sharing supports governed live access without manual copying. In the stated problem, an analyst pulls millions of rows before a selective filter; this choice would not establish the required federated pushdown decision.

Apply minimal catalog, schema and table grants for the analyst. This implement 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, an analyst pulls millions of rows before a selective filter; this choice would not establish the required federated pushdown decision.

Configure the share without building redundant daily copy pipelines. This implement 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, an analyst pulls millions of rows before a selective filter; this choice would not establish the required federated pushdown decision.