Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 59
Question 580
A pipeline owner declines the action: Run a supported uniqueness or cardinality validation during the transformation and surface violations. The business situation is: A curated account table accidentally contains multiple rows per supposedly unique current account ID. What specific failure can follow?
- Duplicate current accounts can multiply joins and financial balances.
- Null business keys can enter Delta targets and make updates or joins nondeterministic.
- Inconsistent schema assumptions create intermittent casts, quarantines or dropped columns.
- Invalid amounts may silently convert to null and skew revenue aggregates.
Explanation
Correct Answer
A:The direct residual exposure is: Duplicate current accounts can multiply joins and financial balances. The triggering condition is: A curated account table accidentally contains multiple rows per supposedly unique current account ID. The omitted safeguard is: Run a supported uniqueness or cardinality validation during the transformation and surface violations. This matters because: Primary business-key uniqueness is a semantic data-quality invariant even without enforced physical primary keys. A corrective test would show: A seeded repeated account ID is detected before the curated dataset is marked ready.
Incorrect Answers
B:This failure mode belongs mainly to another situation: An event pipeline must reject rows with a null transaction ID, but the data engineer checks only the row count after load. Its preventative action would be: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action. The most direct exposure in the current scenario is: Duplicate current accounts can multiply joins and financial balances.
C:This failure mode belongs mainly to another situation: An engineer changes the expected file schema in one notebook but forgets to update the Lakeflow pipeline definition. Its preventative action would be: Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths. The most direct exposure in the current scenario is: Duplicate current accounts can multiply joins and financial balances.
D:This failure mode belongs mainly to another situation: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. Its preventative action would be: Apply type, nullability and range expectations before promoting bronze rows into the silver target. The most direct exposure in the current scenario is: Duplicate current accounts can multiply joins and financial balances.
Question 581
The team implements: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction. The original problem is: A batch integration needs a connector-managed path from a supported operational source into the lakehouse. Which test MOST convincingly demonstrates correctness?
- A test source update appears in the target with correct keys and measurable ingestion lag.
- Readers observe a complete validated target before or after cutover, not partial data.
- Replaying the same microbatch produces one target effect per business key.
- Injected duplicate and malformed source samples follow the intended dedupe or quarantine rules.
Explanation
Correct Answer
A:The strongest acceptance proof is: A test source update appears in the target with correct keys and measurable ingestion lag. It specifically verifies: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction. The original issue was: A batch integration needs a connector-managed path from a supported operational source into the lakehouse. The underlying mechanism is: Managed ingestion connectors can simplify source synchronization when their coverage fits the source. Without it, custom polling without checkpoint or schema handling may miss updates and require fragile maintenance.
Incorrect Answers
B:This result would validate a different measure: Choose a controlled CREATE OR REPLACE TABLE or compatible atomic table-replacement strategy and validate schema/permissions. That is relevant to the distinct problem: An existing table must be rebuilt from corrected historical files while its readers require a consistent atomic replacement. Here the acceptance criterion is: A test source update appears in the target with correct keys and measurable ingestion lag.
C:This result would validate a different measure: Implement idempotent foreachBatch or compatible transactional sink logic keyed by epoch or business identity. That is relevant to the distinct problem: A stream writes into an external sink without stable batch identities and causes duplicate side effects on retry. Here the acceptance criterion is: A test source update appears in the target with correct keys and measurable ingestion lag.
D:This result would validate a different measure: Define Lakeflow Spark Declarative Pipelines source options, incremental behavior and expectations with a durable target. That is relevant to the distinct problem: A declarative pipeline loads cloud object files continuously but its configuration omits how duplicate files and bad records are handled. Here the acceptance criterion is: A test source update appears in the target with correct keys and measurable ingestion lag.
Question 582
The team implements: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. The original problem is: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. Which test MOST convincingly demonstrates correctness?
- A skew-aware plan balances task durations and reduces the critical-stage elapsed time.
- A simulated failure yields archived logs, failed stage IDs and a documented root-cause path.
- Spark storage metrics show released cache and unchanged correctness with improved total runtime.
- A permitted historical query succeeds before and after approved housekeeping within its retention boundary.
Explanation
Correct Answer
D:The strongest acceptance proof is: A permitted historical query succeeds before and after approved housekeeping within its retention boundary. It specifically verifies: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. The original issue was: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. The underlying mechanism is: VACUUM removes old physical files, so aggressive cleanup can break valid historical references. Without it, premature deletion may invalidate time travel or a lagging reader's file references.
Incorrect Answers
A:This result would validate a different measure: Inspect the Spark UI DAG and skewed-key distribution before changing cluster size. That is relevant to the distinct problem: A production Spark query is slow and its stage graph shows one task running far longer than all peers. Here the acceptance criterion is: A permitted historical query succeeds before and after approved housekeeping within its retention boundary.
B:This result would validate a different measure: Preserve diagnostic events and Spark UI stage evidence before restart where possible. That is relevant to the distinct problem: An operator restarts a failed Databricks cluster before collecting the Spark executor and driver logs. Here the acceptance criterion is: A permitted historical query succeeds before and after approved housekeeping within its retention boundary.
C:This result would validate a different measure: Use caching only for beneficial reuse and release persisted state when no longer needed. That is relevant to the distinct problem: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. Here the acceptance criterion is: A permitted historical query succeeds before and after approved housekeeping within its retention boundary.
Question 583
A solution applies: Run a supported uniqueness or cardinality validation during the transformation and surface violations. It addresses: A curated account table accidentally contains multiple rows per supposedly unique current account ID. Which operational outcome MOST directly verifies success?
- A seeded repeated account ID is detected before the curated dataset is marked ready.
- A sample of valid UTC timestamps passes and known ambiguous strings produce the expected exception record.
- A controlled malformed amount is detected and excluded from published silver while legitimate zero values remain.
- Injected critical and noncritical bad rows follow their respective approved actions and emit metrics.
Explanation
Correct Answer
A:The strongest acceptance proof is: A seeded repeated account ID is detected before the curated dataset is marked ready. It specifically verifies: Run a supported uniqueness or cardinality validation during the transformation and surface violations. The original issue was: A curated account table accidentally contains multiple rows per supposedly unique current account ID. The underlying mechanism is: Primary business-key uniqueness is a semantic data-quality invariant even without enforced physical primary keys. Without it, duplicate current accounts can multiply joins and financial balances.
Incorrect Answers
B:This result would validate a different measure: Validate timezone-aware timestamp types and quarantine ambiguous or unparseable event values. That is relevant to the distinct problem: A regulated dataset requires all timestamps to parse as UTC but several rows have ambiguous local values. Here the acceptance criterion is: A seeded repeated account ID is detected before the curated dataset is marked ready.
C:This result would validate a different measure: Apply type, nullability and range expectations before promoting bronze rows into the silver target. That is relevant to the distinct problem: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. Here the acceptance criterion is: A seeded repeated account ID is detected before the curated dataset is marked ready.
D:This result would validate a different measure: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity. That is relevant to the distinct problem: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. Here the acceptance criterion is: A seeded repeated account ID is detected before the curated dataset is marked ready.
Question 584
A data product owner adopts: Define a stable contract through managed views and test compatibility before changing source objects. The reason is: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. What observed result BEST proves effectiveness?
- Authorized principals list and read a governed volume path while unrelated roles receive denied access.
- Contract tests continue to select documented columns through the published view after a staged schema change.
- An access review identifies the view steward and confirms a prohibited reader cannot query it.
- A credential audit shows approved external access and no user-readable storage secret in notebook source.
Explanation
Correct Answer
B:The strongest acceptance proof is: Contract tests continue to select documented columns through the published view after a staged schema change. It specifically verifies: Define a stable contract through managed views and test compatibility before changing source objects. The original issue was: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. The underlying mechanism is: Abstraction views can separate a consumer-facing contract from internal physical table evolution. Without it, direct downstream table references can break when upstream columns are renamed.
Incorrect Answers
A:This result would validate a different measure: Use Unity Catalog volumes with suitable schema and file privileges for supported non-tabular files. That is relevant to the distinct problem: A departmental data owner stores raw file attachments inside ad hoc DBFS directories instead of a governable data space. Here the acceptance criterion is: Contract tests continue to select documented columns through the published view after a staged schema change.
C:This result would validate a different measure: Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema. That is relevant to the distinct problem: A central team creates global views that hide source objects but forgets to document ownership and access grants. Here the acceptance criterion is: Contract tests continue to select documented columns through the published view after a staged schema change.
D:This result would validate a different measure: Register supported external locations and storage credentials, then define governed external tables. That is relevant to the distinct problem: A legacy external Delta table points at a cloud location with an unmanaged storage credential stored in notebook text. Here the acceptance criterion is: Contract tests continue to select documented columns through the published view after a staged schema change.
Question 585
A solution applies: Recreate or update supported external table registration using an approved location and correct access controls. It addresses: A managed Delta table is migrated to external storage but the team does not update table registration or grant scopes. Which operational outcome MOST directly verifies success?
- An architecture test proves the selected object's refresh and query cost meet defined needs.
- A set of known business prompts yields reconciled SQL and approved metric definitions.
- Catalog lookup and controlled read work from the registered target while unapproved principals cannot bypass it.
- A credential audit shows approved external access and no user-readable storage secret in notebook source.
Explanation
Correct Answer
C:The strongest acceptance proof is: Catalog lookup and controlled read work from the registered target while unapproved principals cannot bypass it. It specifically verifies: Recreate or update supported external table registration using an approved location and correct access controls. The original issue was: A managed Delta table is migrated to external storage but the team does not update table registration or grant scopes. The underlying mechanism is: Metadata definitions, locations and privileges must align after a table lifecycle transition. Without it, data may remain readable by direct path while the intended catalog table fails authorization.
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: Catalog lookup and controlled read work from the registered target while unapproved principals cannot bypass it.
B:This result would validate a different measure: Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics. That is relevant to the distinct problem: An AI/BI Genie space is configured with ambiguous metric terminology and produces misleading natural-language interpretations. Here the acceptance criterion is: Catalog lookup and controlled read work from the registered target while unapproved principals cannot bypass it.
D:This result would validate a different measure: Register supported external locations and storage credentials, then define governed external tables. That is relevant to the distinct problem: A legacy external Delta table points at a cloud location with an unmanaged storage credential stored in notebook text. Here the acceptance criterion is: Catalog lookup and controlled read work from the registered target while unapproved principals cannot bypass it.
Question 586
During a lakehouse implementation review, engineers observe: A pipeline automatically retries malformed source records indefinitely and consumes its entire compute budget. What is the BEST next action?
- Add bounded retries with exponential backoff and observable failure after the retry budget.
- Route deterministic validation failures to quarantine rather than retrying them as transient infrastructure errors.
- Write to a staging target, validate row totals and invariants, then perform the approved publication step.
- Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph.
Explanation
Correct Answer
B:The most appropriate action is: Route deterministic validation failures to quarantine rather than retrying them as transient infrastructure errors. It addresses the stated condition: A pipeline automatically retries malformed source records indefinitely and consumes its entire compute budget. The technical basis is: Idempotent retries are suitable for transient conditions, not unchanging invalid data. Without this control, infinite retries on bad records can block valid work and multiply costs. A direct acceptance check is: A malformed input is rejected once with an error record while later valid records continue.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. The corresponding measure there would be: Add bounded retries with exponential backoff and observable failure after the retry budget. The stated situation instead calls for: Route deterministic validation failures to quarantine rather than retrying them as transient infrastructure errors.
C:This alternative primarily addresses a different Azure Databricks problem: A finance transformation writes its output directly into a published table before reconciling totals against the source. The corresponding measure there would be: Write to a staging target, validate row totals and invariants, then perform the approved publication step. The stated situation instead calls for: Route deterministic validation failures to quarantine rather than retrying them as transient infrastructure errors.
D: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: Route deterministic validation failures to quarantine rather than retrying them as transient infrastructure errors.
Question 587
A data engineering team faces this Azure Databricks requirement: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. Which action is MOST appropriate?
- Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema.
- Use fully qualified names and a controlled default namespace in deployment SQL and notebooks.
- Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings.
- Check federation connector capabilities and distinguish read-only remote access from supported writable local tables.
Explanation
Correct Answer
C:The most appropriate action is: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings. It addresses the stated condition: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. The technical basis is: Catalog separation and workspace access controls can help enforce organizational and geography boundaries. Without this control, A broadly shared catalog can expose regulated data to unintended region workspaces. A direct acceptance check is: Approved regional workspaces access their catalogs while a disallowed workspace fails its access test.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A central team creates global views that hide source objects but forgets to document ownership and access grants. The corresponding measure there would be: Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema. The stated situation instead calls for: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings.
B:This alternative primarily addresses a different Azure Databricks problem: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. The corresponding measure there would be: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks. The stated situation instead calls for: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings.
D:This alternative primarily addresses a different Azure Databricks problem: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. The corresponding measure there would be: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. The stated situation instead calls for: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings.
Question 588
During a lakehouse implementation review, engineers observe: A pipeline must run when an upstream Databricks table is updated but analysts have hardcoded a daily time estimate. What is the BEST next action?
- Configure appropriate maximum concurrent runs and idempotent target writes to control overlap.
- Assign a dedicated run-as identity with durable scoped grants and an ownership review.
- Evaluate supported table update triggers or a clear upstream job dependency based on actual availability.
- Set task and job timeout limits with notifications and a documented retry and recovery route.
Explanation
Correct Answer
C:The most appropriate action is: Evaluate supported table update triggers or a clear upstream job dependency based on actual availability. It addresses the stated condition: A pipeline must run when an upstream Databricks table is updated but analysts have hardcoded a daily time estimate. The technical basis is: Event-driven triggers align pipeline execution to upstream readiness where supported. Without this control, A clock-only trigger can start before the dependency has produced the expected dataset. A direct acceptance check is: A delayed upstream refresh starts the dependent job only after the designated table event.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A daily data job runs twice during an incident and both executions write to the same target. The corresponding measure there would be: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap. The stated situation instead calls for: Evaluate supported table update triggers or a clear upstream job dependency based on actual availability.
B: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: Evaluate supported table update triggers or a clear upstream job dependency based on actual availability.
D:This alternative primarily addresses a different Azure Databricks problem: A long-running job occasionally hangs but there is no configured runtime ceiling or escalation. The corresponding measure there would be: Set task and job timeout limits with notifications and a documented retry and recovery route. The stated situation instead calls for: Evaluate supported table update triggers or a clear upstream job dependency based on actual availability.
Question 589
For this Microsoft DP-750 case: A business report must refresh daily at 06:00 in a defined local time zone but a developer schedules it in UTC without conversion. Which design or operational response BEST fits?
- Evaluate supported table update triggers or a clear upstream job dependency based on actual availability.
- Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant.
- Limit retries to appropriate transient errors and set accountable failure handling for permanent logic problems.
- Assign a dedicated run-as identity with durable scoped grants and an ownership review.
Explanation
Correct Answer
B:The most appropriate action is: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant. It addresses the stated condition: 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 technical basis is: Scheduler time zone semantics affect when recurring business windows run. Without this control, an implicit UTC schedule can cause delivery an hour or more away from the required business cutover. A direct acceptance check is: Run history shows the job starts at the agreed local times across representative date transitions.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A pipeline must run when an upstream Databricks table is updated but analysts have hardcoded a daily time estimate. The corresponding measure there would be: Evaluate supported table update triggers or a clear upstream job dependency based on actual availability. The stated situation instead calls for: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant.
C:This alternative primarily addresses a different Azure Databricks problem: A job's retry policy restarts a deterministic bad SQL query six times even though the table is missing. The corresponding measure there would be: Limit retries to appropriate transient errors and set accountable failure handling for permanent logic problems. The stated situation instead calls for: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant.
D: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: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant.
Question 590
A team omits the recommended measure: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. Its environment shows: A company needs to review table-owner changes and permissions after organizational restructuring. What is the MOST direct residual risk?
- An identically named confidential field in a new table could be exposed.
- Accumulated historical grants may give former project teams access to unrelated data products.
- Analysts may combine incompatible metrics and deliver unreliable reports.
- Long-lived shared storage credentials may expose unrelated files or survive contract termination.
Explanation
Correct Answer
B:The direct residual exposure is: Accumulated historical grants may give former project teams access to unrelated data products. The triggering condition is: A company needs to review table-owner changes and permissions after organizational restructuring. The omitted safeguard is: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. This matters because: Object governance is ongoing and must follow organizational role and service identity changes. A corrective test would show: The recertification report identifies owners, changed grants and approved remediation evidence.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A user creates a column mask on a single table and assumes all tables with the same field name are protected. Its preventative action would be: Compare table-level masks against centrally governed ABAC coverage and identify missing assignments. The most direct exposure in the current scenario is: Accumulated historical grants may give former project teams access to unrelated data products.
C:This failure mode belongs mainly to another situation: A business glossary has table names but no indication of which field is net revenue versus gross sales. Its preventative action would be: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. The most direct exposure in the current scenario is: Accumulated historical grants may give former project teams access to unrelated data products.
D:This failure mode belongs mainly to another situation: A data-sharing project emails storage keys to an external partner for reading curated Delta results. Its preventative action would be: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. The most direct exposure in the current scenario is: Accumulated historical grants may give former project teams access to unrelated data products.