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

Inspect ownership and grant-management privileges in production. This diagnose 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, granting SELECT on the raw fact table violates minimization; this choice would not establish the required secure view sharing decision.

Inspect sensitive-column policy and current grants. This diagnose 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, granting SELECT on the raw fact table violates minimization; this choice would not establish the required secure view sharing decision.

Inspect the approved export schema against current selected columns. This diagnose 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, granting SELECT on the raw fact table violates minimization; this choice would not establish the required secure view sharing decision.

Monitor optimization operations and cost savings. This monitor 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, manual clustering keys quickly become stale; this choice would not establish the required automatic clustering decision.

Monitor plans that lose partition pruning. This monitor 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, manual clustering keys quickly become stale; this choice would not establish the required automatic clustering decision.

Monitor reintroduction of incompatible maintenance commands. This monitor action addresses a different case (clustering versus zorder), where the proposed maintenance script also runs ZORDER on that clustered table. Liquid clustering is incompatible with concurrently applying ZORDER to the same table. In the stated problem, manual clustering keys quickly become stale; this choice would not establish the required automatic clustering decision.

Find the expected schema error and confirm it disappears after correction. This validate 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, no baseline is available for the warehouse query execution; this choice would not establish the required sql query history decision.

Confirm the profile scans fewer files with correct result rows. This validate action addresses a different case (query profile scans), where operators assume the query is always CPU-bound. Query Profile identifies scan, pruning and shuffle behavior for SQL workloads. In the stated problem, no baseline is available for the warehouse query execution; this choice would not establish the required sql query history 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, no baseline is available for the warehouse query execution; this choice would not establish the required sql query history decision.

Compare outputs on edge cases and measure stage time on representative data. This validate action addresses a different case (vectorized udf), where row-by-row Python invocation dominates stage runtime. Pandas UDFs process batches through Arrow rather than per-row Python calls. In the stated problem, an API token is committed in a Python notebook tracked in Git; this choice would not establish the required secure configuration decision.

Run the same function in a unit test and in a production job. This validate 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, an API token is committed in a Python notebook tracked in Git; this choice would not establish the required secure configuration decision.

Force a retry and verify no duplicated sink rows. This validate 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, an API token is committed in a Python notebook tracked in Git; this choice would not establish the required secure configuration decision.

Compare production deployment variables with bundle target overrides. This diagnose 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, scattered print statements do not reveal the failing object shape; this choice would not establish the required notebook debugger decision.

Compare deployed job JSON with the version-controlled bundle. This diagnose action addresses a different case (databricks cli resource updates), where production configuration drifts from repository source definitions. Declarative deployment describes resources as reviewed version-controlled artifacts. In the stated problem, scattered print statements do not reveal the failing object shape; this choice would not establish the required notebook debugger decision.

Check ordering and duplicate keys in the source window specification. This diagnose action addresses a different case (window latest record), where the pipeline picks an arbitrary record instead of the newest sequence. ROW_NUMBER ordered by a deterministic sequence within each key selects the desired latest row. In the stated problem, scattered print statements do not reveal the failing object shape; this choice would not establish the required notebook debugger decision.

Inspect Python UDF execution time and batch serialization in Spark UI. This diagnose action addresses a different case (vectorized udf), where row-by-row Python invocation dominates stage runtime. Pandas UDFs process batches through Arrow rather than per-row Python calls. In the stated problem, old keys remain in state indefinitely without a lateness bound; this choice would not establish the required event-time watermarking decision.

Inspect external target keys and batch IDs after failed attempts. This diagnose 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, old keys remain in state indefinitely without a lateness bound; this choice would not establish the required event-time watermarking decision.

Inspect target history columns and CDC sequence ordering. This diagnose 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, old keys remain in state indefinitely without a lateness bound; this choice would not establish the required event-time watermarking decision.

Update foreachBatch to upsert by business key with batch idempotency. This implement 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, an API token is committed in a Python notebook tracked in Git; this choice would not establish the required secure configuration decision.

Replace the Python UDF with Spark SQL built-in functions. This implement action addresses a different case (avoid python udf for sql), where the Python UDF creates an avoidable cross-language execution boundary. Built-in Spark SQL functions can execute in optimized expressions without Python UDF overhead. In the stated problem, an API token is committed in a Python notebook tracked in Git; this choice would not establish the required secure configuration decision.

Compose transformations with DataFrame.transform and explicit configuration. This implement 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, an API token is committed in a Python notebook tracked in Git; this choice would not establish the required secure configuration decision.

Monitor new per-key ordering collisions. This monitor 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, applying events as append-only rows leaves outdated active accounts; this choice would not establish the required auto cdc keys decision.

Detect unmanaged changes to deployed job resources. This monitor action addresses a different case (databricks cli resource updates), where production configuration drifts from repository source definitions. Declarative deployment describes resources as reviewed version-controlled artifacts. In the stated problem, applying events as append-only rows leaves outdated active accounts; this choice would not establish the required auto cdc keys decision.

Audit access to the secret scope and changes to job identity. This monitor action addresses a different case (secure configuration), where an API token is committed in a Python notebook tracked in Git. Secret-backed configuration avoids embedding credentials in notebooks or deployment YAML. In the stated problem, applying events as append-only rows leaves outdated active accounts; this choice would not establish the required auto cdc keys decision.

Monitor recurring task skew in scheduled workloads. This monitor action addresses a different case (spark ui shuffle metrics), where operators only monitor cluster-wide CPU and miss skewed task durations. Spark UI stage metrics reveal shuffle, spill and task skew. In the stated problem, scheduled updates are spaced several hours apart; this choice would not establish the required pipeline update cadence decision.

Monitor missed notification deliveries against failed runs. This monitor 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, scheduled updates are spaced several hours apart; this choice would not establish the required pipeline update cadence decision.

Monitor offset lag and microbatch processing percentiles. This monitor action addresses a different case (streaming backlog), where consumer lag grows while microbatch intervals appear stable. Backlog growth reveals insufficient sustainable processing throughput. In the stated problem, scheduled updates are spaced several hours apart; this choice would not establish the required pipeline update cadence 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, invalid rows currently reach downstream aggregates; this choice would not establish the required expectation drop action decision.

Check valid decimal values and quarantined invalid strings. This validate action addresses a different case (silver schema enforcement), where implicit type coercion risks invalid numeric values being stored. Schema validation and explicit casts make type conversion failures observable. In the stated problem, invalid rows currently reach downstream aggregates; this choice would not establish the required expectation drop action decision.

Count retained fact rows and confirm null-key records are represented. This validate 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, invalid rows currently reach downstream aggregates; this choice would not establish the required expectation drop action decision.

Compare notebook and cluster package versions and import origins. This diagnose 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.

Compare job parameter definitions to hard-coded notebook literals. This diagnose action addresses a different case (job parameters), where code contains hard-coded region IDs and catalog names. Task parameters allow runtime-specific values without changing notebook source. In the stated problem, business logic depends on notebook state and widgets; this choice would not establish the required transform composability decision.

Compare production deployment variables with bundle target overrides. This diagnose 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, business logic depends on notebook state and widgets; this choice would not establish the required transform composability decision.