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

Query supported expectation metric records in the event log. This implement 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, invalid rows currently reach downstream aggregates; this choice would not establish the required expectation drop action decision.

Change to a left join and explicitly handle missing dimension fields. This implement 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.

Use MERGE with matched update and not-matched insert branches. This implement action addresses a different case (cdc merge semantics), where the current INSERT-only target contains duplicate customer keys. A keyed Delta MERGE can update existing rows and insert new keys. In the stated problem, invalid rows currently reach downstream aggregates; this choice would not establish the required expectation drop action decision.

Use group-based least-privilege workspace object permissions. This design 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.

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, deleting a row from only the gold table leaves copies elsewhere; this choice would not establish the required data subject request decision.

Publish a minimal secure view with only approved attributes. This design 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, deleting a row from only the gold table leaves copies elsewhere; this choice would not establish the required data subject request decision.

Define validated region and catalog parameters for each invocation. This design 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, each dashboard query recomputes the same expensive aggregation; this choice would not establish the required materialized view choice decision.

Defer expensive materialization until the required action. This design action addresses a different case (spark lazy evaluation), where engineers assume an intermediate filter executed before any action. Spark transformations are lazy until an action triggers a job. In the stated problem, each dashboard query recomputes the same expensive aggregation; this choice would not establish the required materialized view choice decision.

Choose a return type and null-handling contract matching the output. This design action addresses a different case (udf return schema), where returned values cannot be converted to the declared Spark return type. Pandas UDF return values must conform to the declared Spark data type. In the stated problem, each dashboard query recomputes the same expensive aggregation; this choice would not establish the required materialized view choice 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, the proposed maintenance script also runs ZORDER on that clustered table; this choice would not establish the required clustering versus zorder decision.

Benchmark light and heavy runs to verify runtime and cost objectives. This validate 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 proposed maintenance script also runs ZORDER on that clustered table; this choice would not establish the required clustering versus zorder decision.

Run small and large test inputs and compare execution strategies. This validate 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 proposed maintenance script also runs ZORDER on that clustered table; this choice would not establish the required clustering versus zorder decision.

Inspect query history for SQL text identity, duration and warehouse. This diagnose action addresses a different case (sql query history), where no baseline is available for the warehouse query execution. Query history/system query records support comparison of execution time and workload. 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.

Inspect allowed notification-destination types and current run triggers. This diagnose action addresses a different case (job webhook destination), where only personal email notifications are configured. Supported job notification destinations can integrate workflow status with an incident system. 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.

Inspect Query Profile operators for scan volume and pruning. This diagnose 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, the current dashboard has no automated alert for missing units; this choice would not establish the required sql alert threshold 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, operators manually check the run page every morning; this choice would not establish the required job email notification decision.

Cause a safe test failure and confirm exactly one incident is created. This validate action addresses a different case (job webhook destination), where only personal email notifications are configured. Supported job notification destinations can integrate workflow status with an incident system. In the stated problem, operators manually check the run page every morning; this choice would not establish the required job email notification 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, operators manually check the run page every morning; this choice would not establish the required job email notification decision.

Inspect per-task shuffle read bytes and spilled data. This diagnose 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, provisioning overhead exceeds useful task execution time; this choice would not establish the required serverless job fit decision.

Inspect task skew and key-frequency histograms. This diagnose 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, provisioning overhead exceeds useful task execution time; this choice would not establish the required serverless job fit decision.

Inspect repeated lineage and memory availability for the reference data. This diagnose action addresses a different case (cache reuse), where repeated recomputation dominates each branch's execution. Persistence can avoid repeated work if reused data fits the memory budget. In the stated problem, provisioning overhead exceeds useful task execution time; this choice would not establish the required serverless job fit decision.

Grant only required read privileges on the external location. This implement action addresses a different case (storage credential scope), where engineers propose a credential allowing access to all company buckets. Unity Catalog storage credentials and external locations can constrain storage access. In the stated problem, a Unity Catalog table grant does not restrict web-console network entry; this choice would not establish the required ip-based workspace restrictions decision.

Remove overly broad edit access and grant view permission to readers. This implement 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 Unity Catalog table grant does not restrict web-console network entry; this choice would not establish the required ip-based workspace restrictions decision.

Revoke unnecessary production ownership and grant task-specific roles. This implement 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 Unity Catalog table grant does not restrict web-console network entry; this choice would not establish the required ip-based workspace restrictions 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, development job arguments were deployed into the production target; this choice would not establish the required bundle target overrides decision.

Run two regional jobs with distinct parameters and compare target outputs. This validate 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, development job arguments were deployed into the production target; this choice would not establish the required bundle target overrides decision.

Reverse input arrival order and verify identical final target state. This validate 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, development job arguments were deployed into the production target; this choice would not establish the required bundle target overrides decision.

Monitor state rows and dropped late-event counts. This monitor 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, a retry of a completed batch produces duplicate sink rows; this choice would not establish the required streaming idempotent sink decision.

Monitor divergence between tested package and deployed code version. This monitor 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, a retry of a completed batch produces duplicate sink rows; this choice would not establish the required streaming idempotent sink decision.

Track right-side duplicate-key rate across loads. This monitor 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, a retry of a completed batch produces duplicate sink rows; this choice would not establish the required streaming idempotent sink decision.

Shuffle source row order and verify the same account record survives. This validate 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.

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

Read old and new records and verify null semantics for the new field. This validate 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.