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

Plan an additive nullable dimension attribute with documented defaults. This design action addresses a different case (dimension evolution), where a destructive table recreation would invalidate downstream consumers. Additive schema evolution can preserve contracts when null defaults are acceptable. In the stated problem, interactive queries scan billions of detail rows for identical totals; this choice would not establish the required aggregate gold model decision.

Choose one order-line grain for transaction detail metrics. This design action addresses a different case (fact table grain), where summing revenue double-counts orders with multiple items. A dimensional fact must have one clearly documented row grain. In the stated problem, interactive queries scan billions of detail rows for identical totals; this choice would not establish the required aggregate gold model decision.

Design a customer-plan bridge with valid membership periods. This design action addresses a different case (many-to-many bridge), where joining facts directly to the membership table multiplies totals. A bridge table models many-to-many relationships at an explicit membership grain. In the stated problem, interactive queries scan billions of detail rows for identical totals; this choice would not establish the required aggregate gold model decision.

Confirm dashboard results refresh after source data updates. This validate 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, periodic full-refresh queries miss required incremental freshness; this choice would not establish the required streaming table choice decision.

Replay update and delete events and confirm one accurate current row per key. This validate 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.

Restart and confirm previously committed input is not reprocessed unexpectedly. This validate action addresses a different case (streaming checkpoint identity), where a newly selected checkpoint location makes the stream reread historical input. Streaming checkpoint metadata records progress and state for restart continuity. In the stated problem, periodic full-refresh queries miss required incremental freshness; this choice would not establish the required streaming table choice decision.

Enforce one active record per key with deterministic conflict rules. This design 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, the silver writer rejects every new record after the upstream schema change; this choice would not establish the required controlled schema evolution decision.

Use drop semantics only when invalid records may be excluded by policy. This design 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, the silver writer rejects every new record after the upstream schema change; this choice would not establish the required controlled schema evolution decision.

Separate valid silver rows from a restricted quarantine table. This design 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, the silver writer rejects every new record after the upstream schema change; this choice would not establish the required controlled schema evolution decision.

Inspect runtime support and predictive optimization status. This diagnose action addresses a different case (automatic clustering), where manual clustering keys quickly become stale. Automatic liquid clustering can select keys using query workload when platform prerequisites are met. 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 filters, cardinalities and existing partition layout. This diagnose 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, the proposed maintenance script also runs ZORDER on that clustered table; this choice would not establish the required clustering versus zorder 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, the proposed maintenance script also runs ZORDER on that clustered table; this choice would not establish the required clustering versus zorder decision.

Parse a quoted comma and confirm original column boundaries are preserved. This validate 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, an XML ingest incorrectly flattens multiple line items into one text field; this choice would not establish the required xml repeating elements decision.

Ingest an unknown field and confirm it is retained for triage. This validate 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, an XML ingest incorrectly flattens multiple line items into one text field; this choice would not establish the required xml repeating elements decision.

Compare output content length and checksum to the original object. This validate action addresses a different case (binary payload metadata), where a line-oriented text reader corrupts the raw binary payload. binaryFile input preserves raw file bytes and path metadata rather than decoding lines. In the stated problem, an XML ingest incorrectly flattens multiple line items into one text field; this choice would not establish the required xml repeating elements 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, the Python UDF creates an avoidable cross-language execution boundary; this choice would not establish the required avoid python udf for sql 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 Python UDF creates an avoidable cross-language execution boundary; this choice would not establish the required avoid python udf for sql decision.

Verify the job authenticates without the token appearing in code or logs. This validate 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, the Python UDF creates an avoidable cross-language execution boundary; this choice would not establish the required avoid python udf for sql decision.

Create separate dashboards for rejected data and failed pipeline updates. This design 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, a single campaign dominates rows and one reduce task runs for minutes; this choice would not establish the required skewed group aggregation decision.

Model a one-to-many child table at order_id plus item position grain. This design action addresses a different case (array explosion), where an order-level aggregation mistakenly treats the array as a single item. explode creates item-level rows when the business grain requires each array element. In the stated problem, a single campaign dominates rows and one reduce task runs for minutes; this choice would not establish the required skewed group aggregation decision.

Define a reviewable additive-column evolution policy. This design 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, a single campaign dominates rows and one reduce task runs for minutes; this choice would not establish the required skewed group aggregation 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, an operator proposes aggressive VACUUM retention during active long-running readers; this choice would not establish the required vacuum retention safety decision.

Inspect watermark, state operator metrics and checkpoint size. This diagnose action addresses a different case (streaming state growth), where executor memory pressure grows even though input rate is stable. State retention and checkpoint state-store configuration affect memory requirements. In the stated problem, an operator proposes aggressive VACUUM retention during active long-running readers; this choice would not establish the required vacuum retention safety 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, an operator proposes aggressive VACUUM retention during active long-running readers; this choice would not establish the required vacuum retention safety decision.

Build and attach the published wheel and update the job's library reference. This implement action addresses a different case (python wheel packaging), where a refactor broke a notebook-relative import in the deployed job. A properly packaged versioned wheel gives Python code stable import paths outside notebooks. In the stated problem, a transitive dependency updated to an incompatible version; this choice would not establish the required library version pinning decision.

Move task source under version control and declare jobs or pipelines in bundle resources. This implement 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, a transitive dependency updated to an incompatible version; this choice would not establish the required library version pinning decision.

Remove conflicting notebook installation and attach the tested library version. This implement 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, a transitive dependency updated to an incompatible version; this choice would not establish the required library version pinning 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, each table has custom file cleanup jobs and broad storage permissions; this choice would not establish the required managed table maintenance decision.

Inspect table stats collection and skipped-file counts. This diagnose 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, each table has custom file cleanup jobs and broad storage permissions; this choice would not establish the required managed table maintenance 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, each table has custom file cleanup jobs and broad storage permissions; this choice would not establish the required managed table maintenance decision.

Monitor library compatibility on future runtime upgrades. This monitor action addresses a different case (python dependency triage), where a package import error appears only on the target compute. Runtime-specific wheel compatibility and pinning must be tested in CI. In the stated problem, re-running a huge source in development is slow and risky; this choice would not establish the required pipeline debug sampling decision.

Monitor pipeline error events by dataset and update. This monitor 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, re-running a huge source in development is slow and risky; this choice would not establish the required pipeline debug sampling decision.

Audit repeated authorization errors and new broad grants. This monitor 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, re-running a huge source in development is slow and risky; this choice would not establish the required pipeline debug sampling decision.