Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 33
Question 320
A production data platform experiences this condition: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. Which targeted measure should be selected?
- Define a range expectation with metrics and the approved drop, fail or quarantine disposition.
- Apply type, nullability and range expectations before promoting bronze rows into the silver target.
- Configure expectations with an explicit fail, drop or retention behavior aligned to business severity.
- Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths.
Explanation
Correct Answer
B:The most appropriate action is: Apply type, nullability and range expectations before promoting bronze rows into the silver target. It addresses the stated condition: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. The technical basis is: Layered quality gates prevent malformed source values from contaminating trusted downstream tables. Without this control, invalid amounts may silently convert to null and skew revenue aggregates. A direct acceptance check is: A controlled malformed amount is detected and excluded from published silver while legitimate zero values remain.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A bronze stream sometimes includes ages below zero or above 120 yet the transformation casts every value to integer. The corresponding measure there would be: Define a range expectation with metrics and the approved drop, fail or quarantine disposition. The stated situation instead calls for: Apply type, nullability and range expectations before promoting bronze rows into the silver target.
C:This alternative primarily addresses a different Azure Databricks problem: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. The corresponding measure there would be: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity. The stated situation instead calls for: Apply type, nullability and range expectations before promoting bronze rows into the silver target.
D:This alternative primarily addresses a different Azure Databricks problem: An engineer changes the expected file schema in one notebook but forgets to update the Lakeflow pipeline definition. The corresponding measure there would be: Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths. The stated situation instead calls for: Apply type, nullability and range expectations before promoting bronze rows into the silver target.
Question 321
The team chooses: Define field-specific missing-value rules and quarantine or enrich unknown values before assigning business meaning. Its observed issue is: A customer reference dataset has missing country codes but a pipeline replaces every null with an arbitrary default country. What is the strongest technical basis?
- Spark can reduce shuffle costs by broadcasting a sufficiently small dimension where appropriate.
- Null remediation must preserve the difference between genuinely unknown data and a legitimate default.
- Union operations concatenate rows and require aligned column meanings.
- Temporal join predicates are needed when a dimension contains multiple valid versions per business key.
Explanation
Correct Answer
B:The decisive mechanism is: Null remediation must preserve the difference between genuinely unknown data and a legitimate default. That explains the selected action: Define field-specific missing-value rules and quarantine or enrich unknown values before assigning business meaning. In the original scenario: A customer reference dataset has missing country codes but a pipeline replaces every null with an arbitrary default country. The specific unmanaged risk is: Invented defaults can distort regional regulatory or financial reporting. Validate with: Rows with absent country are flagged for resolution and approved true defaults are applied consistently.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A pipeline joins a huge fact table with a tiny dimension and a normal shuffle join creates excessive network traffic. Its targeted response is: Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans. The current case is governed more directly by: Null remediation must preserve the difference between genuinely unknown data and a legitimate default.
C:This principle concerns a separate data-engineering condition: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. Its targeted response is: Align compatible schemas and use name-based union semantics with explicit type checks. The current case is governed more directly by: Null remediation must preserve the difference between genuinely unknown data and a legitimate default.
D:This principle concerns a separate data-engineering condition: A clickstream fact table is joined to a customer table with multiple status versions but no effective-date condition. Its targeted response is: Join historical dimension rows using business key and validity interval at event time. The current case is governed more directly by: Null remediation must preserve the difference between genuinely unknown data and a legitimate default.
Question 322
The recommended measure is: Declare consistent table names and dependencies and validate the generated pipeline graph. The operational context is: A declarative pipeline transforms several datasets but its source names are ambiguous and a data team cannot reconstruct dependencies. Which data engineering concept applies?
- Quality gates must precede trusted publication, not merely log errors afterwards.
- Staging plus validation separates construction of data from its declaration as trusted.
- Stream progress is not synonymous with completeness for a business reporting interval.
- A correct pipeline graph enables safe execution order and impact analysis.
Explanation
Correct Answer
D:The decisive mechanism is: A correct pipeline graph enables safe execution order and impact analysis. That explains the selected action: Declare consistent table names and dependencies and validate the generated pipeline graph. In the original scenario: A declarative pipeline transforms several datasets but its source names are ambiguous and a data team cannot reconstruct dependencies. The specific unmanaged risk is: Hidden dependencies can cause a downstream table to run against stale input. Validate with: A reviewed graph lists every expected parent and a source change propagates to the correct targets.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A workflow writes to production tables before a validation task examines null keys and duplicates. Its targeted response is: Place validations before publishing and use an atomic cutover or controlled target write. The current case is governed more directly by: A correct pipeline graph enables safe execution order and impact analysis.
B:This principle concerns a separate data-engineering condition: A finance transformation writes its output directly into a published table before reconciling totals against the source. Its targeted response is: Write to a staging target, validate row totals and invariants, then perform the approved publication step. The current case is governed more directly by: A correct pipeline graph enables safe execution order and impact analysis.
C:This principle concerns a separate data-engineering condition: A streaming process depends on a downstream batch closeout but no one defines whether it should wait for the latest watermark. Its targeted response is: Specify the stream watermark and an explicit closeout readiness condition before running downstream aggregation. The current case is governed more directly by: A correct pipeline graph enables safe execution order and impact analysis.
Question 323
A production data team leaves out: Parse and cast monetary values to a suitable decimal type with invalid-value handling. Its scenario is: A finance field arrives as a string with currency symbols and the team aggregates it lexicographically. Which failure mode is MOST relevant?
- A simple key join duplicates click events and misattributes prior users.
- Completion metrics may be inflated or undercounted when duplicate business events are not resolved.
- String summation or floating rounding may materially misstate financial totals.
- Position-based union may quietly corrupt data when column positions differ.
Explanation
Correct Answer
C:The direct residual exposure is: String summation or floating rounding may materially misstate financial totals. The triggering condition is: A finance field arrives as a string with currency symbols and the team aggregates it lexicographically. The omitted safeguard is: Parse and cast monetary values to a suitable decimal type with invalid-value handling. This matters because: Correct numeric types prevent sorting and arithmetic errors from text representations. A corrective test would show: A controlled money sample matches expected exact decimal totals and rejects malformed amounts.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A clickstream fact table is joined to a customer table with multiple status versions but no effective-date condition. Its preventative action would be: Join historical dimension rows using business key and validity interval at event time. The most direct exposure in the current scenario is: String summation or floating rounding may materially misstate financial totals.
B:This failure mode belongs mainly to another situation: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. Its preventative action would be: Validate business keys and choose a deterministic latest-enrollment record before aggregation. The most direct exposure in the current scenario is: String summation or floating rounding may materially misstate financial totals.
D:This failure mode belongs mainly to another situation: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. Its preventative action would be: Align compatible schemas and use name-based union semantics with explicit type checks. The most direct exposure in the current scenario is: String summation or floating rounding may materially misstate financial totals.
Question 324
A platform architect adopts: Prefer appropriate clustering or lower-cardinality partitioning and assess file sizes for the dimension. For this requirement: A data engineer chooses the distinct customer ID as a partition directory for an SCD dimension with millions of customers. Which rationale MOST directly supports it?
- Data models balance redundancy and query simplicity according to workload requirements.
- Delta and Iceberg are different transactional table formats with version-dependent feature support.
- Liquid clustering and traditional ZORDER/partitioning have compatibility constraints and different maintenance paths.
- Partition pruning benefits can be outweighed by extremely fragmented high-cardinality directory layouts.
Explanation
Correct Answer
D:The decisive mechanism is: Partition pruning benefits can be outweighed by extremely fragmented high-cardinality directory layouts. That explains the selected action: Prefer appropriate clustering or lower-cardinality partitioning and assess file sizes for the dimension. In the original scenario: A data engineer chooses the distinct customer ID as a partition directory for an SCD dimension with millions of customers. The specific unmanaged risk is: One-file-per-customer patterns can overwhelm metadata and worsen query startup. Validate with: Storage metrics show a manageable file distribution and point lookups meet query SLAs.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. Its targeted response is: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. The current case is governed more directly by: Partition pruning benefits can be outweighed by extremely fragmented high-cardinality directory layouts.
B:This principle concerns a separate data-engineering condition: A cross-engine consumer expects a Delta table but source is plain Iceberg and engineers assume identical mutation semantics. Its targeted response is: Choose and document a supported format and catalog integration with explicit read/write compatibility tests. The current case is governed more directly by: Partition pruning benefits can be outweighed by extremely fragmented high-cardinality directory layouts.
C:This principle concerns a separate data-engineering condition: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. Its targeted response is: Choose one compatible data layout strategy based on table format, platform support and query evidence. The current case is governed more directly by: Partition pruning benefits can be outweighed by extremely fragmented high-cardinality directory layouts.
Question 325
A team omits the recommended measure: Profile source missingness and define field-specific required versus optional expectations. Its environment shows: A new customer feed is missing optional contact information for 8% of rows and the team treats every null as pipeline failure. What is the MOST direct residual risk?
- Numerically valid but impossible values can contaminate customer metrics and machine-learning features.
- Overly strict validation can block legitimate records while loose validation may permit missing keys.
- Invalid amounts may silently convert to null and skew revenue aggregates.
- A seemingly successful load can conceal a growing upstream data-loss problem.
Explanation
Correct Answer
B:The direct residual exposure is: Overly strict validation can block legitimate records while loose validation may permit missing keys. The triggering condition is: A new customer feed is missing optional contact information for 8% of rows and the team treats every null as pipeline failure. The omitted safeguard is: Profile source missingness and define field-specific required versus optional expectations. This matters because: Completeness thresholds depend on business contracts and cannot be uniform across all columns. A corrective test would show: Quality dashboards separate optional-null rates from prohibited null keys and meet agreed thresholds.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A bronze stream sometimes includes ages below zero or above 120 yet the transformation casts every value to integer. Its preventative action would be: Define a range expectation with metrics and the approved drop, fail or quarantine disposition. The most direct exposure in the current scenario is: Overly strict validation can block legitimate records while loose validation may permit missing keys.
C:This failure mode belongs mainly to another situation: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. Its preventative action would be: Apply type, nullability and range expectations before promoting bronze rows into the silver target. The most direct exposure in the current scenario is: Overly strict validation can block legitimate records while loose validation may permit missing keys.
D:This failure mode belongs mainly to another situation: A pipeline reports zero failed rows because bad records are silently dropped without any count of what was removed. Its preventative action would be: Collect expectation metrics and reconcile input, accepted, quarantined and rejected record counts. The most direct exposure in the current scenario is: Overly strict validation can block legitimate records while loose validation may permit missing keys.
Question 326
A solution applies: Create a Unity Catalog view with approved permissions and verify underlying access semantics. It addresses: An analyst wants to expose a filtered projection of a governed table without copying sensitive source rows. Which operational outcome MOST directly verifies success?
- A set of known business prompts yields reconciled SQL and approved metric definitions.
- Discovery tests distinguish raw from certified curated objects and owners confirm their assigned namespaces.
- The same deployment command creates objects only in its designated staging or production namespace.
- Permitted users query only expected columns and rows through the view without a separately exported file.
Explanation
Correct Answer
D:The strongest acceptance proof is: Permitted users query only expected columns and rows through the view without a separately exported file. It specifically verifies: Create a Unity Catalog view with approved permissions and verify underlying access semantics. The original issue was: An analyst wants to expose a filtered projection of a governed table without copying sensitive source rows. The underlying mechanism is: A view can define a query abstraction without requiring a second physical copy of source data. Without it, replicated extracts may fall outside the original source's governance and retention controls.
Incorrect Answers
A:This result would validate a different measure: Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics. That is relevant to the distinct problem: An AI/BI Genie space is configured with ambiguous metric terminology and produces misleading natural-language interpretations. Here the acceptance criterion is: Permitted users query only expected columns and rows through the view without a separately exported file.
B:This result would validate a different measure: Define a consistent schema and naming architecture separating layers and business domains by purpose. That is relevant to the distinct problem: Multiple data products put raw, refined and curated assets into a single schema with confusing table names. Here the acceptance criterion is: Permitted users query only expected columns and rows through the view without a separately exported file.
C:This result would validate a different measure: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks. That is relevant to the distinct problem: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. Here the acceptance criterion is: Permitted users query only expected columns and rows through the view without a separately exported file.
Question 327
A pipeline owner declines the action: Choose a controlled CREATE OR REPLACE TABLE or compatible atomic table-replacement strategy and validate schema/permissions. The business situation is: An existing table must be rebuilt from corrected historical files while its readers require a consistent atomic replacement. What specific failure can follow?
- An uncheckpointed consumer can replay or omit events after a restart.
- Dropping then recreating tables may interrupt readers and lose associated governance settings.
- Misparsed columns can populate nulls while the batch appears to complete successfully.
- Out-of-order events can regress a target from its latest state to a stale state.
Explanation
Correct Answer
B:The direct residual exposure is: Dropping then recreating tables may interrupt readers and lose associated governance settings. The triggering condition is: An existing table must be rebuilt from corrected historical files while its readers require a consistent atomic replacement. The omitted safeguard is: Choose a controlled CREATE OR REPLACE TABLE or compatible atomic table-replacement strategy and validate schema/permissions. This matters because: Atomic table replacement can avoid exposing a partially loaded intermediate table. A corrective test would show: Readers observe a complete validated target before or after cutover, not partial data.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. Its preventative action would be: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. The most direct exposure in the current scenario is: Dropping then recreating tables may interrupt readers and lose associated governance settings.
C:This failure mode belongs mainly to another situation: An overnight load reads tab-separated files but an engineer assumes comma separators and casts malformed columns to null. Its preventative action would be: Specify the correct input delimiter, header and schema and validate parsing on a representative file. The most direct exposure in the current scenario is: Dropping then recreating tables may interrupt readers and lose associated governance settings.
D:This failure mode belongs mainly to another situation: A transactional feed produces out-of-order CDC events and a naive MERGE overwrites a newer status with an older update. Its preventative action would be: Apply ordered CDC sequencing using source change version or timestamp and consistent delete handling. The most direct exposure in the current scenario is: Dropping then recreating tables may interrupt readers and lose associated governance settings.
Question 328
A pipeline owner declines the action: Keep large results distributed and replace driver collection with bounded sampling or distributed writes. The business situation is: A Spark join reads large inputs but the driver reports failures after an analyst calls collect() on the result. What specific failure can follow?
- A small number of hot tasks can dominate the join while extra workers remain idle.
- Collecting billions of rows can crash the driver despite idle executors.
- Premature deletion may invalidate time travel or a lagging reader's file references.
- Ignoring metadata and file-layout changes can increase latency even though row counts decline.
Explanation
Correct Answer
B:The direct residual exposure is: Collecting billions of rows can crash the driver despite idle executors. The triggering condition is: A Spark join reads large inputs but the driver reports failures after an analyst calls collect() on the result. The omitted safeguard is: Keep large results distributed and replace driver collection with bounded sampling or distributed writes. This matters because: Driver memory is not an unlimited sink for results of distributed computation. A corrective test would show: The job writes results through distributed output and driver memory stays below the approved threshold.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A DataFrame join spills heavily because a single join key occurs in most rows. Its preventative action would be: Use query-profile evidence and a supported skew mitigation such as adaptive execution or key-aware repartitioning. The most direct exposure in the current scenario is: Collecting billions of rows can crash the driver despite idle executors.
C:This failure mode belongs mainly to another situation: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. Its preventative action would be: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. The most direct exposure in the current scenario is: Collecting billions of rows can crash the driver despite idle executors.
D:This failure mode belongs mainly to another situation: A query on a Delta table slows after a small percentage of rows are deleted but data files are not optimized. Its preventative action would be: Review deletion-vector behavior, table layout and suitable optimization for the supported runtime. The most direct exposure in the current scenario is: Collecting billions of rows can crash the driver despite idle executors.
Question 329
The team implements: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. The original problem is: A job owner cannot explain why a task skipped execution after a predecessor failed. Which test MOST convincingly demonstrates correctness?
- A delayed upstream refresh starts the dependent job only after the designated table event.
- Repeated injected failures hit the configured stop threshold and create a human-actionable incident.
- A staged predecessor failure shows the approved downstream skip and cleanup path in run history.
- Run history shows the job starts at the agreed local times across representative date transitions.
Explanation
Correct Answer
C:The strongest acceptance proof is: A staged predecessor failure shows the approved downstream skip and cleanup path in run history. It specifically verifies: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. The original issue was: A job owner cannot explain why a task skipped execution after a predecessor failed. The underlying mechanism is: Job task state transitions follow dependency and conditional execution rules. Without it, misunderstood skip conditions can leave expected cleanup or alerts unexecuted.
Incorrect Answers
A:This result would validate a different measure: Evaluate supported table update triggers or a clear upstream job dependency based on actual availability. That is relevant to the distinct problem: A pipeline must run when an upstream Databricks table is updated but analysts have hardcoded a daily time estimate. Here the acceptance criterion is: A staged predecessor failure shows the approved downstream skip and cleanup path in run history.
B:This result would validate a different measure: Configure bounded restarts and alerting with root-cause investigation for repeated failures. That is relevant to the distinct problem: A continuously running pipeline is scheduled to restart automatically but restart storms consume a growing compute budget. Here the acceptance criterion is: A staged predecessor failure shows the approved downstream skip and cleanup path in run history.
D:This result would validate a different measure: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant. That is relevant to the distinct problem: A business report must refresh daily at 06:00 in a defined local time zone but a developer schedules it in UTC without conversion. Here the acceptance criterion is: A staged predecessor failure shows the approved downstream skip and cleanup path in run history.
Question 330
The team chooses: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark. Its observed issue is: A Databricks job receives daily structured extracts but an upstream schedule occasionally delivers files late. What is the strongest technical basis?
- Data pipeline completeness requires tracking arrivals rather than assuming an exact wall-clock boundary.
- Input extraction semantics determine whether repeated rows are new events or refreshed state.
- Text ingestion options are part of the data contract and affect parsing correctness.
- CDC propagates source mutations without duplicating full snapshots.
Explanation
Correct Answer
A:The decisive mechanism is: Data pipeline completeness requires tracking arrivals rather than assuming an exact wall-clock boundary. That explains the selected action: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark. In the original scenario: A Databricks job receives daily structured extracts but an upstream schedule occasionally delivers files late. The specific unmanaged risk is: A fixed midnight file list can omit valid delayed uploads. Validate with: A deliberately delayed file is ingested exactly once within the allowed arrival window.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A daily file load uses append-only mode for periodic snapshots of the same full inventory. Its targeted response is: Use a snapshot replacement or keyed MERGE strategy instead of appending every full snapshot as new records. The current case is governed more directly by: Data pipeline completeness requires tracking arrivals rather than assuming an exact wall-clock boundary.
C:This principle concerns a separate data-engineering condition: An overnight load reads tab-separated files but an engineer assumes comma separators and casts malformed columns to null. Its targeted response is: Specify the correct input delimiter, header and schema and validate parsing on a representative file. The current case is governed more directly by: Data pipeline completeness requires tracking arrivals rather than assuming an exact wall-clock boundary.
D:This principle concerns a separate data-engineering condition: A SaaS database updates and deletes customer records but a pipeline appends every nightly full extract to a Delta table. Its targeted response is: Use a supported change-data-capture feed and apply insert, update and delete semantics to the target. The current case is governed more directly by: Data pipeline completeness requires tracking arrivals rather than assuming an exact wall-clock boundary.