Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 85
Question 840
A data engineering team faces this Azure Databricks requirement: A shared customer table needs dynamic per-region row restrictions but the business refuses duplicating physical datasets. Which action is MOST appropriate?
- Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance.
- Transfer ownership through approved governance workflow and review grants after reassignment.
- Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage.
- Use row-filter policies on the governed table and test permitted region entitlements.
Explanation
Correct Answer
D:The most appropriate action is: Use row-filter policies on the governed table and test permitted region entitlements. It addresses the stated condition: A shared customer table needs dynamic per-region row restrictions but the business refuses duplicating physical datasets. The technical basis is: Row filters can restrict query results without maintaining separate physical copies by region. Without this control, duplicated datasets can diverge or escape synchronized retention and correction policies. A direct acceptance check is: Queries from two test regions return only their eligible rows from the same table.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A lineage graph shows no relationship for data loaded outside the monitored platform and the team assumes the dataset has no upstream dependency. The corresponding measure there would be: Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance. The stated situation instead calls for: Use row-filter policies on the governed table and test permitted region entitlements.
B:This alternative primarily addresses a different Azure Databricks problem: An audit asks who owns a catalog table but object ownership still points to an inactive employee. The corresponding measure there would be: Transfer ownership through approved governance workflow and review grants after reassignment. The stated situation instead calls for: Use row-filter policies on the governed table and test permitted region entitlements.
C:This alternative primarily addresses a different Azure Databricks problem: An analyst wants to know which upstream pipeline produced a metric displayed in a board dashboard. The corresponding measure there would be: Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage. The stated situation instead calls for: Use row-filter policies on the governed table and test permitted region entitlements.
Question 841
A Databricks engineer recommends: Configure job failure notifications to approved recipients and validate incident routing. It responds to: A scheduled Lakeflow Job has no owner alert when its final task fails overnight. What underlying mechanism BEST explains why?
- Timeouts and incident routing bound the cost and impact of stalled workflow execution.
- Operational scheduling without actionable failure reporting is not sufficient for production reliability.
- Backfills should be separated from ordinary schedules to avoid accidental duplicate processing.
- Concurrency management prevents competing executions from corrupting shared mutable state.
Explanation
Correct Answer
B:The decisive mechanism is: Operational scheduling without actionable failure reporting is not sufficient for production reliability. That explains the selected action: Configure job failure notifications to approved recipients and validate incident routing. In the original scenario: A scheduled Lakeflow Job has no owner alert when its final task fails overnight. The specific unmanaged risk is: A missed overnight job can remain unnoticed until business users complain. Validate with: A staged task failure produces an actionable notification with job ID and run link.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A long-running job occasionally hangs but there is no configured runtime ceiling or escalation. Its targeted response is: Set task and job timeout limits with notifications and a documented retry and recovery route. The current case is governed more directly by: Operational scheduling without actionable failure reporting is not sufficient for production reliability.
C:This principle concerns a separate data-engineering condition: An ingestion job requires a one-time backfill without changing the future daily production schedule. Its targeted response is: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger. The current case is governed more directly by: Operational scheduling without actionable failure reporting is not sufficient for production reliability.
D:This principle concerns a separate data-engineering condition: A daily data job runs twice during an incident and both executions write to the same target. Its targeted response is: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap. The current case is governed more directly by: Operational scheduling without actionable failure reporting is not sufficient for production reliability.
Question 842
A Databricks engineer recommends: Define a supported typed schema for nested structures and expected optional fields before writing to curated Delta. It responds to: A stream produces nested JSON events with optional fields but an analyst hardcodes every field as STRING. What underlying mechanism BEST explains why?
- Liquid clustering and traditional ZORDER/partitioning have compatibility constraints and different maintenance paths.
- Correct data types preserve semantic operations and enable schema validation during ingestion.
- Partition pruning benefits can be outweighed by extremely fragmented high-cardinality directory layouts.
- Views can provide different consumer contracts without unnecessary data duplication.
Explanation
Correct Answer
B:The decisive mechanism is: Correct data types preserve semantic operations and enable schema validation during ingestion. That explains the selected action: Define a supported typed schema for nested structures and expected optional fields before writing to curated Delta. In the original scenario: A stream produces nested JSON events with optional fields but an analyst hardcodes every field as STRING. The specific unmanaged risk is: String-only columns can make numerical aggregation or timestamp ordering incorrect. Validate with: Sample nested records parse into the designated types and invalid inputs follow the documented rejection path.
Incorrect Answers
A: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: Correct data types preserve semantic operations and enable schema validation during ingestion.
C:This principle concerns a separate data-engineering condition: A data engineer chooses the distinct customer ID as a partition directory for an SCD dimension with millions of customers. Its targeted response is: Prefer appropriate clustering or lower-cardinality partitioning and assess file sizes for the dimension. The current case is governed more directly by: Correct data types preserve semantic operations and enable schema validation during ingestion.
D:This principle concerns a separate data-engineering condition: A data product creates multiple physical copies of a curated dimension because teams need different column names. Its targeted response is: Expose stable SQL views over a governed base table when only presentation aliases differ. The current case is governed more directly by: Correct data types preserve semantic operations and enable schema validation during ingestion.
Question 843
A platform architect adopts: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. For this requirement: A lakehouse receives sensor observations with event timestamps that arrive out of order. Which rationale MOST directly supports it?
- Delta version history can provide auditable historical snapshots while underlying files are retained.
- Correct data types preserve semantic operations and enable schema validation during ingestion.
- Event time and processing time represent different facts and affect historical interpretation.
- SCD Type 2 preserves historical attribute versions rather than overwriting the prior business state.
Explanation
Correct Answer
C:The decisive mechanism is: Event time and processing time represent different facts and affect historical interpretation. That explains the selected action: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. In the original scenario: A lakehouse receives sensor observations with event timestamps that arrive out of order. The specific unmanaged risk is: Treating arrival order as occurrence order may miscalculate event windows and temporal joins. Validate with: A controlled late event appears in the correct historical period according to the approved policy.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A business needs to compare two point-in-time table versions during a financial reconciliation. Its targeted response is: Use supported Delta table version history and time travel within the documented retention window. The current case is governed more directly by: Event time and processing time represent different facts and affect historical interpretation.
B:This principle concerns a separate data-engineering condition: A stream produces nested JSON events with optional fields but an analyst hardcodes every field as STRING. Its targeted response is: Define a supported typed schema for nested structures and expected optional fields before writing to curated Delta. The current case is governed more directly by: Event time and processing time represent different facts and affect historical interpretation.
D:This principle concerns a separate data-engineering condition: A retail customer table changes delivery address repeatedly but analysts must reconstruct the address known at any prior invoice date. Its targeted response is: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys. The current case is governed more directly by: Event time and processing time represent different facts and affect historical interpretation.
Question 844
The following control has NOT been implemented: Define a supported typed schema for nested structures and expected optional fields before writing to curated Delta. In this case: A stream produces nested JSON events with optional fields but an analyst hardcodes every field as STRING. Which exposure remains?
- A mismatched partition scheme forces broad scans across unrelated arrival-day files.
- Without recoverable raw inputs the team cannot replay a transformation after discovering a rule defect.
- Using Type 1 updates may silently rewrite the apparent address on older transaction reports.
- String-only columns can make numerical aggregation or timestamp ordering incorrect.
Explanation
Correct Answer
D:The direct residual exposure is: String-only columns can make numerical aggregation or timestamp ordering incorrect. The triggering condition is: A stream produces nested JSON events with optional fields but an analyst hardcodes every field as STRING. The omitted safeguard is: Define a supported typed schema for nested structures and expected optional fields before writing to curated Delta. This matters because: Correct data types preserve semantic operations and enable schema validation during ingestion. A corrective test would show: Sample nested records parse into the designated types and invalid inputs follow the documented rejection path.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. Its preventative action would be: Reevaluate data layout using representative event-time filters and a suitable clustering key. The most direct exposure in the current scenario is: String-only columns can make numerical aggregation or timestamp ordering incorrect.
B:This failure mode belongs mainly to another situation: A bronze ingestion layer stores only final transformed values and loses raw source fields needed for incident replay. Its preventative action would be: Keep a governed raw or bronze representation before applying irreversible cleansing into silver and gold. The most direct exposure in the current scenario is: String-only columns can make numerical aggregation or timestamp ordering incorrect.
C:This failure mode belongs mainly to another situation: A retail customer table changes delivery address repeatedly but analysts must reconstruct the address known at any prior invoice date. Its preventative action would be: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys. The most direct exposure in the current scenario is: String-only columns can make numerical aggregation or timestamp ordering incorrect.
Question 845
The recommended measure is: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data. The operational context is: A team turns on every performance setting for a workload without benchmarking whether disk spills or network shuffle dominate runtime. Which data engineering concept applies?
- Driver-side collection and planning bottlenecks cannot be corrected solely by scaling executor count.
- Workspace compute permissions and access modes help maintain workload and security boundaries.
- SQL warehouses are optimized for SQL analytics and isolate query serving from other compute activities.
- Performance settings should follow measured bottlenecks rather than an assumption that each toggle is beneficial.
Explanation
Correct Answer
D:The decisive mechanism is: Performance settings should follow measured bottlenecks rather than an assumption that each toggle is beneficial. That explains the selected action: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data. In the original scenario: A team turns on every performance setting for a workload without benchmarking whether disk spills or network shuffle dominate runtime. The specific unmanaged risk is: Unmeasured tuning changes can hide the original bottleneck or increase compute costs. Validate with: Before-after measurements report comparable inputs, stage timings, spills and total cost.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A SQL transformation consumes large amounts of memory on the driver despite executor tasks processing most source partitions. Its targeted response is: Inspect driver collection and query planning behavior before simply enlarging every worker. The current case is governed more directly by: Performance settings should follow measured bottlenecks rather than an assumption that each toggle is beneficial.
B:This principle concerns a separate data-engineering condition: A multi-team interactive cluster permits users to attach arbitrary unapproved libraries and run notebooks under broad shared privileges. Its targeted response is: Apply suitable compute access modes, policies and entitlements that restrict who can attach or modify shared compute. The current case is governed more directly by: Performance settings should follow measured bottlenecks rather than an assumption that each toggle is beneficial.
C:This principle concerns a separate data-engineering condition: Analysts run short SQL dashboard queries against a shared lakehouse but their notebooks share a general-purpose Spark cluster with training experiments. Its targeted response is: Use an appropriately sized SQL warehouse with workload isolation and measured concurrency for dashboard queries. The current case is governed more directly by: Performance settings should follow measured bottlenecks rather than an assumption that each toggle is beneficial.
Question 846
An implementation skips: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. Engineers are observing: A lakehouse receives sensor observations with event timestamps that arrive out of order. What consequence is MOST likely?
- A mismatched partition scheme forces broad scans across unrelated arrival-day files.
- Inner joining only currently known dimension rows can undercount legitimate transactions.
- Assuming every engine can use every feature can result in invalid writes or unreadable metadata.
- Treating arrival order as occurrence order may miscalculate event windows and temporal joins.
Explanation
Correct Answer
D:The direct residual exposure is: Treating arrival order as occurrence order may miscalculate event windows and temporal joins. The triggering condition is: A lakehouse receives sensor observations with event timestamps that arrive out of order. The omitted safeguard is: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. This matters because: Event time and processing time represent different facts and affect historical interpretation. A corrective test would show: A controlled late event appears in the correct historical period according to the approved policy.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. Its preventative action would be: Reevaluate data layout using representative event-time filters and a suitable clustering key. The most direct exposure in the current scenario is: Treating arrival order as occurrence order may miscalculate event windows and temporal joins.
B:This failure mode belongs mainly to another situation: A late-arriving purchase refers to a customer identifier whose dimension record has not yet been ingested. Its preventative action would be: Define a deliberate unknown-member or late-dimension reconciliation pattern without silently dropping facts. The most direct exposure in the current scenario is: Treating arrival order as occurrence order may miscalculate event windows and temporal joins.
C:This failure mode belongs mainly to another situation: A cross-engine consumer expects a Delta table but source is plain Iceberg and engineers assume identical mutation semantics. Its preventative action would be: Choose and document a supported format and catalog integration with explicit read/write compatibility tests. The most direct exposure in the current scenario is: Treating arrival order as occurrence order may miscalculate event windows and temporal joins.
Question 847
A data engineering team faces this Azure Databricks requirement: A job is successful in the orchestrator but the business target is not updated because the notebook returns before async work completes. Which action is MOST appropriate?
- Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies.
- Assign a dedicated run-as identity with durable scoped grants and an ownership review.
- Wait for or explicitly verify required external or asynchronous work before reporting task success.
- Configure bounded restarts and alerting with root-cause investigation for repeated failures.
Explanation
Correct Answer
C:The most appropriate action is: Wait for or explicitly verify required external or asynchronous work before reporting task success. It addresses the stated condition: A job is successful in the orchestrator but the business target is not updated because the notebook returns before async work completes. The technical basis is: Task success must correspond to the completion of required data side effects, not just function invocation. Without this control, premature success can start downstream tasks against incomplete writes. A direct acceptance check is: A test run finishes only after the target watermark and expected row counts are confirmed.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. The corresponding measure there would be: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. The stated situation instead calls for: Wait for or explicitly verify required external or asynchronous work before reporting task success.
B:This alternative primarily addresses a different Azure Databricks problem: A job uses a service principal that loses access to the destination schema when an employee leaves. The corresponding measure there would be: Assign a dedicated run-as identity with durable scoped grants and an ownership review. The stated situation instead calls for: Wait for or explicitly verify required external or asynchronous work before reporting task success.
D:This alternative primarily addresses a different Azure Databricks problem: A continuously running pipeline is scheduled to restart automatically but restart storms consume a growing compute budget. The corresponding measure there would be: Configure bounded restarts and alerting with root-cause investigation for repeated failures. The stated situation instead calls for: Wait for or explicitly verify required external or asynchronous work before reporting task success.
Question 848
A production data team leaves out: Define Lakeflow Spark Declarative Pipelines source options, incremental behavior and expectations with a durable target. Its scenario is: A declarative pipeline loads cloud object files continuously but its configuration omits how duplicate files and bad records are handled. Which failure mode is MOST relevant?
- Ignoring changed source structures can halt ingestion or silently lose fields.
- Dropping then recreating tables may interrupt readers and lose associated governance settings.
- A stream can write duplicate or malformed records into curated output without policy.
- Too-short watermark drops legitimate delayed events; too-long state retention may exhaust memory.
Explanation
Correct Answer
C:The direct residual exposure is: A stream can write duplicate or malformed records into curated output without policy. The triggering condition is: A declarative pipeline loads cloud object files continuously but its configuration omits how duplicate files and bad records are handled. The omitted safeguard is: Define Lakeflow Spark Declarative Pipelines source options, incremental behavior and expectations with a durable target. This matters because: Declarative ingestion still requires explicit quality and replay assumptions. A corrective test would show: Injected duplicate and malformed source samples follow the intended dedupe or quarantine rules.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A file feed introduces an unexpected optional column and the stream fails after the first changed file. Its preventative action would be: Configure supported schema evolution or rescued-data handling with explicit compatibility review. The most direct exposure in the current scenario is: A stream can write duplicate or malformed records into curated output without policy.
B:This failure mode belongs mainly to another situation: An existing table must be rebuilt from corrected historical files while its readers require a consistent atomic replacement. Its preventative action would be: Choose a controlled CREATE OR REPLACE TABLE or compatible atomic table-replacement strategy and validate schema/permissions. The most direct exposure in the current scenario is: A stream can write duplicate or malformed records into curated output without policy.
D:This failure mode belongs mainly to another situation: A stream must group clicks into five-minute event-time windows while some mobile devices transmit data several minutes late. Its preventative action would be: Configure event-time windowing and an appropriate watermark based on observed lateness. The most direct exposure in the current scenario is: A stream can write duplicate or malformed records into curated output without policy.
Question 849
The recommended measure is: Select a notebook task within Lakeflow Jobs when procedural control and custom libraries fit the requirements. The operational context is: An ad hoc machine-learning preparation task has complex custom Python orchestration and no declarative table graph. Which data engineering concept applies?
- Notebooks and declarative pipelines serve different orchestration and transformation patterns.
- Job status must accurately reflect failed required operations for alerting and dependency logic.
- Retryable transient failures should be distinguished from permanent data or permission errors.
- Declarative pipelines express table dependencies and data quality rules without bespoke notebook orchestration.
Explanation
Correct Answer
A:The decisive mechanism is: Notebooks and declarative pipelines serve different orchestration and transformation patterns. That explains the selected action: Select a notebook task within Lakeflow Jobs when procedural control and custom libraries fit the requirements. In the original scenario: An ad hoc machine-learning preparation task has complex custom Python orchestration and no declarative table graph. The specific unmanaged risk is: Forcing arbitrary procedural logic into a declarative table pipeline may complicate testing and maintenance. Validate with: A job executes the procedural notebook under controlled dependencies and produces the validated output.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A workflow uses a notebook task that catches exceptions and returns success even when a write step fails. Its targeted response is: Propagate nonrecoverable exceptions to Lakeflow Jobs and attach actionable error metadata. The current case is governed more directly by: Notebooks and declarative pipelines serve different orchestration and transformation patterns.
C:This principle concerns a separate data-engineering condition: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. Its targeted response is: Add bounded retries with exponential backoff and observable failure after the retry budget. The current case is governed more directly by: Notebooks and declarative pipelines serve different orchestration and transformation patterns.
D:This principle concerns a separate data-engineering condition: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. Its targeted response is: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. The current case is governed more directly by: Notebooks and declarative pipelines serve different orchestration and transformation patterns.
Question 850
For this Microsoft DP-750 case: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. Which design or operational response BEST fits?
- Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs.
- Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again.
- Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling.
- Run supported OPTIMIZE or predictive optimization and validate file-size distribution and query cost.
Explanation
Correct Answer
A:The most appropriate action is: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. It addresses the stated condition: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. The technical basis is: VACUUM removes old physical files, so aggressive cleanup can break valid historical references. Without this control, premature deletion may invalidate time travel or a lagging reader's file references. A direct acceptance check is: A permitted historical query succeeds before and after approved housekeeping within its retention boundary.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A warehouse query remains slow even after larger compute is allocated and the profile reports scanning nearly every file. The corresponding measure there would be: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again. The stated situation instead calls for: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs.
C:This alternative primarily addresses a different Azure Databricks problem: A streaming pipeline's throughput falls although event arrival increases and its input backlog grows over time. The corresponding measure there would be: Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling. The stated situation instead calls for: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs.
D:This alternative primarily addresses a different Azure Databricks problem: A Delta table contains millions of tiny files after frequent microbatch updates and SQL scans spend time opening files. The corresponding measure there would be: Run supported OPTIMIZE or predictive optimization and validate file-size distribution and query cost. The stated situation instead calls for: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs.