Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 46
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.
Question 451
A data product owner adopts: Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access. The reason is: A Delta Sharing recipient must stop receiving future updates after an agreement expires. What observed result BEST proves effectiveness?
- A hold rehearsal retrieves the original protected records and documents preservation scope and access.
- A partner query fails after revocation while internal consumers remain able to read the dataset.
- A seeded transformation appears with its expected upstream source and downstream target in lineage.
- A simulated cleanup retains protected history and an audit maps the new duration to approved settings.
Explanation
Correct Answer
B:The strongest acceptance proof is: A partner query fails after revocation while internal consumers remain able to read the dataset. It specifically verifies: Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access. The original issue was: A Delta Sharing recipient must stop receiving future updates after an agreement expires. The underlying mechanism is: External sharing must include explicit revocation and monitoring, not only initial provisioning. Without it, expired partners may retain ongoing data access despite a terminated agreement.
Incorrect Answers
A:This result would validate a different measure: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. That is relevant to the distinct problem: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. Here the acceptance criterion is: A partner query fails after revocation while internal consumers remain able to read the dataset.
C:This result would validate a different measure: Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage. That is relevant to the distinct problem: An analyst wants to know which upstream pipeline produced a metric displayed in a board dashboard. Here the acceptance criterion is: A partner query fails after revocation while internal consumers remain able to read the dataset.
D:This result would validate a different measure: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. That is relevant to the distinct problem: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. Here the acceptance criterion is: A partner query fails after revocation while internal consumers remain able to read the dataset.
Question 452
The design team proposes: Define fact-table grain at the required transaction or line-item level before aggregation. The situation is: A facts table groups product sales at daily level although auditors must inspect individual transaction adjustments. Which technical principle justifies the decision?
- Fact grain determines which analyses can be reconstructed without information loss.
- Views can provide different consumer contracts without unnecessary data duplication.
- Delta version history can provide auditable historical snapshots while underlying files are retained.
- A star schema separates measurable events from descriptive dimensions and controls join cardinality.
Explanation
Correct Answer
A:The decisive mechanism is: Fact grain determines which analyses can be reconstructed without information loss. That explains the selected action: Define fact-table grain at the required transaction or line-item level before aggregation. In the original scenario: A facts table groups product sales at daily level although auditors must inspect individual transaction adjustments. The specific unmanaged risk is: Premature aggregation can make returns, corrections and invoice-line disputes impossible to reconcile. Validate with: Sample invoice lines reconcile exactly to the fact table and roll up to the approved daily total.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A data product creates multiple physical copies of a curated dimension because teams need different column names. Its targeted response is: Expose stable SQL views over a governed base table when only presentation aliases differ. The current case is governed more directly by: Fact grain determines which analyses can be reconstructed without information loss.
C: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: Fact grain determines which analyses can be reconstructed without information loss.
D:This principle concerns a separate data-engineering condition: A finance dashboard needs monthly revenue by customer and must join customer dimensions without multiplying facts. Its targeted response is: Design a conformed star schema with explicit fact grain and unique dimension keys. The current case is governed more directly by: Fact grain determines which analyses can be reconstructed without information loss.
Question 453
During a lakehouse implementation review, engineers observe: A large orders dataset has one column per month but a dashboard expects month-value rows for filtering and grouping. What is the BEST next action?
- Validate business keys and choose a deterministic latest-enrollment record before aggregation.
- Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans.
- Align compatible schemas and use name-based union semantics with explicit type checks.
- Use a compatible unpivot or stack transformation with explicit month and amount columns.
Explanation
Correct Answer
D:The most appropriate action is: Use a compatible unpivot or stack transformation with explicit month and amount columns. It addresses the stated condition: A large orders dataset has one column per month but a dashboard expects month-value rows for filtering and grouping. The technical basis is: Unpivoting converts a wide repeated-measure structure into a normalized row representation. Without this control, directly summing mismatched month columns can produce fragile and incomplete queries. A direct acceptance check is: The unpivoted output contains exactly one row per original item-month and preserves totals.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. The corresponding measure there would be: Validate business keys and choose a deterministic latest-enrollment record before aggregation. The stated situation instead calls for: Use a compatible unpivot or stack transformation with explicit month and amount columns.
B:This alternative primarily addresses a different Azure Databricks problem: A pipeline joins a huge fact table with a tiny dimension and a normal shuffle join creates excessive network traffic. The corresponding measure there would be: Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans. The stated situation instead calls for: Use a compatible unpivot or stack transformation with explicit month and amount columns.
C:This alternative primarily addresses a different Azure Databricks problem: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. The corresponding measure there would be: Align compatible schemas and use name-based union semantics with explicit type checks. The stated situation instead calls for: Use a compatible unpivot or stack transformation with explicit month and amount columns.
Question 454
The following control has NOT been implemented: Add representative unit and integration tests asserting transformation results and schema contracts. In this case: A release modifies transformation logic but tests only whether Python files compile. Which exposure remains?
- Manual workspace copying can omit task settings and point production at development tables.
- The same Git commit may run differently after a dependency's incompatible update.
- Unverified MERGE conditions can overwrite valid history despite passing mocked unit tests.
- A logically incorrect aggregation can pass compilation while corrupting metrics.
Explanation
Correct Answer
D:The direct residual exposure is: A logically incorrect aggregation can pass compilation while corrupting metrics. The triggering condition is: A release modifies transformation logic but tests only whether Python files compile. The omitted safeguard is: Add representative unit and integration tests asserting transformation results and schema contracts. This matters because: Syntax checks do not validate business semantics or interaction with external tables. A corrective test would show: A seeded test dataset returns documented expected outputs and intentionally bad inputs fail.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A team copies Databricks notebooks manually between three workspaces and each uses different hardcoded identifiers. Its preventative action would be: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI. The most direct exposure in the current scenario is: A logically incorrect aggregation can pass compilation while corrupting metrics.
B:This failure mode belongs mainly to another situation: A team cannot reproduce a prior release because package versions are resolved dynamically during deployment. Its preventative action would be: Pin package and runtime versions in the governed release artifact and record its dependency manifest. The most direct exposure in the current scenario is: A logically incorrect aggregation can pass compilation while corrupting metrics.
C:This failure mode belongs mainly to another situation: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. Its preventative action would be: Include an integration test using actual Delta table semantics and representative source changes. The most direct exposure in the current scenario is: A logically incorrect aggregation can pass compilation while corrupting metrics.
Question 455
A pipeline owner declines the action: Apply suitable compute access modes, policies and entitlements that restrict who can attach or modify shared compute. The business situation is: A multi-team interactive cluster permits users to attach arbitrary unapproved libraries and run notebooks under broad shared privileges. What specific failure can follow?
- An untrusted library or unrestricted cluster edit can affect other users' sessions or access to protected data.
- Unrestricted cluster creation can create unpredictable spending and inconsistent operational standards.
- Overspending on memory does not relieve a CPU-bound stage and may worsen the cost-performance ratio.
- A serverless migration may fail when a required library or environment customization cannot be installed.
Explanation
Correct Answer
A:The direct residual exposure is: An untrusted library or unrestricted cluster edit can affect other users' sessions or access to protected data. The triggering condition is: A multi-team interactive cluster permits users to attach arbitrary unapproved libraries and run notebooks under broad shared privileges. The omitted safeguard is: Apply suitable compute access modes, policies and entitlements that restrict who can attach or modify shared compute. This matters because: Workspace compute permissions and access modes help maintain workload and security boundaries. A corrective test would show: Permission tests show approved analysts run their notebooks while unauthorized cluster policy edits and installs fail.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A department wants a self-service sandbox but must prevent users from creating huge unrestricted clusters. Its preventative action would be: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users. The most direct exposure in the current scenario is: An untrusted library or unrestricted cluster edit can affect other users' sessions or access to protected data.
C:This failure mode belongs mainly to another situation: A new job uses a large memory-optimized node merely because its source data is large, although profiling shows compute-bound transforms. Its preventative action would be: Choose node families and driver/worker sizes using CPU, memory, shuffle and workload profile evidence. The most direct exposure in the current scenario is: An untrusted library or unrestricted cluster edit can affect other users' sessions or access to protected data.
D:This failure mode belongs mainly to another situation: A long-running job using an unsupported custom system dependency is moved to serverless without checking feature compatibility. Its preventative action would be: Review current serverless limitations and select compatible classic jobs compute when necessary. The most direct exposure in the current scenario is: An untrusted library or unrestricted cluster edit can affect other users' sessions or access to protected data.
Question 456
A pipeline owner declines the action: Route deterministic validation failures to quarantine rather than retrying them as transient infrastructure errors. The business situation is: A pipeline automatically retries malformed source records indefinitely and consumes its entire compute budget. What specific failure can follow?
- At-least-once task execution can duplicate side effects when outputs are append-only.
- Infinite retries on bad records can block valid work and multiply costs.
- An early downstream task can publish partial business totals without raising an obvious failure.
- Immediate permanent failure on a brief service outage can miss a delivery SLA.
Explanation
Correct Answer
B:The direct residual exposure is: Infinite retries on bad records can block valid work and multiply costs. The triggering condition is: A pipeline automatically retries malformed source records indefinitely and consumes its entire compute budget. The omitted safeguard is: Route deterministic validation failures to quarantine rather than retrying them as transient infrastructure errors. This matters because: Idempotent retries are suitable for transient conditions, not unchanging invalid data. A corrective test would show: A malformed input is rejected once with an error record while later valid records continue.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. Its preventative action would be: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. The most direct exposure in the current scenario is: Infinite retries on bad records can block valid work and multiply costs.
C:This failure mode belongs mainly to another situation: A sales pipeline aggregates gold metrics before the bronze ingestion task finishes and occasionally reports incomplete totals. Its preventative action would be: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed. The most direct exposure in the current scenario is: Infinite retries on bad records can block valid work and multiply costs.
D: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: Infinite retries on bad records can block valid work and multiply costs.
Question 457
During a lakehouse implementation review, engineers observe: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. What is the BEST next action?
- Use Auto Loader with durable checkpointing and an appropriate discovery mode to ingest new files incrementally.
- Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint.
- Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction.
- Deduplicate by stable event identity and business time using documented state and watermark rules.
Explanation
Correct Answer
B:The most appropriate action is: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. It addresses the stated condition: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. The technical basis is: Message-bus streams require offset progress tracking and a durable state boundary. Without this control, an uncheckpointed consumer can replay or omit events after a restart. A direct acceptance check is: An event batch survives a controlled consumer restart and downstream totals match the expected sample.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An Azure storage account receives tens of thousands of small parquet files per hour and a notebook lists the whole container on every run. The corresponding measure there would be: Use Auto Loader with durable checkpointing and an appropriate discovery mode to ingest new files incrementally. The stated situation instead calls for: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint.
C:This alternative primarily addresses a different Azure Databricks problem: A batch integration needs a connector-managed path from a supported operational source into the lakehouse. The corresponding measure there would be: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction. The stated situation instead calls for: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint.
D:This alternative primarily addresses a different Azure Databricks problem: An ingestion pipeline reads cloud events with at-least-once delivery and assumes every event ID appears only once. The corresponding measure there would be: Deduplicate by stable event identity and business time using documented state and watermark rules. The stated situation instead calls for: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint.
Question 458
For this Azure Databricks issue: A feature-engineering notebook requires GPU libraries but the data cleaning jobs never use accelerators. Engineers choose: Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations. What acceptance evidence is BEST?
- Resource telemetry shows accelerator use where needed and CPU jobs satisfy their SLA at lower cost.
- An ordinary user can start an approved small cluster but cannot exceed policy size or runtime limits.
- Load tests for normal and month-end volumes satisfy runtime targets without exceeding the approved worker ceiling.
- A load rehearsal meets dashboard p95 response targets while notebook resource spikes do not affect query service.
Explanation
Correct Answer
A:The strongest acceptance proof is: Resource telemetry shows accelerator use where needed and CPU jobs satisfy their SLA at lower cost. It specifically verifies: Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations. The original issue was: A feature-engineering notebook requires GPU libraries but the data cleaning jobs never use accelerators. The underlying mechanism is: GPU resources are specialized and do not automatically accelerate every Spark or SQL transformation. Without it, A default GPU cluster may charge premium rates while most tasks leave accelerators unused.
Incorrect Answers
B:This result would validate a different measure: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users. That is relevant to the distinct problem: A department wants a self-service sandbox but must prevent users from creating huge unrestricted clusters. Here the acceptance criterion is: Resource telemetry shows accelerator use where needed and CPU jobs satisfy their SLA at lower cost.
C:This result would validate a different measure: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. That is relevant to the distinct problem: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. Here the acceptance criterion is: Resource telemetry shows accelerator use where needed and CPU jobs satisfy their SLA at lower cost.
D:This result would validate a different measure: Use an appropriately sized SQL warehouse with workload isolation and measured concurrency for dashboard queries. That is relevant to the distinct problem: Analysts run short SQL dashboard queries against a shared lakehouse but their notebooks share a general-purpose Spark cluster with training experiments. Here the acceptance criterion is: Resource telemetry shows accelerator use where needed and CPU jobs satisfy their SLA at lower cost.
Question 459
A team omits the recommended measure: Configure supported Databricks audit logging and route relevant events to a secured retention destination. Its environment shows: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. What is the MOST direct residual risk?
- Accumulated historical grants may give former project teams access to unrelated data products.
- Long-lived shared storage credentials may expose unrelated files or survive contract termination.
- Unauthorized grants can remain undetected or be impossible to trace.
- Historical evidence may be lost even when the latest dataset remains complete.
Explanation
Correct Answer
C:The direct residual exposure is: Unauthorized grants can remain undetected or be impossible to trace. The triggering condition is: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. The omitted safeguard is: Configure supported Databricks audit logging and route relevant events to a secured retention destination. This matters because: Security governance requires attributable administrative activity and durable evidence. A corrective test would show: A test GRANT or REVOKE event appears with actor, timestamp and target in the audit sink.
Incorrect Answers
A: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: Unauthorized grants can remain undetected or be impossible to trace.
B:This failure mode belongs mainly to another situation: A data-sharing project emails storage keys to an external partner for reading curated Delta results. Its preventative action would be: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. The most direct exposure in the current scenario is: Unauthorized grants can remain undetected or be impossible to trace.
D:This failure mode belongs mainly to another situation: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. Its preventative action would be: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. The most direct exposure in the current scenario is: Unauthorized grants can remain undetected or be impossible to trace.
Question 460
An implementation skips: Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage. Engineers are observing: An analyst wants to know which upstream pipeline produced a metric displayed in a board dashboard. What consequence is MOST likely?
- Manual protection drift can expose fields on newly created tables before a review.
- Without lineage the team may repair the wrong pipeline after a metric regression.
- Long-lived shared storage credentials may expose unrelated files or survive contract termination.
- Sharing raw transaction tables can disclose protected customer attributes unnecessarily.
Explanation
Correct Answer
B:The direct residual exposure is: Without lineage the team may repair the wrong pipeline after a metric regression. The triggering condition is: An analyst wants to know which upstream pipeline produced a metric displayed in a board dashboard. The omitted safeguard is: Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage. This matters because: Data lineage links producers, transformations and consumers where observed activity is supported. A corrective test would show: A seeded transformation appears with its expected upstream source and downstream target in lineage.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A central security team manually adds row masking rules to every department table and new datasets repeatedly lack protection. Its preventative action would be: Create compatible central ABAC policies based on governed classifications and verify inherited coverage. The most direct exposure in the current scenario is: Without lineage the team may repair the wrong pipeline after a metric regression.
C:This failure mode belongs mainly to another situation: A data-sharing project emails storage keys to an external partner for reading curated Delta results. Its preventative action would be: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. The most direct exposure in the current scenario is: Without lineage the team may repair the wrong pipeline after a metric regression.
D:This failure mode belongs mainly to another situation: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. Its preventative action would be: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. The most direct exposure in the current scenario is: Without lineage the team may repair the wrong pipeline after a metric regression.