Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 10
Question 90
For this Microsoft DP-750 case: A pipeline joins a huge fact table with a tiny dimension and a normal shuffle join creates excessive network traffic. Which design or operational response BEST fits?
- Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans.
- Align compatible schemas and use name-based union semantics with explicit type checks.
- Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics.
- Use an incremental append pattern with suitable deduplication when source events cannot change.
Explanation
Correct Answer
A:The most appropriate action is: Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans. It addresses the stated condition: A pipeline joins a huge fact table with a tiny dimension and a normal shuffle join creates excessive network traffic. The technical basis is: Spark can reduce shuffle costs by broadcasting a sufficiently small dimension where appropriate. Without this control, blindly broadcasting a large table can exhaust executor memory while unnecessary shuffles slow joins. A direct acceptance check is: Spark UI shows reduced shuffle bytes and matching results without executor out-of-memory.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. The corresponding measure there would be: Align compatible schemas and use name-based union semantics with explicit type checks. The stated situation instead calls for: Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans.
C:This alternative primarily addresses a different Azure Databricks problem: An analyst must find records present in the source system but absent in a target migration. The corresponding measure there would be: Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics. The stated situation instead calls for: Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans.
D:This alternative primarily addresses a different Azure Databricks problem: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. The corresponding measure there would be: Use an incremental append pattern with suitable deduplication when source events cannot change. The stated situation instead calls for: Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans.
Question 91
The team implements: Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics. The original problem is: An analyst must find records present in the source system but absent in a target migration. Which test MOST convincingly demonstrates correctness?
- A sample includes all approved categories and status totals reconcile to source rows.
- A controlled money sample matches expected exact decimal totals and rejects malformed amounts.
- A controlled source sample produces exactly the permitted group keys and reconciled sums.
- The gap report returns seeded source-only records and excludes matched records.
Explanation
Correct Answer
D:The strongest acceptance proof is: The gap report returns seeded source-only records and excludes matched records. It specifically verifies: Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics. The original issue was: An analyst must find records present in the source system but absent in a target migration. The underlying mechanism is: Set difference helps identify migration gaps without retrieving matched records. Without it, an inner join hides precisely the missing records the reconciliation needs to surface.
Incorrect Answers
A:This result would validate a different measure: Apply a controlled pivot with a defined set of expected categories and aggregation rule. That is relevant to the distinct problem: A quality report needs one column for each product status category but stores status as separate rows. Here the acceptance criterion is: The gap report returns seeded source-only records and excludes matched records.
B:This result would validate a different measure: Parse and cast monetary values to a suitable decimal type with invalid-value handling. That is relevant to the distinct problem: A finance field arrives as a string with currency symbols and the team aggregates it lexicographically. Here the acceptance criterion is: The gap report returns seeded source-only records and excludes matched records.
C:This result would validate a different measure: Apply the required filters and join conditions before aggregation and validate authorized output groups. That is relevant to the distinct problem: An analyst calculates total revenue grouped by country but a join includes countries not approved for reporting. Here the acceptance criterion is: The gap report returns seeded source-only records and excludes matched records.
Question 92
The team chooses: Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations. Its observed issue is: A feature-engineering notebook requires GPU libraries but the data cleaning jobs never use accelerators. What is the strongest technical basis?
- GPU resources are specialized and do not automatically accelerate every Spark or SQL transformation.
- Photon can accelerate many supported SQL and DataFrame operations but requires workload-specific measurements.
- Performance settings should follow measured bottlenecks rather than an assumption that each toggle is beneficial.
- Compute isolation reduces interference between unrelated application environments and execution libraries.
Explanation
Correct Answer
A:The decisive mechanism is: GPU resources are specialized and do not automatically accelerate every Spark or SQL transformation. That explains the selected action: Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations. In the original scenario: A feature-engineering notebook requires GPU libraries but the data cleaning jobs never use accelerators. The specific unmanaged risk is: A default GPU cluster may charge premium rates while most tasks leave accelerators unused. Validate with: Resource telemetry shows accelerator use where needed and CPU jobs satisfy their SLA at lower cost.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A Spark SQL pipeline spends most of its time executing wide joins and aggregations but the team has not evaluated a compatible vectorized execution engine. Its targeted response is: Benchmark Photon on a supported runtime with representative queries and compare cost, latency and correctness. The current case is governed more directly by: GPU resources are specialized and do not automatically accelerate every Spark or SQL transformation.
C:This principle concerns a separate data-engineering condition: A team turns on every performance setting for a workload without benchmarking whether disk spills or network shuffle dominate runtime. Its targeted response is: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data. The current case is governed more directly by: GPU resources are specialized and do not automatically accelerate every Spark or SQL transformation.
D: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: GPU resources are specialized and do not automatically accelerate every Spark or SQL transformation.
Question 93
The team chooses: Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities. Its observed issue is: A data pipeline creates a physical table for a reporting transformation that would be better maintained as a query definition. What is the strongest technical basis?
- Abstraction views can separate a consumer-facing contract from internal physical table evolution.
- Delegating within a governed schema supports self-service without tenant-wide administrative access.
- Governance of views includes ownership, discovery and authorization just as for tables.
- The object type should reflect whether data is computed on read or persisted and maintained.
Explanation
Correct Answer
D:The decisive mechanism is: The object type should reflect whether data is computed on read or persisted and maintained. That explains the selected action: Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities. In the original scenario: A data pipeline creates a physical table for a reporting transformation that would be better maintained as a query definition. The specific unmanaged risk is: Persisting every intermediate query can create stale and duplicate datasets. Validate with: An architecture test proves the selected object's refresh and query cost meet defined needs.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. Its targeted response is: Define a stable contract through managed views and test compatibility before changing source objects. The current case is governed more directly by: The object type should reflect whether data is computed on read or persisted and maintained.
B:This principle concerns a separate data-engineering condition: A newly onboarded product team wants to create its own tables but should not have administration rights over every catalog. Its targeted response is: Create a team-specific schema with ownership or delegated creation grants limited to that namespace. The current case is governed more directly by: The object type should reflect whether data is computed on read or persisted and maintained.
C:This principle concerns a separate data-engineering condition: A central team creates global views that hide source objects but forgets to document ownership and access grants. Its targeted response is: Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema. The current case is governed more directly by: The object type should reflect whether data is computed on read or persisted and maintained.
Question 94
An Azure Databricks architect reviews the following problem: A lineage graph shows no relationship for data loaded outside the monitored platform and the team assumes the dataset has no upstream dependency. What should the team implement FIRST?
- Design record-level retention and external legal-hold workflows appropriate to the applicable policy.
- Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation.
- Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance.
- Compare table-level masks against centrally governed ABAC coverage and identify missing assignments.
Explanation
Correct Answer
C:The most appropriate action is: Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance. It addresses the stated condition: A lineage graph shows no relationship for data loaded outside the monitored platform and the team assumes the dataset has no upstream dependency. The technical basis is: Automatic lineage visibility has collection boundaries and does not imply every real-world dependency is recorded. Without this control, uncaptured external ingestion may lead to incomplete impact analysis and unsafe upstream changes. A direct acceptance check is: A provenance review identifies both captured Databricks edges and documented external system dependencies.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. The corresponding measure there would be: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. The stated situation instead calls for: Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance.
B:This alternative primarily addresses a different Azure Databricks problem: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. The corresponding measure there would be: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. The stated situation instead calls for: Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance.
D:This alternative primarily addresses a different Azure Databricks problem: A user creates a column mask on a single table and assumes all tables with the same field name are protected. The corresponding measure there would be: Compare table-level masks against centrally governed ABAC coverage and identify missing assignments. The stated situation instead calls for: Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance.
Question 95
An operator introduces: Register the structured dataset as an appropriate managed Delta table rather than treating the volume itself as a SQL table. The situation is: A team exposes structured transaction data as files in a volume but wants SQL analytics and ACID MERGE behavior. Which validation should be required before signoff?
- An architecture test proves the selected object's refresh and query cost meet defined needs.
- A source update followed by the documented refresh produces reconciled aggregate totals.
- A controlled MERGE and SQL query succeed against the governed Delta table with expected records.
- A capability test documents supported query and write operations and prevents unsupported mutations.
Explanation
Correct Answer
C:The strongest acceptance proof is: A controlled MERGE and SQL query succeed against the governed Delta table with expected records. It specifically verifies: Register the structured dataset as an appropriate managed Delta table rather than treating the volume itself as a SQL table. The original issue was: A team exposes structured transaction data as files in a volume but wants SQL analytics and ACID MERGE behavior. The underlying mechanism is: Volumes organize files, whereas Delta tables offer tabular metadata and transactional query operations. Without it, file-only storage may lack table-level transactional update and discoverability semantics.
Incorrect Answers
A:This result would validate a different measure: Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities. That is relevant to the distinct problem: A data pipeline creates a physical table for a reporting transformation that would be better maintained as a query definition. Here the acceptance criterion is: A controlled MERGE and SQL query succeed against the governed Delta table with expected records.
B:This result would validate a different measure: Create an eligible materialized view or managed derived table with appropriate refresh and access rules. That is relevant to the distinct problem: A BI group needs to query a materialized aggregate while the source transaction Delta table changes hourly. Here the acceptance criterion is: A controlled MERGE and SQL query succeed against the governed Delta table with expected records.
D:This result would validate a different measure: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. That is relevant to the distinct problem: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. Here the acceptance criterion is: A controlled MERGE and SQL query succeed against the governed Delta table with expected records.
Question 96
An implementation skips: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. Engineers are observing: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. What consequence is MOST likely?
- An upgrade or runaway task on the shared cluster can compromise finance pipeline availability.
- Overprovisioned validation can cost more in startup overhead than the data being checked warrants.
- A stream may stop unexpectedly and leave event consumption behind its permitted freshness objective.
- A fixed undersized cluster misses month-end deadlines while an oversized fixed cluster wastes daily spend.
Explanation
Correct Answer
C:The direct residual exposure is: A stream may stop unexpectedly and leave event consumption behind its permitted freshness objective. The triggering condition is: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. The omitted safeguard is: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. This matters because: Auto-termination choices must reflect continuously running streams differently from one-shot notebooks. A corrective test would show: A quiet-period rehearsal retains the required streaming operation and subsequent events process without missed offsets.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A notebook pipeline uses a shared cluster with unstable third-party dependencies while a critical finance job needs controlled isolation. Its preventative action would be: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions. The most direct exposure in the current scenario is: A stream may stop unexpectedly and leave event consumption behind its permitted freshness objective.
B:This failure mode belongs mainly to another situation: A data team uses a high-power job cluster for a low-volume data-quality check that spends most runtime starting the cluster. Its preventative action would be: Separate the small validation into an eligible lightweight or serverless task and measure total end-to-end runtime. The most direct exposure in the current scenario is: A stream may stop unexpectedly and leave event consumption behind its permitted freshness objective.
D:This failure mode belongs mainly to another situation: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. Its preventative action would be: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. The most direct exposure in the current scenario is: A stream may stop unexpectedly and leave event consumption behind its permitted freshness objective.
Question 97
A data product owner adopts: Expose stable SQL views over a governed base table when only presentation aliases differ. The reason is: A data product creates multiple physical copies of a curated dimension because teams need different column names. What observed result BEST proves effectiveness?
- A replay from a preserved source batch reproduces the expected silver and gold data after a code fix.
- Two views return consistent key rows while their documented alias columns remain stable.
- A supported optimization command completes and query plans show the chosen layout works.
- Representative business queries return consistent region totals with an acceptable plan.
Explanation
Correct Answer
B:The strongest acceptance proof is: Two views return consistent key rows while their documented alias columns remain stable. It specifically verifies: Expose stable SQL views over a governed base table when only presentation aliases differ. The original issue was: A data product creates multiple physical copies of a curated dimension because teams need different column names. The underlying mechanism is: Views can provide different consumer contracts without unnecessary data duplication. Without it, duplicating physical dimensions can leave teams on inconsistent updates or retention periods.
Incorrect Answers
A:This result would validate a different measure: Keep a governed raw or bronze representation before applying irreversible cleansing into silver and gold. That is relevant to the distinct problem: A bronze ingestion layer stores only final transformed values and loses raw source fields needed for incident replay. Here the acceptance criterion is: Two views return consistent key rows while their documented alias columns remain stable.
C: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: Two views return consistent key rows while their documented alias columns remain stable.
D:This result would validate a different measure: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. That is relevant to the distinct problem: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. Here the acceptance criterion is: Two views return consistent key rows while their documented alias columns remain stable.
Question 98
The recommended measure is: Transfer ownership through approved governance workflow and review grants after reassignment. The operational context is: An audit asks who owns a catalog table but object ownership still points to an inactive employee. Which data engineering concept applies?
- Governance metadata is useful only when ownership and classification are kept current.
- Ordinary table replacement does not automatically constitute defensible preservation of historical legal records.
- Security governance requires attributable administrative activity and durable evidence.
- Governance depends on maintained object ownership as teams and responsibilities change.
Explanation
Correct Answer
D:The decisive mechanism is: Governance depends on maintained object ownership as teams and responsibilities change. That explains the selected action: Transfer ownership through approved governance workflow and review grants after reassignment. In the original scenario: An audit asks who owns a catalog table but object ownership still points to an inactive employee. The specific unmanaged risk is: An orphaned ownership chain can delay access review or emergency remediation. Validate with: The designated active service or steward owns the object and prior inappropriate rights are removed.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A central repository contains schemas with missing column owners and no sensitivity classifications. Its targeted response is: Implement a catalog stewardship process to review metadata and governed tags at dataset publication. The current case is governed more directly by: Governance depends on maintained object ownership as teams and responsibilities change.
B:This principle concerns a separate data-engineering condition: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. Its targeted response is: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. The current case is governed more directly by: Governance depends on maintained object ownership as teams and responsibilities change.
C:This principle concerns a separate data-engineering condition: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. Its targeted response is: Configure supported Databricks audit logging and route relevant events to a secured retention destination. The current case is governed more directly by: Governance depends on maintained object ownership as teams and responsibilities change.
Question 99
An implementation skips: Use a Delta MERGE keyed by SKU with appropriate matched-update and not-matched-insert logic. Engineers are observing: A product catalog receives corrections for existing SKUs plus entirely new items on each incremental load. What consequence is MOST likely?
- Blind append creates multiple current versions and breaks consumer joins.
- An unrestricted join can multiply keys and exaggerate customer counts.
- Position-based union may quietly corrupt data when column positions differ.
- Orders near midnight may be reported under the wrong business day.
Explanation
Correct Answer
A:The direct residual exposure is: Blind append creates multiple current versions and breaks consumer joins. The triggering condition is: A product catalog receives corrections for existing SKUs plus entirely new items on each incremental load. The omitted safeguard is: Use a Delta MERGE keyed by SKU with appropriate matched-update and not-matched-insert logic. This matters because: MERGE combines inserts and updates atomically against a keyed target. A corrective test would show: Two consecutive loads yield one current row per SKU, including corrected price and new items.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A team wants only customer IDs present in both systems but uses an inner join that multiplies repeated rows. Its preventative action would be: Use an appropriate intersect or semi-join operation based on set and duplicate requirements. The most direct exposure in the current scenario is: Blind append creates multiple current versions and breaks consumer joins.
C: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: Blind append creates multiple current versions and breaks consumer joins.
D:This failure mode belongs mainly to another situation: A date field mixes UTC timestamps and local store times but a pipeline groups all values by the raw date string. Its preventative action would be: Normalize time zone semantics before extracting business-local reporting dates. The most direct exposure in the current scenario is: Blind append creates multiple current versions and breaks consumer joins.
Question 100
The design team proposes: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. The situation is: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. Which technical principle justifies the decision?
- Tag-based access control relies on trusted management of the tags themselves.
- Data sharing scope should minimize disclosed fields and rows and specify a refresh contract.
- Ordinary table replacement does not automatically constitute defensible preservation of historical legal records.
- Retention policy must account for physical file cleanup as well as logical table content.
Explanation
Correct Answer
B:The decisive mechanism is: Data sharing scope should minimize disclosed fields and rows and specify a refresh contract. That explains the selected action: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. In the original scenario: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. The specific unmanaged risk is: Sharing raw transaction tables can disclose protected customer attributes unnecessarily. Validate with: A test recipient reads the expected daily aggregate and cannot enumerate underlying detailed transaction records.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. Its targeted response is: Restrict governed-tag administration and audit changes to protected metadata. The current case is governed more directly by: Data sharing scope should minimize disclosed fields and rows and specify a refresh contract.
C:This principle concerns a separate data-engineering condition: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. Its targeted response is: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. The current case is governed more directly by: Data sharing scope should minimize disclosed fields and rows and specify a refresh contract.
D:This principle concerns a separate data-engineering condition: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. Its targeted response is: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. The current case is governed more directly by: Data sharing scope should minimize disclosed fields and rows and specify a refresh contract.