Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 25
Question 240
A team omits the recommended measure: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. Its environment shows: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. What is the MOST direct residual risk?
- Skew and memory limits may remain invisible until a full-scale run misses its SLA.
- A faulty last-minute edit can create an untested release with no accountable reviewer.
- Duplicate jobs may run on the same schedule and load data twice.
- Manual post-deployment edits can bypass review and silently change retry or security settings.
Explanation
Correct Answer
D:The direct residual exposure is: Manual post-deployment edits can bypass review and silently change retry or security settings. The triggering condition is: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. The omitted safeguard is: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. This matters because: Source control only provides operational truth when actual resource settings match the approved definition. A corrective test would show: A test UI change is flagged and the approved deployment restores the intended configuration.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An engineering test suite passes on miniature in-memory data yet fails in production on skewed billion-row joins. Its preventative action would be: Include performance and end-to-end tests using representative scale and data distributions. The most direct exposure in the current scenario is: Manual post-deployment edits can bypass review and silently change retry or security settings.
B:This failure mode belongs mainly to another situation: A release process merges unreviewed notebook changes directly into the main branch minutes before a production run. Its preventative action would be: Protect the main branch with peer review, required tests and controlled promotion windows. The most direct exposure in the current scenario is: Manual post-deployment edits can bypass review and silently change retry or security settings.
C:This failure mode belongs mainly to another situation: A REST deployment script creates duplicate jobs every time CI reruns after a timeout. Its preventative action would be: Use idempotent deployment methods or reconcile existing resource IDs before creating replacements. The most direct exposure in the current scenario is: Manual post-deployment edits can bypass review and silently change retry or security settings.
Question 241
A production data team leaves out: Transfer ownership through approved governance workflow and review grants after reassignment. Its scenario is: An audit asks who owns a catalog table but object ownership still points to an inactive employee. Which failure mode is MOST relevant?
- Old cleanup tasks can destroy files that the revised retention requirement still protects.
- Duplicated datasets can diverge or escape synchronized retention and correction policies.
- An orphaned ownership chain can delay access review or emergency remediation.
- Accumulated historical grants may give former project teams access to unrelated data products.
Explanation
Correct Answer
C:The direct residual exposure is: An orphaned ownership chain can delay access review or emergency remediation. The triggering condition is: An audit asks who owns a catalog table but object ownership still points to an inactive employee. The omitted safeguard is: Transfer ownership through approved governance workflow and review grants after reassignment. This matters because: Governance depends on maintained object ownership as teams and responsibilities change. A corrective test would show: The designated active service or steward owns the object and prior inappropriate rights are removed.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. Its preventative action would be: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. The most direct exposure in the current scenario is: An orphaned ownership chain can delay access review or emergency remediation.
B:This failure mode belongs mainly to another situation: A shared customer table needs dynamic per-region row restrictions but the business refuses duplicating physical datasets. Its preventative action would be: Use row-filter policies on the governed table and test permitted region entitlements. The most direct exposure in the current scenario is: An orphaned ownership chain can delay access review or emergency remediation.
D:This failure mode belongs mainly to another situation: A company needs to review table-owner changes and permissions after organizational restructuring. Its preventative action would be: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. The most direct exposure in the current scenario is: An orphaned ownership chain can delay access review or emergency remediation.
Question 242
The following control has NOT been implemented: Use Lakeflow Jobs repair at the failed task when dependency outputs remain valid. In this case: A job fails during a temporary Azure storage outage but operators rerun every successful upstream task. Which exposure remains?
- Unused cached data can cause eviction, spilling and unexpected failures for later stages.
- Unnecessary replay may duplicate writes and extend incident recovery time.
- A failed cluster can disappear before operators gather evidence of its root cause.
- Collecting billions of rows can crash the driver despite idle executors.
Explanation
Correct Answer
B:The direct residual exposure is: Unnecessary replay may duplicate writes and extend incident recovery time. The triggering condition is: A job fails during a temporary Azure storage outage but operators rerun every successful upstream task. The omitted safeguard is: Use Lakeflow Jobs repair at the failed task when dependency outputs remain valid. This matters because: Task-level repair can reduce replay cost while preserving successful work. A corrective test would show: A controlled transient outage is repaired without rerunning completed expensive ingestion.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. Its preventative action would be: Use caching only for beneficial reuse and release persisted state when no longer needed. The most direct exposure in the current scenario is: Unnecessary replay may duplicate writes and extend incident recovery time.
C:This failure mode belongs mainly to another situation: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. Its preventative action would be: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention. The most direct exposure in the current scenario is: Unnecessary replay may duplicate writes and extend incident recovery time.
D:This failure mode belongs mainly to another situation: A Spark join reads large inputs but the driver reports failures after an analyst calls collect() on the result. Its preventative action would be: Keep large results distributed and replace driver collection with bounded sampling or distributed writes. The most direct exposure in the current scenario is: Unnecessary replay may duplicate writes and extend incident recovery time.
Question 243
The design team proposes: Use an external Unity Catalog table with an approved registered location instead of assuming managed storage ownership. The situation is: A dataset has a strict requirement that Azure storage ownership and lifecycle remain under a separate platform team. Which technical principle justifies the decision?
- Liquid clustering and traditional ZORDER/partitioning have compatibility constraints and different maintenance paths.
- Delta tables support transactional mutations and versioned metadata beyond raw delimiter files.
- High-cardinality partition columns can fragment file layout and increase metadata overhead.
- External tables separate catalog management from independently controlled underlying file lifecycle.
Explanation
Correct Answer
D:The decisive mechanism is: External tables separate catalog management from independently controlled underlying file lifecycle. That explains the selected action: Use an external Unity Catalog table with an approved registered location instead of assuming managed storage ownership. In the original scenario: A dataset has a strict requirement that Azure storage ownership and lifecycle remain under a separate platform team. The specific unmanaged risk is: Migrating data into a managed table can violate external storage governance agreements. Validate with: The platform team retains approved storage lifecycle authority while Databricks queries the registered data.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. Its targeted response is: Choose one compatible data layout strategy based on table format, platform support and query evidence. The current case is governed more directly by: External tables separate catalog management from independently controlled underlying file lifecycle.
B:This principle concerns a separate data-engineering condition: A reporting team stores frequent updates in raw CSV files and expects atomic MERGE and historical time travel. Its targeted response is: Use a managed Delta table for transactional updates and controlled schema evolution. The current case is governed more directly by: External tables separate catalog management from independently controlled underlying file lifecycle.
C:This principle concerns a separate data-engineering condition: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. Its targeted response is: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality. The current case is governed more directly by: External tables separate catalog management from independently controlled underlying file lifecycle.
Question 244
A production data team leaves out: Select a notebook task within Lakeflow Jobs when procedural control and custom libraries fit the requirements. Its scenario is: An ad hoc machine-learning preparation task has complex custom Python orchestration and no declarative table graph. Which failure mode is MOST relevant?
- Forcing arbitrary procedural logic into a declarative table pipeline may complicate testing and maintenance.
- At-least-once task execution can duplicate side effects when outputs are append-only.
- A downstream report can close before late but permitted events are incorporated.
- Unnecessary serial execution can extend the critical path beyond the freshness target.
Explanation
Correct Answer
A:The direct residual exposure is: Forcing arbitrary procedural logic into a declarative table pipeline may complicate testing and maintenance. The triggering condition is: An ad hoc machine-learning preparation task has complex custom Python orchestration and no declarative table graph. The omitted safeguard is: Select a notebook task within Lakeflow Jobs when procedural control and custom libraries fit the requirements. This matters because: Notebooks and declarative pipelines serve different orchestration and transformation patterns. A corrective test would show: A job executes the procedural notebook under controlled dependencies and produces the validated output.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. Its preventative action would be: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. The most direct exposure in the current scenario is: Forcing arbitrary procedural logic into a declarative table pipeline may complicate testing and maintenance.
C:This failure mode belongs mainly to another situation: A streaming process depends on a downstream batch closeout but no one defines whether it should wait for the latest watermark. Its preventative action would be: Specify the stream watermark and an explicit closeout readiness condition before running downstream aggregation. The most direct exposure in the current scenario is: Forcing arbitrary procedural logic into a declarative table pipeline may complicate testing and maintenance.
D:This failure mode belongs mainly to another situation: A pipeline uses a single notebook to read four sources sequentially even though two can be processed independently. Its preventative action would be: Design a task DAG with parallel independent ingestion and an aggregation dependency after both complete. The most direct exposure in the current scenario is: Forcing arbitrary procedural logic into a declarative table pipeline may complicate testing and maintenance.
Question 245
An operator introduces: Include an integration test using actual Delta table semantics and representative source changes. The situation is: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. Which validation should be required before signoff?
- A merged branch passes regression tests for both bug fixes and shows reviewed conflict decisions.
- An integration fixture with historical updates yields exactly the intended target versions.
- A seeded test dataset returns documented expected outputs and intentionally bad inputs fail.
- A product owner signs off a sample report and its reconciled acceptance criteria before rollout.
Explanation
Correct Answer
B:The strongest acceptance proof is: An integration fixture with historical updates yields exactly the intended target versions. It specifically verifies: Include an integration test using actual Delta table semantics and representative source changes. The original issue was: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. The underlying mechanism is: Storage-layer transaction behavior must be tested in addition to pure function outputs. Without it, unverified MERGE conditions can overwrite valid history despite passing mocked unit tests.
Incorrect Answers
A:This result would validate a different measure: Resolve Git merge conflicts with tests and reviewed integration before merging the release branch. That is relevant to the distinct problem: Two engineers change the same ingestion function on separate branches and one silently overwrites the other's fix. Here the acceptance criterion is: An integration fixture with historical updates yields exactly the intended target versions.
C:This result would validate a different measure: Add representative unit and integration tests asserting transformation results and schema contracts. That is relevant to the distinct problem: A release modifies transformation logic but tests only whether Python files compile. Here the acceptance criterion is: An integration fixture with historical updates yields exactly the intended target versions.
D:This result would validate a different measure: Add user acceptance tests for the relevant reporting contract before production promotion. That is relevant to the distinct problem: A developer changes a transformation with a user-visible business effect but omits acceptance testing by the data product owner. Here the acceptance criterion is: An integration fixture with historical updates yields exactly the intended target versions.
Question 246
A production data platform experiences this condition: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. Which targeted measure should be selected?
- Validate business keys and choose a deterministic latest-enrollment record before aggregation.
- Implement explicit null predicates rather than treating zero and null as equivalent.
- Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans.
- Define and test consistent trimming, Unicode normalization and case comparison for the business key.
Explanation
Correct Answer
A:The most appropriate action is: Validate business keys and choose a deterministic latest-enrollment record before aggregation. It addresses the stated condition: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. The technical basis is: Aggregation alone cannot distinguish valid repeat enrollments from accidental duplicates. Without this control, completion metrics may be inflated or undercounted when duplicate business events are not resolved. A direct acceptance check is: Test histories with retries and real re-enrollments produce the approved per-student count.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. The corresponding measure there would be: Implement explicit null predicates rather than treating zero and null as equivalent. The stated situation instead calls for: Validate business keys and choose a deterministic latest-enrollment record before aggregation.
C:This alternative primarily addresses a different Azure Databricks problem: A pipeline joins a huge fact table with a tiny dimension and a normal shuffle join creates excessive network traffic. The corresponding measure there would be: Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans. The stated situation instead calls for: Validate business keys and choose a deterministic latest-enrollment record before aggregation.
D:This alternative primarily addresses a different Azure Databricks problem: A customer-name cleansing script uses an arbitrary lowercase conversion without preserving Unicode and leading/trailing whitespace rules. The corresponding measure there would be: Define and test consistent trimming, Unicode normalization and case comparison for the business key. The stated situation instead calls for: Validate business keys and choose a deterministic latest-enrollment record before aggregation.
Question 247
A platform architect adopts: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks. For this requirement: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. Which rationale MOST directly supports it?
- Catalog separation and workspace access controls can help enforce organizational and geography boundaries.
- The object type should reflect whether data is computed on read or persisted and maintained.
- Explicit namespace resolution makes deployment deterministic across different workspaces.
- External table metadata can be governed even when the underlying object files remain in external storage.
Explanation
Correct Answer
C:The decisive mechanism is: Explicit namespace resolution makes deployment deterministic across different workspaces. That explains the selected action: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks. In the original scenario: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. The specific unmanaged risk is: An environment-default schema can route production data definitions into an incorrect catalog. Validate with: The same deployment command creates objects only in its designated staging or production namespace.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. Its targeted response is: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings. The current case is governed more directly by: Explicit namespace resolution makes deployment deterministic across different workspaces.
B:This principle concerns a separate data-engineering condition: A data pipeline creates a physical table for a reporting transformation that would be better maintained as a query definition. Its targeted response is: Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities. The current case is governed more directly by: Explicit namespace resolution makes deployment deterministic across different workspaces.
D:This principle concerns a separate data-engineering condition: A legacy external Delta table points at a cloud location with an unmanaged storage credential stored in notebook text. Its targeted response is: Register supported external locations and storage credentials, then define governed external tables. The current case is governed more directly by: Explicit namespace resolution makes deployment deterministic across different workspaces.
Question 248
A data product owner adopts: Configure a supported external location and specific creation privileges rather than bypassing the catalog to write directly. The reason is: A user is granted CREATE TABLE but cannot create an external table at an unregistered cloud path. What observed result BEST proves effectiveness?
- The job authenticates successfully and audited logs contain no raw secret or token.
- An approved DDL operation creates the external table at a registered location and an arbitrary path is rejected.
- An East-region identity cannot read West-region test rows while the approved manager has the intended view.
- Approved and disallowed identities receive the expected records without filter execution errors.
Explanation
Correct Answer
B:The strongest acceptance proof is: An approved DDL operation creates the external table at a registered location and an arbitrary path is rejected. It specifically verifies: Configure a supported external location and specific creation privileges rather than bypassing the catalog to write directly. The original issue was: A user is granted CREATE TABLE but cannot create an external table at an unregistered cloud path. The underlying mechanism is: Creating an external table requires governed location and storage authorization beyond a generic schema creation grant. Without it, direct-path writes can bypass registration and leave unowned storage artifacts.
Incorrect Answers
A:This result would validate a different measure: Use supported Databricks secret access with least-privilege scope access and remove secret values from logs. That is relevant to the distinct problem: An application uses an external Azure Key Vault secret scope but a notebook prints the secret into task logs. Here the acceptance criterion is: An approved DDL operation creates the external table at a registered location and an arbitrary path is rejected.
C:This result would validate a different measure: Configure a tested Unity Catalog row filter or suitable ABAC policy based on the authorized identity. That is relevant to the distinct problem: A user must see only the East region rows of a common sales table while managers see all territories. Here the acceptance criterion is: An approved DDL operation creates the external table at a registered location and an arbitrary path is rejected.
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: An approved DDL operation creates the external table at a registered location and an arbitrary path is rejected.
Question 249
An operator introduces: Define a range expectation with metrics and the approved drop, fail or quarantine disposition. The situation is: A bronze stream sometimes includes ages below zero or above 120 yet the transformation casts every value to integer. Which validation should be required before signoff?
- A controlled negative-age record triggers the configured expectation event without being silently published.
- Injected critical and noncritical bad rows follow their respective approved actions and emit metrics.
- A seeded null-ID row is blocked or quarantined while valid records complete successfully.
- A seeded repeated account ID is detected before the curated dataset is marked ready.
Explanation
Correct Answer
A:The strongest acceptance proof is: A controlled negative-age record triggers the configured expectation event without being silently published. It specifically verifies: Define a range expectation with metrics and the approved drop, fail or quarantine disposition. The original issue was: A bronze stream sometimes includes ages below zero or above 120 yet the transformation casts every value to integer. The underlying mechanism is: Valid data type does not guarantee semantic range correctness. Without it, numerically valid but impossible values can contaminate customer metrics and machine-learning features.
Incorrect Answers
B: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 controlled negative-age record triggers the configured expectation event without being silently published.
C:This result would validate a different measure: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action. That is relevant to the distinct problem: An event pipeline must reject rows with a null transaction ID, but the data engineer checks only the row count after load. Here the acceptance criterion is: A controlled negative-age record triggers the configured expectation event without being silently published.
D:This result would validate a different measure: Run a supported uniqueness or cardinality validation during the transformation and surface violations. That is relevant to the distinct problem: A curated account table accidentally contains multiple rows per supposedly unique current account ID. Here the acceptance criterion is: A controlled negative-age record triggers the configured expectation event without being silently published.
Question 250
For this Microsoft DP-750 case: A finance analyst must read an approved table but was granted broad MODIFY rights at the schema level. Which design or operational response BEST fits?
- Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants.
- Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants.
- Issue time-bounded group membership or an approved scoped SELECT grant with an access review.
- Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles.
Explanation
Correct Answer
A:The most appropriate action is: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants. It addresses the stated condition: A finance analyst must read an approved table but was granted broad MODIFY rights at the schema level. The technical basis is: Unity Catalog privileges are scoped to securable objects and can be inherited from containers. Without this control, unnecessary modification rights can let a compromised analyst alter financial records. A direct acceptance check is: The analyst can SELECT the authorized table but cannot UPDATE it or read an unrelated protected table.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: An engineering pipeline attempts to insert records into a production Delta table using an account with SELECT only. The corresponding measure there would be: Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants. The stated situation instead calls for: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants.
C:This alternative primarily addresses a different Azure Databricks problem: A data steward wants to grant temporary read access without handing over Unity Catalog ownership of a schema. The corresponding measure there would be: Issue time-bounded group membership or an approved scoped SELECT grant with an access review. The stated situation instead calls for: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants.
D:This alternative primarily addresses a different Azure Databricks problem: A customer service dashboard must show the last four digits of account identifiers but never full account values. The corresponding measure there would be: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles. The stated situation instead calls for: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants.