Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 30
Question 290
A data engineering team faces this Azure Databricks requirement: A regulated pipeline needs consistent transaction boundaries across multiple table writes but updates are published one at a time. Which action is MOST appropriate?
- Design a compatible atomic publication or versioned readiness contract so consumers see consistent results.
- Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph.
- Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed.
- Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid.
Explanation
Correct Answer
A:The most appropriate action is: Design a compatible atomic publication or versioned readiness contract so consumers see consistent results. It addresses the stated condition: A regulated pipeline needs consistent transaction boundaries across multiple table writes but updates are published one at a time. The technical basis is: Multi-table orchestration requires a defined consistency point even if each individual Delta write is atomic. Without this control, readers can combine incompatible versions when related tables update independently. A direct acceptance check is: A controlled consumer test sees only one approved publication version across dependent datasets.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. The corresponding measure there would be: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. The stated situation instead calls for: Design a compatible atomic publication or versioned readiness contract so consumers see consistent results.
C:This alternative primarily addresses a different Azure Databricks problem: A sales pipeline aggregates gold metrics before the bronze ingestion task finishes and occasionally reports incomplete totals. The corresponding measure there would be: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed. The stated situation instead calls for: Design a compatible atomic publication or versioned readiness contract so consumers see consistent results.
D:This alternative primarily addresses a different Azure Databricks problem: A bulk repair executes all pipeline tasks again even when only the final reporting notebook failed. The corresponding measure there would be: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid. The stated situation instead calls for: Design a compatible atomic publication or versioned readiness contract so consumers see consistent results.
Question 291
An operator introduces: Wait for or explicitly verify required external or asynchronous work before reporting task success. The situation is: A job is successful in the orchestrator but the business target is not updated because the notebook returns before async work completes. Which validation should be required before signoff?
- A scheduled run succeeds under the named service principal after the former owner account is disabled.
- A test run finishes only after the target watermark and expected row counts are confirmed.
- A staged predecessor failure shows the approved downstream skip and cleanup path in run history.
- A failed downstream task is repaired without repeating successful non-idempotent upstream work.
Explanation
Correct Answer
B:The strongest acceptance proof is: A test run finishes only after the target watermark and expected row counts are confirmed. It specifically verifies: Wait for or explicitly verify required external or asynchronous work before reporting task success. The original issue was: A job is successful in the orchestrator but the business target is not updated because the notebook returns before async work completes. The underlying mechanism is: Task success must correspond to the completion of required data side effects, not just function invocation. Without it, premature success can start downstream tasks against incomplete writes.
Incorrect Answers
A:This result would validate a different measure: Assign a dedicated run-as identity with durable scoped grants and an ownership review. That is relevant to the distinct problem: A job uses a service principal that loses access to the destination schema when an employee leaves. Here the acceptance criterion is: A test run finishes only after the target watermark and expected row counts are confirmed.
C:This result would validate a different measure: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. That is relevant to the distinct problem: A job owner cannot explain why a task skipped execution after a predecessor failed. Here the acceptance criterion is: A test run finishes only after the target watermark and expected row counts are confirmed.
D: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 test run finishes only after the target watermark and expected row counts are confirmed.
Question 292
For this Microsoft DP-750 case: A job owner cannot explain why a task skipped execution after a predecessor failed. Which design or operational response BEST fits?
- Review explicit dependency and run-if settings and validate skip behavior through a staged failure.
- Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant.
- Assign a dedicated run-as identity with durable scoped grants and an ownership review.
- Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger.
Explanation
Correct Answer
A:The most appropriate action is: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. It addresses the stated condition: A job owner cannot explain why a task skipped execution after a predecessor failed. The technical basis is: Job task state transitions follow dependency and conditional execution rules. Without this control, misunderstood skip conditions can leave expected cleanup or alerts unexecuted. A direct acceptance check is: A staged predecessor failure shows the approved downstream skip and cleanup path in run history.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A business report must refresh daily at 06:00 in a defined local time zone but a developer schedules it in UTC without conversion. The corresponding measure there would be: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant. The stated situation instead calls for: Review explicit dependency and run-if settings and validate skip behavior through a staged failure.
C: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: Review explicit dependency and run-if settings and validate skip behavior through a staged failure.
D:This alternative primarily addresses a different Azure Databricks problem: An ingestion job requires a one-time backfill without changing the future daily production schedule. The corresponding measure there would be: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger. The stated situation instead calls for: Review explicit dependency and run-if settings and validate skip behavior through a staged failure.
Question 293
A data engineering team faces this Azure Databricks requirement: A pipeline ingests Event Hubs messages into a bronze table but never captures the partition, offset or event timestamp. Which action is MOST appropriate?
- Configure supported schema evolution or rescued-data handling with explicit compatibility review.
- Persist necessary source metadata and checkpoint lineage for troubleshooting and replay.
- Use a snapshot replacement or keyed MERGE strategy instead of appending every full snapshot as new records.
- Store checkpoint and schema tracking files in durable protected locations with retention matching the stream lifecycle.
Explanation
Correct Answer
B:The most appropriate action is: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay. It addresses the stated condition: A pipeline ingests Event Hubs messages into a bronze table but never captures the partition, offset or event timestamp. The technical basis is: Streaming source metadata supports provenance and exact-range incident investigation. Without this control, A failed data-quality rule cannot be traced back to the event-bus record that produced it. A direct acceptance check is: A sampled bronze row links to the expected stream partition and source event time.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A file feed introduces an unexpected optional column and the stream fails after the first changed file. The corresponding measure there would be: Configure supported schema evolution or rescued-data handling with explicit compatibility review. The stated situation instead calls for: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay.
C:This alternative primarily addresses a different Azure Databricks problem: A daily file load uses append-only mode for periodic snapshots of the same full inventory. The corresponding measure there would be: Use a snapshot replacement or keyed MERGE strategy instead of appending every full snapshot as new records. The stated situation instead calls for: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay.
D:This alternative primarily addresses a different Azure Databricks problem: A long-running ingestion job persists its checkpoint in the same temporary folder that daily cleanup deletes. The corresponding measure there would be: Store checkpoint and schema tracking files in durable protected locations with retention matching the stream lifecycle. The stated situation instead calls for: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay.
Question 294
A data product owner adopts: Apply a deterministic deduplication rule based on stable order identity and source version before aggregation. The reason is: An incoming orders table contains repeated order IDs because a vendor retransmits the same daily extract. What observed result BEST proves effectiveness?
- A controlled source sample produces exactly the permitted group keys and reconciled sums.
- Mixed-case, whitespace and non-ASCII test records resolve according to the documented mapping policy.
- A seeded repeated-ID sample yields one chosen current order version and reconciled totals.
- A seeded dataset retains zero-quantity items while rows with null quantities follow the documented rule.
Explanation
Correct Answer
C:The strongest acceptance proof is: A seeded repeated-ID sample yields one chosen current order version and reconciled totals. It specifically verifies: Apply a deterministic deduplication rule based on stable order identity and source version before aggregation. The original issue was: An incoming orders table contains repeated order IDs because a vendor retransmits the same daily extract. The underlying mechanism is: Deduplication should use meaningful business keys, not arbitrary full-row equality alone. Without it, duplicate orders inflate sales totals and can trigger incorrect downstream payouts.
Incorrect Answers
A: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: A seeded repeated-ID sample yields one chosen current order version and reconciled totals.
B:This result would validate a different measure: Define and test consistent trimming, Unicode normalization and case comparison for the business key. That is relevant to the distinct problem: A customer-name cleansing script uses an arbitrary lowercase conversion without preserving Unicode and leading/trailing whitespace rules. Here the acceptance criterion is: A seeded repeated-ID sample yields one chosen current order version and reconciled totals.
D: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: A seeded repeated-ID sample yields one chosen current order version and reconciled totals.
Question 295
A data product owner adopts: Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants. The reason is: An engineering pipeline attempts to insert records into a production Delta table using an account with SELECT only. What observed result BEST proves effectiveness?
- A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
- A privilege inspection shows the narrow parent usage grants and the contractor can query only the intended table.
- The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
- The writer inserts a validated test row and reader accounts are denied modification attempts.
Explanation
Correct Answer
D:The strongest acceptance proof is: The writer inserts a validated test row and reader accounts are denied modification attempts. It specifically verifies: Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants. The original issue was: An engineering pipeline attempts to insert records into a production Delta table using an account with SELECT only. The underlying mechanism is: Read and write operations require distinct Unity Catalog privileges and operating identities. Without it, giving all analysts write rights merely to repair one pipeline expands accidental corruption risk.
Incorrect Answers
A: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: The writer inserts a validated test row and reader accounts are denied modification attempts.
B:This result would validate a different measure: Check required parent catalog and schema usage privileges alongside the table SELECT grant. That is relevant to the distinct problem: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. Here the acceptance criterion is: The writer inserts a validated test row and reader accounts are denied modification attempts.
C:This result would validate a different measure: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. That is relevant to the distinct problem: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. Here the acceptance criterion is: The writer inserts a validated test row and reader accounts are denied modification attempts.
Question 296
An operator introduces: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. The situation is: A data-sharing project emails storage keys to an external partner for reading curated Delta results. Which validation should be required before signoff?
- A test recipient reads the expected daily aggregate and cannot enumerate underlying detailed transaction records.
- The partner reads only the approved shared table and fails to access a nonshared table.
- A publish-time check rejects missing required descriptions, owners and classification tags.
- A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
Explanation
Correct Answer
B:The strongest acceptance proof is: The partner reads only the approved shared table and fails to access a nonshared table. It specifically verifies: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. The original issue was: A data-sharing project emails storage keys to an external partner for reading curated Delta results. The underlying mechanism is: Delta Sharing can provide governed data access without distributing underlying storage account keys. Without it, long-lived shared storage credentials may expose unrelated files or survive contract termination.
Incorrect Answers
A:This result would validate a different measure: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. That is relevant to the distinct problem: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. Here the acceptance criterion is: The partner reads only the approved shared table and fails to access a nonshared table.
C:This result would validate a different measure: Implement a catalog stewardship process to review metadata and governed tags at dataset publication. That is relevant to the distinct problem: A central repository contains schemas with missing column owners and no sensitivity classifications. Here the acceptance criterion is: The partner reads only the approved shared table and fails to access a nonshared table.
D:This result would validate a different measure: Restrict governed-tag administration and audit changes to protected metadata. That is relevant to the distinct problem: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. Here the acceptance criterion is: The partner reads only the approved shared table and fails to access a nonshared table.
Question 297
The team chooses: Restrict governed-tag administration and audit changes to protected metadata. Its observed issue is: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. What is the strongest technical basis?
- Permission reviews should follow actual securable objects and their dependencies rather than name assumptions.
- Data lineage links producers, transformations and consumers where observed activity is supported.
- Data sharing scope should minimize disclosed fields and rows and specify a refresh contract.
- Tag-based access control relies on trusted management of the tags themselves.
Explanation
Correct Answer
D:The decisive mechanism is: Tag-based access control relies on trusted management of the tags themselves. That explains the selected action: Restrict governed-tag administration and audit changes to protected metadata. In the original scenario: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. The specific unmanaged risk is: Unauthorized retagging may neutralize masking or row restrictions on sensitive information. Validate with: A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. Its targeted response is: Reconcile catalog object identity, lineage and current grants after schema or owner changes. The current case is governed more directly by: Tag-based access control relies on trusted management of the tags themselves.
B:This principle concerns a separate data-engineering condition: An analyst wants to know which upstream pipeline produced a metric displayed in a board dashboard. Its targeted response is: Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage. The current case is governed more directly by: Tag-based access control relies on trusted management of the tags themselves.
C:This principle concerns a separate data-engineering condition: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. Its targeted response is: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. The current case is governed more directly by: Tag-based access control relies on trusted management of the tags themselves.
Question 298
The team chooses: Use supported Databricks secret access with least-privilege scope access and remove secret values from logs. Its observed issue is: An application uses an external Azure Key Vault secret scope but a notebook prints the secret into task logs. What is the strongest technical basis?
- Object discovery or BROWSE is not a grant to read its underlying data.
- Object access can require permission to traverse its parent hierarchy as well as read the child.
- Secret retrieval must be paired with permissions and safe handling to avoid disclosure after retrieval.
- Central data-plane access rules reduce reliance on every application path applying tenant filtering.
Explanation
Correct Answer
C:The decisive mechanism is: Secret retrieval must be paired with permissions and safe handling to avoid disclosure after retrieval. That explains the selected action: Use supported Databricks secret access with least-privilege scope access and remove secret values from logs. In the original scenario: An application uses an external Azure Key Vault secret scope but a notebook prints the secret into task logs. The specific unmanaged risk is: A protected secret can still leak through debug output or unrestricted notebook results. Validate with: The job authenticates successfully and audited logs contain no raw secret or token.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. Its targeted response is: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. The current case is governed more directly by: Secret retrieval must be paired with permissions and safe handling to avoid disclosure after retrieval.
B: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: Secret retrieval must be paired with permissions and safe handling to avoid disclosure after retrieval.
D:This principle concerns a separate data-engineering condition: A multi-tenant analytics table relies on application code to append customer_id filtering. Its targeted response is: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. The current case is governed more directly by: Secret retrieval must be paired with permissions and safe handling to avoid disclosure after retrieval.
Question 299
An operator introduces: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. The situation is: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. Which validation should be required before signoff?
- A simulated cleanup retains protected history and an audit maps the new duration to approved settings.
- A provenance review identifies both captured Databricks edges and documented external system dependencies.
- The partner reads only the approved shared table and fails to access a nonshared table.
- A publish-time check rejects missing required descriptions, owners and classification tags.
Explanation
Correct Answer
A:The strongest acceptance proof is: A simulated cleanup retains protected history and an audit maps the new duration to approved settings. It specifically verifies: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. The original issue was: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. The underlying mechanism is: Technical retention settings and organizational policy need an auditable, consistent lifecycle. Without it, old cleanup tasks can destroy files that the revised retention requirement still protects.
Incorrect Answers
B:This result would validate a different measure: Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance. That is relevant to the distinct problem: A lineage graph shows no relationship for data loaded outside the monitored platform and the team assumes the dataset has no upstream dependency. Here the acceptance criterion is: A simulated cleanup retains protected history and an audit maps the new duration to approved settings.
C:This result would validate a different measure: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. That is relevant to the distinct problem: A data-sharing project emails storage keys to an external partner for reading curated Delta results. Here the acceptance criterion is: A simulated cleanup retains protected history and an audit maps the new duration to approved settings.
D:This result would validate a different measure: Implement a catalog stewardship process to review metadata and governed tags at dataset publication. That is relevant to the distinct problem: A central repository contains schemas with missing column owners and no sensitivity classifications. Here the acceptance criterion is: A simulated cleanup retains protected history and an audit maps the new duration to approved settings.
Question 300
The team implements: Choose one compatible data layout strategy based on table format, platform support and query evidence. The original problem is: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. Which test MOST convincingly demonstrates correctness?
- Sample invoice lines reconcile exactly to the fact table and roll up to the approved daily total.
- A supported optimization command completes and query plans show the chosen layout works.
- A backdated invoice joins to the address valid on its transaction date while the current record shows the latest address.
- A controlled late event appears in the correct historical period according to the approved policy.
Explanation
Correct Answer
B:The strongest acceptance proof is: A supported optimization command completes and query plans show the chosen layout works. It specifically verifies: Choose one compatible data layout strategy based on table format, platform support and query evidence. The original issue was: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. The underlying mechanism is: Liquid clustering and traditional ZORDER/partitioning have compatibility constraints and different maintenance paths. Without it, mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations.
Incorrect Answers
A: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: A supported optimization command completes and query plans show the chosen layout works.
C:This result would validate a different measure: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys. That is relevant to the distinct problem: A retail customer table changes delivery address repeatedly but analysts must reconstruct the address known at any prior invoice date. Here the acceptance criterion is: A supported optimization command completes and query plans show the chosen layout works.
D:This result would validate a different measure: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. That is relevant to the distinct problem: A lakehouse receives sensor observations with event timestamps that arrive out of order. Here the acceptance criterion is: A supported optimization command completes and query plans show the chosen layout works.