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

Add representative expected DataFrame fixtures and schema assertions. This design action addresses a different case (dataframe testing), where tests only assert that the DataFrame is nonempty. DataFrame equality and schema assertions test data behavior and contracts. In the stated problem, an employee departure causes permissions failures during scheduled runs; this choice would not establish the required job run-as identity decision.

Move resource definitions into bundle YAML with review gates. This design 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, an employee departure causes permissions failures during scheduled runs; this choice would not establish the required job run-as identity decision.

Use one managed and repeatable dependency source for the workload. This design 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, an employee departure causes permissions failures during scheduled runs; this choice would not establish the required job run-as identity decision.

Alert when p95 duration exceeds the agreed baseline. This monitor action addresses a different case (sql query history), where no baseline is available for the warehouse query execution. Query history/system query records support comparison of execution time and workload. In the stated problem, the current dashboard has no automated alert for missing units; this choice would not establish the required sql alert threshold decision.

Alert on freshness lag rather than only job failure. This monitor 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, the current dashboard has no automated alert for missing units; this choice would not establish the required sql alert threshold decision.

Monitor API failures, lag and pagination completeness. This monitor action addresses a different case (jobs rest monitoring), where a manual UI report omits failed tasks and paginated runs. The Jobs API exposes run records that a program can paginate and aggregate. In the stated problem, the current dashboard has no automated alert for missing units; this choice would not establish the required sql alert threshold decision.

Process an update and an insert and verify one correct current row per key. This validate action addresses a different case (cdc merge semantics), where the current INSERT-only target contains duplicate customer keys. A keyed Delta MERGE can update existing rows and insert new keys. 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.

Compare injected bad-row counts to quality metrics and task status. This validate 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.

Verify an order with four items yields four item-level rows. This validate 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.

Verify shuffle spill decreases without excessive scheduling overhead. This validate 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, a fixed high-worker count wastes resources on quiet days; this choice would not establish the required autoscaling right-size 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, a fixed high-worker count wastes resources on quiet days; this choice would not establish the required autoscaling right-size decision.

Benchmark identical queries with correct outputs and controlled resources. This validate 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, a fixed high-worker count wastes resources on quiet days; this choice would not establish the required autoscaling right-size decision.

Alert on freshness lag rather than only job failure. This monitor 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, analysts confuse successful pipeline status with zero rejected records; this choice would not establish the required expectation monitoring 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, analysts confuse successful pipeline status with zero rejected records; this choice would not establish the required expectation monitoring decision.

Alert when p95 duration exceeds the agreed baseline. This monitor action addresses a different case (sql query history), where no baseline is available for the warehouse query execution. Query history/system query records support comparison of execution time and workload. In the stated problem, analysts confuse successful pipeline status with zero rejected records; this choice would not establish the required expectation monitoring 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, a newly selected checkpoint location makes the stream reread historical input; this choice would not establish the required streaming checkpoint identity 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, a newly selected checkpoint location makes the stream reread historical input; this choice would not establish the required streaming checkpoint identity decision.

Compare deployed resource definitions against committed bundle configuration. This monitor 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 newly selected checkpoint location makes the stream reread historical input; this choice would not establish the required streaming checkpoint identity decision.

Inspect run status, task IDs and time windows in supported jobs system tables. This diagnose 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, most provisioned resources sit idle between job runs; this choice would not establish the required compute utilization decision.

Inspect source offsets, processed offsets and per-batch duration. This diagnose action addresses a different case (streaming backlog), where consumer lag grows while microbatch intervals appear stable. Backlog growth reveals insufficient sustainable processing throughput. In the stated problem, most provisioned resources sit idle between job runs; this choice would not establish the required compute utilization decision.

Inspect the relevant billing usage system table and available tags. This diagnose action addresses a different case (billing usage monitoring), where cost reports omit some job and workspace labels. Databricks system billing tables can expose usage records for cost attribution. In the stated problem, most provisioned resources sit idle between job runs; this choice would not establish the required compute utilization 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, it uses notebook-specific private metadata APIs that break after upgrades; this choice would not establish the required information schema discovery decision.

Add meaningful table and column comments through supported metadata commands. This implement action addresses a different case (catalog descriptions), where table and column metadata lack meaningful descriptions. Unity Catalog comments improve discoverability of governed data assets. In the stated problem, it uses notebook-specific private metadata APIs that break after upgrades; this choice would not establish the required information schema discovery decision.

Apply approved tags to the catalog objects or columns. This implement action addresses a different case (governed tags), where naming conventions alone are inconsistent across teams. Governed tags can classify assets for discovery and policy workflows. In the stated problem, it uses notebook-specific private metadata APIs that break after upgrades; this choice would not establish the required information schema discovery decision.

Add representative expected DataFrame fixtures and schema assertions. This design action addresses a different case (dataframe testing), where tests only assert that the DataFrame is nonempty. DataFrame equality and schema assertions test data behavior and contracts. In the stated problem, applying events as append-only rows leaves outdated active accounts; this choice would not establish the required auto cdc keys decision.

Use transactional merge or a committed batch-ID deduplication design. This design 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, applying events as append-only rows leaves outdated active accounts; this choice would not establish the required auto cdc keys decision.

Define a composite or otherwise unique ordering key for competing CDC events. This design 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, applying events as append-only rows leaves outdated active accounts; this choice would not establish the required auto cdc keys decision.

Rank events by business key, event time and a deterministic tie-breaker. This design action addresses a different case (latest-per-key with ties), where two events have the same event time and yield different surviving rows. A deterministic tie-breaker is required in a per-key window ranking. In the stated problem, analysts misread a quality count as the number of pipeline task failures; this choice would not establish the required quality metric interpretation decision.

Select appropriate salting or staged aggregation for a hot key. This design 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, analysts misread a quality count as the number of pipeline task failures; this choice would not establish the required quality metric interpretation 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, analysts misread a quality count as the number of pipeline task failures; this choice would not establish the required quality metric interpretation decision.

Inspect ownership and grant-management privileges in production. This diagnose 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, granting SELECT on the raw fact table violates minimization; this choice would not establish the required secure view sharing decision.

Inspect sensitive-column policy and current grants. This diagnose 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, granting SELECT on the raw fact table violates minimization; this choice would not establish the required secure view sharing decision.

Inspect the approved export schema against current selected columns. This diagnose 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, granting SELECT on the raw fact table violates minimization; this choice would not establish the required secure view sharing decision.