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

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, a partially processed input file is loaded twice into Delta; this choice would not establish the required retry-safe file loads decision.

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, a partially processed input file is loaded twice into Delta; this choice would not establish the required retry-safe file loads 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, a partially processed input file is loaded twice into Delta; this choice would not establish the required retry-safe file loads decision.

Apply a governed column mask while preserving needed analytic access. This design 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, engineers propose a credential allowing access to all company buckets; this choice would not establish the required storage credential scope decision.

Use group-based least-privilege workspace object permissions. This design 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, engineers propose a credential allowing access to all company buckets; this choice would not establish the required storage credential scope decision.

Assign distinct deployment operators and data stewards with scoped privileges. This design 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, engineers propose a credential allowing access to all company buckets; this choice would not establish the required storage credential scope decision.

Verify recipient sees the selected dataset but not excluded tables. This validate 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, partners risk losing access or using a leaked long-lived credential; this choice would not establish the required sharing credential rotation 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, partners risk losing access or using a leaked long-lived credential; this choice would not establish the required sharing credential rotation decision.

Confirm the partner reads only the approved shared dataset. This validate action addresses a different case (open protocol recipient), where the partner cannot use an internal Databricks-to-Databricks credential flow. Open Delta Sharing can support non-Databricks recipients using the sharing protocol. In the stated problem, partners risk losing access or using a leaked long-lived credential; this choice would not establish the required sharing credential rotation decision.

Monitor pipeline error and warning event rates. This monitor action addresses a different case (pipeline event log), where the Jobs status only reports a high-level failure. Lakeflow pipeline event logs include update-level errors and progress events. In the stated problem, operators monitor compute uptime rather than data freshness; this choice would not establish the required end-to-end sla decision.

Monitor recurring task skew in scheduled workloads. This monitor action addresses a different case (spark ui shuffle metrics), where operators only monitor cluster-wide CPU and miss skewed task durations. Spark UI stage metrics reveal shuffle, spill and task skew. In the stated problem, operators monitor compute uptime rather than data freshness; this choice would not establish the required end-to-end sla decision.

Monitor alert evaluations and delivery failures. This monitor action addresses a different case (sql alert threshold), where the current dashboard has no automated alert for missing units. SQL alerts can evaluate a query result against a configured threshold. In the stated problem, operators monitor compute uptime rather than data freshness; this choice would not establish the required end-to-end sla decision.

Remove unapproved assets and add only the vetted table to the share. This implement 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.

Create a share, authorize the recipient and attach the approved tables. This implement 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.

Create a supported connection and foreign catalog with least-privilege credentials. This implement 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, consumers assume the share is a nightly static export; this choice would not establish the required shared table freshness decision.

Reconcile rows and compare scan cost against text storage. This validate 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, static join strategy performs poorly at varying input volumes; this choice would not establish the required adaptive execution decision.

Delete a few rows and confirm snapshot consistency without unnecessary rewrites. This validate 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, static join strategy performs poorly at varying input volumes; this choice would not establish the required adaptive execution decision.

Compare results and max task time before and after. This validate 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, static join strategy performs poorly at varying input volumes; this choice would not establish the required adaptive execution decision.

Confirm totals match while customer identifiers cannot be queried. This validate 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, all developers currently own production catalogs and can grant access; this choice would not establish the required separation of duties decision.

Query as two regional users and confirm different allowed row sets. This validate action addresses a different case (unity catalog row filter), where a shared table currently returns all regions to every reader. Unity Catalog row filters can restrict row visibility through governed policies. In the stated problem, all developers currently own production catalogs and can grant access; this choice would not establish the required separation of duties decision.

Confirm reader cannot edit but approved maintainer can deploy. This validate 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, all developers currently own production catalogs and can grant access; this choice would not establish the required separation of duties 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, no baseline is available for the warehouse query execution; this choice would not establish the required sql query history decision.

Define an alert query counting missing active units. This design action addresses a different case (sql alert threshold), where the current dashboard has no automated alert for missing units. SQL alerts can evaluate a query result against a configured threshold. In the stated problem, no baseline is available for the warehouse query execution; this choice would not establish the required sql query history 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, no baseline is available for the warehouse query execution; this choice would not establish the required sql query history 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, a notebook-scoped installation overrides the expected cluster version; this choice would not establish the required library precedence decision.

Recreate compute and confirm imports and ETL tests pass. This validate action addresses a different case (library version pinning), where a transitive dependency updated to an incompatible version. Explicit compatible dependency versions improve reproducibility across new compute environments. In the stated problem, a notebook-scoped installation overrides the expected cluster version; this choice would not establish the required library precedence decision.

Run a task that imports the packaged module on fresh job compute. This validate 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 notebook-scoped installation overrides the expected cluster version; this choice would not establish the required library precedence decision.

Deploy the wheel task with its documented entrypoint and parameters. This implement action addresses a different case (python task entrypoints), where the task exits before setting up its argument parser. A standard Python entrypoint and explicit arguments avoid notebook runtime assumptions. In the stated problem, old keys remain in state indefinitely without a lateness bound; this choice would not establish the required event-time watermarking decision.

Replace a scalar Python UDF with supported column expressions or a Pandas UDF. This implement 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, old keys remain in state indefinitely without a lateness bound; this choice would not establish the required event-time watermarking decision.

Compose transformations with DataFrame.transform and explicit configuration. This implement action addresses a different case (transform composability), where business logic depends on notebook state and widgets. DataFrame.transform supports composable DataFrame-to-DataFrame functions. In the stated problem, old keys remain in state indefinitely without a lateness bound; this choice would not establish the required event-time watermarking decision.

Keep filter predicates aligned with the stored partition column. This design 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, file-level statistics are missing for the filter column; this choice would not establish the required data skipping statistics decision.

Choose supported liquid clustering on commonly filtered device fields. This design 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, file-level statistics are missing for the filter column; this choice would not establish the required data skipping statistics decision.

Use predictive optimization on supported managed Delta tables. This design 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, file-level statistics are missing for the filter column; this choice would not establish the required data skipping statistics decision.