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

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.

Find the expected schema error and confirm it disappears after correction. This validate 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, analysts confuse successful pipeline status with zero rejected records; this choice would not establish the required expectation monitoring decision.

Trigger a controlled failure and confirm notification delivery. This validate 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, analysts confuse successful pipeline status with zero rejected records; this choice would not establish the required expectation monitoring decision.

Confirm the profile scans fewer files with correct result rows. This validate action addresses a different case (query profile scans), where operators assume the query is always CPU-bound. Query Profile identifies scan, pruning and shuffle behavior for SQL workloads. In the stated problem, analysts confuse successful pipeline status with zero rejected records; this choice would not establish the required expectation monitoring decision.

Update the task dependency list and deploy a tested wheel or requirements set. This implement 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, both the normal and repair tasks run despite a branching requirement; this choice would not establish the required conditional task branches 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, both the normal and repair tasks run despite a branching requirement; this choice would not establish the required conditional task branches decision.

Set silver task depends_on edges pointing to the bronze task. This implement 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, both the normal and repair tasks run despite a branching requirement; this choice would not establish the required conditional task branches decision.

Choose a materialized view for refreshable precomputed analytics. This design 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, developers tune executor size without inspecting actual exchanges; this choice would not establish the required spark explain plans decision.

Choose a watermark tolerance based on allowed late-arrival behavior. This design action addresses a different case (event-time watermarking), where old keys remain in state indefinitely without a lateness bound. Watermarks provide a lateness threshold for bounded stateful streaming operations. In the stated problem, developers tune executor size without inspecting actual exchanges; this choice would not establish the required spark explain plans decision.

Choose a return type and null-handling contract matching the output. This design action addresses a different case (udf return schema), where returned values cannot be converted to the declared Spark return type. Pandas UDF return values must conform to the declared Spark data type. In the stated problem, developers tune executor size without inspecting actual exchanges; this choice would not establish the required spark explain plans decision.

Update foreachBatch to upsert by business key with batch idempotency. This implement 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, returned values cannot be converted to the declared Spark return type; this choice would not establish the required udf return schema 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, returned values cannot be converted to the declared Spark return type; this choice would not establish the required udf return schema decision.

Update the task dependency list and deploy a tested wheel or requirements set. This implement 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, returned values cannot be converted to the declared Spark return type; this choice would not establish the required udf return schema decision.

Inspect per-key sequence collisions and upstream log offsets. This diagnose action addresses a different case (cdc duplicate sequence), where the processing order for tied source events is nondeterministic. A deterministic sequencing contract needs a unique ordered event position. In the stated problem, microbatch processing time exceeds the configured trigger interval; this choice would not establish the required streaming trigger tuning decision.

Inspect event-time distribution and state-store growth. This diagnose action addresses a different case (event-time watermarking), where old keys remain in state indefinitely without a lateness bound. Watermarks provide a lateness threshold for bounded stateful streaming operations. In the stated problem, microbatch processing time exceeds the configured trigger interval; this choice would not establish the required streaming trigger tuning 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, microbatch processing time exceeds the configured trigger interval; this choice would not establish the required streaming trigger tuning decision.

Use supported AQE with appropriate shuffle and join settings. This design action addresses a different case (adaptive execution), where static join strategy performs poorly at varying input volumes. Adaptive Query Execution can adjust supported shuffle partitions and join strategies at runtime. In the stated problem, row-oriented text storage increases scans and transfer volumes; this choice would not establish the required columnar compression 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, row-oriented text storage increases scans and transfer volumes; this choice would not establish the required columnar compression decision.

Choose a single clustering layout mechanism for this table. This design 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, row-oriented text storage increases scans and transfer volumes; this choice would not establish the required columnar compression 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, customers receive repeated notifications for the same batch; this choice would not establish the required idempotent retry repair decision.

Monitor CI authentication failures and principal grants. This monitor action addresses a different case (api deployment authentication), where scheduled production deployment fails when the developer's token expires. Workload identity or service principal authentication decouples CI from employees. In the stated problem, customers receive repeated notifications for the same batch; this choice would not establish the required idempotent retry repair 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, customers receive repeated notifications for the same batch; this choice would not establish the required idempotent retry repair decision.

Monitor utilization and cost per processed gigabyte. This monitor action addresses a different case (compute utilization), where most provisioned resources sit idle between job runs. Compute metrics and usage history distinguish idle capacity from active work. In the stated problem, a manual UI report omits failed tasks and paginated runs; this choice would not establish the required jobs rest monitoring 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, a manual UI report omits failed tasks and paginated runs; this choice would not establish the required jobs rest monitoring decision.

Monitor missed notification deliveries against failed runs. This monitor 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, a manual UI report omits failed tasks and paginated runs; this choice would not establish the required jobs rest monitoring decision.

Compare returned metadata to known visible catalog objects. This validate action addresses a different case (information schema discovery), where it uses notebook-specific private metadata APIs that break after upgrades. INFORMATION_SCHEMA provides SQL metadata views subject to visibility permissions. In the stated problem, both environments use the same default catalog name in notebooks; this choice would not establish the required environment catalog isolation decision.

Confirm stewards can manage the table while readers retain intended access. This validate 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, both environments use the same default catalog name in notebooks; this choice would not establish the required environment catalog isolation decision.

Query the table successfully while unapproved tables stay blocked. This validate 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, both environments use the same default catalog name in notebooks; this choice would not establish the required environment catalog isolation decision.

Query old and new rows and confirm existing measures and keys remain valid. This validate 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, malformed source events contaminate metrics without an intermediate quality boundary; this choice would not establish the required medallion bronze silver gold decision.

Reconcile sample reports and verify dimensions join without duplication. This validate action addresses a different case (star schema analytics), where a denormalized mixed-grain table produces redundant attributes and expensive corrections. A star schema links a clear-grain fact to reusable dimensions for consistent analytics. In the stated problem, malformed source events contaminate metrics without an intermediate quality boundary; this choice would not establish the required medallion bronze silver gold decision.

Reconcile gold totals and dashboard response time against direct fact queries. This validate 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, malformed source events contaminate metrics without an intermediate quality boundary; this choice would not establish the required medallion bronze silver gold decision.