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

Use Auto Loader with managed file discovery and checkpoint/schema locations. This design 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, a partially processed input file is loaded twice into Delta; this choice would not establish the required retry-safe file loads decision.

Use a stable checkpoint with a compatible idempotent Delta sink. This design 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, a partially processed input file is loaded twice into Delta; this choice would not establish the required retry-safe file loads decision.

Document delimiters, quote rules and corrupt-record handling for the feed. This design 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, a partially processed input file is loaded twice into Delta; this choice would not establish the required retry-safe file loads decision.

Create a test table and confirm approved analysts can query it. This validate 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, teams grant SELECT merely to expose object listings; this choice would not establish the required browse metadata privilege decision.

Confirm managed table storage resolves to the approved location. This validate action addresses a different case (managed storage ownership), where the data platform cannot apply consistent lifecycle governance. Managed locations centralize storage ownership for Unity Catalog managed assets. In the stated problem, teams grant SELECT merely to expose object listings; this choice would not establish the required browse metadata privilege 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, teams grant SELECT merely to expose object listings; this choice would not establish the required browse metadata privilege decision.

Monitor cache hit rate and eviction pressure. This monitor action addresses a different case (cache reuse), where repeated recomputation dominates each branch's execution. Persistence can avoid repeated work if reused data fits the memory budget. In the stated problem, each small delete rewrites large data files and increases write cost; this choice would not establish the required deletion vectors 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, each small delete rewrites large data files and increases write cost; this choice would not establish the required deletion vectors decision.

Monitor optimization operations and cost savings. This monitor action addresses a different case (predictive optimization), where operators run blanket manual OPTIMIZE jobs regardless of table use. Predictive optimization can automate supported managed-table maintenance based on workload signals. In the stated problem, each small delete rewrites large data files and increases write cost; this choice would not establish the required deletion vectors decision.

Configure the JSON reader and evolution options supported by the ingestion mechanism. This implement 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 older consumer cannot deserialize records from a newer producer schema; this choice would not establish the required avro schema evolution decision.

Cast or quarantine incompatible records before writing the destination. This implement 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, an older consumer cannot deserialize records from a newer producer schema; this choice would not establish the required avro schema evolution decision.

Configure the supported XML reader with the correct rowTag and schema. This implement action addresses a different case (xml repeating elements), where an XML ingest incorrectly flattens multiple line items into one text field. XML ingestion must specify the repeating row element and preserve nested structure. In the stated problem, an older consumer cannot deserialize records from a newer producer schema; this choice would not establish the required avro schema evolution decision.

Monitor task retries and repeated sink key counts. This monitor 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, dependent tasks sometimes run before the bronze load finishes; this choice would not establish the required job task dag decision.

Track dependency upgrades and compatibility test failures. This monitor 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, dependent tasks sometimes run before the bronze load finishes; this choice would not establish the required job task dag decision.

Monitor entrypoint failures after runtime or package upgrades. This monitor 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, dependent tasks sometimes run before the bronze load finishes; this choice would not establish the required job task dag decision.

Monitor view definition changes and access to raw source. This monitor 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 shared table currently returns all regions to every reader; this choice would not establish the required unity catalog row filter 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, a shared table currently returns all regions to every reader; this choice would not establish the required unity catalog row filter decision.

Audit privilege escalation attempts and run-as changes. This monitor action addresses a different case (service principal access), where the individual's credentials create unnecessary privilege and lifecycle risk. Production automation should use least-privilege service principals for stable identity. In the stated problem, a shared table currently returns all regions to every reader; this choice would not establish the required unity catalog row filter decision.

Monitor schema changes and rescued-field counts. This monitor 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.

Monitor unexpected file sizes and unsupported media types. This monitor 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.

Monitor duplicated ingest event IDs and retry pressure. This monitor 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.

Run small and large test inputs and compare execution strategies. This validate action addresses a different case (adaptive execution), where static join strategy performs poorly at varying input volumes. Adaptive Query Execution can adjust supported shuffle partitions and join strategies at runtime. In the stated problem, row-oriented text storage increases scans and transfer volumes; this choice would not establish the required columnar compression decision.

Delete a few rows and confirm snapshot consistency without unnecessary rewrites. This validate action addresses a different case (deletion vectors), where each small delete rewrites large data files and increases write cost. Deletion vectors can mark deleted rows without immediate whole-file rewrite when supported. In the stated problem, row-oriented text storage increases scans and transfer volumes; this choice would not establish the required columnar compression decision.

Reconcile changed rows and compare scanned file counts. This validate 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, row-oriented text storage increases scans and transfer volumes; this choice would not establish the required columnar compression decision.

Remove overly broad edit access and grant view permission to readers. This implement 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, engineers propose a credential allowing access to all company buckets; this choice would not establish the required storage credential scope decision.

Revoke unnecessary production ownership and grant task-specific roles. This implement 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, engineers propose a credential allowing access to all company buckets; this choice would not establish the required storage credential scope decision.

Create the aggregation view and grant SELECT only on the view. This implement action addresses a different case (secure view sharing), where granting SELECT on the raw fact table violates minimization. A governed aggregation view can expose only approved derived information. In the stated problem, engineers propose a credential allowing access to all company buckets; this choice would not establish the required storage credential scope decision.

Use supported AQE with appropriate shuffle and join settings. This design action addresses a different case (adaptive execution), where static join strategy performs poorly at varying input volumes. Adaptive Query Execution can adjust supported shuffle partitions and join strategies at runtime. In the stated problem, manual clustering keys quickly become stale; this choice would not establish the required automatic clustering decision.

Choose supported liquid clustering on commonly filtered device fields. This design 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, manual clustering keys quickly become stale; this choice would not establish the required automatic clustering decision.

Choose a supported columnar Delta or Parquet layout for analytics. This design 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, manual clustering keys quickly become stale; this choice would not establish the required automatic clustering decision.

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.