Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 26
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.
Question 251
A solution applies: Use a secure service identity and protected credential handling for bundle or REST API deployment. It addresses: A CI pipeline deploys Databricks assets under an engineer's personal token stored in repository variables. Which operational outcome MOST directly verifies success?
- CI deploys under the named service principal and the personal token is rejected and revoked.
- Two identical deployment executions leave exactly one intended job with approved settings.
- A rendered staging plan references only staging catalogs and refuses production resource paths.
- A test UI change is flagged and the approved deployment restores the intended configuration.
Explanation
Correct Answer
A:The strongest acceptance proof is: CI deploys under the named service principal and the personal token is rejected and revoked. It specifically verifies: Use a secure service identity and protected credential handling for bundle or REST API deployment. The original issue was: A CI pipeline deploys Databricks assets under an engineer's personal token stored in repository variables. The underlying mechanism is: Automated releases should not depend on personal accounts or broadly exposed long-lived credentials. Without it, an exposed or disabled personal token can compromise or halt all production deployments.
Incorrect Answers
B:This result would validate a different measure: Use idempotent deployment methods or reconcile existing resource IDs before creating replacements. That is relevant to the distinct problem: A REST deployment script creates duplicate jobs every time CI reruns after a timeout. Here the acceptance criterion is: CI deploys under the named service principal and the personal token is rejected and revoked.
C:This result would validate a different measure: Define and validate environment-specific catalog, workspace and identity targets in deployment configuration. That is relevant to the distinct problem: A multi-environment setup uses the same catalog for test and production because bundle target variables were omitted. Here the acceptance criterion is: CI deploys under the named service principal and the personal token is rejected and revoked.
D:This result would validate a different measure: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. That is relevant to the distinct problem: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. Here the acceptance criterion is: CI deploys under the named service principal and the personal token is rejected and revoked.
Question 252
For this Microsoft DP-750 case: A new pipeline passes unit tests but production fails because the service principal lacks a catalog grant. Which design or operational response BEST fits?
- Include an integration test using actual Delta table semantics and representative source changes.
- Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI.
- Validate API status and returned resource identifiers, then use bounded retries only for transient failures.
- Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging.
Explanation
Correct Answer
D:The most appropriate action is: Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging. It addresses the stated condition: A new pipeline passes unit tests but production fails because the service principal lacks a catalog grant. The technical basis is: Release readiness includes environment contracts and authorization beyond pure transformation logic. Without this control, A deployment may succeed while the first production job cannot access its storage or schema. A direct acceptance check is: A staging run under the intended service principal reads and writes only its authorized objects.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. The corresponding measure there would be: Include an integration test using actual Delta table semantics and representative source changes. The stated situation instead calls for: Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging.
B:This alternative primarily addresses a different Azure Databricks problem: A team copies Databricks notebooks manually between three workspaces and each uses different hardcoded identifiers. The corresponding measure there would be: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI. The stated situation instead calls for: Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging.
C:This alternative primarily addresses a different Azure Databricks problem: An automation job uses Databricks REST APIs but omits response-code checks and assumes every HTTP request succeeded. The corresponding measure there would be: Validate API status and returned resource identifiers, then use bounded retries only for transient failures. The stated situation instead calls for: Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging.
Question 253
An implementation skips: Configure a supported external location and specific creation privileges rather than bypassing the catalog to write directly. Engineers are observing: A user is granted CREATE TABLE but cannot create an external table at an unregistered cloud path. What consequence is MOST likely?
- Granting SELECT alone may not make a catalog object usable and lead to excessive troubleshooting grants.
- Unnecessary modification rights can let a compromised analyst alter financial records.
- Direct-path writes can bypass registration and leave unowned storage artifacts.
- A user could retrieve other regions by querying the table without an application filter.
Explanation
Correct Answer
C:The direct residual exposure is: Direct-path writes can bypass registration and leave unowned storage artifacts. The triggering condition is: A user is granted CREATE TABLE but cannot create an external table at an unregistered cloud path. The omitted safeguard is: Configure a supported external location and specific creation privileges rather than bypassing the catalog to write directly. This matters because: Creating an external table requires governed location and storage authorization beyond a generic schema creation grant. A corrective test would show: An approved DDL operation creates the external table at a registered location and an arbitrary path is rejected.
Incorrect Answers
A: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: Direct-path writes can bypass registration and leave unowned storage artifacts.
B:This failure mode belongs mainly to another situation: A finance analyst must read an approved table but was granted broad MODIFY rights at the schema level. Its preventative action would be: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants. The most direct exposure in the current scenario is: Direct-path writes can bypass registration and leave unowned storage artifacts.
D:This failure mode belongs mainly to another situation: A user must see only the East region rows of a common sales table while managers see all territories. Its preventative action would be: Configure a tested Unity Catalog row filter or suitable ABAC policy based on the authorized identity. The most direct exposure in the current scenario is: Direct-path writes can bypass registration and leave unowned storage artifacts.
Question 254
The design team proposes: Inspect driver collection and query planning behavior before simply enlarging every worker. The situation is: A SQL transformation consumes large amounts of memory on the driver despite executor tasks processing most source partitions. Which technical principle justifies the decision?
- Interactive compute should have a governed idle lifecycle distinct from persistent services.
- Workload bottlenecks rather than raw input size should drive Spark cluster shape and resource selection.
- Spark and runtime upgrades can change supported APIs, dependency versions and execution behavior.
- Driver-side collection and planning bottlenecks cannot be corrected solely by scaling executor count.
Explanation
Correct Answer
D:The decisive mechanism is: Driver-side collection and planning bottlenecks cannot be corrected solely by scaling executor count. That explains the selected action: Inspect driver collection and query planning behavior before simply enlarging every worker. In the original scenario: A SQL transformation consumes large amounts of memory on the driver despite executor tasks processing most source partitions. The specific unmanaged risk is: Blindly increasing worker nodes leaves driver out-of-memory failures unchanged and increases cost. Validate with: Spark UI and driver metrics show bounded driver memory after correcting the collection pattern.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A newly created cluster remains available for hours after manual exploration even though the organization has a strict idle-cost policy. Its targeted response is: Set appropriate auto-termination or idle controls for interactive compute while excluding workloads requiring continuous availability. The current case is governed more directly by: Driver-side collection and planning bottlenecks cannot be corrected solely by scaling executor count.
B:This principle concerns a separate data-engineering condition: A new job uses a large memory-optimized node merely because its source data is large, although profiling shows compute-bound transforms. Its targeted response is: Choose node families and driver/worker sizes using CPU, memory, shuffle and workload profile evidence. The current case is governed more directly by: Driver-side collection and planning bottlenecks cannot be corrected solely by scaling executor count.
C:This principle concerns a separate data-engineering condition: A developer selects a new Databricks Runtime version for production despite an untested JDBC driver dependency. Its targeted response is: Pin a supported Databricks Runtime version and validate application libraries against it before deployment. The current case is governed more directly by: Driver-side collection and planning bottlenecks cannot be corrected solely by scaling executor count.
Question 255
The design team proposes: Define a deliberate unknown-member or late-dimension reconciliation pattern without silently dropping facts. The situation is: A late-arriving purchase refers to a customer identifier whose dimension record has not yet been ingested. Which technical principle justifies the decision?
- Delta tables support transactional mutations and versioned metadata beyond raw delimiter files.
- Physical layout should match selective consumer predicates rather than convenience of ingestion.
- Late facts and missing dimension keys require explicit referential handling.
- Delta version history can provide auditable historical snapshots while underlying files are retained.
Explanation
Correct Answer
C:The decisive mechanism is: Late facts and missing dimension keys require explicit referential handling. That explains the selected action: Define a deliberate unknown-member or late-dimension reconciliation pattern without silently dropping facts. In the original scenario: A late-arriving purchase refers to a customer identifier whose dimension record has not yet been ingested. The specific unmanaged risk is: Inner joining only currently known dimension rows can undercount legitimate transactions. Validate with: The purchase remains traceable and later dimension arrival resolves the customer association without duplication.
Incorrect Answers
A: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: Late facts and missing dimension keys require explicit referential handling.
B:This principle concerns a separate data-engineering condition: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. Its targeted response is: Reevaluate data layout using representative event-time filters and a suitable clustering key. The current case is governed more directly by: Late facts and missing dimension keys require explicit referential handling.
D:This principle concerns a separate data-engineering condition: A business needs to compare two point-in-time table versions during a financial reconciliation. Its targeted response is: Use supported Delta table version history and time travel within the documented retention window. The current case is governed more directly by: Late facts and missing dimension keys require explicit referential handling.
Question 256
A data engineering team faces this Azure Databricks requirement: An engineer changes the expected file schema in one notebook but forgets to update the Lakeflow pipeline definition. Which action is MOST appropriate?
- Apply schema enforcement with explicit drift handling and alert on incompatible structural changes.
- Run a supported uniqueness or cardinality validation during the transformation and surface violations.
- Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths.
- Validate timezone-aware timestamp types and quarantine ambiguous or unparseable event values.
Explanation
Correct Answer
C:The most appropriate action is: Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths. It addresses the stated condition: An engineer changes the expected file schema in one notebook but forgets to update the Lakeflow pipeline definition. The technical basis is: Schema governance must span all ingestion paths that write to a common table. Without this control, inconsistent schema assumptions create intermittent casts, quarantines or dropped columns. A direct acceptance check is: Both pipeline paths validate the same additive and incompatible change samples consistently.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A source API changes a quantity from integer to nested JSON and the pipeline silently produces nulls downstream. The corresponding measure there would be: Apply schema enforcement with explicit drift handling and alert on incompatible structural changes. The stated situation instead calls for: Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths.
B:This alternative primarily addresses a different Azure Databricks problem: A curated account table accidentally contains multiple rows per supposedly unique current account ID. The corresponding measure there would be: Run a supported uniqueness or cardinality validation during the transformation and surface violations. The stated situation instead calls for: Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths.
D:This alternative primarily addresses a different Azure Databricks problem: A regulated dataset requires all timestamps to parse as UTC but several rows have ambiguous local values. The corresponding measure there would be: Validate timezone-aware timestamp types and quarantine ambiguous or unparseable event values. The stated situation instead calls for: Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths.
Question 257
A data product owner adopts: Use a Delta MERGE keyed by SKU with appropriate matched-update and not-matched-insert logic. The reason is: A product catalog receives corrections for existing SKUs plus entirely new items on each incremental load. What observed result BEST proves effectiveness?
- Rows with absent country are flagged for resolution and approved true defaults are applied consistently.
- A timed append comparison meets the freshness and duplicate controls with lower compute consumption.
- A controlled money sample matches expected exact decimal totals and rejects malformed amounts.
- Two consecutive loads yield one current row per SKU, including corrected price and new items.
Explanation
Correct Answer
D:The strongest acceptance proof is: Two consecutive loads yield one current row per SKU, including corrected price and new items. It specifically verifies: Use a Delta MERGE keyed by SKU with appropriate matched-update and not-matched-insert logic. The original issue was: A product catalog receives corrections for existing SKUs plus entirely new items on each incremental load. The underlying mechanism is: MERGE combines inserts and updates atomically against a keyed target. Without it, blind append creates multiple current versions and breaks consumer joins.
Incorrect Answers
A:This result would validate a different measure: Define field-specific missing-value rules and quarantine or enrich unknown values before assigning business meaning. That is relevant to the distinct problem: A customer reference dataset has missing country codes but a pipeline replaces every null with an arbitrary default country. Here the acceptance criterion is: Two consecutive loads yield one current row per SKU, including corrected price and new items.
B:This result would validate a different measure: Use an incremental append pattern with suitable deduplication when source events cannot change. That is relevant to the distinct problem: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. Here the acceptance criterion is: Two consecutive loads yield one current row per SKU, including corrected price and new items.
C:This result would validate a different measure: Parse and cast monetary values to a suitable decimal type with invalid-value handling. That is relevant to the distinct problem: A finance field arrives as a string with currency symbols and the team aggregates it lexicographically. Here the acceptance criterion is: Two consecutive loads yield one current row per SKU, including corrected price and new items.
Question 258
For this Azure Databricks issue: A team copies Databricks notebooks manually between three workspaces and each uses different hardcoded identifiers. Engineers choose: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI. What acceptance evidence is BEST?
- A rehearsed rollback restores a prior tested bundle and recovers the expected job definitions.
- A rendered staging plan references only staging catalogs and refuses production resource paths.
- A staging and production deployment use one versioned definition but distinct approved parameters.
- Deployment plans show the intended trigger for each target and a test job fires at the correct interval.
Explanation
Correct Answer
C:The strongest acceptance proof is: A staging and production deployment use one versioned definition but distinct approved parameters. It specifically verifies: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI. The original issue was: A team copies Databricks notebooks manually between three workspaces and each uses different hardcoded identifiers. The underlying mechanism is: Declarative bundle definitions can make job and pipeline deployments repeatable across environments. Without it, manual workspace copying can omit task settings and point production at development tables.
Incorrect Answers
A:This result would validate a different measure: Tag and retain approved bundle releases and document a verified redeploy or rollback procedure. That is relevant to the distinct problem: An operations group wants to roll back a broken Lakeflow workflow but keeps no previous package version. Here the acceptance criterion is: A staging and production deployment use one versioned definition but distinct approved parameters.
B:This result would validate a different measure: Define and validate environment-specific catalog, workspace and identity targets in deployment configuration. That is relevant to the distinct problem: A multi-environment setup uses the same catalog for test and production because bundle target variables were omitted. Here the acceptance criterion is: A staging and production deployment use one versioned definition but distinct approved parameters.
D:This result would validate a different measure: Validate per-target bundle variable resolution and compare rendered job definitions before deployment. That is relevant to the distinct problem: A data engineer updates a bundled job trigger but another environment's deployment silently uses the wrong schedule. Here the acceptance criterion is: A staging and production deployment use one versioned definition but distinct approved parameters.
Question 259
The design team proposes: Define and validate environment-specific catalog, workspace and identity targets in deployment configuration. The situation is: A multi-environment setup uses the same catalog for test and production because bundle target variables were omitted. Which technical principle justifies the decision?
- Conflict resolution must preserve intended behavior from both change sets.
- Deployment isolation depends on correct values for each environment's object references.
- Source control only provides operational truth when actual resource settings match the approved definition.
- Release readiness includes environment contracts and authorization beyond pure transformation logic.
Explanation
Correct Answer
B:The decisive mechanism is: Deployment isolation depends on correct values for each environment's object references. That explains the selected action: Define and validate environment-specific catalog, workspace and identity targets in deployment configuration. In the original scenario: A multi-environment setup uses the same catalog for test and production because bundle target variables were omitted. The specific unmanaged risk is: A staging test might overwrite production assets when default variables point to shared locations. Validate with: A rendered staging plan references only staging catalogs and refuses production resource paths.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: Two engineers change the same ingestion function on separate branches and one silently overwrites the other's fix. Its targeted response is: Resolve Git merge conflicts with tests and reviewed integration before merging the release branch. The current case is governed more directly by: Deployment isolation depends on correct values for each environment's object references.
C:This principle concerns a separate data-engineering condition: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. Its targeted response is: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. The current case is governed more directly by: Deployment isolation depends on correct values for each environment's object references.
D:This principle concerns a separate data-engineering condition: A new pipeline passes unit tests but production fails because the service principal lacks a catalog grant. Its targeted response is: Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging. The current case is governed more directly by: Deployment isolation depends on correct values for each environment's object references.
Question 260
The following control has NOT been implemented: Set appropriate auto-termination or idle controls for interactive compute while excluding workloads requiring continuous availability. In this case: A newly created cluster remains available for hours after manual exploration even though the organization has a strict idle-cost policy. Which exposure remains?
- Forgotten development clusters can consume cloud resources long after the last useful notebook cell.
- A fixed undersized cluster misses month-end deadlines while an oversized fixed cluster wastes daily spend.
- A stream may stop unexpectedly and leave event consumption behind its permitted freshness objective.
- Unmeasured tuning changes can hide the original bottleneck or increase compute costs.
Explanation
Correct Answer
A:The direct residual exposure is: Forgotten development clusters can consume cloud resources long after the last useful notebook cell. The triggering condition is: A newly created cluster remains available for hours after manual exploration even though the organization has a strict idle-cost policy. The omitted safeguard is: Set appropriate auto-termination or idle controls for interactive compute while excluding workloads requiring continuous availability. This matters because: Interactive compute should have a governed idle lifecycle distinct from persistent services. A corrective test would show: An inactive test cluster terminates after the configured interval and users can restart it when authorized.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. Its preventative action would be: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. The most direct exposure in the current scenario is: Forgotten development clusters can consume cloud resources long after the last useful notebook cell.
C:This failure mode belongs mainly to another situation: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. Its preventative action would be: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. The most direct exposure in the current scenario is: Forgotten development clusters can consume cloud resources long after the last useful notebook cell.
D:This failure mode belongs mainly to another situation: A team turns on every performance setting for a workload without benchmarking whether disk spills or network shuffle dominate runtime. Its preventative action would be: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data. The most direct exposure in the current scenario is: Forgotten development clusters can consume cloud resources long after the last useful notebook cell.