Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 45
Question 440
For this Azure Databricks issue: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. Engineers choose: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. What acceptance evidence is BEST?
- Representative business queries return consistent region totals with an acceptable plan.
- The top event-time queries show improved data skipping and reconciled row counts.
- The platform team retains approved storage lifecycle authority while Databricks queries the registered data.
- A controlled late event appears in the correct historical period according to the approved policy.
Explanation
Correct Answer
A:The strongest acceptance proof is: Representative business queries return consistent region totals with an acceptable plan. It specifically verifies: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. The original issue was: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. The underlying mechanism is: Data models balance redundancy and query simplicity according to workload requirements. Without it, unneeded normalization can add joins while denormalization without governance can produce inconsistent descriptions.
Incorrect Answers
B:This result would validate a different measure: Reevaluate data layout using representative event-time filters and a suitable clustering key. That is relevant to the distinct problem: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. Here the acceptance criterion is: Representative business queries return consistent region totals with an acceptable plan.
C:This result would validate a different measure: Use an external Unity Catalog table with an approved registered location instead of assuming managed storage ownership. That is relevant to the distinct problem: A dataset has a strict requirement that Azure storage ownership and lifecycle remain under a separate platform team. Here the acceptance criterion is: Representative business queries return consistent region totals with an acceptable plan.
D:This result would validate a different measure: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. That is relevant to the distinct problem: A lakehouse receives sensor observations with event timestamps that arrive out of order. Here the acceptance criterion is: Representative business queries return consistent region totals with an acceptable plan.
Question 441
A Databricks engineer recommends: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. It responds to: A data-sharing project emails storage keys to an external partner for reading curated Delta results. What underlying mechanism BEST explains why?
- Security governance requires attributable administrative activity and durable evidence.
- Delta Sharing can provide governed data access without distributing underlying storage account keys.
- External sharing must include explicit revocation and monitoring, not only initial provisioning.
- Ordinary table replacement does not automatically constitute defensible preservation of historical legal records.
Explanation
Correct Answer
B:The decisive mechanism is: Delta Sharing can provide governed data access without distributing underlying storage account keys. That explains the selected action: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. In the original scenario: A data-sharing project emails storage keys to an external partner for reading curated Delta results. The specific unmanaged risk is: Long-lived shared storage credentials may expose unrelated files or survive contract termination. Validate with: The partner reads only the approved shared table and fails to access a nonshared table.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. Its targeted response is: Configure supported Databricks audit logging and route relevant events to a secured retention destination. The current case is governed more directly by: Delta Sharing can provide governed data access without distributing underlying storage account keys.
C:This principle concerns a separate data-engineering condition: A Delta Sharing recipient must stop receiving future updates after an agreement expires. Its targeted response is: Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access. The current case is governed more directly by: Delta Sharing can provide governed data access without distributing underlying storage account keys.
D:This principle concerns a separate data-engineering condition: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. Its targeted response is: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. The current case is governed more directly by: Delta Sharing can provide governed data access without distributing underlying storage account keys.
Question 442
A platform architect adopts: Use Spark-native distributed read and transformation APIs or partition-safe processing. For this requirement: A Python notebook reads a massive table into pandas on the driver before processing data intended for Spark executors. Which rationale MOST directly supports it?
- Data pipeline completeness requires tracking arrivals rather than assuming an exact wall-clock boundary.
- Message-bus streams require offset progress tracking and a durable state boundary.
- Delivery guarantees alone do not remove duplicate producer or consumer events.
- Pulling distributed data to a single driver defeats parallel execution and memory limits.
Explanation
Correct Answer
D:The decisive mechanism is: Pulling distributed data to a single driver defeats parallel execution and memory limits. That explains the selected action: Use Spark-native distributed read and transformation APIs or partition-safe processing. In the original scenario: A Python notebook reads a massive table into pandas on the driver before processing data intended for Spark executors. The specific unmanaged risk is: Driver out-of-memory can fail the load despite adequate executor resources. Validate with: The workload completes without driver collection and Spark metrics show distributed processing.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A Databricks job receives daily structured extracts but an upstream schedule occasionally delivers files late. Its targeted response is: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark. The current case is governed more directly by: Pulling distributed data to a single driver defeats parallel execution and memory limits.
B:This principle concerns a separate data-engineering condition: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. Its targeted response is: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. The current case is governed more directly by: Pulling distributed data to a single driver defeats parallel execution and memory limits.
C:This principle concerns a separate data-engineering condition: An ingestion pipeline reads cloud events with at-least-once delivery and assumes every event ID appears only once. Its targeted response is: Deduplicate by stable event identity and business time using documented state and watermark rules. The current case is governed more directly by: Pulling distributed data to a single driver defeats parallel execution and memory limits.
Question 443
During a lakehouse implementation review, engineers observe: A data engineer updates a bundled job trigger but another environment's deployment silently uses the wrong schedule. What is the BEST next action?
- Run end-to-end contract tests for dependent readers and obtain owner approval for breaking changes.
- Validate API status and returned resource identifiers, then use bounded retries only for transient failures.
- Validate per-target bundle variable resolution and compare rendered job definitions before deployment.
- Define and validate environment-specific catalog, workspace and identity targets in deployment configuration.
Explanation
Correct Answer
C:The most appropriate action is: Validate per-target bundle variable resolution and compare rendered job definitions before deployment. It addresses the stated condition: A data engineer updates a bundled job trigger but another environment's deployment silently uses the wrong schedule. The technical basis is: Configuration-as-code requires environment-specific parameter checks as well as common source control. Without this control, A wrong schedule can duplicate loads or miss critical reporting windows. A direct acceptance check is: Deployment plans show the intended trigger for each target and a test job fires at the correct interval.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A sensitive SQL view is renamed in the release but the team does not test downstream dashboards before promotion. The corresponding measure there would be: Run end-to-end contract tests for dependent readers and obtain owner approval for breaking changes. The stated situation instead calls for: Validate per-target bundle variable resolution and compare rendered job definitions before deployment.
B: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: Validate per-target bundle variable resolution and compare rendered job definitions before deployment.
D: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: Validate per-target bundle variable resolution and compare rendered job definitions before deployment.
Question 444
The following control has NOT been implemented: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings. In this case: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. Which exposure remains?
- A broadly shared catalog can expose regulated data to unintended region workspaces.
- Direct downstream table references can break when upstream columns are renamed.
- Data may remain readable by direct path while the intended catalog table fails authorization.
- An ownerless shared view may expose unreviewed columns or become impossible to maintain safely.
Explanation
Correct Answer
A:The direct residual exposure is: A broadly shared catalog can expose regulated data to unintended region workspaces. The triggering condition is: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. The omitted safeguard is: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings. This matters because: Catalog separation and workspace access controls can help enforce organizational and geography boundaries. A corrective test would show: Approved regional workspaces access their catalogs while a disallowed workspace fails its access test.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. Its preventative action would be: Define a stable contract through managed views and test compatibility before changing source objects. The most direct exposure in the current scenario is: A broadly shared catalog can expose regulated data to unintended region workspaces.
C:This failure mode belongs mainly to another situation: A managed Delta table is migrated to external storage but the team does not update table registration or grant scopes. Its preventative action would be: Recreate or update supported external table registration using an approved location and correct access controls. The most direct exposure in the current scenario is: A broadly shared catalog can expose regulated data to unintended region workspaces.
D:This failure mode belongs mainly to another situation: A central team creates global views that hide source objects but forgets to document ownership and access grants. Its preventative action would be: Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema. The most direct exposure in the current scenario is: A broadly shared catalog can expose regulated data to unintended region workspaces.
Question 445
The team implements: Use query-profile evidence and a supported skew mitigation such as adaptive execution or key-aware repartitioning. The original problem is: A DataFrame join spills heavily because a single join key occurs in most rows. Which test MOST convincingly demonstrates correctness?
- A benchmark shows lower total maintenance-plus-query cost without compromising retention.
- Post-mitigation stage durations are balanced and joined row counts remain correct.
- A representative run shows reduced spill bytes and matching aggregate results with improved runtime.
- A peak-load rehearsal stabilizes backlog and keeps end-to-end event age within target.
Explanation
Correct Answer
B:The strongest acceptance proof is: Post-mitigation stage durations are balanced and joined row counts remain correct. It specifically verifies: Use query-profile evidence and a supported skew mitigation such as adaptive execution or key-aware repartitioning. The original issue was: A DataFrame join spills heavily because a single join key occurs in most rows. The underlying mechanism is: Severe key skew causes uneven task work even with many executors. Without it, A small number of hot tasks can dominate the join while extra workers remain idle.
Incorrect Answers
A:This result would validate a different measure: Set a measured maintenance cadence or evaluate supported predictive optimization for eligible managed tables. That is relevant to the distinct problem: A new Delta table maintenance job combines repeated OPTIMIZE and VACUUM at every microbatch even though changes are tiny. Here the acceptance criterion is: Post-mitigation stage durations are balanced and joined row counts remain correct.
C:This result would validate a different measure: Examine shuffle metrics, memory pressure and partition sizing to target the spilling stage. That is relevant to the distinct problem: A large aggregation has repeated shuffle spills to disk even though source scans finish quickly. Here the acceptance criterion is: Post-mitigation stage durations are balanced and joined row counts remain correct.
D:This result would validate a different measure: Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling. That is relevant to the distinct problem: A streaming pipeline's throughput falls although event arrival increases and its input backlog grows over time. Here the acceptance criterion is: Post-mitigation stage durations are balanced and joined row counts remain correct.
Question 446
The following control has NOT been implemented: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay. In this case: A pipeline ingests Event Hubs messages into a bronze table but never captures the partition, offset or event timestamp. Which exposure remains?
- A failed data-quality rule cannot be traced back to the event-bus record that produced it.
- Ignoring changed source structures can halt ingestion or silently lose fields.
- Retries can duplicate invoices or notifications even if the source checkpoint is correct.
- Deleting stream state can cause full reprocessing or skipped incremental data.
Explanation
Correct Answer
A:The direct residual exposure is: A failed data-quality rule cannot be traced back to the event-bus record that produced it. The triggering condition is: A pipeline ingests Event Hubs messages into a bronze table but never captures the partition, offset or event timestamp. The omitted safeguard is: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay. This matters because: Streaming source metadata supports provenance and exact-range incident investigation. A corrective test would show: A sampled bronze row links to the expected stream partition and source event time.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A file feed introduces an unexpected optional column and the stream fails after the first changed file. Its preventative action would be: Configure supported schema evolution or rescued-data handling with explicit compatibility review. The most direct exposure in the current scenario is: A failed data-quality rule cannot be traced back to the event-bus record that produced it.
C:This failure mode belongs mainly to another situation: A stream writes into an external sink without stable batch identities and causes duplicate side effects on retry. Its preventative action would be: Implement idempotent foreachBatch or compatible transactional sink logic keyed by epoch or business identity. The most direct exposure in the current scenario is: A failed data-quality rule cannot be traced back to the event-bus record that produced it.
D:This failure mode belongs mainly to another situation: A long-running ingestion job persists its checkpoint in the same temporary folder that daily cleanup deletes. Its preventative action would be: Store checkpoint and schema tracking files in durable protected locations with retention matching the stream lifecycle. The most direct exposure in the current scenario is: A failed data-quality rule cannot be traced back to the event-bus record that produced it.
Question 447
A solution applies: Assign a dedicated run-as identity with durable scoped grants and an ownership review. It addresses: A job uses a service principal that loses access to the destination schema when an employee leaves. Which operational outcome MOST directly verifies success?
- A staged predecessor failure shows the approved downstream skip and cleanup path in run history.
- A test file arrives and starts one valid job run without repeated empty polling.
- A scheduled run succeeds under the named service principal after the former owner account is disabled.
- Run history shows the job starts at the agreed local times across representative date transitions.
Explanation
Correct Answer
C:The strongest acceptance proof is: A scheduled run succeeds under the named service principal after the former owner account is disabled. It specifically verifies: Assign a dedicated run-as identity with durable scoped grants and an ownership review. The original issue was: A job uses a service principal that loses access to the destination schema when an employee leaves. The underlying mechanism is: Production job run identities must be stable and authorized independent of a human notebook editor. Without it, user-linked credentials can break scheduled jobs after account deactivation or team reassignment.
Incorrect Answers
A:This result would validate a different measure: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. That is relevant to the distinct problem: A job owner cannot explain why a task skipped execution after a predecessor failed. Here the acceptance criterion is: A scheduled run succeeds under the named service principal after the former owner account is disabled.
B:This result would validate a different measure: Use a supported file-arrival trigger where its prerequisites and source location are compatible. That is relevant to the distinct problem: A cloud file feed needs a job triggered by arriving files instead of polling every minute. Here the acceptance criterion is: A scheduled run succeeds under the named service principal after the former owner account is disabled.
D:This result would validate a different measure: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant. That is relevant to the distinct problem: A business report must refresh daily at 06:00 in a defined local time zone but a developer schedules it in UTC without conversion. Here the acceptance criterion is: A scheduled run succeeds under the named service principal after the former owner account is disabled.
Question 448
A team omits the recommended measure: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid. Its environment shows: A bulk repair executes all pipeline tasks again even when only the final reporting notebook failed. What is the MOST direct residual risk?
- One late-stage error may force a costly replay of all preceding successful processing.
- Readers can combine incompatible versions when related tables update independently.
- A bad transformation may make a broken dataset immediately visible to consumers.
- Full reruns can repeat expensive historical ingestion and duplicate side effects.
Explanation
Correct Answer
D:The direct residual exposure is: Full reruns can repeat expensive historical ingestion and duplicate side effects. The triggering condition is: A bulk repair executes all pipeline tasks again even when only the final reporting notebook failed. The omitted safeguard is: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid. This matters because: Task-level repair reduces unnecessary recomputation while preserving dependency correctness. A corrective test would show: After a final-task failure, a repair completes the target without reprocessing validated upstream data.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A multi-step notebook workflow handles source extraction and final reporting in one cell sequence with no recoverable checkpoints. Its preventative action would be: Split ingestion, validation and publishing into explicit orchestrated tasks with durable intermediate outputs. The most direct exposure in the current scenario is: Full reruns can repeat expensive historical ingestion and duplicate side effects.
B: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: Full reruns can repeat expensive historical ingestion and duplicate side effects.
C:This failure mode belongs mainly to another situation: A finance transformation writes its output directly into a published table before reconciling totals against the source. Its preventative action would be: Write to a staging target, validate row totals and invariants, then perform the approved publication step. The most direct exposure in the current scenario is: Full reruns can repeat expensive historical ingestion and duplicate side effects.
Question 449
For this Microsoft DP-750 case: A release process merges unreviewed notebook changes directly into the main branch minutes before a production run. Which design or operational response BEST fits?
- Protect the main branch with peer review, required tests and controlled promotion windows.
- Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI.
- Tag and retain approved bundle releases and document a verified redeploy or rollback procedure.
- Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle.
Explanation
Correct Answer
A:The most appropriate action is: Protect the main branch with peer review, required tests and controlled promotion windows. It addresses the stated condition: A release process merges unreviewed notebook changes directly into the main branch minutes before a production run. The technical basis is: Reviewed changes with required status checks reduce uncontrolled production configuration drift. Without this control, A faulty last-minute edit can create an untested release with no accountable reviewer. A direct acceptance check is: An unauthorized direct push is rejected and a reviewed pull request completes all required gates.
Incorrect Answers
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: Protect the main branch with peer review, required tests and controlled promotion windows.
C:This alternative primarily addresses a different Azure Databricks problem: An operations group wants to roll back a broken Lakeflow workflow but keeps no previous package version. The corresponding measure there would be: Tag and retain approved bundle releases and document a verified redeploy or rollback procedure. The stated situation instead calls for: Protect the main branch with peer review, required tests and controlled promotion windows.
D: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: Protect the main branch with peer review, required tests and controlled promotion windows.
Question 450
A data product owner adopts: Store deployment source in Git with reviewed branches and pull requests before promoting changes. The reason is: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. What observed result BEST proves effectiveness?
- A staging dashboard loads its documented fields and a breaking-change simulation is rejected.
- A production run references an approved immutable commit and a prior version can be restored.
- A seeded test dataset returns documented expected outputs and intentionally bad inputs fail.
- Two identical deployment executions leave exactly one intended job with approved settings.
Explanation
Correct Answer
B:The strongest acceptance proof is: A production run references an approved immutable commit and a prior version can be restored. It specifically verifies: Store deployment source in Git with reviewed branches and pull requests before promoting changes. The original issue was: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. The underlying mechanism is: Version control and code review establish provenance and repeatable release history. Without it, unreviewed direct edits can break jobs without a reproducible rollback commit.
Incorrect Answers
A:This result would validate a different measure: Run end-to-end contract tests for dependent readers and obtain owner approval for breaking changes. That is relevant to the distinct problem: A sensitive SQL view is renamed in the release but the team does not test downstream dashboards before promotion. Here the acceptance criterion is: A production run references an approved immutable commit and a prior version can be restored.
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: A production run references an approved immutable commit and a prior version can be restored.
D: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: A production run references an approved immutable commit and a prior version can be restored.