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

Use supported noninteractive service principal or workload identity authentication. This design action addresses a different case (api deployment authentication), where scheduled production deployment fails when the developer's token expires. Workload identity or service principal authentication decouples CI from employees. In the stated problem, the wrong workspace is selected because target is implicit; this choice would not establish the required target-safe deployment decision.

Require unit and integration tests plus deployment validation. This design 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, the wrong workspace is selected because target is implicit; this choice would not establish the required target-safe deployment decision.

Gate deployment on successful bundle validation. This design 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, the wrong workspace is selected because target is implicit; this choice would not establish the required target-safe deployment decision.

Enable Photon on the selected supported warehouse or compute. This implement 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, operators run blanket manual OPTIMIZE jobs regardless of table use; this choice would not establish the required predictive optimization decision.

Create the managed table under the approved catalog and migrate governed data. This implement 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, operators run blanket manual OPTIMIZE jobs regardless of table use; this choice would not establish the required predictive optimization decision.

Run OPTIMIZE or enable managed optimization where supported. This implement 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, operators run blanket manual OPTIMIZE jobs regardless of table use; this choice would not establish the required predictive optimization decision.

Inspect array lengths and expected order-item row counts. This diagnose 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.

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, a single campaign dominates rows and one reduce task runs for minutes; this choice would not establish the required skewed group aggregation decision.

Inspect row-level expectation metrics alongside pipeline event types. This diagnose 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.

Read mixed-version samples and verify consistent target data types. This validate action addresses a different case (parquet schema mismatch), where a merge step fails after a producer changes an integer field to string. Parquet schema compatibility matters even when column names are unchanged. In the stated problem, the initial reader assumes one unchanging flat schema and loses new fields; this choice would not establish the required nested json ingest decision.

Restart the job and verify no duplicate committed records. This validate action addresses a different case (kafka offset durability), where restarting with a fresh checkpoint replays previously ingested messages. A stable streaming checkpoint maintains Kafka offsets and sink progress across restarts. In the stated problem, the initial reader assumes one unchanging flat schema and loses new fields; this choice would not establish the required nested json ingest decision.

Ingest an unknown field and confirm it is retained for triage. This validate action addresses a different case (auto loader rescued data), where unknown or mismatched fields disappear during the bronze load. The rescued data column can preserve records with unexpected schema content for later remediation. In the stated problem, the initial reader assumes one unchanging flat schema and loses new fields; this choice would not establish the required nested json ingest decision.

Inspect effective grants on source, target and parent containers for the run-as principal. This diagnose 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, there is no controlled code review or rollback history; this choice would not establish the required git folder collaboration decision.

Inspect executor stderr and driver logs near the failed stage. This diagnose action addresses a different case (cluster log diagnostics), where the notebook cell shows only a generic stage failure. Driver and executor logs often contain the exact import or JVM error. In the stated problem, there is no controlled code review or rollback history; this choice would not establish the required git folder collaboration decision.

Inspect CLI target resolution and workspace host for the command. This diagnose 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, there is no controlled code review or rollback history; this choice would not establish the required git folder collaboration decision.

Monitor ownership transfers and stale personal owners. This monitor 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.

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, analysts must repeatedly request identical SELECT grants for each table; this choice would not establish the required schema-level grant inheritance decision.

Audit subsequent data access requests and grants. This monitor 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.

Monitor recipient access and credential expiry. This monitor action addresses a different case (open protocol recipient), where the partner cannot use an internal Databricks-to-Databricks credential flow. Open Delta Sharing can support non-Databricks recipients using the sharing protocol. In the stated problem, the recipient can discover unintended datasets; this choice would not establish the required share catalog scope 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, the recipient can discover unintended datasets; this choice would not establish the required share catalog scope 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, the recipient can discover unintended datasets; this choice would not establish the required share catalog scope decision.

Query the export view and confirm prohibited fields are absent. This validate 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, a raw SELECT on an approved table exposes plaintext email; this choice would not establish the required column masking decision.

Trigger a test error and confirm logs reveal no PII content. This validate action addresses a different case (restricted event logging), where logs expose PII to broader operations readers. Logging should redact or omit sensitive payload fields while preserving diagnostic codes. In the stated problem, a raw SELECT on an approved table exposes plaintext email; this choice would not establish the required column masking decision.

Verify expired subjects are inaccessible through approved retrieval paths. This validate action addresses a different case (retention purge), where expired records remain available in historical serving tables. Retention design must remove records and account for Delta time travel and obsolete files. In the stated problem, a raw SELECT on an approved table exposes plaintext email; this choice would not establish the required column masking decision.

Replay duplicate IDs within the accepted window and confirm only one survives. This validate 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.

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, the current INSERT-only target contains duplicate customer keys; this choice would not establish the required cdc merge semantics 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 current INSERT-only target contains duplicate customer keys; this choice would not establish the required cdc merge semantics decision.

Compare ingestion delay percentiles with current watermark threshold. This diagnose action addresses a different case (late event semantics), where reports silently discard legitimate late events under an aggressive watermark. A watermark trades supported lateness for state size and timeliness. 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.

Inspect job run-as user and dependent Unity Catalog grants. This diagnose 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, small logic regressions are discovered late and costly to debug; this choice would not establish the required unit versus integration tests decision.

Identify transformations depending on hidden notebook variables. This diagnose 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.

Configure cloudFiles ingestion into a Delta bronze streaming table. This implement action addresses a different case (auto loader file discovery), where listing the full historical directory every run exceeds the ingestion SLA. Auto Loader is designed for incremental new-file discovery with persisted state. In the stated problem, the initial reader assumes one unchanging flat schema and loses new fields; this choice would not establish the required nested json ingest decision.

Configure CSV quote/escape and malformed-record capture. This implement action addresses a different case (malformed csv quotes), where an ingestion reader splits quoted names into extra columns. CSV quoting and escape configurations must match the source serialization. In the stated problem, the initial reader assumes one unchanging flat schema and loses new fields; this choice would not establish the required nested json ingest decision.

Read objects with the supported binaryFile source and retain content/path fields. This implement 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, the initial reader assumes one unchanging flat schema and loses new fields; this choice would not establish the required nested json ingest decision.