Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 32
Question 310
A production data team leaves out: Resolve Git merge conflicts with tests and reviewed integration before merging the release branch. Its scenario is: Two engineers change the same ingestion function on separate branches and one silently overwrites the other's fix. Which failure mode is MOST relevant?
- Unreviewed overwrites can remove validation or idempotency logic from the deployed pipeline.
- Unreviewed direct edits can break jobs without a reproducible rollback commit.
- A logically incorrect aggregation can pass compilation while corrupting metrics.
- Skew and memory limits may remain invisible until a full-scale run misses its SLA.
Explanation
Correct Answer
A:The direct residual exposure is: Unreviewed overwrites can remove validation or idempotency logic from the deployed pipeline. The triggering condition is: Two engineers change the same ingestion function on separate branches and one silently overwrites the other's fix. The omitted safeguard is: Resolve Git merge conflicts with tests and reviewed integration before merging the release branch. This matters because: Conflict resolution must preserve intended behavior from both change sets. A corrective test would show: A merged branch passes regression tests for both bug fixes and shows reviewed conflict decisions.
Incorrect Answers
B:This failure mode belongs mainly to another situation: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. Its preventative action would be: Store deployment source in Git with reviewed branches and pull requests before promoting changes. The most direct exposure in the current scenario is: Unreviewed overwrites can remove validation or idempotency logic from the deployed pipeline.
C:This failure mode belongs mainly to another situation: A release modifies transformation logic but tests only whether Python files compile. Its preventative action would be: Add representative unit and integration tests asserting transformation results and schema contracts. The most direct exposure in the current scenario is: Unreviewed overwrites can remove validation or idempotency logic from the deployed pipeline.
D: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: Unreviewed overwrites can remove validation or idempotency logic from the deployed pipeline.
Question 311
An implementation skips: Reconcile catalog object identity, lineage and current grants after schema or owner changes. Engineers are observing: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. What consequence is MOST likely?
- Deleting a field without documented change history can leave unanswerable regulatory questions.
- Consumers can use incorrectly labeled confidential fields without recognizing their sensitivity.
- A migrated table can retain unintended access or lose required controls after namespace changes.
- Accumulated historical grants may give former project teams access to unrelated data products.
Explanation
Correct Answer
C:The direct residual exposure is: A migrated table can retain unintended access or lose required controls after namespace changes. The triggering condition is: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. The omitted safeguard is: Reconcile catalog object identity, lineage and current grants after schema or owner changes. This matters because: Permission reviews should follow actual securable objects and their dependencies rather than name assumptions. A corrective test would show: An access matrix tests current schema objects and verifies intended principals after migration.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A shared table includes an old regulated field and the business needs reproducible evidence of when it was removed. Its preventative action would be: Use appropriate table history, schema change records and approved retention/audit evidence rather than relying on memory. The most direct exposure in the current scenario is: A migrated table can retain unintended access or lose required controls after namespace changes.
B:This failure mode belongs mainly to another situation: A central repository contains schemas with missing column owners and no sensitivity classifications. Its preventative action would be: Implement a catalog stewardship process to review metadata and governed tags at dataset publication. The most direct exposure in the current scenario is: A migrated table can retain unintended access or lose required controls after namespace changes.
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: A migrated table can retain unintended access or lose required controls after namespace changes.
Question 312
For this Azure Databricks issue: An administrator attaches a row-filter function that returns errors for unauthorized query contexts and treats the issue as data corruption. Engineers choose: Test the identity-aware filter function, its permissions and supported execution context on representative queries. What acceptance evidence is BEST?
- The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
- A storage access test and catalog grant review both pass for the designated service principal.
- Approved and disallowed identities receive the expected records without filter execution errors.
- A new tagged test column receives the required masking behavior without a separate manual table exception.
Explanation
Correct Answer
C:The strongest acceptance proof is: Approved and disallowed identities receive the expected records without filter execution errors. It specifically verifies: Test the identity-aware filter function, its permissions and supported execution context on representative queries. The original issue was: An administrator attaches a row-filter function that returns errors for unauthorized query contexts and treats the issue as data corruption. The underlying mechanism is: Fine-grained security functions are part of the query execution path and can affect availability. Without it, A broken policy function may deny intended users or expose inconsistent query results if bypassed.
Incorrect Answers
A: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: Approved and disallowed identities receive the expected records without filter execution errors.
B:This result would validate a different measure: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges. That is relevant to the distinct problem: A managed identity can read a storage container but a newly created external table is denied in Databricks. Here the acceptance criterion is: Approved and disallowed identities receive the expected records without filter execution errors.
D:This result would validate a different measure: Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported. That is relevant to the distinct problem: A data compliance team needs consistent redaction of columns tagged as personal data across hundreds of catalog tables. Here the acceptance criterion is: Approved and disallowed identities receive the expected records without filter execution errors.
Question 313
A data engineering team faces this Azure Databricks requirement: A historical compliance table must show how account status changed at precise effective intervals. Which action is MOST appropriate?
- Evaluate Parquet or supported open-table formats against reader compatibility and mutation requirements.
- Evaluate dimensional normalization against query complexity, maintenance and expected cardinality.
- Choose incremental append or merge based on immutable versus mutable source behavior.
- Use a temporal history model with nonoverlapping effective-from and effective-to boundaries.
Explanation
Correct Answer
D:The most appropriate action is: Use a temporal history model with nonoverlapping effective-from and effective-to boundaries. It addresses the stated condition: A historical compliance table must show how account status changed at precise effective intervals. The technical basis is: Temporal tables describe the validity of state over time rather than only its latest value. Without this control, overlapping intervals can cause a historical lookup to return multiple contradictory statuses. A direct acceptance check is: A boundary-date test resolves each account to exactly one status for every audited instant.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An external sharing integration needs interoperable columnar read files but not native Delta updates. The corresponding measure there would be: Evaluate Parquet or supported open-table formats against reader compatibility and mutation requirements. The stated situation instead calls for: Use a temporal history model with nonoverlapping effective-from and effective-to boundaries.
B:This alternative primarily addresses a different Azure Databricks problem: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. The corresponding measure there would be: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. The stated situation instead calls for: Use a temporal history model with nonoverlapping effective-from and effective-to boundaries.
C:This alternative primarily addresses a different Azure Databricks problem: A raw event lake contains append-only records but a developer chooses daily full overwrite of the curated Delta table. The corresponding measure there would be: Choose incremental append or merge based on immutable versus mutable source behavior. The stated situation instead calls for: Use a temporal history model with nonoverlapping effective-from and effective-to boundaries.
Question 314
The design team proposes: Assign a dedicated run-as identity with durable scoped grants and an ownership review. The situation is: A job uses a service principal that loses access to the destination schema when an employee leaves. Which technical principle justifies the decision?
- Consistent parameter passing ensures dependent tasks operate on the same business interval.
- Retries cannot repair missing tables or invalid schema references without corrective action.
- Production job run identities must be stable and authorized independent of a human notebook editor.
- Job task state transitions follow dependency and conditional execution rules.
Explanation
Correct Answer
C:The decisive mechanism is: Production job run identities must be stable and authorized independent of a human notebook editor. That explains the selected action: Assign a dedicated run-as identity with durable scoped grants and an ownership review. In the original scenario: A job uses a service principal that loses access to the destination schema when an employee leaves. The specific unmanaged risk is: User-linked credentials can break scheduled jobs after account deactivation or team reassignment. Validate with: A scheduled run succeeds under the named service principal after the former owner account is disabled.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A workflow needs to pass a date parameter from a scheduled trigger into all its downstream notebook tasks. Its targeted response is: Define validated job parameters and propagate them through supported task parameter bindings. The current case is governed more directly by: Production job run identities must be stable and authorized independent of a human notebook editor.
B:This principle concerns a separate data-engineering condition: A job's retry policy restarts a deterministic bad SQL query six times even though the table is missing. Its targeted response is: Limit retries to appropriate transient errors and set accountable failure handling for permanent logic problems. The current case is governed more directly by: Production job run identities must be stable and authorized independent of a human notebook editor.
D:This principle concerns a separate data-engineering condition: A job owner cannot explain why a task skipped execution after a predecessor failed. Its targeted response is: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. The current case is governed more directly by: Production job run identities must be stable and authorized independent of a human notebook editor.
Question 315
A production data team leaves out: Place validations before publishing and use an atomic cutover or controlled target write. Its scenario is: A workflow writes to production tables before a validation task examines null keys and duplicates. Which failure mode is MOST relevant?
- Immediate permanent failure on a brief service outage can miss a delivery SLA.
- A downstream report can close before late but permitted events are incorporated.
- Consumers can query invalid data during the interval before quality checks finish.
- Readers can combine incompatible versions when related tables update independently.
Explanation
Correct Answer
C:The direct residual exposure is: Consumers can query invalid data during the interval before quality checks finish. The triggering condition is: A workflow writes to production tables before a validation task examines null keys and duplicates. The omitted safeguard is: Place validations before publishing and use an atomic cutover or controlled target write. This matters because: Quality gates must precede trusted publication, not merely log errors afterwards. A corrective test would show: Invalid input blocks publication while the previous approved dataset remains available.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. Its preventative action would be: Add bounded retries with exponential backoff and observable failure after the retry budget. The most direct exposure in the current scenario is: Consumers can query invalid data during the interval before quality checks finish.
B: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: Consumers can query invalid data during the interval before quality checks finish.
D:This failure mode belongs mainly to another situation: A regulated pipeline needs consistent transaction boundaries across multiple table writes but updates are published one at a time. Its preventative action would be: Design a compatible atomic publication or versioned readiness contract so consumers see consistent results. The most direct exposure in the current scenario is: Consumers can query invalid data during the interval before quality checks finish.
Question 316
A solution applies: Use an external Unity Catalog table with an approved registered location instead of assuming managed storage ownership. It addresses: A dataset has a strict requirement that Azure storage ownership and lifecycle remain under a separate platform team. Which operational outcome MOST directly verifies success?
- A sampled monthly report reconciles to source invoices and a join-cardinality test finds no fanout.
- The purchase remains traceable and later dimension arrival resolves the customer association without duplication.
- The platform team retains approved storage lifecycle authority while Databricks queries the registered data.
- A replay from a preserved source batch reproduces the expected silver and gold data after a code fix.
Explanation
Correct Answer
C:The strongest acceptance proof is: The platform team retains approved storage lifecycle authority while Databricks queries the registered data. It specifically verifies: Use an external Unity Catalog table with an approved registered location instead of assuming managed storage ownership. The original issue was: A dataset has a strict requirement that Azure storage ownership and lifecycle remain under a separate platform team. The underlying mechanism is: External tables separate catalog management from independently controlled underlying file lifecycle. Without it, migrating data into a managed table can violate external storage governance agreements.
Incorrect Answers
A:This result would validate a different measure: Design a conformed star schema with explicit fact grain and unique dimension keys. That is relevant to the distinct problem: A finance dashboard needs monthly revenue by customer and must join customer dimensions without multiplying facts. Here the acceptance criterion is: The platform team retains approved storage lifecycle authority while Databricks queries the registered data.
B:This result would validate a different measure: Define a deliberate unknown-member or late-dimension reconciliation pattern without silently dropping facts. That is relevant to the distinct problem: A late-arriving purchase refers to a customer identifier whose dimension record has not yet been ingested. Here the acceptance criterion is: The platform team retains approved storage lifecycle authority while Databricks queries the registered data.
D:This result would validate a different measure: Keep a governed raw or bronze representation before applying irreversible cleansing into silver and gold. That is relevant to the distinct problem: A bronze ingestion layer stores only final transformed values and loses raw source fields needed for incident replay. Here the acceptance criterion is: The platform team retains approved storage lifecycle authority while Databricks queries the registered data.
Question 317
A production data platform experiences this condition: An operations group wants to roll back a broken Lakeflow workflow but keeps no previous package version. Which targeted measure should be selected?
- Define and validate environment-specific catalog, workspace and identity targets in deployment configuration.
- Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging.
- Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle.
- Tag and retain approved bundle releases and document a verified redeploy or rollback procedure.
Explanation
Correct Answer
D:The most appropriate action is: Tag and retain approved bundle releases and document a verified redeploy or rollback procedure. It addresses the stated condition: An operations group wants to roll back a broken Lakeflow workflow but keeps no previous package version. The technical basis is: Immutable release versions enable controlled recovery of pipeline configuration and code. Without this control, without versioned artifacts, recovery may require reconstructing past settings by memory. A direct acceptance check is: A rehearsed rollback restores a prior tested bundle and recovers the expected job definitions.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A multi-environment setup uses the same catalog for test and production because bundle target variables were omitted. The corresponding measure there would be: Define and validate environment-specific catalog, workspace and identity targets in deployment configuration. The stated situation instead calls for: Tag and retain approved bundle releases and document a verified redeploy or rollback procedure.
B:This alternative primarily addresses a different Azure Databricks problem: A new pipeline passes unit tests but production fails because the service principal lacks a catalog grant. The corresponding measure there would be: Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging. The stated situation instead calls for: Tag and retain approved bundle releases and document a verified redeploy or rollback procedure.
C:This alternative primarily addresses a different Azure Databricks problem: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. The corresponding measure there would be: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. The stated situation instead calls for: Tag and retain approved bundle releases and document a verified redeploy or rollback procedure.
Question 318
A Databricks engineer recommends: Add user acceptance tests for the relevant reporting contract before production promotion. It responds to: A developer changes a transformation with a user-visible business effect but omits acceptance testing by the data product owner. What underlying mechanism BEST explains why?
- Technical tests cannot replace business approval of the reported meaning of data.
- Deployment APIs can reject requests even when the calling script continues to run.
- Infrastructure automation must tolerate retries without multiplying the intended target resources.
- Schema and object naming changes can break consumers even when new ETL succeeds.
Explanation
Correct Answer
A:The decisive mechanism is: Technical tests cannot replace business approval of the reported meaning of data. That explains the selected action: Add user acceptance tests for the relevant reporting contract before production promotion. In the original scenario: A developer changes a transformation with a user-visible business effect but omits acceptance testing by the data product owner. The specific unmanaged risk is: A numerically correct but semantically changed field can mislead business users. Validate with: A product owner signs off a sample report and its reconciled acceptance criteria before rollout.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: An automation job uses Databricks REST APIs but omits response-code checks and assumes every HTTP request succeeded. Its targeted response is: Validate API status and returned resource identifiers, then use bounded retries only for transient failures. The current case is governed more directly by: Technical tests cannot replace business approval of the reported meaning of data.
C:This principle concerns a separate data-engineering condition: A REST deployment script creates duplicate jobs every time CI reruns after a timeout. Its targeted response is: Use idempotent deployment methods or reconcile existing resource IDs before creating replacements. The current case is governed more directly by: Technical tests cannot replace business approval of the reported meaning of data.
D:This principle concerns a separate data-engineering condition: A sensitive SQL view is renamed in the release but the team does not test downstream dashboards before promotion. Its targeted response is: Run end-to-end contract tests for dependent readers and obtain owner approval for breaking changes. The current case is governed more directly by: Technical tests cannot replace business approval of the reported meaning of data.
Question 319
The following control has NOT been implemented: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. In this case: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. Which exposure remains?
- Direct-path writes can bypass registration and leave unowned storage artifacts.
- Granting SELECT alone may not make a catalog object usable and lead to excessive troubleshooting grants.
- Confusing catalog visibility with data authorization can lead to unnecessary sensitive table access.
- One missing tenant predicate can expose another customer’s records.
Explanation
Correct Answer
C:The direct residual exposure is: Confusing catalog visibility with data authorization can lead to unnecessary sensitive table access. The triggering condition is: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. The omitted safeguard is: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. This matters because: Object discovery or BROWSE is not a grant to read its underlying data. A corrective test would show: An auditor lists allowed table metadata without retrieving restricted row contents.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A user is granted CREATE TABLE but cannot create an external table at an unregistered cloud path. Its preventative action would be: Configure a supported external location and specific creation privileges rather than bypassing the catalog to write directly. The most direct exposure in the current scenario is: Confusing catalog visibility with data authorization can lead to unnecessary sensitive table access.
B:This failure mode belongs mainly to another situation: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. Its preventative action would be: Check required parent catalog and schema usage privileges alongside the table SELECT grant. The most direct exposure in the current scenario is: Confusing catalog visibility with data authorization can lead to unnecessary sensitive table access.
D:This failure mode belongs mainly to another situation: A multi-tenant analytics table relies on application code to append customer_id filtering. Its preventative action would be: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. The most direct exposure in the current scenario is: Confusing catalog visibility with data authorization can lead to unnecessary sensitive table access.
Question 320
A production data platform experiences this condition: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. Which targeted measure should be selected?
- Define a range expectation with metrics and the approved drop, fail or quarantine disposition.
- Apply type, nullability and range expectations before promoting bronze rows into the silver target.
- Configure expectations with an explicit fail, drop or retention behavior aligned to business severity.
- Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths.
Explanation
Correct Answer
B:The most appropriate action is: Apply type, nullability and range expectations before promoting bronze rows into the silver target. It addresses the stated condition: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. The technical basis is: Layered quality gates prevent malformed source values from contaminating trusted downstream tables. Without this control, invalid amounts may silently convert to null and skew revenue aggregates. A direct acceptance check is: A controlled malformed amount is detected and excluded from published silver while legitimate zero values remain.
Incorrect Answers
A: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: Apply type, nullability and range expectations before promoting bronze rows into the silver target.
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: Apply type, nullability and range expectations before promoting bronze rows into the silver target.
D: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: Apply type, nullability and range expectations before promoting bronze rows into the silver target.