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

Monitor expectation-drop counts and upstream correction rates. This monitor action addresses a different case (expectation drop action), where invalid rows currently reach downstream aggregates. A Lakeflow expectation configured to drop invalid rows filters violations from target output. In the stated problem, events from different regions are ordered incorrectly in a UTC dashboard; this choice would not establish the required timestamp timezone normalization decision.

Monitor tied timestamps and nondeterministic upstream sequence values. This monitor 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, events from different regions are ordered incorrectly in a UTC dashboard; this choice would not establish the required timestamp timezone normalization decision.

Monitor null-key rate and unmatched dimension lookups. This monitor 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, events from different regions are ordered incorrectly in a UTC dashboard; this choice would not establish the required timestamp timezone normalization 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 row count doubles because the right side contains duplicate join keys; this choice would not establish the required sql join cardinality decision.

Force a retry and verify no duplicated sink rows. This validate 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, the row count doubles because the right side contains duplicate join keys; this choice would not establish the required sql join cardinality decision.

Test late events on both sides of the threshold and reconcile counts. This validate 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, the row count doubles because the right side contains duplicate join keys; this choice would not establish the required sql join cardinality decision.

Inspect fact primary keys and duplicates at candidate grains. This diagnose action addresses a different case (fact table grain), where summing revenue double-counts orders with multiple items. A dimensional fact must have one clearly documented row grain. In the stated problem, joining facts directly to the membership table multiplies totals; this choice would not establish the required many-to-many bridge decision.

Inspect fact query predicates and current data-skipping statistics. This diagnose action addresses a different case (liquid clustering for fact models), where rigid daily partitions offer little pruning for customer filters. Liquid clustering enables query-aware data layout without high-cardinality partitioning. In the stated problem, joining facts directly to the membership table multiplies totals; this choice would not establish the required many-to-many bridge 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, joining facts directly to the membership table multiplies totals; this choice would not establish the required many-to-many bridge decision.

Verify subject absence from all in-scope queryable datasets. This validate action addresses a different case (data subject request), where deleting a row from only the gold table leaves copies elsewhere. A complete delete workflow tracks identifiers and propagation across all governed copies. In the stated problem, expired records remain available in historical serving tables; this choice would not establish the required retention purge decision.

Query as privileged and standard readers and verify intended masked values. This validate 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, expired records remain available in historical serving tables; this choice would not establish the required retention purge 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, expired records remain available in historical serving tables; this choice would not establish the required retention purge decision.

Search Catalog Explorer and verify definitions distinguish the assets. This validate 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, the team lacks USE CATALOG and USE SCHEMA on the parent containers; this choice would not establish the required catalog privilege inheritance 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, the team lacks USE CATALOG and USE SCHEMA on the parent containers; this choice would not establish the required catalog privilege inheritance decision.

Run development tasks and confirm no production objects change. This validate action addresses a different case (environment catalog isolation), where both environments use the same default catalog name in notebooks. Environment-specific catalogs and explicit target names reduce cross-environment writes. In the stated problem, the team lacks USE CATALOG and USE SCHEMA on the parent containers; this choice would not establish the required catalog privilege inheritance decision.

Monitor small-file accumulation and optimization jobs. This monitor action addresses a different case (small file compaction), where read overhead grows because query plans open excessive small files. OPTIMIZE can compact compatible Delta files without changing logical table contents. In the stated problem, a query wraps business_date in a transformation and reads many partitions; this choice would not establish the required partition pruning decision.

Monitor shuffle size per task and batch runtime. This monitor 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 query wraps business_date in a transformation and reads many partitions; this choice would not establish the required partition pruning decision.

Monitor cluster-key usefulness as query patterns change. This monitor 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, a query wraps business_date in a transformation and reads many partitions; this choice would not establish the required partition pruning decision.

Apply row_number partitioned by key with explicit descending sequence. This implement 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, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records decision.

Query supported expectation metric records in the event log. This implement 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, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records decision.

Quarantine or reconcile duplicate active-key records before publishing silver. This implement action addresses a different case (uniqueness quality rule), where an upstream replay creates multiple active versions. An explicit uniqueness check identifies duplicate business keys before serving data. In the stated problem, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records decision.

Publish a minimal secure view with only approved attributes. This design 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, databricks notebook redaction is incorrectly treated as a comprehensive security control; this choice would not establish the required secret retrieval logs decision.

Use a row filter keyed to approved region mapping. This design 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, databricks notebook redaction is incorrectly treated as a comprehensive security control; this choice would not establish the required secret retrieval logs 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, databricks notebook redaction is incorrectly treated as a comprehensive security control; this choice would not establish the required secret retrieval logs decision.

Monitor serverless task failures and cost per run. This monitor action addresses a different case (serverless job fit), where provisioning overhead exceeds useful task execution time. Supported serverless jobs can reduce infrastructure management and startup overhead. In the stated problem, the current partition count is too low for data volume; this choice would not establish the required shuffle partition count decision.

Monitor hot-key frequencies and spill metrics. This monitor 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 current partition count is too low for data volume; this choice would not establish the required shuffle partition count decision.

Monitor worker scaling and long queue time. This monitor action addresses a different case (autoscaling right-size), where a fixed high-worker count wastes resources on quiet days. Supported autoscaling can adapt worker count within configured bounds. In the stated problem, the current partition count is too low for data volume; this choice would not establish the required shuffle partition count decision.

Shuffle source row order and verify the same account record survives. This validate 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, the silver writer rejects every new record after the upstream schema change; this choice would not establish the required controlled schema evolution 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 silver writer rejects every new record after the upstream schema change; this choice would not establish the required controlled schema evolution 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 silver writer rejects every new record after the upstream schema change; this choice would not establish the required controlled schema evolution decision.

Confirm each key has one selected row matching the maximum sequence. This validate action addresses a different case (window latest record), where the pipeline picks an arbitrary record instead of the newest sequence. ROW_NUMBER ordered by a deterministic sequence within each key selects the desired latest row. 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.

Restart a fresh session and confirm the imported module version. This validate 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, a newly selected checkpoint location makes the stream reread historical input; this choice would not establish the required streaming checkpoint identity decision.

Append new files and confirm only new input is processed under checkpoint tracking. This validate action addresses a different case (streaming table choice), where periodic full-refresh queries miss required incremental freshness. A streaming table tracks continuously arriving source data incrementally. 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.