Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 28
Question 270
A production data team leaves out: Protect the main branch with peer review, required tests and controlled promotion windows. Its scenario is: A release process merges unreviewed notebook changes directly into the main branch minutes before a production run. Which failure mode is MOST relevant?
- A faulty last-minute edit can create an untested release with no accountable reviewer.
- Without versioned artifacts, recovery may require reconstructing past settings by memory.
- A deployment may succeed while the first production job cannot access its storage or schema.
- Unreviewed direct edits can break jobs without a reproducible rollback commit.
Explanation
Correct Answer
A:The direct residual exposure is: A faulty last-minute edit can create an untested release with no accountable reviewer. The triggering condition is: A release process merges unreviewed notebook changes directly into the main branch minutes before a production run. The omitted safeguard is: Protect the main branch with peer review, required tests and controlled promotion windows. This matters because: Reviewed changes with required status checks reduce uncontrolled production configuration drift. A corrective test would show: An unauthorized direct push is rejected and a reviewed pull request completes all required gates.
Incorrect Answers
B:This failure mode belongs mainly to another situation: An operations group wants to roll back a broken Lakeflow workflow but keeps no previous package version. Its preventative action would be: Tag and retain approved bundle releases and document a verified redeploy or rollback procedure. The most direct exposure in the current scenario is: A faulty last-minute edit can create an untested release with no accountable reviewer.
C:This failure mode belongs mainly to another situation: A new pipeline passes unit tests but production fails because the service principal lacks a catalog grant. Its preventative action would be: Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging. The most direct exposure in the current scenario is: A faulty last-minute edit can create an untested release with no accountable reviewer.
D:This failure mode belongs mainly to another situation: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. Its preventative action would be: Store deployment source in Git with reviewed branches and pull requests before promoting changes. The most direct exposure in the current scenario is: A faulty last-minute edit can create an untested release with no accountable reviewer.
Question 271
The recommended measure is: Validate API status and returned resource identifiers, then use bounded retries only for transient failures. The operational context is: An automation job uses Databricks REST APIs but omits response-code checks and assumes every HTTP request succeeded. Which data engineering concept applies?
- Deployment APIs can reject requests even when the calling script continues to run.
- Schema and object naming changes can break consumers even when new ETL succeeds.
- Declarative bundle definitions can make job and pipeline deployments repeatable across environments.
- Automated releases should not depend on personal accounts or broadly exposed long-lived credentials.
Explanation
Correct Answer
A:The decisive mechanism is: Deployment APIs can reject requests even when the calling script continues to run. That explains the selected action: Validate API status and returned resource identifiers, then use bounded retries only for transient failures. In the original scenario: An automation job uses Databricks REST APIs but omits response-code checks and assumes every HTTP request succeeded. The specific unmanaged risk is: A failed job update can be silently treated as a successful release. Validate with: An injected API rejection makes CI fail with a traceable error and leaves production unchanged.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A sensitive SQL view is renamed in the release but the team does not test downstream dashboards before promotion. Its targeted response is: Run end-to-end contract tests for dependent readers and obtain owner approval for breaking changes. The current case is governed more directly by: Deployment APIs can reject requests even when the calling script continues to run.
C:This principle concerns a separate data-engineering condition: A team copies Databricks notebooks manually between three workspaces and each uses different hardcoded identifiers. Its targeted response is: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI. The current case is governed more directly by: Deployment APIs can reject requests even when the calling script continues to run.
D:This principle concerns a separate data-engineering condition: A CI pipeline deploys Databricks assets under an engineer's personal token stored in repository variables. Its targeted response is: Use a secure service identity and protected credential handling for bundle or REST API deployment. The current case is governed more directly by: Deployment APIs can reject requests even when the calling script continues to run.
Question 272
An operator introduces: Use a temporal history model with nonoverlapping effective-from and effective-to boundaries. The situation is: A historical compliance table must show how account status changed at precise effective intervals. Which validation should be required before signoff?
- All required engines pass a controlled read and supported mutation matrix before production.
- A controlled late event appears in the correct historical period according to the approved policy.
- The purchase remains traceable and later dimension arrival resolves the customer association without duplication.
- A boundary-date test resolves each account to exactly one status for every audited instant.
Explanation
Correct Answer
D:The strongest acceptance proof is: A boundary-date test resolves each account to exactly one status for every audited instant. It specifically verifies: Use a temporal history model with nonoverlapping effective-from and effective-to boundaries. The original issue was: A historical compliance table must show how account status changed at precise effective intervals. The underlying mechanism is: Temporal tables describe the validity of state over time rather than only its latest value. Without it, overlapping intervals can cause a historical lookup to return multiple contradictory statuses.
Incorrect Answers
A:This result would validate a different measure: Choose and document a supported format and catalog integration with explicit read/write compatibility tests. That is relevant to the distinct problem: A cross-engine consumer expects a Delta table but source is plain Iceberg and engineers assume identical mutation semantics. Here the acceptance criterion is: A boundary-date test resolves each account to exactly one status for every audited instant.
B: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: A boundary-date test resolves each account to exactly one status for every audited instant.
C:This result would validate a different measure: Define a deliberate unknown-member or late-dimension reconciliation pattern without silently dropping facts. That is relevant to the distinct problem: A late-arriving purchase refers to a customer identifier whose dimension record has not yet been ingested. Here the acceptance criterion is: A boundary-date test resolves each account to exactly one status for every audited instant.
Question 273
A team omits the recommended measure: Create an eligible materialized view or managed derived table with appropriate refresh and access rules. Its environment shows: A BI group needs to query a materialized aggregate while the source transaction Delta table changes hourly. What is the MOST direct residual risk?
- Users can unknowingly consume stale aggregates if refresh ownership and schedule are unspecified.
- Persisting every intermediate query can create stale and duplicate datasets.
- Users may query raw unvalidated records as though they were approved curated metrics.
- Overbroad catalog privileges can let ordinary readers create misleading or unauthorized data products.
Explanation
Correct Answer
A:The direct residual exposure is: Users can unknowingly consume stale aggregates if refresh ownership and schedule are unspecified. The triggering condition is: A BI group needs to query a materialized aggregate while the source transaction Delta table changes hourly. The omitted safeguard is: Create an eligible materialized view or managed derived table with appropriate refresh and access rules. This matters because: Materialized views can persist derived query results, but refresh behavior must match freshness expectations. A corrective test would show: A source update followed by the documented refresh produces reconciled aggregate totals.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A data pipeline creates a physical table for a reporting transformation that would be better maintained as a query definition. Its preventative action would be: Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities. The most direct exposure in the current scenario is: Users can unknowingly consume stale aggregates if refresh ownership and schedule are unspecified.
C:This failure mode belongs mainly to another situation: Multiple data products put raw, refined and curated assets into a single schema with confusing table names. Its preventative action would be: Define a consistent schema and naming architecture separating layers and business domains by purpose. The most direct exposure in the current scenario is: Users can unknowingly consume stale aggregates if refresh ownership and schedule are unspecified.
D:This failure mode belongs mainly to another situation: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. Its preventative action would be: Grant precise container-use and object-creation privileges based on actual job roles. The most direct exposure in the current scenario is: Users can unknowingly consume stale aggregates if refresh ownership and schedule are unspecified.
Question 274
A production data platform experiences this condition: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. Which targeted measure should be selected?
- Create an authorized connection and supported foreign catalog for the external source.
- Use fully qualified names and a controlled default namespace in deployment SQL and notebooks.
- Select managed or external Unity Catalog table ownership intentionally and verify lifecycle semantics.
- Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers.
Explanation
Correct Answer
A:The most appropriate action is: Create an authorized connection and supported foreign catalog for the external source. It addresses the stated condition: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. The technical basis is: Lakehouse Federation lets governed queries access supported external systems through a connection abstraction. Without this control, copying the whole remote source for a narrow lookup can create unnecessary latency, duplication and privacy exposure. A direct acceptance check is: A restricted query through the foreign catalog returns current permitted rows and honors source connectivity limits.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. The corresponding measure there would be: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks. The stated situation instead calls for: Create an authorized connection and supported foreign catalog for the external source.
C:This alternative primarily addresses a different Azure Databricks problem: A team expects dropping a managed table to preserve all physical data as though it were an external table. The corresponding measure there would be: Select managed or external Unity Catalog table ownership intentionally and verify lifecycle semantics. The stated situation instead calls for: Create an authorized connection and supported foreign catalog for the external source.
D:This alternative primarily addresses a different Azure Databricks problem: An ingestion team creates a table with a reserved or inconsistent name and automation fails in one environment. The corresponding measure there would be: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers. The stated situation instead calls for: Create an authorized connection and supported foreign catalog for the external source.
Question 275
An operator introduces: Normalize time zone semantics before extracting business-local reporting dates. The situation is: A date field mixes UTC timestamps and local store times but a pipeline groups all values by the raw date string. Which validation should be required before signoff?
- Known events around midnight map to the intended store-local date and correct UTC instant.
- A controlled money sample matches expected exact decimal totals and rejects malformed amounts.
- Test histories with retries and real re-enrollments produce the approved per-student count.
- A sample includes all approved categories and status totals reconcile to source rows.
Explanation
Correct Answer
A:The strongest acceptance proof is: Known events around midnight map to the intended store-local date and correct UTC instant. It specifically verifies: Normalize time zone semantics before extracting business-local reporting dates. The original issue was: A date field mixes UTC timestamps and local store times but a pipeline groups all values by the raw date string. The underlying mechanism is: Time zone conversion and calendar boundary choice affect the grouping of events. Without it, orders near midnight may be reported under the wrong business day.
Incorrect Answers
B: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: Known events around midnight map to the intended store-local date and correct UTC instant.
C:This result would validate a different measure: Validate business keys and choose a deterministic latest-enrollment record before aggregation. That is relevant to the distinct problem: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. Here the acceptance criterion is: Known events around midnight map to the intended store-local date and correct UTC instant.
D:This result would validate a different measure: Apply a controlled pivot with a defined set of expected categories and aggregation rule. That is relevant to the distinct problem: A quality report needs one column for each product status category but stores status as separate rows. Here the acceptance criterion is: Known events around midnight map to the intended store-local date and correct UTC instant.
Question 276
An implementation skips: Collect expectation metrics and reconcile input, accepted, quarantined and rejected record counts. Engineers are observing: A pipeline reports zero failed rows because bad records are silently dropped without any count of what was removed. What consequence is MOST likely?
- Invalid amounts may silently convert to null and skew revenue aggregates.
- Numerically valid but impossible values can contaminate customer metrics and machine-learning features.
- Unclear expectation handling may allow financial errors to reach gold tables or stop all low-risk events unnecessarily.
- A seemingly successful load can conceal a growing upstream data-loss problem.
Explanation
Correct Answer
D:The direct residual exposure is: A seemingly successful load can conceal a growing upstream data-loss problem. The triggering condition is: A pipeline reports zero failed rows because bad records are silently dropped without any count of what was removed. The omitted safeguard is: Collect expectation metrics and reconcile input, accepted, quarantined and rejected record counts. This matters because: Measurable quality controls need observable outcomes and accounting for rejected data. A corrective test would show: Each run reports complete input-to-output reconciliation and alerts when rejected fraction exceeds its SLO.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. Its preventative action would be: Apply type, nullability and range expectations before promoting bronze rows into the silver target. The most direct exposure in the current scenario is: A seemingly successful load can conceal a growing upstream data-loss problem.
B:This failure mode belongs mainly to another situation: A bronze stream sometimes includes ages below zero or above 120 yet the transformation casts every value to integer. Its preventative action would be: Define a range expectation with metrics and the approved drop, fail or quarantine disposition. The most direct exposure in the current scenario is: A seemingly successful load can conceal a growing upstream data-loss problem.
C: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: A seemingly successful load can conceal a growing upstream data-loss problem.
Question 277
During a lakehouse implementation review, engineers observe: A facts table groups product sales at daily level although auditors must inspect individual transaction adjustments. What is the BEST next action?
- Use an external Unity Catalog table with an approved registered location instead of assuming managed storage ownership.
- Define fact-table grain at the required transaction or line-item level before aggregation.
- Enable supported liquid clustering with appropriate keys and run compatible optimization.
- Use supported Delta table version history and time travel within the documented retention window.
Explanation
Correct Answer
B:The most appropriate action is: Define fact-table grain at the required transaction or line-item level before aggregation. It addresses the stated condition: A facts table groups product sales at daily level although auditors must inspect individual transaction adjustments. The technical basis is: Fact grain determines which analyses can be reconstructed without information loss. Without this control, premature aggregation can make returns, corrections and invoice-line disputes impossible to reconcile. A direct acceptance check is: Sample invoice lines reconcile exactly to the fact table and roll up to the approved daily total.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A dataset has a strict requirement that Azure storage ownership and lifecycle remain under a separate platform team. The corresponding measure there would be: Use an external Unity Catalog table with an approved registered location instead of assuming managed storage ownership. The stated situation instead calls for: Define fact-table grain at the required transaction or line-item level before aggregation.
C:This alternative primarily addresses a different Azure Databricks problem: A large Delta fact table is filtered primarily on high-cardinality account IDs with changing query patterns. The corresponding measure there would be: Enable supported liquid clustering with appropriate keys and run compatible optimization. The stated situation instead calls for: Define fact-table grain at the required transaction or line-item level before aggregation.
D:This alternative primarily addresses a different Azure Databricks problem: A business needs to compare two point-in-time table versions during a financial reconciliation. The corresponding measure there would be: Use supported Delta table version history and time travel within the documented retention window. The stated situation instead calls for: Define fact-table grain at the required transaction or line-item level before aggregation.
Question 278
An implementation skips: Apply the required filters and join conditions before aggregation and validate authorized output groups. Engineers are observing: An analyst calculates total revenue grouped by country but a join includes countries not approved for reporting. What consequence is MOST likely?
- Position-based union may quietly corrupt data when column positions differ.
- Unknown statuses may be dropped or duplicated if pivot categories are assumed without validation.
- Aggregating unauthorized or irrelevant rows can disclose or distort regional totals.
- An inner join hides precisely the missing records the reconciliation needs to surface.
Explanation
Correct Answer
C:The direct residual exposure is: Aggregating unauthorized or irrelevant rows can disclose or distort regional totals. The triggering condition is: An analyst calculates total revenue grouped by country but a join includes countries not approved for reporting. The omitted safeguard is: Apply the required filters and join conditions before aggregation and validate authorized output groups. This matters because: Filter placement and join predicates determine which rows contribute to a grouped measure. A corrective test would show: A controlled source sample produces exactly the permitted group keys and reconciled sums.
Incorrect Answers
A:This failure mode belongs mainly to another situation: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. Its preventative action would be: Align compatible schemas and use name-based union semantics with explicit type checks. The most direct exposure in the current scenario is: Aggregating unauthorized or irrelevant rows can disclose or distort regional totals.
B:This failure mode belongs mainly to another situation: A quality report needs one column for each product status category but stores status as separate rows. Its preventative action would be: Apply a controlled pivot with a defined set of expected categories and aggregation rule. The most direct exposure in the current scenario is: Aggregating unauthorized or irrelevant rows can disclose or distort regional totals.
D:This failure mode belongs mainly to another situation: An analyst must find records present in the source system but absent in a target migration. Its preventative action would be: Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics. The most direct exposure in the current scenario is: Aggregating unauthorized or irrelevant rows can disclose or distort regional totals.
Question 279
A data engineering team faces this Azure Databricks requirement: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. Which action is MOST appropriate?
- Align compatible schemas and use name-based union semantics with explicit type checks.
- Normalize transaction sign semantics before grouping by business date and customer.
- Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans.
- Validate business keys and choose a deterministic latest-enrollment record before aggregation.
Explanation
Correct Answer
A:The most appropriate action is: Align compatible schemas and use name-based union semantics with explicit type checks. It addresses the stated condition: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. The technical basis is: Union operations concatenate rows and require aligned column meanings. Without this control, position-based union may quietly corrupt data when column positions differ. A direct acceptance check is: The merged dataset preserves typed values and column names from both input feeds.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A daily revenue report double-counts refunds because both debit and credit rows are summed as positive numbers. The corresponding measure there would be: Normalize transaction sign semantics before grouping by business date and customer. The stated situation instead calls for: Align compatible schemas and use name-based union semantics with explicit type checks.
C: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: Align compatible schemas and use name-based union semantics with explicit type checks.
D: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: Align compatible schemas and use name-based union semantics with explicit type checks.
Question 280
A team omits the recommended measure: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap. Its environment shows: A daily data job runs twice during an incident and both executions write to the same target. What is the MOST direct residual risk?
- Overlapping runs may race to overwrite outputs or duplicate appended records.
- A clock-only trigger can start before the dependency has produced the expected dataset.
- Temporarily editing the main schedule may skip normal deliveries or replay wrong dates.
- User-linked credentials can break scheduled jobs after account deactivation or team reassignment.
Explanation
Correct Answer
A:The direct residual exposure is: Overlapping runs may race to overwrite outputs or duplicate appended records. The triggering condition is: A daily data job runs twice during an incident and both executions write to the same target. The omitted safeguard is: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap. This matters because: Concurrency management prevents competing executions from corrupting shared mutable state. A corrective test would show: A controlled dual-trigger test respects the run limit and produces one correct final target.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A pipeline must run when an upstream Databricks table is updated but analysts have hardcoded a daily time estimate. Its preventative action would be: Evaluate supported table update triggers or a clear upstream job dependency based on actual availability. The most direct exposure in the current scenario is: Overlapping runs may race to overwrite outputs or duplicate appended records.
C:This failure mode belongs mainly to another situation: An ingestion job requires a one-time backfill without changing the future daily production schedule. Its preventative action would be: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger. The most direct exposure in the current scenario is: Overlapping runs may race to overwrite outputs or duplicate appended records.
D:This failure mode belongs mainly to another situation: A job uses a service principal that loses access to the destination schema when an employee leaves. Its preventative action would be: Assign a dedicated run-as identity with durable scoped grants and an ownership review. The most direct exposure in the current scenario is: Overlapping runs may race to overwrite outputs or duplicate appended records.