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

Inspect per-key frequencies and Spark task duration distribution. This diagnose action addresses a different case (skewed group aggregation), where a single campaign dominates rows and one reduce task runs for minutes. A hot aggregation key causes skew despite ample parallelism. In the stated problem, the current INSERT-only target contains duplicate customer keys; this choice would not establish the required cdc merge semantics decision.

Inspect input schema, target schema and invalid decimal examples. This diagnose action addresses a different case (silver schema enforcement), where implicit type coercion risks invalid numeric values being stored. Schema validation and explicit casts make type conversion failures observable. In the stated problem, the current INSERT-only target contains duplicate customer keys; this choice would not establish the required cdc merge semantics decision.

Inspect resend delay distribution and state-store size. This diagnose action addresses a different case (streaming dedup watermark), where a plain dropDuplicates retains state without a practical bound for never-ending keys. Watermarked streaming deduplication can bound retained duplicate state under an explicit lateness policy. In the stated problem, the current INSERT-only target contains duplicate customer keys; this choice would not establish the required cdc merge semantics decision.

Compare notebook and cluster package versions and import origins. This diagnose 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, code contains hard-coded region IDs and catalog names; this choice would not establish the required job parameters decision.

Inspect repository paths and bundle deployment definitions for hard-coded workspace identifiers. This diagnose 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, code contains hard-coded region IDs and catalog names; this choice would not establish the required job parameters decision.

Compare deployed job JSON with the version-controlled bundle. This diagnose 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, code contains hard-coded region IDs and catalog names; this choice would not establish the required job parameters decision.

Alter the dimension schema and backfill the new field safely. This implement 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, the same country appears under conflicting dimension keys across marts; this choice would not establish the required conformed dimensions decision.

On change, close the prior version and insert a new dimension version. This implement 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, the same country appears under conflicting dimension keys across marts; this choice would not establish the required conformed dimensions decision.

Create governed dimension tables and stable foreign keys in the fact. This implement 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, the same country appears under conflicting dimension keys across marts; this choice would not establish the required conformed dimensions decision.

Replay a batch ID and confirm target rows are not duplicated. This validate 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.

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, the pipeline picks an arbitrary record instead of the newest sequence; this choice would not establish the required window latest record 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, the pipeline picks an arbitrary record instead of the newest sequence; this choice would not establish the required window latest record decision.

Deploy using an explicit reviewed production target. This implement action addresses a different case (target-safe deployment), where the wrong workspace is selected because target is implicit. Explicit bundle target selection prevents accidental environment deployment. In the stated problem, scheduled production deployment fails when the developer's token expires; this choice would not establish the required api deployment authentication decision.

Run databricks bundle validate for the intended target in CI. This implement action addresses a different case (bundle validation), where an invalid resource key would be rejected only after production change. Bundle validation detects many configuration problems before deployment. In the stated problem, scheduled production deployment fails when the developer's token expires; this choice would not establish the required api deployment authentication decision.

Add relevant test jobs and environment approval gates to the pipeline. This implement action addresses a different case (ci quality gates), where the deployment pipeline only checks YAML syntax. CI must run transformation tests and controlled integration checks before deployment. In the stated problem, scheduled production deployment fails when the developer's token expires; this choice would not establish the required api deployment authentication decision.

Apply USE CATALOG, USE SCHEMA and table SELECT to the consumer group. This implement 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, analysts must repeatedly request identical SELECT grants for each table; this choice would not establish the required schema-level grant inheritance decision.

Transfer ownership to the approved group under supported permissions. This implement 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, analysts must repeatedly request identical SELECT grants for each table; this choice would not establish the required schema-level grant inheritance decision.

Grant appropriate BROWSE and keep sensitive table SELECT restricted. This implement 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, analysts must repeatedly request identical SELECT grants for each table; this choice would not establish the required schema-level grant inheritance decision.

Re-run and confirm failed partitions complete with stable outputs. This validate action addresses a different case (spark ui failure stage), where operators increase driver memory but failures occur on executors. Spark UI task failures and shuffle/spill metrics distinguish worker pressure from driver issues. In the stated problem, operators rerun the entire job and duplicate completed side effects; this choice would not establish the required repair failed tasks decision.

Submit a known broken transformation and confirm deployment is blocked. This validate action addresses a different case (ci quality gates), where the deployment pipeline only checks YAML syntax. CI must run transformation tests and controlled integration checks before deployment. In the stated problem, operators rerun the entire job and duplicate completed side effects; this choice would not establish the required repair failed tasks decision.

Rerun and verify the intended write succeeds while other tables stay blocked. This validate 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, operators rerun the entire job and duplicate completed side effects; this choice would not establish the required repair failed tasks 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, both the normal and repair tasks run despite a branching requirement; this choice would not establish the required conditional task branches decision.

Monitor task retries and repeated sink key counts. This monitor 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, both the normal and repair tasks run despite a branching requirement; this choice would not establish the required conditional task branches decision.

Monitor job run arguments for unexpected target or region values. This monitor 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, both the normal and repair tasks run despite a branching requirement; this choice would not establish the required conditional task branches decision.

Audit missing-parent-usage failures and overly broad grants. This monitor 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.

Audit new location definitions and path overlaps. This monitor 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, both environments use the same default catalog name in notebooks; this choice would not establish the required environment catalog isolation decision.

Monitor unexpected new tables entering the governed schema. This monitor 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, both environments use the same default catalog name in notebooks; this choice would not establish the required environment catalog isolation 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, the proposed maintenance script also runs ZORDER on that clustered table; this choice would not establish the required clustering versus zorder decision.

Choose a supported columnar Delta or Parquet layout for analytics. This design 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, the proposed maintenance script also runs ZORDER on that clustered table; this choice would not establish the required clustering versus zorder decision.

Choose adaptive skew join handling or a justified hot-key strategy. This design 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, the proposed maintenance script also runs ZORDER on that clustered table; this choice would not establish the required clustering versus zorder decision.

Scan logs and code for new secret exposure patterns. This monitor action addresses a different case (secret retrieval logs), where databricks notebook redaction is incorrectly treated as a comprehensive security control. Secrets should never be deliberately printed or put in logs, regardless of redaction behavior. In the stated problem, the hard-coded service password has not rotated for a year; this choice would not establish the required credential rotation procedure decision.

Monitor view definition changes and access to raw source. This monitor action addresses a different case (sensitive data suppression), where a broad SELECT still includes unstructured notes. Column suppression and data minimization prevent unnecessary sensitive-field release. In the stated problem, the hard-coded service password has not rotated for a year; this choice would not establish the required credential rotation procedure decision.

Audit token service access and key rotation schedules. This monitor action addresses a different case (pseudonymized join keys), where a naive hash without controlled key management risks predictable identifiers. Keyed pseudonymization can preserve joins while reducing identifier exposure. In the stated problem, the hard-coded service password has not rotated for a year; this choice would not establish the required credential rotation procedure decision.