Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 19
Question 180
A data engineering team faces this Azure Databricks requirement: A data product needs to copy a supported Azure Data Factory pipeline output into governed Databricks tables. Which action is MOST appropriate?
- Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model.
- Specify the correct input delimiter, header and schema and validate parsing on a representative file.
- Use Spark-native distributed read and transformation APIs or partition-safe processing.
- Apply ordered CDC sequencing using source change version or timestamp and consistent delete handling.
Explanation
Correct Answer
A:The most appropriate action is: Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model. It addresses the stated condition: A data product needs to copy a supported Azure Data Factory pipeline output into governed Databricks tables. The technical basis is: An external orchestrator can trigger Databricks processing while governance and failure handling remain explicit. Without this control, uncoordinated retries can run transformations before ingestion finishes or under the wrong identity. A direct acceptance check is: ADF completion evidence and Databricks job dependencies show an end-to-end successful load.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: An overnight load reads tab-separated files but an engineer assumes comma separators and casts malformed columns to null. The corresponding measure there would be: Specify the correct input delimiter, header and schema and validate parsing on a representative file. The stated situation instead calls for: Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model.
C:This alternative primarily addresses a different Azure Databricks problem: A Python notebook reads a massive table into pandas on the driver before processing data intended for Spark executors. The corresponding measure there would be: Use Spark-native distributed read and transformation APIs or partition-safe processing. The stated situation instead calls for: Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model.
D:This alternative primarily addresses a different Azure Databricks problem: A transactional feed produces out-of-order CDC events and a naive MERGE overwrites a newer status with an older update. The corresponding measure there would be: Apply ordered CDC sequencing using source change version or timestamp and consistent delete handling. The stated situation instead calls for: Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model.
Question 181
An operator introduces: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. The situation is: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. Which validation should be required before signoff?
- A seeded mismatch prevents cutover and the prior certified table remains queryable.
- A reviewed graph lists every expected parent and a source change propagates to the correct targets.
- A pipeline run updates tables in valid dependency order and records expectation outcomes.
- Two executions of the same input batch yield one approved current record per order.
Explanation
Correct Answer
D:The strongest acceptance proof is: Two executions of the same input batch yield one approved current record per order. It specifically verifies: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. The original issue was: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. The underlying mechanism is: A recoverable pipeline should produce the same logical state after an equivalent retry. Without it, at-least-once task execution can duplicate side effects when outputs are append-only.
Incorrect Answers
A:This result would validate a different measure: Write to a staging target, validate row totals and invariants, then perform the approved publication step. That is relevant to the distinct problem: A finance transformation writes its output directly into a published table before reconciling totals against the source. Here the acceptance criterion is: Two executions of the same input batch yield one approved current record per order.
B:This result would validate a different measure: Declare consistent table names and dependencies and validate the generated pipeline graph. That is relevant to the distinct problem: A declarative pipeline transforms several datasets but its source names are ambiguous and a data team cannot reconstruct dependencies. Here the acceptance criterion is: Two executions of the same input batch yield one approved current record per order.
C:This result would validate a different measure: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. That is relevant to the distinct problem: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. Here the acceptance criterion is: Two executions of the same input batch yield one approved current record per order.
Question 182
A pipeline owner declines the action: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. The business situation is: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. What specific failure can follow?
- Custom polling without checkpoint or schema handling may miss updates and require fragile maintenance.
- Append-only full extracts can multiply current records and leave deleted source rows active.
- Appending full inventories multiplies items and distorts on-hand quantities.
- An uncheckpointed consumer can replay or omit events after a restart.
Explanation
Correct Answer
D:The direct residual exposure is: An uncheckpointed consumer can replay or omit events after a restart. The triggering condition is: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. The omitted safeguard is: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. This matters because: Message-bus streams require offset progress tracking and a durable state boundary. A corrective test would show: An event batch survives a controlled consumer restart and downstream totals match the expected sample.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A batch integration needs a connector-managed path from a supported operational source into the lakehouse. Its preventative action would be: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction. The most direct exposure in the current scenario is: An uncheckpointed consumer can replay or omit events after a restart.
B:This failure mode belongs mainly to another situation: A SaaS database updates and deletes customer records but a pipeline appends every nightly full extract to a Delta table. Its preventative action would be: Use a supported change-data-capture feed and apply insert, update and delete semantics to the target. The most direct exposure in the current scenario is: An uncheckpointed consumer can replay or omit events after a restart.
C:This failure mode belongs mainly to another situation: A daily file load uses append-only mode for periodic snapshots of the same full inventory. Its preventative action would be: Use a snapshot replacement or keyed MERGE strategy instead of appending every full snapshot as new records. The most direct exposure in the current scenario is: An uncheckpointed consumer can replay or omit events after a restart.
Question 183
For this Microsoft DP-750 case: An audit asks who owns a catalog table but object ownership still points to an inactive employee. Which design or operational response BEST fits?
- Reconcile catalog object identity, lineage and current grants after schema or owner changes.
- Compare table-level masks against centrally governed ABAC coverage and identify missing assignments.
- Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management.
- Transfer ownership through approved governance workflow and review grants after reassignment.
Explanation
Correct Answer
D:The most appropriate action is: Transfer ownership through approved governance workflow and review grants after reassignment. It addresses the stated condition: An audit asks who owns a catalog table but object ownership still points to an inactive employee. The technical basis is: Governance depends on maintained object ownership as teams and responsibilities change. Without this control, an orphaned ownership chain can delay access review or emergency remediation. A direct acceptance check is: The designated active service or steward owns the object and prior inappropriate rights are removed.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. The corresponding measure there would be: Reconcile catalog object identity, lineage and current grants after schema or owner changes. The stated situation instead calls for: Transfer ownership through approved governance workflow and review grants after reassignment.
B:This alternative primarily addresses a different Azure Databricks problem: A user creates a column mask on a single table and assumes all tables with the same field name are protected. The corresponding measure there would be: Compare table-level masks against centrally governed ABAC coverage and identify missing assignments. The stated situation instead calls for: Transfer ownership through approved governance workflow and review grants after reassignment.
C:This alternative primarily addresses a different Azure Databricks problem: A data-sharing project emails storage keys to an external partner for reading curated Delta results. The corresponding measure there would be: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. The stated situation instead calls for: Transfer ownership through approved governance workflow and review grants after reassignment.
Question 184
A pipeline owner declines the action: Inspect the Spark UI DAG and skewed-key distribution before changing cluster size. The business situation is: A production Spark query is slow and its stage graph shows one task running far longer than all peers. What specific failure can follow?
- Premature deletion may invalidate time travel or a lagging reader's file references.
- Adding workers may not speed the one overloaded partition and increases total spend.
- A warehouse sized to average load may breach dashboard p95 latency during business opening.
- Ignoring metadata and file-layout changes can increase latency even though row counts decline.
Explanation
Correct Answer
B:The direct residual exposure is: Adding workers may not speed the one overloaded partition and increases total spend. The triggering condition is: A production Spark query is slow and its stage graph shows one task running far longer than all peers. The omitted safeguard is: Inspect the Spark UI DAG and skewed-key distribution before changing cluster size. This matters because: A single hot partition can dominate a distributed stage despite idle executor capacity. A corrective test would show: A skew-aware plan balances task durations and reduces the critical-stage elapsed time.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. Its preventative action would be: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. The most direct exposure in the current scenario is: Adding workers may not speed the one overloaded partition and increases total spend.
C:This failure mode belongs mainly to another situation: An interactive warehouse has high query queues during the morning but low CPU utilization after lunch. Its preventative action would be: Analyze concurrent query load and scaling policies rather than selecting capacity from daily averages. The most direct exposure in the current scenario is: Adding workers may not speed the one overloaded partition and increases total spend.
D:This failure mode belongs mainly to another situation: A query on a Delta table slows after a small percentage of rows are deleted but data files are not optimized. Its preventative action would be: Review deletion-vector behavior, table layout and suitable optimization for the supported runtime. The most direct exposure in the current scenario is: Adding workers may not speed the one overloaded partition and increases total spend.
Question 185
The following control has NOT been implemented: Register supported external locations and storage credentials, then define governed external tables. In this case: A legacy external Delta table points at a cloud location with an unmanaged storage credential stored in notebook text. Which exposure remains?
- An unqualified table reference may redirect a production job to a developer's test dataset.
- An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts.
- File-only storage may lack table-level transactional update and discoverability semantics.
- Credentials embedded in notebooks can be copied and used outside the intended catalog authorization.
Explanation
Correct Answer
D:The direct residual exposure is: Credentials embedded in notebooks can be copied and used outside the intended catalog authorization. The triggering condition is: A legacy external Delta table points at a cloud location with an unmanaged storage credential stored in notebook text. The omitted safeguard is: Register supported external locations and storage credentials, then define governed external tables. This matters because: External table metadata can be governed even when the underlying object files remain in external storage. A corrective test would show: A credential audit shows approved external access and no user-readable storage secret in notebook source.
Incorrect Answers
A:This failure mode belongs mainly to another situation: Production and development teams create identically named data objects in one catalog and accidentally overwrite test tables. Its preventative action would be: Create environment-specific Unity Catalog catalogs or schemas and enforce clear ownership and naming conventions. The most direct exposure in the current scenario is: Credentials embedded in notebooks can be copied and used outside the intended catalog authorization.
B:This failure mode belongs mainly to another situation: An ingestion team creates a table with a reserved or inconsistent name and automation fails in one environment. Its preventative action would be: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers. The most direct exposure in the current scenario is: Credentials embedded in notebooks can be copied and used outside the intended catalog authorization.
C:This failure mode belongs mainly to another situation: A team exposes structured transaction data as files in a volume but wants SQL analytics and ACID MERGE behavior. Its preventative action would be: Register the structured dataset as an appropriate managed Delta table rather than treating the volume itself as a SQL table. The most direct exposure in the current scenario is: Credentials embedded in notebooks can be copied and used outside the intended catalog authorization.
Question 186
For this Azure Databricks issue: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. Engineers choose: Restrict governed-tag administration and audit changes to protected metadata. What acceptance evidence is BEST?
- A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
- A controlled historical read succeeds within the mandated window and approved cleanup starts only afterwards.
- An access matrix tests current schema objects and verifies intended principals after migration.
- The partner reads only the approved shared table and fails to access a nonshared table.
Explanation
Correct Answer
A:The strongest acceptance proof is: A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence. It specifically verifies: Restrict governed-tag administration and audit changes to protected metadata. The original issue was: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. The underlying mechanism is: Tag-based access control relies on trusted management of the tags themselves. Without it, unauthorized retagging may neutralize masking or row restrictions on sensitive information.
Incorrect Answers
B:This result would validate a different measure: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. That is relevant to the distinct problem: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. Here the acceptance criterion is: A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
C:This result would validate a different measure: Reconcile catalog object identity, lineage and current grants after schema or owner changes. That is relevant to the distinct problem: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. Here the acceptance criterion is: A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
D:This result would validate a different measure: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. That is relevant to the distinct problem: A data-sharing project emails storage keys to an external partner for reading curated Delta results. Here the acceptance criterion is: A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
Question 187
The design team proposes: Evaluate Parquet or supported open-table formats against reader compatibility and mutation requirements. The situation is: An external sharing integration needs interoperable columnar read files but not native Delta updates. Which technical principle justifies the decision?
- File and table format choices depend on transactional features and consumer interoperability.
- Partition pruning benefits can be outweighed by extremely fragmented high-cardinality directory layouts.
- Type 1 dimensions replace nonhistorical descriptive attributes without retaining obsolete versions.
- Layered lakehouse processing separates source fidelity from approved business transformations.
Explanation
Correct Answer
A:The decisive mechanism is: File and table format choices depend on transactional features and consumer interoperability. That explains the selected action: Evaluate Parquet or supported open-table formats against reader compatibility and mutation requirements. In the original scenario: An external sharing integration needs interoperable columnar read files but not native Delta updates. The specific unmanaged risk is: Choosing Delta-specific mutation assumptions for ordinary Parquet files can break consumers. Validate with: The external reader loads approved columns and a documented compatibility test passes.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A data engineer chooses the distinct customer ID as a partition directory for an SCD dimension with millions of customers. Its targeted response is: Prefer appropriate clustering or lower-cardinality partitioning and assess file sizes for the dimension. The current case is governed more directly by: File and table format choices depend on transactional features and consumer interoperability.
C:This principle concerns a separate data-engineering condition: A reference table stores only the latest airport name and business users explicitly do not need historical values. Its targeted response is: Implement the required SCD Type 1 overwrite with stable business keys and validated updates. The current case is governed more directly by: File and table format choices depend on transactional features and consumer interoperability.
D:This principle concerns a separate data-engineering condition: A bronze ingestion layer stores only final transformed values and loses raw source fields needed for incident replay. Its targeted response is: Keep a governed raw or bronze representation before applying irreversible cleansing into silver and gold. The current case is governed more directly by: File and table format choices depend on transactional features and consumer interoperability.
Question 188
A production data platform experiences this condition: A bulk repair executes all pipeline tasks again even when only the final reporting notebook failed. Which targeted measure should be selected?
- Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid.
- Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution.
- Add bounded retries with exponential backoff and observable failure after the retry budget.
- Parameterize environment-specific paths, catalogs and identities through governed deployment configuration.
Explanation
Correct Answer
A:The most appropriate action is: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid. It addresses the stated condition: A bulk repair executes all pipeline tasks again even when only the final reporting notebook failed. The technical basis is: Task-level repair reduces unnecessary recomputation while preserving dependency correctness. Without this control, full reruns can repeat expensive historical ingestion and duplicate side effects. A direct acceptance check is: After a final-task failure, a repair completes the target without reprocessing validated upstream data.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. The corresponding measure there would be: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. The stated situation instead calls for: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid.
C:This alternative primarily addresses a different Azure Databricks problem: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. The corresponding measure there would be: Add bounded retries with exponential backoff and observable failure after the retry budget. The stated situation instead calls for: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid.
D:This alternative primarily addresses a different Azure Databricks problem: A multi-team notebook uses hard-coded workspace names and credentials, making the same pipeline fail in staging. The corresponding measure there would be: Parameterize environment-specific paths, catalogs and identities through governed deployment configuration. The stated situation instead calls for: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid.
Question 189
The following control has NOT been implemented: Align compatible schemas and use name-based union semantics with explicit type checks. In this case: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. Which exposure remains?
- An unrestricted join can multiply keys and exaggerate customer counts.
- Aggregating unauthorized or irrelevant rows can disclose or distort regional totals.
- Unnecessary MERGE operations can add substantial cost and contention without correctness benefit.
- Position-based union may quietly corrupt data when column positions differ.
Explanation
Correct Answer
D:The direct residual exposure is: Position-based union may quietly corrupt data when column positions differ. The triggering condition is: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. The omitted safeguard is: Align compatible schemas and use name-based union semantics with explicit type checks. This matters because: Union operations concatenate rows and require aligned column meanings. A corrective test would show: The merged dataset preserves typed values and column names from both input feeds.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A team wants only customer IDs present in both systems but uses an inner join that multiplies repeated rows. Its preventative action would be: Use an appropriate intersect or semi-join operation based on set and duplicate requirements. The most direct exposure in the current scenario is: Position-based union may quietly corrupt data when column positions differ.
B:This failure mode belongs mainly to another situation: An analyst calculates total revenue grouped by country but a join includes countries not approved for reporting. Its preventative action would be: Apply the required filters and join conditions before aggregation and validate authorized output groups. The most direct exposure in the current scenario is: Position-based union may quietly corrupt data when column positions differ.
C:This failure mode belongs mainly to another situation: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. Its preventative action would be: Use an incremental append pattern with suitable deduplication when source events cannot change. The most direct exposure in the current scenario is: Position-based union may quietly corrupt data when column positions differ.
Question 190
A team omits the recommended measure: Apply type, nullability and range expectations before promoting bronze rows into the silver target. Its environment shows: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. What is the MOST direct residual risk?
- Invalid amounts may silently convert to null and skew revenue aggregates.
- Null business keys can enter Delta targets and make updates or joins nondeterministic.
- Silently coercing a breaking type can erase measurable values while a job appears successful.
- Numerically valid but impossible values can contaminate customer metrics and machine-learning features.
Explanation
Correct Answer
A:The direct residual exposure is: Invalid amounts may silently convert to null and skew revenue aggregates. The triggering condition is: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. The omitted safeguard is: Apply type, nullability and range expectations before promoting bronze rows into the silver target. This matters because: Layered quality gates prevent malformed source values from contaminating trusted downstream tables. A corrective test would show: A controlled malformed amount is detected and excluded from published silver while legitimate zero values remain.
Incorrect Answers
B:This failure mode belongs mainly to another situation: An event pipeline must reject rows with a null transaction ID, but the data engineer checks only the row count after load. Its preventative action would be: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action. The most direct exposure in the current scenario is: Invalid amounts may silently convert to null and skew revenue aggregates.
C: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: Invalid amounts may silently convert to null and skew revenue aggregates.
D: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: Invalid amounts may silently convert to null and skew revenue aggregates.