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

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.

Monitor storage growth and compression effectiveness. This monitor 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, static join strategy performs poorly at varying input volumes; this choice would not establish the required adaptive execution 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, static join strategy performs poorly at varying input volumes; this choice would not establish the required adaptive execution decision.

Monitor hot-key frequencies and spill metrics. This monitor 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.

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, teams grant SELECT merely to expose object listings; this choice would not establish the required browse metadata privilege decision.

Define a metadata quality standard for business purpose, grain and sensitivity. This design 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, teams grant SELECT merely to expose object listings; this choice would not establish the required browse metadata privilege decision.

Grant parent usage plus specific SELECT rather than broad ownership. This design 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, teams grant SELECT merely to expose object listings; this choice would not establish the required browse metadata privilege decision.

Generate dimension surrogate IDs and reference them from fact rows. This implement action addresses a different case (surrogate dimension keys), where joining facts directly on mutable business IDs links history incorrectly. Stable surrogate keys decouple dimensional identity from changing source identifiers. In the stated problem, a denormalized mixed-grain table produces redundant attributes and expensive corrections; this choice would not establish the required star schema analytics decision.

On change, close the prior version and insert a new dimension version. This implement 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 denormalized mixed-grain table produces redundant attributes and expensive corrections; this choice would not establish the required star schema analytics decision.

Map both marts to the governed conformed dimension. This implement 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 denormalized mixed-grain table produces redundant attributes and expensive corrections; this choice would not establish the required star schema analytics 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, operators manually check the run page every morning; this choice would not establish the required job email notification 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, operators manually check the run page every morning; this choice would not establish the required job email notification decision.

Monitor API failures, lag and pagination completeness. This monitor action addresses a different case (jobs rest monitoring), where a manual UI report omits failed tasks and paginated runs. The Jobs API exposes run records that a program can paginate and aggregate. In the stated problem, operators manually check the run page every morning; this choice would not establish the required job email notification decision.

Monitor uniqueness violations at the chosen grain. This monitor action addresses a different case (fact table grain), where summing revenue double-counts orders with multiple items. A dimensional fact must have one clearly documented row grain. In the stated problem, rigid daily partitions offer little pruning for customer filters; this choice would not establish the required liquid clustering for fact models decision.

Monitor freshness and quality at each layer. This monitor 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, rigid daily partitions offer little pruning for customer filters; this choice would not establish the required liquid clustering for fact models decision.

Monitor overlapping intervals and multiple current versions. This monitor 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, rigid daily partitions offer little pruning for customer filters; this choice would not establish the required liquid clustering for fact models decision.

Monitor notification retries and duplicate incidents. This monitor action addresses a different case (job webhook destination), where only personal email notifications are configured. Supported job notification destinations can integrate workflow status with an incident system. 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 pipeline error and warning event rates. This monitor 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.

Monitor recurring task skew in scheduled workloads. This monitor 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.

Design a customer-plan bridge with valid membership periods. This design action addresses a different case (many-to-many bridge), where joining facts directly to the membership table multiplies totals. A bridge table models many-to-many relationships at an explicit membership grain. In the stated problem, malformed source events contaminate metrics without an intermediate quality boundary; this choice would not establish the required medallion bronze silver gold decision.

Choose one order-line grain for transaction detail metrics. This design action addresses a different case (fact table grain), where summing revenue double-counts orders with multiple items. A dimensional fact must have one clearly documented row grain. In the stated problem, malformed source events contaminate metrics without an intermediate quality boundary; this choice would not establish the required medallion bronze silver gold decision.

Create a gold aggregate keyed by day and product with documented measures. This design action addresses a different case (aggregate gold model), where interactive queries scan billions of detail rows for identical totals. A summarized gold table can serve a stable reporting grain efficiently. In the stated problem, malformed source events contaminate metrics without an intermediate quality boundary; this choice would not establish the required medallion bronze silver gold 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, workspace notebook logs do not show the full audited account activity; this choice would not establish the required audit log review 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, workspace notebook logs do not show the full audited account activity; this choice would not establish the required audit log review 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, workspace notebook logs do not show the full audited account activity; this choice would not establish the required audit log review decision.

Make writes idempotent before enabling retries. This design 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, microbatch processing time exceeds the configured trigger interval; this choice would not establish the required streaming trigger tuning 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, microbatch processing time exceeds the configured trigger interval; this choice would not establish the required streaming trigger tuning decision.

Defer expensive materialization until the required action. This design action addresses a different case (spark lazy evaluation), where engineers assume an intermediate filter executed before any action. Spark transformations are lazy until an action triggers a job. In the stated problem, microbatch processing time exceeds the configured trigger interval; this choice would not establish the required streaming trigger tuning decision.

Audit row filter changes and unexpectedly broad query results. This monitor 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, the team needs read-only access for most users; this choice would not establish the required workspace object acl decision.

Audit deletion request completion and failed dependencies. This monitor 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, the team needs read-only access for most users; this choice would not establish the required workspace object acl 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, the team needs read-only access for most users; this choice would not establish the required workspace object acl decision.