Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 84
Question 830
An operator introduces: Set task and job timeout limits with notifications and a documented retry and recovery route. The situation is: A long-running job occasionally hangs but there is no configured runtime ceiling or escalation. Which validation should be required before signoff?
- A staged task failure produces an actionable notification with job ID and run link.
- A failed downstream task is repaired without repeating successful non-idempotent upstream work.
- The historical batch completes with reconciled counts and next daily scheduled run remains unchanged.
- A simulated stall exceeds the threshold, stops correctly and alerts the support team.
Explanation
Correct Answer
D:The strongest acceptance proof is: A simulated stall exceeds the threshold, stops correctly and alerts the support team. It specifically verifies: Set task and job timeout limits with notifications and a documented retry and recovery route. The original issue was: A long-running job occasionally hangs but there is no configured runtime ceiling or escalation. The underlying mechanism is: Timeouts and incident routing bound the cost and impact of stalled workflow execution. Without it, A hung task can consume cluster hours indefinitely and prevent expected downstream refresh.
Incorrect Answers
A:This result would validate a different measure: Configure job failure notifications to approved recipients and validate incident routing. That is relevant to the distinct problem: A scheduled Lakeflow Job has no owner alert when its final task fails overnight. Here the acceptance criterion is: A simulated stall exceeds the threshold, stops correctly and alerts the support team.
B:This result would validate a different measure: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. That is relevant to the distinct problem: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. Here the acceptance criterion is: A simulated stall exceeds the threshold, stops correctly and alerts the support team.
C:This result would validate a different measure: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger. That is relevant to the distinct problem: An ingestion job requires a one-time backfill without changing the future daily production schedule. Here the acceptance criterion is: A simulated stall exceeds the threshold, stops correctly and alerts the support team.
Question 831
During a lakehouse implementation review, engineers observe: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. What is the BEST next action?
- Use row-filter policies on the governed table and test permitted region entitlements.
- Design record-level retention and external legal-hold workflows appropriate to the applicable policy.
- Configure supported Databricks audit logging and route relevant events to a secured retention destination.
- Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage.
Explanation
Correct Answer
B:The most appropriate action is: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. It addresses the stated condition: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. The technical basis is: Ordinary table replacement does not automatically constitute defensible preservation of historical legal records. Without this control, historical evidence may be lost even when the latest dataset remains complete. A direct acceptance check is: A hold rehearsal retrieves the original protected records and documents preservation scope and access.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A shared customer table needs dynamic per-region row restrictions but the business refuses duplicating physical datasets. The corresponding measure there would be: Use row-filter policies on the governed table and test permitted region entitlements. The stated situation instead calls for: Design record-level retention and external legal-hold workflows appropriate to the applicable policy.
C:This alternative primarily addresses a different Azure Databricks problem: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. The corresponding measure there would be: Configure supported Databricks audit logging and route relevant events to a secured retention destination. The stated situation instead calls for: Design record-level retention and external legal-hold workflows appropriate to the applicable policy.
D: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: Design record-level retention and external legal-hold workflows appropriate to the applicable policy.
Question 832
A Databricks engineer recommends: Record and pin supported package versions in the workload deployment specification and test reproducibility. It responds to: A notebook workflow imports a Python package without pinning its version, producing different results after an environment update. What underlying mechanism BEST explains why?
- Compute isolation reduces interference between unrelated application environments and execution libraries.
- Reproducible dependencies avoid unintentional behavior changes across cluster restarts and deployments.
- End-to-end task time includes compute startup and orchestration overhead, not just transformation CPU time.
- Autoscaling can adapt worker resources to changing parallel workload demand within a defined limit.
Explanation
Correct Answer
B:The decisive mechanism is: Reproducible dependencies avoid unintentional behavior changes across cluster restarts and deployments. That explains the selected action: Record and pin supported package versions in the workload deployment specification and test reproducibility. In the original scenario: A notebook workflow imports a Python package without pinning its version, producing different results after an environment update. The specific unmanaged risk is: Implicit latest-version resolution can introduce breaking API changes into unchanged pipeline code. Validate with: Clean-environment executions install the approved versions and return matching deterministic results.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A notebook pipeline uses a shared cluster with unstable third-party dependencies while a critical finance job needs controlled isolation. Its targeted response is: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions. The current case is governed more directly by: Reproducible dependencies avoid unintentional behavior changes across cluster restarts and deployments.
C:This principle concerns a separate data-engineering condition: A data team uses a high-power job cluster for a low-volume data-quality check that spends most runtime starting the cluster. Its targeted response is: Separate the small validation into an eligible lightweight or serverless task and measure total end-to-end runtime. The current case is governed more directly by: Reproducible dependencies avoid unintentional behavior changes across cluster restarts and deployments.
D:This principle concerns a separate data-engineering condition: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. Its targeted response is: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. The current case is governed more directly by: Reproducible dependencies avoid unintentional behavior changes across cluster restarts and deployments.
Question 833
The design team proposes: Review current serverless limitations and select compatible classic jobs compute when necessary. The situation is: A long-running job using an unsupported custom system dependency is moved to serverless without checking feature compatibility. Which technical principle justifies the decision?
- Driver-side collection and planning bottlenecks cannot be corrected solely by scaling executor count.
- Serverless and classic compute have different configuration surfaces and supported dependency patterns.
- SQL warehouses are optimized for SQL analytics and isolate query serving from other compute activities.
- Interactive compute should have a governed idle lifecycle distinct from persistent services.
Explanation
Correct Answer
B:The decisive mechanism is: Serverless and classic compute have different configuration surfaces and supported dependency patterns. That explains the selected action: Review current serverless limitations and select compatible classic jobs compute when necessary. In the original scenario: A long-running job using an unsupported custom system dependency is moved to serverless without checking feature compatibility. The specific unmanaged risk is: A serverless migration may fail when a required library or environment customization cannot be installed. Validate with: A compatibility matrix and staging execution demonstrate every necessary dependency on the chosen compute.
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: Serverless and classic compute have different configuration surfaces and supported dependency patterns.
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: Serverless and classic compute have different configuration surfaces and supported dependency patterns.
D:This principle concerns a separate data-engineering condition: A newly created cluster remains available for hours after manual exploration even though the organization has a strict idle-cost policy. Its targeted response is: Set appropriate auto-termination or idle controls for interactive compute while excluding workloads requiring continuous availability. The current case is governed more directly by: Serverless and classic compute have different configuration surfaces and supported dependency patterns.
Question 834
The following control has NOT been implemented: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality. In this case: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. Which exposure remains?
- Excessive partitions create small files and poor query planning without useful pruning.
- Poorly chosen keys increase full scans and maintenance overhead as traffic grows.
- Treating arrival order as occurrence order may miscalculate event windows and temporal joins.
- Rigid directory partitioning can cause imbalance and require costly redesign as filters change.
Explanation
Correct Answer
A:The direct residual exposure is: Excessive partitions create small files and poor query planning without useful pruning. The triggering condition is: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. The omitted safeguard is: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality. This matters because: High-cardinality partition columns can fragment file layout and increase metadata overhead. A corrective test would show: File-count and query-profile comparisons show fewer fragments and faster targeted scans.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A query repeatedly filters by customer, date and product but the physical data design was selected without query-profile evidence. Its preventative action would be: Compare selective filter patterns and data-skipping statistics before committing partition and clustering keys. The most direct exposure in the current scenario is: Excessive partitions create small files and poor query planning without useful pruning.
C:This failure mode belongs mainly to another situation: A lakehouse receives sensor observations with event timestamps that arrive out of order. Its preventative action would be: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. The most direct exposure in the current scenario is: Excessive partitions create small files and poor query planning without useful pruning.
D:This failure mode belongs mainly to another situation: A large Delta fact table is filtered primarily on high-cardinality account IDs with changing query patterns. Its preventative action would be: Enable supported liquid clustering with appropriate keys and run compatible optimization. The most direct exposure in the current scenario is: Excessive partitions create small files and poor query planning without useful pruning.
Question 835
The team chooses: Parameterize environment-specific paths, catalogs and identities through governed deployment configuration. Its observed issue is: A multi-team notebook uses hard-coded workspace names and credentials, making the same pipeline fail in staging. What is the strongest technical basis?
- Declarative pipelines express table dependencies and data quality rules without bespoke notebook orchestration.
- Separating pipeline stages creates observable failure boundaries and supports targeted recovery.
- Portable pipelines should separate code logic from environment-specific configuration.
- A correct pipeline graph enables safe execution order and impact analysis.
Explanation
Correct Answer
C:The decisive mechanism is: Portable pipelines should separate code logic from environment-specific configuration. That explains the selected action: Parameterize environment-specific paths, catalogs and identities through governed deployment configuration. In the original scenario: A multi-team notebook uses hard-coded workspace names and credentials, making the same pipeline fail in staging. The specific unmanaged risk is: Hard-coded development resources can cause a production job to read or overwrite the wrong data. Validate with: A staging and production run use the same code with distinct approved configuration and no credential leakage.
Incorrect Answers
A: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: Portable pipelines should separate code logic from environment-specific configuration.
B:This principle concerns a separate data-engineering condition: A multi-step notebook workflow handles source extraction and final reporting in one cell sequence with no recoverable checkpoints. Its targeted response is: Split ingestion, validation and publishing into explicit orchestrated tasks with durable intermediate outputs. The current case is governed more directly by: Portable pipelines should separate code logic from environment-specific configuration.
D:This principle concerns a separate data-engineering condition: A declarative pipeline transforms several datasets but its source names are ambiguous and a data team cannot reconstruct dependencies. Its targeted response is: Declare consistent table names and dependencies and validate the generated pipeline graph. The current case is governed more directly by: Portable pipelines should separate code logic from environment-specific configuration.
Question 836
For this Azure Databricks issue: A customer reference dataset has missing country codes but a pipeline replaces every null with an arbitrary default country. Engineers choose: Define field-specific missing-value rules and quarantine or enrich unknown values before assigning business meaning. What acceptance evidence is BEST?
- A seeded dataset retains zero-quantity items while rows with null quantities follow the documented rule.
- A test invoice with a linked refund produces the approved net amount.
- Rows with absent country are flagged for resolution and approved true defaults are applied consistently.
- Spark UI shows reduced shuffle bytes and matching results without executor out-of-memory.
Explanation
Correct Answer
C:The strongest acceptance proof is: Rows with absent country are flagged for resolution and approved true defaults are applied consistently. It specifically verifies: Define field-specific missing-value rules and quarantine or enrich unknown values before assigning business meaning. The original issue was: A customer reference dataset has missing country codes but a pipeline replaces every null with an arbitrary default country. The underlying mechanism is: Null remediation must preserve the difference between genuinely unknown data and a legitimate default. Without it, invented defaults can distort regional regulatory or financial reporting.
Incorrect Answers
A:This result would validate a different measure: Implement explicit null predicates rather than treating zero and null as equivalent. That is relevant to the distinct problem: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. Here the acceptance criterion is: Rows with absent country are flagged for resolution and approved true defaults are applied consistently.
B:This result would validate a different measure: Normalize transaction sign semantics before grouping by business date and customer. That is relevant to the distinct problem: A daily revenue report double-counts refunds because both debit and credit rows are summed as positive numbers. Here the acceptance criterion is: Rows with absent country are flagged for resolution and approved true defaults are applied consistently.
D:This result would validate a different measure: Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans. That is relevant to the distinct problem: A pipeline joins a huge fact table with a tiny dimension and a normal shuffle join creates excessive network traffic. Here the acceptance criterion is: Rows with absent country are flagged for resolution and approved true defaults are applied consistently.
Question 837
During a lakehouse implementation review, engineers observe: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. What is the BEST next action?
- Choose node families and driver/worker sizes using CPU, memory, shuffle and workload profile evidence.
- Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior.
- Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met.
- Use an appropriately sized SQL warehouse with workload isolation and measured concurrency for dashboard queries.
Explanation
Correct Answer
B:The most appropriate action is: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. It addresses the stated condition: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. The technical basis is: Autoscaling can adapt worker resources to changing parallel workload demand within a defined limit. Without this control, A fixed undersized cluster misses month-end deadlines while an oversized fixed cluster wastes daily spend. A direct acceptance check is: Load tests for normal and month-end volumes satisfy runtime targets without exceeding the approved worker ceiling.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A new job uses a large memory-optimized node merely because its source data is large, although profiling shows compute-bound transforms. The corresponding measure there would be: Choose node families and driver/worker sizes using CPU, memory, shuffle and workload profile evidence. The stated situation instead calls for: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior.
C:This alternative primarily addresses a different Azure Databricks problem: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. The corresponding measure there would be: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. The stated situation instead calls for: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior.
D:This alternative primarily addresses a different Azure Databricks problem: Analysts run short SQL dashboard queries against a shared lakehouse but their notebooks share a general-purpose Spark cluster with training experiments. The corresponding measure there would be: Use an appropriately sized SQL warehouse with workload isolation and measured concurrency for dashboard queries. The stated situation instead calls for: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior.
Question 838
For this Azure Databricks issue: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. Engineers choose: Check required parent catalog and schema usage privileges alongside the table SELECT grant. What acceptance evidence is BEST?
- The job authenticates successfully and audited logs contain no raw secret or token.
- A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
- The writer inserts a validated test row and reader accounts are denied modification attempts.
- A privilege inspection shows the narrow parent usage grants and the contractor can query only the intended table.
Explanation
Correct Answer
D:The strongest acceptance proof is: A privilege inspection shows the narrow parent usage grants and the contractor can query only the intended table. It specifically verifies: Check required parent catalog and schema usage privileges alongside the table SELECT grant. The original issue was: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. The underlying mechanism is: Object access can require permission to traverse its parent hierarchy as well as read the child. Without it, granting SELECT alone may not make a catalog object usable and lead to excessive troubleshooting grants.
Incorrect Answers
A:This result would validate a different measure: Use supported Databricks secret access with least-privilege scope access and remove secret values from logs. That is relevant to the distinct problem: An application uses an external Azure Key Vault secret scope but a notebook prints the secret into task logs. Here the acceptance criterion is: A privilege inspection shows the narrow parent usage grants and the contractor can query only the intended table.
B:This result would validate a different measure: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. That is relevant to the distinct problem: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. Here the acceptance criterion is: A privilege inspection shows the narrow parent usage grants and the contractor can query only the intended table.
C:This result would validate a different measure: Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants. That is relevant to the distinct problem: An engineering pipeline attempts to insert records into a production Delta table using an account with SELECT only. Here the acceptance criterion is: A privilege inspection shows the narrow parent usage grants and the contractor can query only the intended table.
Question 839
A platform architect adopts: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. For this requirement: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. Which rationale MOST directly supports it?
- Declarative pipelines express table dependencies and data quality rules without bespoke notebook orchestration.
- Notebooks and declarative pipelines serve different orchestration and transformation patterns.
- Staging plus validation separates construction of data from its declaration as trusted.
- A correct pipeline graph enables safe execution order and impact analysis.
Explanation
Correct Answer
A:The decisive mechanism is: Declarative pipelines express table dependencies and data quality rules without bespoke notebook orchestration. That explains the selected action: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. In the original scenario: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. The specific unmanaged risk is: Hand-built ordering can drift from the actual dependency graph as tables are added. Validate with: A pipeline run updates tables in valid dependency order and records expectation outcomes.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: An ad hoc machine-learning preparation task has complex custom Python orchestration and no declarative table graph. Its targeted response is: Select a notebook task within Lakeflow Jobs when procedural control and custom libraries fit the requirements. The current case is governed more directly by: Declarative pipelines express table dependencies and data quality rules without bespoke notebook orchestration.
C: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: Declarative pipelines express table dependencies and data quality rules without bespoke notebook orchestration.
D:This principle concerns a separate data-engineering condition: A declarative pipeline transforms several datasets but its source names are ambiguous and a data team cannot reconstruct dependencies. Its targeted response is: Declare consistent table names and dependencies and validate the generated pipeline graph. The current case is governed more directly by: Declarative pipelines express table dependencies and data quality rules without bespoke notebook orchestration.
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.