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

Attach the supported row filter to the eligible table. This implement 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, expired records remain available in historical serving tables; this choice would not establish the required retention purge decision.

Apply deletes to eligible tables and update derived datasets as required. This implement 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.

Attach a supported mask function to the email column. This implement 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.

Run representative device filters and compare data skipping. This validate 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, file-level statistics are missing for the filter column; this choice would not establish the required data skipping statistics decision.

Reconcile rows and compare scan cost against text storage. This validate 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, file-level statistics are missing for the filter column; this choice would not establish the required data skipping statistics 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, file-level statistics are missing for the filter column; this choice would not establish the required data skipping statistics decision.

Append one new object and verify it is ingested only once. This validate 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, restarting with a fresh checkpoint replays previously ingested messages; this choice would not establish the required kafka offset durability decision.

Ingest old and new samples and verify nested fields and rescued data are retained. This validate 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, restarting with a fresh checkpoint replays previously ingested messages; this choice would not establish the required kafka offset durability decision.

Deserialize old and new messages with the intended projection. This validate action addresses a different case (avro schema evolution), where an older consumer cannot deserialize records from a newer producer schema. Avro writer-reader schema compatibility must be maintained for evolution. In the stated problem, restarting with a fresh checkpoint replays previously ingested messages; this choice would not establish the required kafka offset durability decision.

Query facts as of past dates and verify the appropriate historical tier. This validate action addresses a different case (scd type 2 effective dates), where a single current tier overwrites history in the dimension. SCD Type 2 stores effective start/end intervals for distinct historical dimension versions. In the stated problem, a destructive table recreation would invalidate downstream consumers; this choice would not establish the required dimension evolution decision.

Join reports across marts and verify consistent country totals. This validate action addresses a different case (conformed dimensions), where the same country appears under conflicting dimension keys across marts. A conformed dimension provides common attribute definitions across fact models. In the stated problem, a destructive table recreation would invalidate downstream consumers; this choice would not establish the required dimension evolution decision.

Inject malformed input and confirm it never contaminates gold. This validate action addresses a different case (medallion bronze silver gold), where malformed source events contaminate metrics without an intermediate quality boundary. Bronze, silver and gold layers separate raw capture, validated refinement and business presentation. In the stated problem, a destructive table recreation would invalidate downstream consumers; this choice would not establish the required dimension evolution decision.

Inspect current table features, delete patterns and runtime compatibility. This diagnose 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, the merge scans unrelated historical partitions; this choice would not establish the required predicate-limited merge decision.

Inspect filters, cardinalities and existing partition layout. This diagnose 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, the merge scans unrelated historical partitions; this choice would not establish the required predicate-limited merge decision.

Inspect schema, compression ratio and scan bytes for current storage. This diagnose 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, the merge scans unrelated historical partitions; this choice would not establish the required predicate-limited merge decision.

Monitor discovered-file backlog and ingestion freshness. This monitor 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 nightly overwrite accidentally removes historical audit events; this choice would not establish the required append-only delta bronze 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, a nightly overwrite accidentally removes historical audit events; this choice would not establish the required append-only delta bronze decision.

Alert when rescued-data volume rises after schema changes. This monitor 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, a nightly overwrite accidentally removes historical audit events; this choice would not establish the required append-only delta bronze decision.

Use predictive optimization on supported managed Delta tables. This design 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.

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, each small delete rewrites large data files and increases write cost; this choice would not establish the required deletion vectors decision.

Schedule appropriate compaction or predictive optimization for the table. This design 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.

Confirm totals match while customer identifiers cannot be queried. This validate 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, a naive hash without controlled key management risks predictable identifiers; this choice would not establish the required pseudonymized join keys 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, a naive hash without controlled key management risks predictable identifiers; this choice would not establish the required pseudonymized join keys 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 naive hash without controlled key management risks predictable identifiers; this choice would not establish the required pseudonymized join keys decision.

Monitor missing child-element and parser error counts. This monitor 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, the initial reader assumes one unchanging flat schema and loses new fields; this choice would not establish the required nested json ingest decision.

Monitor malformed CSV rows and supplier format drift. This monitor 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.

Monitor newly arriving file-schema mismatches. This monitor 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.

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, provisioning overhead exceeds useful task execution time; this choice would not establish the required serverless job fit 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, provisioning overhead exceeds useful task execution time; this choice would not establish the required serverless job fit 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, provisioning overhead exceeds useful task execution time; this choice would not establish the required serverless job fit decision.

Audit unapproved external paths and location changes. This monitor 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, naming conventions alone are inconsistent across teams; this choice would not establish the required governed tags 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, naming conventions alone are inconsistent across teams; this choice would not establish the required governed tags decision.

Audit new location definitions and path overlaps. This monitor action addresses a different case (external location governance), where raw cloud permissions bypass central catalog governance. External locations map cloud paths to governed Unity Catalog storage credentials. In the stated problem, naming conventions alone are inconsistent across teams; this choice would not establish the required governed tags decision.