Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 66
Question 650
The design team proposes: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger. The situation is: An ingestion job requires a one-time backfill without changing the future daily production schedule. Which technical principle justifies the decision?
- Backfills should be separated from ordinary schedules to avoid accidental duplicate processing.
- Concurrency management prevents competing executions from corrupting shared mutable state.
- Job task state transitions follow dependency and conditional execution rules.
- Consistent parameter passing ensures dependent tasks operate on the same business interval.
Explanation
Correct Answer
A:The decisive mechanism is: Backfills should be separated from ordinary schedules to avoid accidental duplicate processing. That explains the selected action: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger. In the original scenario: An ingestion job requires a one-time backfill without changing the future daily production schedule. The specific unmanaged risk is: Temporarily editing the main schedule may skip normal deliveries or replay wrong dates. Validate with: The historical batch completes with reconciled counts and next daily scheduled run remains unchanged.
Incorrect Answers
B: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: Backfills should be separated from ordinary schedules to avoid accidental duplicate processing.
C:This principle concerns a separate data-engineering condition: A job owner cannot explain why a task skipped execution after a predecessor failed. Its targeted response is: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. The current case is governed more directly by: Backfills should be separated from ordinary schedules to avoid accidental duplicate processing.
D:This principle concerns a separate data-engineering condition: A workflow needs to pass a date parameter from a scheduled trigger into all its downstream notebook tasks. Its targeted response is: Define validated job parameters and propagate them through supported task parameter bindings. The current case is governed more directly by: Backfills should be separated from ordinary schedules to avoid accidental duplicate processing.
Question 651
A production data platform experiences this condition: An alert triggers on every harmless microbatch delay while real hour-long ingestion stalls go unnoticed. Which targeted measure should be selected?
- Inspect the Spark UI DAG and skewed-key distribution before changing cluster size.
- Define meaningful latency, error and backlog thresholds with alert routing based on the business SLO.
- Use caching only for beneficial reuse and release persisted state when no longer needed.
- Set a measured maintenance cadence or evaluate supported predictive optimization for eligible managed tables.
Explanation
Correct Answer
B:The most appropriate action is: Define meaningful latency, error and backlog thresholds with alert routing based on the business SLO. It addresses the stated condition: An alert triggers on every harmless microbatch delay while real hour-long ingestion stalls go unnoticed. The technical basis is: Alert quality depends on actionable thresholds and distinguishing transient variation from sustained failure. Without this control, excessive false alerts can obscure serious freshness incidents. A direct acceptance check is: A short benign delay does not page staff while a sustained backlog triggers the documented severity.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A production Spark query is slow and its stage graph shows one task running far longer than all peers. The corresponding measure there would be: Inspect the Spark UI DAG and skewed-key distribution before changing cluster size. The stated situation instead calls for: Define meaningful latency, error and backlog thresholds with alert routing based on the business SLO.
C:This alternative primarily addresses a different Azure Databricks problem: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. The corresponding measure there would be: Use caching only for beneficial reuse and release persisted state when no longer needed. The stated situation instead calls for: Define meaningful latency, error and backlog thresholds with alert routing based on the business SLO.
D:This alternative primarily addresses a different Azure Databricks problem: A new Delta table maintenance job combines repeated OPTIMIZE and VACUUM at every microbatch even though changes are tiny. The corresponding measure there would be: Set a measured maintenance cadence or evaluate supported predictive optimization for eligible managed tables. The stated situation instead calls for: Define meaningful latency, error and backlog thresholds with alert routing based on the business SLO.
Question 652
An Azure Databricks architect reviews the following problem: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. What should the team implement FIRST?
- Register the structured dataset as an appropriate managed Delta table rather than treating the volume itself as a SQL table.
- Create a team-specific schema with ownership or delegated creation grants limited to that namespace.
- Use fully qualified names and a controlled default namespace in deployment SQL and notebooks.
- Create a Unity Catalog view with approved permissions and verify underlying access semantics.
Explanation
Correct Answer
C:The most appropriate action is: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks. It addresses the stated condition: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. The technical basis is: Explicit namespace resolution makes deployment deterministic across different workspaces. Without this control, an environment-default schema can route production data definitions into an incorrect catalog. A direct acceptance check is: The same deployment command creates objects only in its designated staging or production namespace.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A team exposes structured transaction data as files in a volume but wants SQL analytics and ACID MERGE behavior. The corresponding measure there would be: Register the structured dataset as an appropriate managed Delta table rather than treating the volume itself as a SQL table. The stated situation instead calls for: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks.
B:This alternative primarily addresses a different Azure Databricks problem: A newly onboarded product team wants to create its own tables but should not have administration rights over every catalog. The corresponding measure there would be: Create a team-specific schema with ownership or delegated creation grants limited to that namespace. The stated situation instead calls for: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks.
D:This alternative primarily addresses a different Azure Databricks problem: An analyst wants to expose a filtered projection of a governed table without copying sensitive source rows. The corresponding measure there would be: Create a Unity Catalog view with approved permissions and verify underlying access semantics. The stated situation instead calls for: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks.
Question 653
A Databricks engineer recommends: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. It responds to: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. What underlying mechanism BEST explains why?
- Security of a view depends on the complete authorization path, not merely its SELECT projection.
- Managed identity authentication avoids exposing reusable static secrets and ties authorization to a governed identity.
- Object access can require permission to traverse its parent hierarchy as well as read the child.
- Row-level security evaluates access rules at query time rather than relying on users to remember a WHERE clause.
Explanation
Correct Answer
B:The decisive mechanism is: Managed identity authentication avoids exposing reusable static secrets and ties authorization to a governed identity. That explains the selected action: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. In the original scenario: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. The specific unmanaged risk is: A copied notebook may leak storage access keys beyond the intended data-processing environment. Validate with: The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. Its targeted response is: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. The current case is governed more directly by: Managed identity authentication avoids exposing reusable static secrets and ties authorization to a governed identity.
C:This principle concerns a separate data-engineering condition: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. Its targeted response is: Check required parent catalog and schema usage privileges alongside the table SELECT grant. The current case is governed more directly by: Managed identity authentication avoids exposing reusable static secrets and ties authorization to a governed identity.
D:This principle concerns a separate data-engineering condition: A user must see only the East region rows of a common sales table while managers see all territories. Its targeted response is: Configure a tested Unity Catalog row filter or suitable ABAC policy based on the authorized identity. The current case is governed more directly by: Managed identity authentication avoids exposing reusable static secrets and ties authorization to a governed identity.
Question 654
A Databricks engineer recommends: Include an integration test using actual Delta table semantics and representative source changes. It responds to: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. What underlying mechanism BEST explains why?
- Source control only provides operational truth when actual resource settings match the approved definition.
- Reproducible deployments require versioned execution dependencies as well as application code.
- Version control and code review establish provenance and repeatable release history.
- Storage-layer transaction behavior must be tested in addition to pure function outputs.
Explanation
Correct Answer
D:The decisive mechanism is: Storage-layer transaction behavior must be tested in addition to pure function outputs. That explains the selected action: Include an integration test using actual Delta table semantics and representative source changes. In the original scenario: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. The specific unmanaged risk is: Unverified MERGE conditions can overwrite valid history despite passing mocked unit tests. Validate with: An integration fixture with historical updates yields exactly the intended target versions.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. Its targeted response is: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. The current case is governed more directly by: Storage-layer transaction behavior must be tested in addition to pure function outputs.
B:This principle concerns a separate data-engineering condition: A team cannot reproduce a prior release because package versions are resolved dynamically during deployment. Its targeted response is: Pin package and runtime versions in the governed release artifact and record its dependency manifest. The current case is governed more directly by: Storage-layer transaction behavior must be tested in addition to pure function outputs.
C:This principle concerns a separate data-engineering condition: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. Its targeted response is: Store deployment source in Git with reviewed branches and pull requests before promoting changes. The current case is governed more directly by: Storage-layer transaction behavior must be tested in addition to pure function outputs.
Question 655
An operator introduces: Reevaluate data layout using representative event-time filters and a suitable clustering key. The situation is: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. Which validation should be required before signoff?
- Two views return consistent key rows while their documented alias columns remain stable.
- Two successive batches load only new records while preserved history and counts reconcile.
- The top event-time queries show improved data skipping and reconciled row counts.
- Sample invoice lines reconcile exactly to the fact table and roll up to the approved daily total.
Explanation
Correct Answer
C:The strongest acceptance proof is: The top event-time queries show improved data skipping and reconciled row counts. It specifically verifies: Reevaluate data layout using representative event-time filters and a suitable clustering key. The original issue was: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. The underlying mechanism is: Physical layout should match selective consumer predicates rather than convenience of ingestion. Without it, A mismatched partition scheme forces broad scans across unrelated arrival-day files.
Incorrect Answers
A:This result would validate a different measure: Expose stable SQL views over a governed base table when only presentation aliases differ. That is relevant to the distinct problem: A data product creates multiple physical copies of a curated dimension because teams need different column names. Here the acceptance criterion is: The top event-time queries show improved data skipping and reconciled row counts.
B:This result would validate a different measure: Choose incremental append or merge based on immutable versus mutable source behavior. That is relevant to the distinct problem: A raw event lake contains append-only records but a developer chooses daily full overwrite of the curated Delta table. Here the acceptance criterion is: The top event-time queries show improved data skipping and reconciled row counts.
D:This result would validate a different measure: Define fact-table grain at the required transaction or line-item level before aggregation. That is relevant to the distinct problem: A facts table groups product sales at daily level although auditors must inspect individual transaction adjustments. Here the acceptance criterion is: The top event-time queries show improved data skipping and reconciled row counts.
Question 656
A production data platform experiences this condition: A raw event lake contains append-only records but a developer chooses daily full overwrite of the curated Delta table. Which targeted measure should be selected?
- Design a conformed star schema with explicit fact grain and unique dimension keys.
- Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys.
- Choose incremental append or merge based on immutable versus mutable source behavior.
- Implement the required SCD Type 1 overwrite with stable business keys and validated updates.
Explanation
Correct Answer
C:The most appropriate action is: Choose incremental append or merge based on immutable versus mutable source behavior. It addresses the stated condition: A raw event lake contains append-only records but a developer chooses daily full overwrite of the curated Delta table. The technical basis is: Ingestion strategy should match whether source records can be corrected or deleted. Without this control, unnecessary overwrites increase compute cost and can cause data loss during partial reruns. A direct acceptance check is: Two successive batches load only new records while preserved history and counts reconcile.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A finance dashboard needs monthly revenue by customer and must join customer dimensions without multiplying facts. The corresponding measure there would be: Design a conformed star schema with explicit fact grain and unique dimension keys. The stated situation instead calls for: Choose incremental append or merge based on immutable versus mutable source behavior.
B:This alternative primarily addresses a different Azure Databricks problem: A retail customer table changes delivery address repeatedly but analysts must reconstruct the address known at any prior invoice date. The corresponding measure there would be: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys. The stated situation instead calls for: Choose incremental append or merge based on immutable versus mutable source behavior.
D:This alternative primarily addresses a different Azure Databricks problem: A reference table stores only the latest airport name and business users explicitly do not need historical values. The corresponding measure there would be: Implement the required SCD Type 1 overwrite with stable business keys and validated updates. The stated situation instead calls for: Choose incremental append or merge based on immutable versus mutable source behavior.
Question 657
The team chooses: Define meaningful latency, error and backlog thresholds with alert routing based on the business SLO. Its observed issue is: An alert triggers on every harmless microbatch delay while real hour-long ingestion stalls go unnoticed. What is the strongest technical basis?
- Alert quality depends on actionable thresholds and distinguishing transient variation from sustained failure.
- Driver memory is not an unlimited sink for results of distributed computation.
- A single hot partition can dominate a distributed stage despite idle executor capacity.
- File compaction reduces metadata and small-file overhead without changing logical table records.
Explanation
Correct Answer
A:The decisive mechanism is: Alert quality depends on actionable thresholds and distinguishing transient variation from sustained failure. That explains the selected action: Define meaningful latency, error and backlog thresholds with alert routing based on the business SLO. In the original scenario: An alert triggers on every harmless microbatch delay while real hour-long ingestion stalls go unnoticed. The specific unmanaged risk is: Excessive false alerts can obscure serious freshness incidents. Validate with: A short benign delay does not page staff while a sustained backlog triggers the documented severity.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A Spark join reads large inputs but the driver reports failures after an analyst calls collect() on the result. Its targeted response is: Keep large results distributed and replace driver collection with bounded sampling or distributed writes. The current case is governed more directly by: Alert quality depends on actionable thresholds and distinguishing transient variation from sustained failure.
C:This principle concerns a separate data-engineering condition: A production Spark query is slow and its stage graph shows one task running far longer than all peers. Its targeted response is: Inspect the Spark UI DAG and skewed-key distribution before changing cluster size. The current case is governed more directly by: Alert quality depends on actionable thresholds and distinguishing transient variation from sustained failure.
D:This principle concerns a separate data-engineering condition: A Delta table contains millions of tiny files after frequent microbatch updates and SQL scans spend time opening files. Its targeted response is: Run supported OPTIMIZE or predictive optimization and validate file-size distribution and query cost. The current case is governed more directly by: Alert quality depends on actionable thresholds and distinguishing transient variation from sustained failure.
Question 658
For this Microsoft DP-750 case: A team turns on every performance setting for a workload without benchmarking whether disk spills or network shuffle dominate runtime. Which design or operational response BEST fits?
- Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations.
- Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data.
- Apply suitable compute access modes, policies and entitlements that restrict who can attach or modify shared compute.
- Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution.
Explanation
Correct Answer
B:The most appropriate action is: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data. It addresses the stated condition: A team turns on every performance setting for a workload without benchmarking whether disk spills or network shuffle dominate runtime. The technical basis is: Performance settings should follow measured bottlenecks rather than an assumption that each toggle is beneficial. Without this control, unmeasured tuning changes can hide the original bottleneck or increase compute costs. A direct acceptance check is: Before-after measurements report comparable inputs, stage timings, spills and total cost.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A feature-engineering notebook requires GPU libraries but the data cleaning jobs never use accelerators. The corresponding measure there would be: Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations. The stated situation instead calls for: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data.
C:This alternative primarily addresses a different Azure Databricks problem: A multi-team interactive cluster permits users to attach arbitrary unapproved libraries and run notebooks under broad shared privileges. The corresponding measure there would be: Apply suitable compute access modes, policies and entitlements that restrict who can attach or modify shared compute. The stated situation instead calls for: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data.
D:This alternative primarily addresses a different Azure Databricks problem: A nightly batch transformation uses a continuously running all-purpose cluster even though no analyst interacts with the workload between runs. The corresponding measure there would be: Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution. The stated situation instead calls for: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data.
Question 659
An operator introduces: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality. The situation is: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. Which validation should be required before signoff?
- The external reader loads approved columns and a documented compatibility test passes.
- The business key resolves to one current row after an update and no unintended duplicate joins occur.
- File-count and query-profile comparisons show fewer fragments and faster targeted scans.
- A supported optimization command completes and query plans show the chosen layout works.
Explanation
Correct Answer
C:The strongest acceptance proof is: File-count and query-profile comparisons show fewer fragments and faster targeted scans. It specifically verifies: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality. The original issue was: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. The underlying mechanism is: High-cardinality partition columns can fragment file layout and increase metadata overhead. Without it, excessive partitions create small files and poor query planning without useful pruning.
Incorrect Answers
A:This result would validate a different measure: Evaluate Parquet or supported open-table formats against reader compatibility and mutation requirements. That is relevant to the distinct problem: An external sharing integration needs interoperable columnar read files but not native Delta updates. Here the acceptance criterion is: File-count and query-profile comparisons show fewer fragments and faster targeted scans.
B:This result would validate a different measure: Implement the required SCD Type 1 overwrite with stable business keys and validated updates. That is relevant to the distinct problem: A reference table stores only the latest airport name and business users explicitly do not need historical values. Here the acceptance criterion is: File-count and query-profile comparisons show fewer fragments and faster targeted scans.
D:This result would validate a different measure: Choose one compatible data layout strategy based on table format, platform support and query evidence. That is relevant to the distinct problem: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. Here the acceptance criterion is: File-count and query-profile comparisons show fewer fragments and faster targeted scans.
Question 660
A production data team leaves out: Choose one compatible data layout strategy based on table format, platform support and query evidence. Its scenario is: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. Which failure mode is MOST relevant?
- Duplicating physical dimensions can leave teams on inconsistent updates or retention periods.
- Poorly chosen keys increase full scans and maintenance overhead as traffic grows.
- Mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations.
- Assuming every engine can use every feature can result in invalid writes or unreadable metadata.
Explanation
Correct Answer
C:The direct residual exposure is: Mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations. The triggering condition is: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. The omitted safeguard is: Choose one compatible data layout strategy based on table format, platform support and query evidence. This matters because: Liquid clustering and traditional ZORDER/partitioning have compatibility constraints and different maintenance paths. A corrective test would show: A supported optimization command completes and query plans show the chosen layout works.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A data product creates multiple physical copies of a curated dimension because teams need different column names. Its preventative action would be: Expose stable SQL views over a governed base table when only presentation aliases differ. The most direct exposure in the current scenario is: Mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations.
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: Mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations.
D: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: Mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations.