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

Configure cloudFiles ingestion into a Delta bronze streaming table. This implement 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, an XML ingest incorrectly flattens multiple line items into one text field; this choice would not establish the required xml repeating elements decision.

Configure CSV quote/escape and malformed-record capture. This implement 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.

Configure the Kafka stream and persistent checkpoint path. This implement action addresses a different case (kafka offset durability), where restarting with a fresh checkpoint replays previously ingested messages. A stable streaming checkpoint maintains Kafka offsets and sink progress across restarts. 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, a merge step fails after a producer changes an integer field to string; this choice would not establish the required parquet schema mismatch decision.

Ingest old and new samples and verify nested fields and rescued data are retained. This validate 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 merge step fails after a producer changes an integer field to string; this choice would not establish the required parquet schema mismatch decision.

Deserialize old and new messages with the intended projection. This validate 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, a merge step fails after a producer changes an integer field to string; this choice would not establish the required parquet schema mismatch decision.

Detect unmanaged changes to deployed job resources. This monitor action addresses a different case (databricks cli resource updates), where production configuration drifts from repository source definitions. Declarative deployment describes resources as reviewed version-controlled artifacts. In the stated problem, source files and deployment definitions are coupled to one developer workspace; this choice would not establish the required bundle repository layout decision.

Compare installed wheel versions with the CI release manifest. This monitor 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, source files and deployment definitions are coupled to one developer workspace; this choice would not establish the required bundle repository layout decision.

Audit access to the secret scope and changes to job identity. This monitor 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, source files and deployment definitions are coupled to one developer workspace; this choice would not establish the required bundle repository layout 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, the consumer reads only newly appended rows and cannot see updates or deletes; this choice would not establish the required change data feed consumers decision.

Rewrite filtering so business_date is compared directly where semantics allow. This implement action addresses a different case (partition pruning), where a query wraps business_date in a transformation and reads many partitions. Direct predicates on partition keys can enable partition pruning. In the stated problem, the consumer reads only newly appended rows and cannot see updates or deletes; this choice would not establish the required change data feed consumers decision.

Run VACUUM only after verifying the supported retention policy. This implement action addresses a different case (vacuum retention safety), where an operator proposes aggressive VACUUM retention during active long-running readers. VACUUM retention must protect older snapshots still needed by readers and streams. In the stated problem, the consumer reads only newly appended rows and cannot see updates or deletes; this choice would not establish the required change data feed consumers decision.

Inspect dependency graph and upstream task statuses. This diagnose action addresses a different case (job task dag), where dependent tasks sometimes run before the bronze load finishes. Lakeflow Job task dependencies form a directed acyclic execution graph. In the stated problem, the task exits before setting up its argument parser; this choice would not establish the required python task entrypoints decision.

Inspect whether a Spark action was issued and review the execution plan. This diagnose 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, the task exits before setting up its argument parser; this choice would not establish the required python task entrypoints 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, the task exits before setting up its argument parser; this choice would not establish the required python task entrypoints decision.

Write governed Delta/Parquet output with compatible compression settings. This implement action addresses a different case (columnar compression), where row-oriented text storage increases scans and transfer volumes. Columnar formats and appropriate encoding improve analytical read efficiency. In the stated problem, provisioning overhead exceeds useful task execution time; this choice would not establish the required serverless job fit 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, provisioning overhead exceeds useful task execution time; this choice would not establish the required serverless job fit decision.

Create or alter an eligible table with CLUSTER BY for approved keys. This implement 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, provisioning overhead exceeds useful task execution time; this choice would not establish the required serverless job fit decision.

Inspect dashboard queries and the required day-product aggregation grain. This diagnose action addresses a different case (aggregate gold model), where interactive queries scan billions of detail rows for identical totals. A summarized gold table can serve a stable reporting grain efficiently. In the stated problem, a denormalized mixed-grain table produces redundant attributes and expensive corrections; this choice would not establish the required star schema analytics decision.

Inspect dimension history and event order for each account key. This diagnose action addresses a different case (scd type 2 effective dates), where a single current tier overwrites history in the dimension. SCD Type 2 stores effective start/end intervals for distinct historical dimension versions. In the stated problem, a denormalized mixed-grain table produces redundant attributes and expensive corrections; this choice would not establish the required star schema analytics decision.

Inspect country codes and business definitions used by both marts. This diagnose action addresses a different case (conformed dimensions), where the same country appears under conflicting dimension keys across marts. A conformed dimension provides common attribute definitions across fact models. In the stated problem, a denormalized mixed-grain table produces redundant attributes and expensive corrections; this choice would not establish the required star schema analytics decision.

Confirm rows with and without region codes both appear correctly. This validate action addresses a different case (conditional enrichment), where an unconditional inner join discards rows with missing region codes. A left join with explicit CASE logic preserves rows while enriching those that match. In the stated problem, the join triggers a costly shuffle of the large fact dataset; this choice would not establish the required broadcast lookup table decision.

Inject an invalid record and confirm the update fails visibly. This validate 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, the join triggers a costly shuffle of the large fact dataset; this choice would not establish the required broadcast lookup table decision.

Count retained fact rows and confirm null-key records are represented. This validate 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, the join triggers a costly shuffle of the large fact dataset; this choice would not establish the required broadcast lookup table decision.

Detect unexpected package version changes in startup validation. This monitor 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, production configuration drifts from repository source definitions; this choice would not establish the required databricks cli resource updates decision.

Alert when the deployed checkpoint path differs from baseline. This monitor 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, production configuration drifts from repository source definitions; this choice would not establish the required databricks cli resource updates decision.

Alert on unexpected target drift after CI deployments. This monitor 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, production configuration drifts from repository source definitions; this choice would not establish the required databricks cli resource updates decision.

Make writes idempotent before enabling retries. This design action addresses a different case (job retry semantics), where the downstream write repeats non-idempotent side effects on retry. Retries re-execute task logic; application code must protect repeated effects. 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.

Pass nonsecret configuration separately and reference an approved secret store for credentials. This design 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, a retry of a completed batch produces duplicate sink rows; this choice would not establish the required streaming idempotent sink decision.

Normalize the right side to its intended grain before joining. This design 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.

Confirm authorized query succeeds while excluded tables remain inaccessible. This validate action addresses a different case (foreign catalog permission), where catalog discovery was mistaken for full table access. Unity Catalog usage and object privileges are still required for foreign data objects. In the stated problem, an analyst pulls millions of rows before a selective filter; this choice would not establish the required federated pushdown decision.

Verify the recipient can query the shared table without a file copy. This validate 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, an analyst pulls millions of rows before a selective filter; this choice would not establish the required federated pushdown decision.

Query a foreign table from Databricks and reconcile sampled source rows. This validate action addresses a different case (federated connection), where engineers export the full source database into cloud object storage each hour. Lakehouse Federation can query supported external sources through a catalog connection. In the stated problem, an analyst pulls millions of rows before a selective filter; this choice would not establish the required federated pushdown decision.