Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 61
Question 600
During a lakehouse implementation review, engineers observe: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. What is the BEST next action?
- Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements.
- Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation.
- Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access.
- Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery.
Explanation
Correct Answer
B:The most appropriate action is: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. It addresses the stated condition: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. The technical basis is: Data sharing scope should minimize disclosed fields and rows and specify a refresh contract. Without this control, sharing raw transaction tables can disclose protected customer attributes unnecessarily. A direct acceptance check is: A test recipient reads the expected daily aggregate and cannot enumerate underlying detailed transaction records.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. The corresponding measure there would be: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. The stated situation instead calls for: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation.
C:This alternative primarily addresses a different Azure Databricks problem: A Delta Sharing recipient must stop receiving future updates after an agreement expires. The corresponding measure there would be: Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access. The stated situation instead calls for: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation.
D:This alternative primarily addresses a different Azure Databricks problem: A business glossary has table names but no indication of which field is net revenue versus gross sales. The corresponding measure there would be: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. The stated situation instead calls for: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation.
Question 601
For this Microsoft DP-750 case: An AI/BI Genie space is configured with ambiguous metric terminology and produces misleading natural-language interpretations. Which design or operational response BEST fits?
- Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics.
- Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities.
- Create environment-specific Unity Catalog catalogs or schemas and enforce clear ownership and naming conventions.
- Define a consistent schema and naming architecture separating layers and business domains by purpose.
Explanation
Correct Answer
A:The most appropriate action is: Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics. It addresses the stated condition: An AI/BI Genie space is configured with ambiguous metric terminology and produces misleading natural-language interpretations. The technical basis is: Natural-language discovery needs business context and governed metadata to disambiguate metrics. Without this control, an unreviewed semantic instruction can return a plausible but incorrect business measure. A direct acceptance check is: A set of known business prompts yields reconciled SQL and approved metric definitions.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A data pipeline creates a physical table for a reporting transformation that would be better maintained as a query definition. The corresponding measure there would be: Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities. The stated situation instead calls for: Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics.
C:This alternative primarily addresses a different Azure Databricks problem: Production and development teams create identically named data objects in one catalog and accidentally overwrite test tables. The corresponding measure there would be: Create environment-specific Unity Catalog catalogs or schemas and enforce clear ownership and naming conventions. The stated situation instead calls for: Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics.
D:This alternative primarily addresses a different Azure Databricks problem: Multiple data products put raw, refined and curated assets into a single schema with confusing table names. The corresponding measure there would be: Define a consistent schema and naming architecture separating layers and business domains by purpose. The stated situation instead calls for: Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics.
Question 602
An implementation skips: Create environment-specific Unity Catalog catalogs or schemas and enforce clear ownership and naming conventions. Engineers are observing: Production and development teams create identically named data objects in one catalog and accidentally overwrite test tables. What consequence is MOST likely?
- An unqualified table reference may redirect a production job to a developer's test dataset.
- An unreviewed semantic instruction can return a plausible but incorrect business measure.
- File-only storage may lack table-level transactional update and discoverability semantics.
- Direct downstream table references can break when upstream columns are renamed.
Explanation
Correct Answer
A:The direct residual exposure is: An unqualified table reference may redirect a production job to a developer's test dataset. The triggering condition is: Production and development teams create identically named data objects in one catalog and accidentally overwrite test tables. The omitted safeguard is: Create environment-specific Unity Catalog catalogs or schemas and enforce clear ownership and naming conventions. This matters because: Catalog and schema hierarchy can isolate environments while making object ownership and purpose explicit. A corrective test would show: Production jobs resolve fully qualified names and fail safely when pointed at a nonproduction catalog.
Incorrect Answers
B:This failure mode belongs mainly to another situation: An AI/BI Genie space is configured with ambiguous metric terminology and produces misleading natural-language interpretations. Its preventative action would be: Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics. The most direct exposure in the current scenario is: An unqualified table reference may redirect a production job to a developer's test dataset.
C:This failure mode belongs mainly to another situation: A team exposes structured transaction data as files in a volume but wants SQL analytics and ACID MERGE behavior. Its preventative action would be: Register the structured dataset as an appropriate managed Delta table rather than treating the volume itself as a SQL table. The most direct exposure in the current scenario is: An unqualified table reference may redirect a production job to a developer's test dataset.
D:This failure mode belongs mainly to another situation: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. Its preventative action would be: Define a stable contract through managed views and test compatibility before changing source objects. The most direct exposure in the current scenario is: An unqualified table reference may redirect a production job to a developer's test dataset.
Question 603
The team implements: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles. The original problem is: A customer service dashboard must show the last four digits of account identifiers but never full account values. Which test MOST convincingly demonstrates correctness?
- Role-based sample queries show masked values for support and exact values only for approved security operators.
- The analyst can SELECT the authorized table but cannot UPDATE it or read an unrelated protected table.
- A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
- Approved and disallowed identities receive the expected records without filter execution errors.
Explanation
Correct Answer
A:The strongest acceptance proof is: Role-based sample queries show masked values for support and exact values only for approved security operators. It specifically verifies: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles. The original issue was: A customer service dashboard must show the last four digits of account identifiers but never full account values. The underlying mechanism is: Column masking can transform sensitive values at query time according to the querying principal. Without it, granting SELECT without masking may expose full account identifiers to unauthorized readers.
Incorrect Answers
B:This result would validate a different measure: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants. That is relevant to the distinct problem: A finance analyst must read an approved table but was granted broad MODIFY rights at the schema level. Here the acceptance criterion is: Role-based sample queries show masked values for support and exact values only for approved security operators.
C: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: Role-based sample queries show masked values for support and exact values only for approved security operators.
D:This result would validate a different measure: Test the identity-aware filter function, its permissions and supported execution context on representative queries. That is relevant to the distinct problem: An administrator attaches a row-filter function that returns errors for unauthorized query contexts and treats the issue as data corruption. Here the acceptance criterion is: Role-based sample queries show masked values for support and exact values only for approved security operators.
Question 604
A data engineering team faces this Azure Databricks requirement: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. Which action is MOST appropriate?
- Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path.
- Use a dedicated service principal with scoped Unity Catalog grants and governed credential lifecycle.
- Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension.
- Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported.
Explanation
Correct Answer
C:The most appropriate action is: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. It addresses the stated condition: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. The technical basis is: Workspace access scope and principal privileges enforce different aspects of authorization. Without this control, an object may be available to overprivileged identities in unintended contexts if either boundary is ignored. A direct acceptance check is: A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. The corresponding measure there would be: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. The stated situation instead calls for: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension.
B:This alternative primarily addresses a different Azure Databricks problem: An ETL service principal is granted permissions through a personal employee account that will leave the company. The corresponding measure there would be: Use a dedicated service principal with scoped Unity Catalog grants and governed credential lifecycle. The stated situation instead calls for: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension.
D:This alternative primarily addresses a different Azure Databricks problem: A data compliance team needs consistent redaction of columns tagged as personal data across hundreds of catalog tables. The corresponding measure there would be: Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported. The stated situation instead calls for: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension.
Question 605
During a lakehouse implementation review, engineers observe: An event pipeline must reject rows with a null transaction ID, but the data engineer checks only the row count after load. What is the BEST next action?
- Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths.
- Define a range expectation with metrics and the approved drop, fail or quarantine disposition.
- Configure expectations with an explicit fail, drop or retention behavior aligned to business severity.
- Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action.
Explanation
Correct Answer
D:The most appropriate action is: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action. It addresses the stated condition: An event pipeline must reject rows with a null transaction ID, but the data engineer checks only the row count after load. The technical basis is: Explicit quality constraints protect critical key semantics rather than relying on aggregate row totals. Without this control, null business keys can enter Delta targets and make updates or joins nondeterministic. A direct acceptance check is: A seeded null-ID row is blocked or quarantined while valid records complete successfully.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An engineer changes the expected file schema in one notebook but forgets to update the Lakeflow pipeline definition. The corresponding measure there would be: Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths. The stated situation instead calls for: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action.
B:This alternative primarily addresses a different Azure Databricks problem: A bronze stream sometimes includes ages below zero or above 120 yet the transformation casts every value to integer. The corresponding measure there would be: Define a range expectation with metrics and the approved drop, fail or quarantine disposition. The stated situation instead calls for: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action.
C:This alternative primarily addresses a different Azure Databricks problem: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. The corresponding measure there would be: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity. The stated situation instead calls for: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action.
Question 606
An operator introduces: Split ingestion, validation and publishing into explicit orchestrated tasks with durable intermediate outputs. The situation is: A multi-step notebook workflow handles source extraction and final reporting in one cell sequence with no recoverable checkpoints. Which validation should be required before signoff?
- A simulated hung request times out, alerts the owner and avoids publishing incomplete data.
- After a final-task failure, a repair completes the target without reprocessing validated upstream data.
- Two executions of the same input batch yield one approved current record per order.
- A simulated final-task failure can be repaired without rerunning already validated upstream ingestion.
Explanation
Correct Answer
D:The strongest acceptance proof is: A simulated final-task failure can be repaired without rerunning already validated upstream ingestion. It specifically verifies: Split ingestion, validation and publishing into explicit orchestrated tasks with durable intermediate outputs. The original issue was: A multi-step notebook workflow handles source extraction and final reporting in one cell sequence with no recoverable checkpoints. The underlying mechanism is: Separating pipeline stages creates observable failure boundaries and supports targeted recovery. Without it, one late-stage error may force a costly replay of all preceding successful processing.
Incorrect Answers
A:This result would validate a different measure: Use controlled task-level timeouts and isolate unpredictable external calls from bounded transform stages. That is relevant to the distinct problem: A scheduled notebook contains both transformation SQL and a long-running external API loop that occasionally hangs. Here the acceptance criterion is: A simulated final-task failure can be repaired without rerunning already validated upstream ingestion.
B:This result would validate a different measure: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid. That is relevant to the distinct problem: A bulk repair executes all pipeline tasks again even when only the final reporting notebook failed. Here the acceptance criterion is: A simulated final-task failure can be repaired without rerunning already validated upstream ingestion.
C:This result would validate a different measure: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. That is relevant to the distinct problem: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. Here the acceptance criterion is: A simulated final-task failure can be repaired without rerunning already validated upstream ingestion.
Question 607
The following control has NOT been implemented: Use a temporal history model with nonoverlapping effective-from and effective-to boundaries. In this case: A historical compliance table must show how account status changed at precise effective intervals. Which exposure remains?
- Excessive partitions create small files and poor query planning without useful pruning.
- Overlapping intervals can cause a historical lookup to return multiple contradictory statuses.
- Rigid directory partitioning can cause imbalance and require costly redesign as filters change.
- Keeping unnecessary historical rows can produce multiple matches and incorrect lookup joins.
Explanation
Correct Answer
B:The direct residual exposure is: Overlapping intervals can cause a historical lookup to return multiple contradictory statuses. The triggering condition is: A historical compliance table must show how account status changed at precise effective intervals. The omitted safeguard is: Use a temporal history model with nonoverlapping effective-from and effective-to boundaries. This matters because: Temporal tables describe the validity of state over time rather than only its latest value. A corrective test would show: A boundary-date test resolves each account to exactly one status for every audited instant.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. Its preventative action would be: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality. The most direct exposure in the current scenario is: Overlapping intervals can cause a historical lookup to return multiple contradictory statuses.
C: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: Overlapping intervals can cause a historical lookup to return multiple contradictory statuses.
D:This failure mode belongs mainly to another situation: A reference table stores only the latest airport name and business users explicitly do not need historical values. Its preventative action would be: Implement the required SCD Type 1 overwrite with stable business keys and validated updates. The most direct exposure in the current scenario is: Overlapping intervals can cause a historical lookup to return multiple contradictory statuses.
Question 608
A team omits the recommended measure: Use a supported change-data-capture feed and apply insert, update and delete semantics to the target. Its environment shows: A SaaS database updates and deletes customer records but a pipeline appends every nightly full extract to a Delta table. What is the MOST direct residual risk?
- An uncheckpointed consumer can replay or omit events after a restart.
- Append-only full extracts can multiply current records and leave deleted source rows active.
- Driver out-of-memory can fail the load despite adequate executor resources.
- A stream can write duplicate or malformed records into curated output without policy.
Explanation
Correct Answer
B:The direct residual exposure is: Append-only full extracts can multiply current records and leave deleted source rows active. The triggering condition is: A SaaS database updates and deletes customer records but a pipeline appends every nightly full extract to a Delta table. The omitted safeguard is: Use a supported change-data-capture feed and apply insert, update and delete semantics to the target. This matters because: CDC propagates source mutations without duplicating full snapshots. A corrective test would show: Insert-update-delete test events produce one correct current target record per key.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. Its preventative action would be: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. The most direct exposure in the current scenario is: Append-only full extracts can multiply current records and leave deleted source rows active.
C:This failure mode belongs mainly to another situation: A Python notebook reads a massive table into pandas on the driver before processing data intended for Spark executors. Its preventative action would be: Use Spark-native distributed read and transformation APIs or partition-safe processing. The most direct exposure in the current scenario is: Append-only full extracts can multiply current records and leave deleted source rows active.
D:This failure mode belongs mainly to another situation: A declarative pipeline loads cloud object files continuously but its configuration omits how duplicate files and bad records are handled. Its preventative action would be: Define Lakeflow Spark Declarative Pipelines source options, incremental behavior and expectations with a durable target. The most direct exposure in the current scenario is: Append-only full extracts can multiply current records and leave deleted source rows active.
Question 609
The design team proposes: Route deterministic validation failures to quarantine rather than retrying them as transient infrastructure errors. The situation is: A pipeline automatically retries malformed source records indefinitely and consumes its entire compute budget. Which technical principle justifies the decision?
- Task-level repair reduces unnecessary recomputation while preserving dependency correctness.
- A recoverable pipeline should produce the same logical state after an equivalent retry.
- Idempotent retries are suitable for transient conditions, not unchanging invalid data.
- Declarative pipelines express table dependencies and data quality rules without bespoke notebook orchestration.
Explanation
Correct Answer
C:The decisive mechanism is: Idempotent retries are suitable for transient conditions, not unchanging invalid data. That explains the selected action: Route deterministic validation failures to quarantine rather than retrying them as transient infrastructure errors. In the original scenario: A pipeline automatically retries malformed source records indefinitely and consumes its entire compute budget. The specific unmanaged risk is: Infinite retries on bad records can block valid work and multiply costs. Validate with: A malformed input is rejected once with an error record while later valid records continue.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A bulk repair executes all pipeline tasks again even when only the final reporting notebook failed. Its targeted response is: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid. The current case is governed more directly by: Idempotent retries are suitable for transient conditions, not unchanging invalid data.
B:This principle concerns a separate data-engineering condition: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. Its targeted response is: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. The current case is governed more directly by: Idempotent retries are suitable for transient conditions, not unchanging invalid data.
D:This principle concerns a separate data-engineering condition: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. Its targeted response is: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. The current case is governed more directly by: Idempotent retries are suitable for transient conditions, not unchanging invalid data.
Question 610
A production data team leaves out: Grant precise container-use and object-creation privileges based on actual job roles. Its scenario is: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. Which failure mode is MOST relevant?
- An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts.
- Data may remain readable by direct path while the intended catalog table fails authorization.
- Overbroad catalog privileges can let ordinary readers create misleading or unauthorized data products.
- Persisting every intermediate query can create stale and duplicate datasets.
Explanation
Correct Answer
C:The direct residual exposure is: Overbroad catalog privileges can let ordinary readers create misleading or unauthorized data products. The triggering condition is: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. The omitted safeguard is: Grant precise container-use and object-creation privileges based on actual job roles. This matters because: Reading a governed object does not imply permission to create or administer peer objects. A corrective test would show: An analyst can query approved tables but cannot create a schema without a separate grant.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An ingestion team creates a table with a reserved or inconsistent name and automation fails in one environment. Its preventative action would be: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers. The most direct exposure in the current scenario is: Overbroad catalog privileges can let ordinary readers create misleading or unauthorized data products.
B:This failure mode belongs mainly to another situation: A managed Delta table is migrated to external storage but the team does not update table registration or grant scopes. Its preventative action would be: Recreate or update supported external table registration using an approved location and correct access controls. The most direct exposure in the current scenario is: Overbroad catalog privileges can let ordinary readers create misleading or unauthorized data products.
D:This failure mode belongs mainly to another situation: A data pipeline creates a physical table for a reporting transformation that would be better maintained as a query definition. Its preventative action would be: Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities. The most direct exposure in the current scenario is: Overbroad catalog privileges can let ordinary readers create misleading or unauthorized data products.