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

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.

Permit metadata discovery while requiring separate approvals for SELECT. This design action addresses a different case (browse metadata privilege), where teams grant SELECT merely to expose object listings. BROWSE enables controlled metadata discovery without granting data read access. In the stated problem, it uses notebook-specific private metadata APIs that break after upgrades; this choice would not establish the required information schema discovery decision.

Define a metadata quality standard for business purpose, grain and sensitivity. This design 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, it uses notebook-specific private metadata APIs that break after upgrades; this choice would not establish the required information schema discovery decision.

Grant parent usage plus specific SELECT rather than broad ownership. This design action addresses a different case (catalog privilege inheritance), where the team lacks USE CATALOG and USE SCHEMA on the parent containers. Unity Catalog object access generally requires relevant parent usage privileges. In the stated problem, it uses notebook-specific private metadata APIs that break after upgrades; this choice would not establish the required information schema discovery 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, the hard-coded service password has not rotated for a year; this choice would not establish the required credential rotation procedure decision.

Inspect log statements and secret retrieval paths without revealing values. This diagnose action addresses a different case (secret retrieval logs), where databricks notebook redaction is incorrectly treated as a comprehensive security control. Secrets should never be deliberately printed or put in logs, regardless of redaction behavior. In the stated problem, the hard-coded service password has not rotated for a year; this choice would not establish the required credential rotation procedure decision.

Inspect consumer business need and raw table grants. This diagnose 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, the hard-coded service password has not rotated for a year; this choice would not establish the required credential rotation procedure decision.

Model repeated child elements as arrays or separate normalized child records. This design 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 line-oriented text reader corrupts the raw binary payload; this choice would not establish the required binary payload metadata decision.

Use a governed nested schema contract with an approved evolution policy. This design action addresses a different case (nested json ingest), where the initial reader assumes one unchanging flat schema and loses new fields. Explicit schema management and rescued data handling protect evolving semi-structured ingestion. In the stated problem, a line-oriented text reader corrupts the raw binary payload; this choice would not establish the required binary payload metadata decision.

Retain the raw payload and a rescued-data route before silver validation. This design action addresses a different case (auto loader rescued data), where unknown or mismatched fields disappear during the bronze load. The rescued data column can preserve records with unexpected schema content for later remediation. In the stated problem, a line-oriented text reader corrupts the raw binary payload; this choice would not establish the required binary payload metadata decision.

Choose approved managed storage locations for governed tables. This design 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, new data stewards cannot maintain its grants; this choice would not establish the required ownership reassignment decision.

Grant parent usage plus specific SELECT rather than broad ownership. This design action addresses a different case (catalog privilege inheritance), where the team lacks USE CATALOG and USE SCHEMA on the parent containers. Unity Catalog object access generally requires relevant parent usage privileges. In the stated problem, new data stewards cannot maintain its grants; this choice would not establish the required ownership reassignment decision.

Use lineage alongside data-quality checks to trace source-to-output transformations. This design action addresses a different case (lineage tracking), where investigators cannot tell which upstream transformation produced it. Unity Catalog lineage records relationships between governed data assets. In the stated problem, new data stewards cannot maintain its grants; this choice would not establish the required ownership reassignment decision.

Query jobs system tables with appropriate retention-aware time filters. This implement 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, operators only monitor cluster-wide CPU and miss skewed task durations; this choice would not establish the required spark ui shuffle metrics decision.

Capture supported query-history metrics in a restricted view. This implement 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, operators only monitor cluster-wide CPU and miss skewed task durations; this choice would not establish the required spark ui shuffle metrics 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, operators only monitor cluster-wide CPU and miss skewed task durations; this choice would not establish the required spark ui shuffle metrics 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, manual clustering keys quickly become stale; this choice would not establish the required automatic clustering 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, manual clustering keys quickly become stale; this choice would not establish the required automatic clustering 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, manual clustering keys quickly become stale; this choice would not establish the required automatic clustering decision.

Replay a batch ID and confirm target rows are not duplicated. This validate 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, the wheel works on a developer laptop but fails with a binary compatibility error; this choice would not establish the required wheel abi compatibility decision.

Deploy the same revision to test and staging using distinct bundle targets. This validate action addresses a different case (bundle repository layout), where source files and deployment definitions are coupled to one developer workspace. A versioned Declarative Automation Bundle defines code and resource configurations separately from the target workspace. In the stated problem, the wheel works on a developer laptop but fails with a binary compatibility error; this choice would not establish the required wheel abi compatibility 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, the wheel works on a developer laptop but fails with a binary compatibility error; this choice would not establish the required wheel abi compatibility decision.

Inspect current table features, delete patterns and runtime compatibility. This diagnose action addresses a different case (deletion vectors), where each small delete rewrites large data files and increases write cost. Deletion vectors can mark deleted rows without immediate whole-file rewrite when supported. In the stated problem, manual clustering keys quickly become stale; this choice would not establish the required automatic clustering decision.

Inspect existing clustering metadata and OPTIMIZE commands. This diagnose 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.

Inspect managed table eligibility and current optimization settings. This diagnose 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.

Inspect the remote query plan and filter pushdown support. This diagnose action addresses a different case (federated pushdown), where an analyst pulls millions of rows before a selective filter. Supported predicate pushdown can reduce data transferred from a federated source. In the stated problem, consumers assume the share is a nightly static export; this choice would not establish the required shared table freshness decision.

Inspect share contents and approved sharing manifest. This diagnose action addresses a different case (share catalog scope), where the recipient can discover unintended datasets. A Delta Sharing share should contain only explicitly approved assets. In the stated problem, consumers assume the share is a nightly static export; this choice would not establish the required shared table freshness decision.

Inspect intended recipient identity and existing share membership. This diagnose 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, consumers assume the share is a nightly static export; this choice would not establish the required shared table freshness decision.

Inspect pipeline event log update IDs and error messages. This diagnose 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, operators rerun the entire job and duplicate completed side effects; this choice would not establish the required repair failed tasks decision.

Inspect executor stderr and driver logs near the failed stage. This diagnose 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, operators rerun the entire job and duplicate completed side effects; this choice would not establish the required repair failed tasks 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, operators rerun the entire job and duplicate completed side effects; this choice would not establish the required repair failed tasks decision.