Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 78
Question 770
The team implements: Validate timezone-aware timestamp types and quarantine ambiguous or unparseable event values. The original problem is: A regulated dataset requires all timestamps to parse as UTC but several rows have ambiguous local values. Which test MOST convincingly demonstrates correctness?
- A sample of valid UTC timestamps passes and known ambiguous strings produce the expected exception record.
- Each run reports complete input-to-output reconciliation and alerts when rejected fraction exceeds its SLO.
- Injected critical and noncritical bad rows follow their respective approved actions and emit metrics.
- A controlled negative-age record triggers the configured expectation event without being silently published.
Explanation
Correct Answer
A:The strongest acceptance proof is: A sample of valid UTC timestamps passes and known ambiguous strings produce the expected exception record. It specifically verifies: Validate timezone-aware timestamp types and quarantine ambiguous or unparseable event values. The original issue was: A regulated dataset requires all timestamps to parse as UTC but several rows have ambiguous local values. The underlying mechanism is: Type checks and temporal semantics must be aligned to prevent incorrect time-series results. Without it, ambiguous timestamp parsing can move financial events across reporting windows.
Incorrect Answers
B:This result would validate a different measure: Collect expectation metrics and reconcile input, accepted, quarantined and rejected record counts. That is relevant to the distinct problem: A pipeline reports zero failed rows because bad records are silently dropped without any count of what was removed. Here the acceptance criterion is: A sample of valid UTC timestamps passes and known ambiguous strings produce the expected exception record.
C: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 sample of valid UTC timestamps passes and known ambiguous strings produce the expected exception record.
D:This result would validate a different measure: Define a range expectation with metrics and the approved drop, fail or quarantine disposition. That is relevant to the distinct problem: A bronze stream sometimes includes ages below zero or above 120 yet the transformation casts every value to integer. Here the acceptance criterion is: A sample of valid UTC timestamps passes and known ambiguous strings produce the expected exception record.
Question 771
The team implements: Grant precise container-use and object-creation privileges based on actual job roles. The original problem is: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. Which test MOST convincingly demonstrates correctness?
- Contract tests continue to select documented columns through the published view after a staged schema change.
- A restricted query through the foreign catalog returns current permitted rows and honors source connectivity limits.
- Permitted users query only expected columns and rows through the view without a separately exported file.
- An analyst can query approved tables but cannot create a schema without a separate grant.
Explanation
Correct Answer
D:The strongest acceptance proof is: An analyst can query approved tables but cannot create a schema without a separate grant. It specifically verifies: Grant precise container-use and object-creation privileges based on actual job roles. The original issue was: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. The underlying mechanism is: Reading a governed object does not imply permission to create or administer peer objects. Without it, overbroad catalog privileges can let ordinary readers create misleading or unauthorized data products.
Incorrect Answers
A:This result would validate a different measure: Define a stable contract through managed views and test compatibility before changing source objects. That is relevant to the distinct problem: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. Here the acceptance criterion is: An analyst can query approved tables but cannot create a schema without a separate grant.
B:This result would validate a different measure: Create an authorized connection and supported foreign catalog for the external source. That is relevant to the distinct problem: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. Here the acceptance criterion is: An analyst can query approved tables but cannot create a schema without a separate grant.
C:This result would validate a different measure: Create a Unity Catalog view with approved permissions and verify underlying access semantics. That is relevant to the distinct problem: An analyst wants to expose a filtered projection of a governed table without copying sensitive source rows. Here the acceptance criterion is: An analyst can query approved tables but cannot create a schema without a separate grant.
Question 772
For this Microsoft DP-750 case: A retail customer table changes delivery address repeatedly but analysts must reconstruct the address known at any prior invoice date. Which design or operational response BEST fits?
- Define a deliberate unknown-member or late-dimension reconciliation pattern without silently dropping facts.
- Reevaluate data layout using representative event-time filters and a suitable clustering key.
- Define fact-table grain at the required transaction or line-item level before aggregation.
- Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys.
Explanation
Correct Answer
D:The most appropriate action is: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys. It addresses the stated condition: A retail customer table changes delivery address repeatedly but analysts must reconstruct the address known at any prior invoice date. The technical basis is: SCD Type 2 preserves historical attribute versions rather than overwriting the prior business state. Without this control, using Type 1 updates may silently rewrite the apparent address on older transaction reports. A direct acceptance check is: A backdated invoice joins to the address valid on its transaction date while the current record shows the latest address.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A late-arriving purchase refers to a customer identifier whose dimension record has not yet been ingested. The corresponding measure there would be: Define a deliberate unknown-member or late-dimension reconciliation pattern without silently dropping facts. The stated situation instead calls for: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys.
B:This alternative primarily addresses a different Azure Databricks problem: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. The corresponding measure there would be: Reevaluate data layout using representative event-time filters and a suitable clustering key. The stated situation instead calls for: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys.
C:This alternative primarily addresses a different Azure Databricks problem: A facts table groups product sales at daily level although auditors must inspect individual transaction adjustments. The corresponding measure there would be: Define fact-table grain at the required transaction or line-item level before aggregation. The stated situation instead calls for: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys.
Question 773
The following control has NOT been implemented: Investigate stage runtime growth and enforce appropriate concurrency policy before raising frequency. In this case: A job scheduled each hour starts running for 80 minutes and overlaps the next run. Which exposure remains?
- Increasing source throughput without repairing processing bottlenecks can worsen queue age.
- Over-maintenance can spend more resources rewriting files than it saves in queries.
- Overlapping backlogs can amplify compute consumption and create conflicting writes.
- Unobserved performance drift can cause the pipeline to miss future delivery windows.
Explanation
Correct Answer
C:The direct residual exposure is: Overlapping backlogs can amplify compute consumption and create conflicting writes. The triggering condition is: A job scheduled each hour starts running for 80 minutes and overlaps the next run. The omitted safeguard is: Investigate stage runtime growth and enforce appropriate concurrency policy before raising frequency. This matters because: Scheduling cannot guarantee freshness when actual execution exceeds the interval. A corrective test would show: Load testing shows completion within the target window and queued runs do not overlap unsafely.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A streaming pipeline's throughput falls although event arrival increases and its input backlog grows over time. Its preventative action would be: Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling. The most direct exposure in the current scenario is: Overlapping backlogs can amplify compute consumption and create conflicting writes.
B:This failure mode belongs mainly to another situation: A new Delta table maintenance job combines repeated OPTIMIZE and VACUUM at every microbatch even though changes are tiny. Its preventative action would be: Set a measured maintenance cadence or evaluate supported predictive optimization for eligible managed tables. The most direct exposure in the current scenario is: Overlapping backlogs can amplify compute consumption and create conflicting writes.
D:This failure mode belongs mainly to another situation: A job's duration doubles but an administrator sees only its final success status with no phase-level metrics. Its preventative action would be: Collect job timing, task duration and relevant Spark stage metrics in a monitored baseline. The most direct exposure in the current scenario is: Overlapping backlogs can amplify compute consumption and create conflicting writes.
Question 774
For this Azure Databricks issue: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. Engineers choose: Configure supported Databricks audit logging and route relevant events to a secured retention destination. What acceptance evidence is BEST?
- Authorized privacy reviewers see full test values while ordinary report roles see only permitted redactions.
- A test GRANT or REVOKE event appears with actor, timestamp and target in the audit sink.
- A data steward can find the certified revenue definition and verify the correct field in Catalog Explorer.
- A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
Explanation
Correct Answer
B:The strongest acceptance proof is: A test GRANT or REVOKE event appears with actor, timestamp and target in the audit sink. It specifically verifies: Configure supported Databricks audit logging and route relevant events to a secured retention destination. The original issue was: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. The underlying mechanism is: Security governance requires attributable administrative activity and durable evidence. Without it, unauthorized grants can remain undetected or be impossible to trace.
Incorrect Answers
A:This result would validate a different measure: Develop an approved role-aware column mask and test its outputs across supported query clients. That is relevant to the distinct problem: A data product stores PII in a shared Delta table but several reports require different masking for each audience. Here the acceptance criterion is: A test GRANT or REVOKE event appears with actor, timestamp and target in the audit sink.
C:This result would validate a different measure: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. That is relevant to the distinct problem: A business glossary has table names but no indication of which field is net revenue versus gross sales. Here the acceptance criterion is: A test GRANT or REVOKE event appears with actor, timestamp and target in the audit sink.
D:This result would validate a different measure: Restrict governed-tag administration and audit changes to protected metadata. That is relevant to the distinct problem: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. Here the acceptance criterion is: A test GRANT or REVOKE event appears with actor, timestamp and target in the audit sink.
Question 775
A data product owner adopts: Limit retries to appropriate transient errors and set accountable failure handling for permanent logic problems. The reason is: A job's retry policy restarts a deterministic bad SQL query six times even though the table is missing. What observed result BEST proves effectiveness?
- A failed downstream task is repaired without repeating successful non-idempotent upstream work.
- A missing-table test stops with the expected error while a transient failure recovers according to policy.
- A controlled dual-trigger test respects the run limit and produces one correct final target.
- A scheduled run succeeds under the named service principal after the former owner account is disabled.
Explanation
Correct Answer
B:The strongest acceptance proof is: A missing-table test stops with the expected error while a transient failure recovers according to policy. It specifically verifies: Limit retries to appropriate transient errors and set accountable failure handling for permanent logic problems. The original issue was: A job's retry policy restarts a deterministic bad SQL query six times even though the table is missing. The underlying mechanism is: Retries cannot repair missing tables or invalid schema references without corrective action. Without it, repeated invalid retries consume compute and obscure the original fixable error.
Incorrect Answers
A:This result would validate a different measure: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. That is relevant to the distinct problem: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. Here the acceptance criterion is: A missing-table test stops with the expected error while a transient failure recovers according to policy.
C:This result would validate a different measure: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap. That is relevant to the distinct problem: A daily data job runs twice during an incident and both executions write to the same target. Here the acceptance criterion is: A missing-table test stops with the expected error while a transient failure recovers according to policy.
D:This result would validate a different measure: Assign a dedicated run-as identity with durable scoped grants and an ownership review. That is relevant to the distinct problem: A job uses a service principal that loses access to the destination schema when an employee leaves. Here the acceptance criterion is: A missing-table test stops with the expected error while a transient failure recovers according to policy.
Question 776
A production data platform experiences this condition: A notebook pipeline uses a shared cluster with unstable third-party dependencies while a critical finance job needs controlled isolation. Which targeted measure should be selected?
- Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met.
- Benchmark Photon on a supported runtime with representative queries and compare cost, latency and correctness.
- Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution.
- Run the finance job on dedicated supported job compute with its own pinned libraries and permissions.
Explanation
Correct Answer
D:The most appropriate action is: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions. It addresses the stated condition: A notebook pipeline uses a shared cluster with unstable third-party dependencies while a critical finance job needs controlled isolation. The technical basis is: Compute isolation reduces interference between unrelated application environments and execution libraries. Without this control, an upgrade or runaway task on the shared cluster can compromise finance pipeline availability. A direct acceptance check is: A test upgrade on the interactive cluster does not change the isolated finance job's dependency versions or results.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. The corresponding measure there would be: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. The stated situation instead calls for: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions.
B:This alternative primarily addresses a different Azure Databricks problem: A Spark SQL pipeline spends most of its time executing wide joins and aggregations but the team has not evaluated a compatible vectorized execution engine. The corresponding measure there would be: Benchmark Photon on a supported runtime with representative queries and compare cost, latency and correctness. The stated situation instead calls for: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions.
C:This alternative primarily addresses a different Azure Databricks problem: A nightly batch transformation uses a continuously running all-purpose cluster even though no analyst interacts with the workload between runs. The corresponding measure there would be: Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution. The stated situation instead calls for: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions.
Question 777
An implementation skips: Collect job timing, task duration and relevant Spark stage metrics in a monitored baseline. Engineers are observing: A job's duration doubles but an administrator sees only its final success status with no phase-level metrics. What consequence is MOST likely?
- A critical SLA may depend on unrelated teams' scheduling and resource usage.
- Unobserved performance drift can cause the pipeline to miss future delivery windows.
- Excessive false alerts can obscure serious freshness incidents.
- A recurring failure may never be diagnosed if its only logs are destroyed repeatedly.
Explanation
Correct Answer
B:The direct residual exposure is: Unobserved performance drift can cause the pipeline to miss future delivery windows. The triggering condition is: A job's duration doubles but an administrator sees only its final success status with no phase-level metrics. The omitted safeguard is: Collect job timing, task duration and relevant Spark stage metrics in a monitored baseline. This matters because: Success alone cannot show degradation against latency or cost service objectives. A corrective test would show: A dashboard highlights task and stage regressions before the total job breaches its SLA.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A production notebook intermittently times out only when many other jobs share the same classic cluster. Its preventative action would be: Compare workload contention and resource reservations, then isolate or resize the critical job compute. The most direct exposure in the current scenario is: Unobserved performance drift can cause the pipeline to miss future delivery windows.
C:This failure mode belongs mainly to another situation: An alert triggers on every harmless microbatch delay while real hour-long ingestion stalls go unnoticed. Its preventative action would be: Define meaningful latency, error and backlog thresholds with alert routing based on the business SLO. The most direct exposure in the current scenario is: Unobserved performance drift can cause the pipeline to miss future delivery windows.
D:This failure mode belongs mainly to another situation: An operator restarts a failed Databricks cluster before collecting the Spark executor and driver logs. Its preventative action would be: Preserve diagnostic events and Spark UI stage evidence before restart where possible. The most direct exposure in the current scenario is: Unobserved performance drift can cause the pipeline to miss future delivery windows.
Question 778
A pipeline owner declines the action: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action. The business situation is: An event pipeline must reject rows with a null transaction ID, but the data engineer checks only the row count after load. What specific failure can follow?
- Unclear expectation handling may allow financial errors to reach gold tables or stop all low-risk events unnecessarily.
- Silently coercing a breaking type can erase measurable values while a job appears successful.
- Inconsistent schema assumptions create intermittent casts, quarantines or dropped columns.
- Null business keys can enter Delta targets and make updates or joins nondeterministic.
Explanation
Correct Answer
D:The direct residual exposure is: Null business keys can enter Delta targets and make updates or joins nondeterministic. The triggering condition is: An event pipeline must reject rows with a null transaction ID, but the data engineer checks only the row count after load. The omitted safeguard is: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action. This matters because: Explicit quality constraints protect critical key semantics rather than relying on aggregate row totals. A corrective test would show: A seeded null-ID row is blocked or quarantined while valid records complete successfully.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. Its preventative action would be: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity. The most direct exposure in the current scenario is: Null business keys can enter Delta targets and make updates or joins nondeterministic.
B:This failure mode belongs mainly to another situation: A source API changes a quantity from integer to nested JSON and the pipeline silently produces nulls downstream. Its preventative action would be: Apply schema enforcement with explicit drift handling and alert on incompatible structural changes. The most direct exposure in the current scenario is: Null business keys can enter Delta targets and make updates or joins nondeterministic.
C:This failure mode belongs mainly to another situation: An engineer changes the expected file schema in one notebook but forgets to update the Lakeflow pipeline definition. Its preventative action would be: Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths. The most direct exposure in the current scenario is: Null business keys can enter Delta targets and make updates or joins nondeterministic.
Question 779
For this Microsoft DP-750 case: A customer service dashboard must show the last four digits of account identifiers but never full account values. Which design or operational response BEST fits?
- Review and revoke stale grants and any linked service credentials, preserving required internal ownership.
- Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles.
- Replace committed personal credentials with supported workload authentication and revoke exposed tokens.
- Revoke inappropriate base-table access and publish only the authorized view or policy-governed object.
Explanation
Correct Answer
B:The most appropriate action is: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles. It addresses the stated condition: A customer service dashboard must show the last four digits of account identifiers but never full account values. The technical basis is: Column masking can transform sensitive values at query time according to the querying principal. Without this control, granting SELECT without masking may expose full account identifiers to unauthorized readers. A direct acceptance check is: Role-based sample queries show masked values for support and exact values only for approved security operators.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A vendor's service principal was granted global access for a one-month integration and the project ended. The corresponding measure there would be: Review and revoke stale grants and any linked service credentials, preserving required internal ownership. The stated situation instead calls for: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles.
C:This alternative primarily addresses a different Azure Databricks problem: A production workload uses a personal access token stored in Git for Databricks REST calls. The corresponding measure there would be: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. The stated situation instead calls for: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles.
D:This alternative primarily addresses a different Azure Databricks problem: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. The corresponding measure there would be: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. The stated situation instead calls for: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles.
Question 780
An operator introduces: Deduplicate by stable event identity and business time using documented state and watermark rules. The situation is: An ingestion pipeline reads cloud events with at-least-once delivery and assumes every event ID appears only once. Which validation should be required before signoff?
- A shuffled CDC test results in the correct highest-version value after replay.
- A duplicate-event test yields one current business event while preserving valid distinct events.
- A deliberately delayed file is ingested exactly once within the allowed arrival window.
- An event batch survives a controlled consumer restart and downstream totals match the expected sample.
Explanation
Correct Answer
B:The strongest acceptance proof is: A duplicate-event test yields one current business event while preserving valid distinct events. It specifically verifies: Deduplicate by stable event identity and business time using documented state and watermark rules. The original issue was: An ingestion pipeline reads cloud events with at-least-once delivery and assumes every event ID appears only once. The underlying mechanism is: Delivery guarantees alone do not remove duplicate producer or consumer events. Without it, replayed events can double-count orders in downstream aggregates.
Incorrect Answers
A:This result would validate a different measure: Apply ordered CDC sequencing using source change version or timestamp and consistent delete handling. That is relevant to the distinct problem: A transactional feed produces out-of-order CDC events and a naive MERGE overwrites a newer status with an older update. Here the acceptance criterion is: A duplicate-event test yields one current business event while preserving valid distinct events.
C:This result would validate a different measure: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark. That is relevant to the distinct problem: A Databricks job receives daily structured extracts but an upstream schedule occasionally delivers files late. Here the acceptance criterion is: A duplicate-event test yields one current business event while preserving valid distinct events.
D:This result would validate a different measure: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. That is relevant to the distinct problem: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. Here the acceptance criterion is: A duplicate-event test yields one current business event while preserving valid distinct events.