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

Use a durable steward group as owner rather than a personal principal. This design 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, the data platform cannot apply consistent lifecycle governance; this choice would not establish the required managed storage ownership decision.

Adopt centrally governed classification tags for sensitive assets. This design action addresses a different case (governed tags), where naming conventions alone are inconsistent across teams. Governed tags can classify assets for discovery and policy workflows. In the stated problem, the data platform cannot apply consistent lifecycle governance; this choice would not establish the required managed storage ownership decision.

Use a narrowly scoped external location with a controlled storage credential. This design action addresses a different case (external location governance), where raw cloud permissions bypass central catalog governance. External locations map cloud paths to governed Unity Catalog storage credentials. In the stated problem, the data platform cannot apply consistent lifecycle governance; this choice would not establish the required managed storage ownership decision.

Monitor schema-registry incompatibility and decode failures. This monitor action addresses a different case (avro schema evolution), where an older consumer cannot deserialize records from a newer producer schema. Avro writer-reader schema compatibility must be maintained for evolution. In the stated problem, unknown or mismatched fields disappear during the bronze load; this choice would not establish the required auto loader rescued data decision.

Monitor newly arriving file-schema mismatches. This monitor action addresses a different case (parquet schema mismatch), where a merge step fails after a producer changes an integer field to string. Parquet schema compatibility matters even when column names are unchanged. In the stated problem, unknown or mismatched fields disappear during the bronze load; this choice would not establish the required auto loader rescued data decision.

Monitor unexpected overwrite or delete operations on bronze. This monitor action addresses a different case (append-only delta bronze), where a nightly overwrite accidentally removes historical audit events. Append-only ingestion keeps previous raw records while adding new batches. In the stated problem, unknown or mismatched fields disappear during the bronze load; this choice would not establish the required auto loader rescued data decision.

Monitor direct edits that bypass Git review. This monitor action addresses a different case (git folder collaboration), where there is no controlled code review or rollback history. Databricks Git folders connect workspace development to version control. In the stated problem, deployers have no record of the previous working configuration; this choice would not establish the required rollback deployment decision.

Monitor dependency-related task failure signatures. This monitor 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, deployers have no record of the previous working configuration; this choice would not establish the required rollback deployment decision.

Monitor repeated repairs and remaining downstream failures. This monitor action addresses a different case (repair failed tasks), where operators rerun the entire job and duplicate completed side effects. Repair runs can rerun failed or selected tasks while preserving successful predecessor work under supported semantics. In the stated problem, deployers have no record of the previous working configuration; this choice would not establish the required rollback deployment 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, row-oriented text storage increases scans and transfer volumes; this choice would not establish the required columnar compression decision.

Inspect MERGE condition and target files read. This diagnose 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, row-oriented text storage increases scans and transfer volumes; this choice would not establish the required columnar compression 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, row-oriented text storage increases scans and transfer volumes; this choice would not establish the required columnar compression 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, the pipeline picks an arbitrary record instead of the newest sequence; this choice would not establish the required window latest record decision.

Profile key uniqueness and expected join cardinality on both sides. This diagnose 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, the pipeline picks an arbitrary record instead of the newest sequence; this choice would not establish the required window latest record decision.

Check business keys and sequence fields on source CDC events. This diagnose action addresses a different case (auto cdc keys), where applying events as append-only rows leaves outdated active accounts. AUTO CDC or applicable APPLY CHANGES needs stable keys and sequence ordering for stateful upserts. In the stated problem, the pipeline picks an arbitrary record instead of the newest sequence; this choice would not establish the required window latest record decision.

Inspect catalog BROWSE and SELECT grants for the discovery group. This diagnose 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, naming conventions alone are inconsistent across teams; this choice would not establish the required governed tags decision.

Inspect the schema permission model and current group grants. This diagnose action addresses a different case (schema-level grant inheritance), where analysts must repeatedly request identical SELECT grants for each table. Unity Catalog schema-level privileges can apply to existing and future child objects. In the stated problem, naming conventions alone are inconsistent across teams; this choice would not establish the required governed tags decision.

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, naming conventions alone are inconsistent across teams; this choice would not establish the required governed tags decision.

Alert when active-key uniqueness violations recur. This monitor action addresses a different case (uniqueness quality rule), where an upstream replay creates multiple active versions. An explicit uniqueness check identifies duplicate business keys before serving data. In the stated problem, two events have the same event time and yield different surviving rows; this choice would not establish the required latest-per-key with ties decision.

Monitor expectation-drop counts and upstream correction rates. This monitor 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, two events have the same event time and yield different surviving rows; this choice would not establish the required latest-per-key with ties decision.

Monitor invalid timezone offsets and parsing errors. This monitor action addresses a different case (timestamp timezone normalization), where events from different regions are ordered incorrectly in a UTC dashboard. Time-zone normalization is required before comparing timestamps from different sources. In the stated problem, two events have the same event time and yield different surviving rows; this choice would not establish the required latest-per-key with ties 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, a query wraps business_date in a transformation and reads many partitions; this choice would not establish the required partition pruning 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, a query wraps business_date in a transformation and reads many partitions; this choice would not establish the required partition pruning decision.

Inspect MERGE condition and target files read. This diagnose 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, a query wraps business_date in a transformation and reads many partitions; this choice would not establish the required partition pruning 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, operators assume the query is always CPU-bound; this choice would not establish the required query profile scans 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, operators assume the query is always CPU-bound; this choice would not establish the required query profile scans 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, operators assume the query is always CPU-bound; this choice would not establish the required query profile scans 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, logs expose PII to broader operations readers; this choice would not establish the required restricted event logging 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, logs expose PII to broader operations readers; this choice would not establish the required restricted event logging 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, logs expose PII to broader operations readers; this choice would not establish the required restricted event logging 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, periodic full-refresh queries miss required incremental freshness; this choice would not establish the required streaming table choice decision.

Design a keyed CDC target using a reliable sequence and delete handling. This design action addresses a different case (auto cdc keys), where applying events as append-only rows leaves outdated active accounts. AUTO CDC or applicable APPLY CHANGES needs stable keys and sequence ordering for stateful upserts. In the stated problem, periodic full-refresh queries miss required incremental freshness; this choice would not establish the required streaming table choice decision.

Use a managed service principal with only required production privileges. This design 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, periodic full-refresh queries miss required incremental freshness; this choice would not establish the required streaming table choice decision.