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

Permit metadata discovery while requiring separate approvals for SELECT. This design 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, the team lacks USE CATALOG and USE SCHEMA on the parent containers; this choice would not establish the required catalog privilege inheritance decision.

Use an approved schema-level SELECT grant where broad table access is intended. This design 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, the team lacks USE CATALOG and USE SCHEMA on the parent containers; this choice would not establish the required catalog privilege inheritance decision.

Use a durable steward group as owner rather than a personal principal. This design 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.

Prefer native Spark expressions or a compatible vectorized Pandas UDF for the calculation. This design 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, a newly selected checkpoint location makes the stream reread historical input; this choice would not establish the required streaming checkpoint identity 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, a newly selected checkpoint location makes the stream reread historical input; this choice would not establish the required streaming checkpoint identity decision.

Choose compatible pinned versions using a tested dependency lock strategy. This design 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, a newly selected checkpoint location makes the stream reread historical input; this choice would not establish the required streaming checkpoint identity 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, logs expose PII to broader operations readers; this choice would not establish the required restricted event logging decision.

Audit unauthorized changes to workspace objects. This monitor 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, logs expose PII to broader operations readers; this choice would not establish the required restricted event logging decision.

Alert on secret expiry and authentication failures. This monitor action addresses a different case (credential rotation procedure), where the hard-coded service password has not rotated for a year. Secret management and controlled rotation reduce long-lived credential exposure. In the stated problem, logs expose PII to broader operations readers; this choice would not establish the required restricted event logging decision.

Monitor managed table optimization and ownership changes. This monitor action addresses a different case (managed table maintenance), where each table has custom file cleanup jobs and broad storage permissions. Unity Catalog managed tables provide platform-managed data placement and maintenance capabilities. In the stated problem, repeated recomputation dominates each branch's execution; this choice would not establish the required cache reuse decision.

Monitor state-store row counts, checkpoint size and spill. This monitor action addresses a different case (streaming state growth), where executor memory pressure grows even though input rate is stable. State retention and checkpoint state-store configuration affect memory requirements. In the stated problem, repeated recomputation dominates each branch's execution; this choice would not establish the required cache reuse 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, repeated recomputation dominates each branch's execution; this choice would not establish the required cache reuse decision.

Confirm job and pipeline IDs appear only in the intended workspace. This validate 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.

Introduce an invalid key and confirm CI prevents deployment. This validate 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.

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, subsequent CI redeployment unexpectedly overwrites it; this choice would not establish the required unmanaged resource drift 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, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records 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, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records decision.

Check valid decimal values and quarantined invalid strings. This validate 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, dropping invalid rows silently hides upstream quality failures; this choice would not establish the required quarantine bad records 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 only monitor cluster-wide CPU and miss skewed task durations; this choice would not establish the required spark ui shuffle metrics decision.

Inspect Query Profile operators for scan volume and pruning. This diagnose 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, operators only monitor cluster-wide CPU and miss skewed task durations; this choice would not establish the required spark ui shuffle metrics 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 only monitor cluster-wide CPU and miss skewed task durations; this choice would not establish the required spark ui shuffle metrics 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, it uses notebook-specific private metadata APIs that break after upgrades; this choice would not establish the required information schema discovery 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, it uses notebook-specific private metadata APIs that break after upgrades; this choice would not establish the required information schema discovery 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, it uses notebook-specific private metadata APIs that break after upgrades; this choice would not establish the required information schema discovery 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 refactor broke a notebook-relative import in the deployed job; this choice would not establish the required python wheel packaging decision.

Recreate compute and confirm imports and ETL tests pass. This validate 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, a refactor broke a notebook-relative import in the deployed job; this choice would not establish the required python wheel packaging decision.

Start a fresh job run and verify parameters reach the intended function. This validate 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, a refactor broke a notebook-relative import in the deployed job; this choice would not establish the required python wheel packaging decision.

Configure appropriate stats columns and recompute statistics as required. This implement action addresses a different case (data skipping statistics), where file-level statistics are missing for the filter column. Delta data skipping uses collected column statistics to eliminate files. 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.

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, the proposed maintenance script also runs ZORDER on that clustered table; this choice would not establish the required clustering versus zorder decision.

Add supported partition or clustering predicates to MERGE match conditions. This implement action addresses a different case (predicate-limited merge), where the merge scans unrelated historical partitions. Constraining merge matches to relevant partitions can reduce unnecessary target scanning. 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.

Recreate compute and confirm imports and ETL tests pass. This validate 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, small logic regressions are discovered late and costly to debug; this choice would not establish the required unit versus integration tests decision.

Run the same function in a unit test and in a production job. This validate action addresses a different case (transform composability), where business logic depends on notebook state and widgets. DataFrame.transform supports composable DataFrame-to-DataFrame functions. In the stated problem, small logic regressions are discovered late and costly to debug; this choice would not establish the required unit versus integration tests 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, small logic regressions are discovered late and costly to debug; this choice would not establish the required unit versus integration tests decision.