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

Audit share membership changes against approvals. This monitor 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.

Monitor provider refresh and recipient visibility delays. This monitor action addresses a different case (shared table freshness), where consumers assume the share is a nightly static export. Delta Sharing exposes current authorized data as the provider updates the source. 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.

Audit federation-specific grants and unexpected access. This monitor 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.

Choose tracked history columns and a Type 2 CDC target. This design action addresses a different case (scd type 2 history), where overwrite-style updates destroy historical state needed for point-in-time reporting. SCD Type 2 records effective history instead of replacing the previous version. In the stated problem, reports silently discard legitimate late events under an aggressive watermark; this choice would not establish the required late event semantics 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, reports silently discard legitimate late events under an aggressive watermark; this choice would not establish the required late event semantics 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, reports silently discard legitimate late events under an aggressive watermark; this choice would not establish the required late event semantics decision.

Inspect current notification settings and run failure statuses. This diagnose 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, operators assume the query is always CPU-bound; this choice would not establish the required query profile scans decision.

Inspect query history for SQL text identity, duration and warehouse. This diagnose 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, operators assume the query is always CPU-bound; this choice would not establish the required query profile scans 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, operators assume the query is always CPU-bound; this choice would not establish the required query profile scans decision.

Build structured operational diagnostics from pipeline event records. This design 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 only see the most recent run in the Jobs UI; this choice would not establish the required job operational history decision.

Configure failure notifications for the job to an approved on-call channel. This design 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, operators only see the most recent run in the Jobs UI; this choice would not establish the required job operational history decision.

Build a tuning plan from the specific skew or spill evidence. This design 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 only see the most recent run in the Jobs UI; this choice would not establish the required job operational history decision.

Monitor out-of-order changes and CDC application errors. This monitor action addresses a different case (auto cdc keys), where applying events as append-only rows leaves outdated active accounts. AUTO CDC or applicable APPLY CHANGES needs stable keys and sequence ordering for stateful upserts. In the stated problem, periodic full-refresh queries miss required incremental freshness; this choice would not establish the required streaming table choice decision.

Monitor new per-key ordering collisions. This monitor 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, periodic full-refresh queries miss required incremental freshness; this choice would not establish the required streaming table choice decision.

Monitor refresh duration and staleness against dashboard SLA. This monitor 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, periodic full-refresh queries miss required incremental freshness; this choice would not establish the required streaming table choice decision.

Inspect sample suspicious values with strictly controlled access. This diagnose action addresses a different case (pii quarantine), where the silver pipeline allows unexpected identifiers into a broad analyst dataset. A data-quality filter can isolate suspect records before release. In the stated problem, the team needs read-only access for most users; this choice would not establish the required workspace object acl decision.

Inspect storage credential permissions and external-location path scopes. This diagnose action addresses a different case (storage credential scope), where engineers propose a credential allowing access to all company buckets. Unity Catalog storage credentials and external locations can constrain storage access. In the stated problem, the team needs read-only access for most users; this choice would not establish the required workspace object acl 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, the team needs read-only access for most users; this choice would not establish the required workspace object acl 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, subsequent CI redeployment unexpectedly overwrites it; this choice would not establish the required unmanaged resource drift decision.

Pin or rebuild incompatible wheels and update the bundle library. This implement action addresses a different case (python dependency triage), where a package import error appears only on the target compute. Runtime-specific wheel compatibility and pinning must be tested in CI. In the stated problem, subsequent CI redeployment unexpectedly overwrites it; this choice would not establish the required unmanaged resource drift 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, subsequent CI redeployment unexpectedly overwrites it; this choice would not establish the required unmanaged resource drift 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, the task exits before setting up its argument parser; this choice would not establish the required python task entrypoints decision.

Observe silver tasks start after bronze succeeds and run concurrently where eligible. This validate 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, the task exits before setting up its argument parser; this choice would not establish the required python task entrypoints decision.

Run the workflow while the author is inactive and verify intended access. This validate action addresses a different case (job run-as identity), where an employee departure causes permissions failures during scheduled runs. A stable least-privilege service principal can provide durable job identity. In the stated problem, the task exits before setting up its argument parser; this choice would not establish the required python task entrypoints decision.

Monitor scan bytes per query over time. This monitor 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, no baseline is available for the warehouse query execution; this choice would not establish the required sql query history 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, no baseline is available for the warehouse query execution; this choice would not establish the required sql query history 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, no baseline is available for the warehouse query execution; this choice would not establish the required sql query history decision.

Tune adaptive query execution or implement controlled key salting. This implement 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.

Tune shuffle partitions or adaptive coalescing on the affected workload. This implement 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, static join strategy performs poorly at varying input volumes; this choice would not establish the required adaptive execution decision.

Enable automatic clustering and required predictive optimization settings. This implement action addresses a different case (automatic clustering), where manual clustering keys quickly become stale. Automatic liquid clustering can select keys using query workload when platform prerequisites are met. In the stated problem, static join strategy performs poorly at varying input volumes; this choice would not establish the required adaptive execution decision.

Inspect inferred schemas and rescued or null fields in recently ingested rows. This diagnose action addresses a different case (nested json ingest), where the initial reader assumes one unchanging flat schema and loses new fields. Explicit schema management and rescued data handling protect evolving semi-structured ingestion. In the stated problem, an XML ingest incorrectly flattens multiple line items into one text field; this choice would not establish the required xml repeating elements decision.

Inspect duplicate file IDs and the ingestion checkpoint state. This diagnose action addresses a different case (retry-safe file loads), where a partially processed input file is loaded twice into Delta. Checkpointed incremental ingestion or stable event-level deduplication prevents repeated effects. In the stated problem, an XML ingest incorrectly flattens multiple line items into one text field; this choice would not establish the required xml repeating elements decision.

Inspect file media types and current input source format. This diagnose action addresses a different case (binary payload metadata), where a line-oriented text reader corrupts the raw binary payload. binaryFile input preserves raw file bytes and path metadata rather than decoding lines. In the stated problem, an XML ingest incorrectly flattens multiple line items into one text field; this choice would not establish the required xml repeating elements decision.