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

Inspect current owner and authorized ownership transfer process. This diagnose action addresses a different case (ownership reassignment), where new data stewards cannot maintain its grants. Unity Catalog ownership should be assigned to a maintained principal. In the stated problem, investigators cannot tell which upstream transformation produced it; this choice would not establish the required lineage tracking decision.

Inspect asset comments and ownership for critical reporting tables. This diagnose action addresses a different case (catalog descriptions), where table and column metadata lack meaningful descriptions. Unity Catalog comments improve discoverability of governed data assets. In the stated problem, investigators cannot tell which upstream transformation produced it; this choice would not establish the required lineage tracking decision.

Inspect catalog and schema managed-location settings. This diagnose 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, investigators cannot tell which upstream transformation produced it; this choice would not establish the required lineage tracking decision.

Attach a supported mask function to the email column. This implement 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.

Create the aggregation view and grant SELECT only on the view. This implement action addresses a different case (secure view sharing), where granting SELECT on the raw fact table violates minimization. A governed aggregation view can expose only approved derived information. In the stated problem, a broad SELECT still includes unstructured notes; this choice would not establish the required sensitive data suppression decision.

Change the job run-as principal and validate the required data permissions. This implement 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.

Use TRY_CAST or equivalent safe conversion before writing the typed target. This implement 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, a plain dropDuplicates retains state without a practical bound for never-ending keys; this choice would not establish the required streaming dedup watermark decision.

Add a supported expectation with ON VIOLATION DROP ROW to the dataset definition. This implement 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, a plain dropDuplicates retains state without a practical bound for never-ending keys; this choice would not establish the required streaming dedup watermark decision.

Declare a supported fail-on-violation expectation for the required field. This implement 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, a plain dropDuplicates retains state without a practical bound for never-ending keys; this choice would not establish the required streaming dedup watermark decision.

Create the materialized view and configure its supported refresh schedule. This implement 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, a newly selected checkpoint location makes the stream reread historical input; this choice would not establish the required streaming checkpoint identity decision.

Assign the approved run-as identity and reconfigure required grants. This implement action addresses a different case (job run-as identity), where an employee departure causes permissions failures during scheduled runs. A stable least-privilege service principal can provide durable job identity. In the stated problem, a newly selected checkpoint location makes the stream reread historical input; this choice would not establish the required streaming checkpoint identity 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, a newly selected checkpoint location makes the stream reread historical input; this choice would not establish the required streaming checkpoint identity decision.

Define a stable fingerprint and runtime baseline for the query. This design 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.

Create a historical failure and runtime dashboard by workflow. This design 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, the current dashboard has no automated alert for missing units; this choice would not establish the required sql alert threshold decision.

Define freshness SLO based on end-to-end observed lag. This design 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, the current dashboard has no automated alert for missing units; this choice would not establish the required sql alert threshold decision.

Inspect event-time distribution and state-store growth. This diagnose 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, overwrite-style updates destroy historical state needed for point-in-time reporting; this choice would not establish the required scd type 2 history decision.

Inspect per-key sequence collisions and upstream log offsets. This diagnose 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, overwrite-style updates destroy historical state needed for point-in-time reporting; this choice would not establish the required scd type 2 history 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, overwrite-style updates destroy historical state needed for point-in-time reporting; this choice would not establish the required scd type 2 history decision.

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, a shared table currently returns all regions to every reader; this choice would not establish the required unity catalog row filter decision.

Inspect job identity and the effective catalog privileges it can use. This diagnose 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 shared table currently returns all regions to every reader; this choice would not establish the required unity catalog row filter decision.

Inspect current workspace network access controls and identity sign-in rules. This diagnose action addresses a different case (ip-based workspace restrictions), where a Unity Catalog table grant does not restrict web-console network entry. Workspace access controls and data-object privileges address different security layers. 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.

Create the managed table under the approved catalog and migrate governed data. This implement action addresses a different case (managed table maintenance), where each table has custom file cleanup jobs and broad storage permissions. Unity Catalog managed tables provide platform-managed data placement and maintenance capabilities. In the stated problem, repeated recomputation dominates each branch's execution; this choice would not establish the required cache reuse decision.

Configure appropriate stats columns and recompute statistics as required. This implement 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, repeated recomputation dominates each branch's execution; this choice would not establish the required cache reuse decision.

Enable Photon on the selected supported warehouse or compute. This implement action addresses a different case (photon query execution), where an unsupported execution mode limits vectorized engine use. Photon can accelerate supported SQL and DataFrame operators on compatible compute. In the stated problem, repeated recomputation dominates each branch's execution; this choice would not establish the required cache reuse 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, reports silently discard legitimate late events under an aggressive watermark; this choice would not establish the required late event semantics 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, reports silently discard legitimate late events under an aggressive watermark; this choice would not establish the required late event semantics decision.

Cast returned values consistently and update the UDF schema declaration. This implement 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, reports silently discard legitimate late events under an aggressive watermark; this choice would not establish the required late event semantics decision.

Confirm live settings match repository after redeployment. This validate action addresses a different case (unmanaged resource drift), where subsequent CI redeployment unexpectedly overwrites it. Declarative source of truth should include intentional job-resource changes. In the stated problem, an invalid resource key would be rejected only after production change; this choice would not establish the required bundle validation decision.

Rotate the human token and verify CI deployment still authenticates. This validate 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, an invalid resource key would be rejected only after production change; this choice would not establish the required bundle validation 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, an invalid resource key would be rejected only after production change; this choice would not establish the required bundle validation decision.

Monitor malformed CSV rows and supplier format drift. This monitor action addresses a different case (malformed csv quotes), where an ingestion reader splits quoted names into extra columns. CSV quoting and escape configurations must match the source serialization. In the stated problem, a partially processed input file is loaded twice into Delta; this choice would not establish the required retry-safe file loads decision.

Monitor missing child-element and parser error counts. This monitor action addresses a different case (xml repeating elements), where an XML ingest incorrectly flattens multiple line items into one text field. XML ingestion must specify the repeating row element and preserve nested structure. In the stated problem, a partially processed input file is loaded twice into Delta; this choice would not establish the required retry-safe file loads decision.

Monitor discovered-file backlog and ingestion freshness. This monitor action addresses a different case (auto loader file discovery), where listing the full historical directory every run exceeds the ingestion SLA. Auto Loader is designed for incremental new-file discovery with persisted state. In the stated problem, a partially processed input file is loaded twice into Delta; this choice would not establish the required retry-safe file loads decision.