Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 72
Question 710
A solution applies: Evaluate Parquet or supported open-table formats against reader compatibility and mutation requirements. It addresses: An external sharing integration needs interoperable columnar read files but not native Delta updates. Which operational outcome MOST directly verifies success?
- A representative account-filter query reads fewer irrelevant files after optimized clustering.
- The top event-time queries show improved data skipping and reconciled row counts.
- The external reader loads approved columns and a documented compatibility test passes.
- Representative business queries return consistent region totals with an acceptable plan.
Explanation
Correct Answer
C:The strongest acceptance proof is: The external reader loads approved columns and a documented compatibility test passes. It specifically verifies: Evaluate Parquet or supported open-table formats against reader compatibility and mutation requirements. The original issue was: An external sharing integration needs interoperable columnar read files but not native Delta updates. The underlying mechanism is: File and table format choices depend on transactional features and consumer interoperability. Without it, choosing Delta-specific mutation assumptions for ordinary Parquet files can break consumers.
Incorrect Answers
A:This result would validate a different measure: Enable supported liquid clustering with appropriate keys and run compatible optimization. That is relevant to the distinct problem: A large Delta fact table is filtered primarily on high-cardinality account IDs with changing query patterns. Here the acceptance criterion is: The external reader loads approved columns and a documented compatibility test passes.
B:This result would validate a different measure: Reevaluate data layout using representative event-time filters and a suitable clustering key. That is relevant to the distinct problem: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. Here the acceptance criterion is: The external reader loads approved columns and a documented compatibility test passes.
D:This result would validate a different measure: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. That is relevant to the distinct problem: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. Here the acceptance criterion is: The external reader loads approved columns and a documented compatibility test passes.
Question 711
A production data team leaves out: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant. Its scenario is: A business report must refresh daily at 06:00 in a defined local time zone but a developer schedules it in UTC without conversion. Which failure mode is MOST relevant?
- An implicit UTC schedule can cause delivery an hour or more away from the required business cutover.
- Unbounded restarts can amplify resource consumption while no useful records are processed.
- Overlapping runs may race to overwrite outputs or duplicate appended records.
- A missed overnight job can remain unnoticed until business users complain.
Explanation
Correct Answer
A:The direct residual exposure is: An implicit UTC schedule can cause delivery an hour or more away from the required business cutover. The triggering condition is: A business report must refresh daily at 06:00 in a defined local time zone but a developer schedules it in UTC without conversion. The omitted safeguard is: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant. This matters because: Scheduler time zone semantics affect when recurring business windows run. A corrective test would show: Run history shows the job starts at the agreed local times across representative date transitions.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A continuously running pipeline is scheduled to restart automatically but restart storms consume a growing compute budget. Its preventative action would be: Configure bounded restarts and alerting with root-cause investigation for repeated failures. The most direct exposure in the current scenario is: An implicit UTC schedule can cause delivery an hour or more away from the required business cutover.
C:This failure mode belongs mainly to another situation: A daily data job runs twice during an incident and both executions write to the same target. Its preventative action would be: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap. The most direct exposure in the current scenario is: An implicit UTC schedule can cause delivery an hour or more away from the required business cutover.
D:This failure mode belongs mainly to another situation: A scheduled Lakeflow Job has no owner alert when its final task fails overnight. Its preventative action would be: Configure job failure notifications to approved recipients and validate incident routing. The most direct exposure in the current scenario is: An implicit UTC schedule can cause delivery an hour or more away from the required business cutover.
Question 712
During a lakehouse implementation review, engineers observe: A Spark join reads large inputs but the driver reports failures after an analyst calls collect() on the result. What is the BEST next action?
- Keep large results distributed and replace driver collection with bounded sampling or distributed writes.
- Profile aggregation key distribution, shuffle partitions and executor memory before choosing a targeted change.
- Use Lakeflow Jobs repair at the failed task when dependency outputs remain valid.
- Collect job timing, task duration and relevant Spark stage metrics in a monitored baseline.
Explanation
Correct Answer
A:The most appropriate action is: Keep large results distributed and replace driver collection with bounded sampling or distributed writes. It addresses the stated condition: A Spark join reads large inputs but the driver reports failures after an analyst calls collect() on the result. The technical basis is: Driver memory is not an unlimited sink for results of distributed computation. Without this control, collecting billions of rows can crash the driver despite idle executors. A direct acceptance check is: The job writes results through distributed output and driver memory stays below the approved threshold.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A Spark workload repeatedly fails with executor out-of-memory errors on a high-cardinality groupBy. The corresponding measure there would be: Profile aggregation key distribution, shuffle partitions and executor memory before choosing a targeted change. The stated situation instead calls for: Keep large results distributed and replace driver collection with bounded sampling or distributed writes.
C:This alternative primarily addresses a different Azure Databricks problem: A job fails during a temporary Azure storage outage but operators rerun every successful upstream task. The corresponding measure there would be: Use Lakeflow Jobs repair at the failed task when dependency outputs remain valid. The stated situation instead calls for: Keep large results distributed and replace driver collection with bounded sampling or distributed writes.
D:This alternative primarily addresses a different Azure Databricks problem: A job's duration doubles but an administrator sees only its final success status with no phase-level metrics. The corresponding measure there would be: Collect job timing, task duration and relevant Spark stage metrics in a monitored baseline. The stated situation instead calls for: Keep large results distributed and replace driver collection with bounded sampling or distributed writes.
Question 713
The recommended measure is: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys. The operational context is: A retail customer table changes delivery address repeatedly but analysts must reconstruct the address known at any prior invoice date. Which data engineering concept applies?
- A star schema separates measurable events from descriptive dimensions and controls join cardinality.
- Delta version history can provide auditable historical snapshots while underlying files are retained.
- Delta and Iceberg are different transactional table formats with version-dependent feature support.
- SCD Type 2 preserves historical attribute versions rather than overwriting the prior business state.
Explanation
Correct Answer
D:The decisive mechanism is: SCD Type 2 preserves historical attribute versions rather than overwriting the prior business state. That explains the selected action: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys. In the original scenario: A retail customer table changes delivery address repeatedly but analysts must reconstruct the address known at any prior invoice date. The specific unmanaged risk is: Using Type 1 updates may silently rewrite the apparent address on older transaction reports. Validate with: A backdated invoice joins to the address valid on its transaction date while the current record shows the latest address.
Incorrect Answers
A: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: SCD Type 2 preserves historical attribute versions rather than overwriting the prior business state.
B: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: SCD Type 2 preserves historical attribute versions rather than overwriting the prior business state.
C:This principle concerns a separate data-engineering condition: A cross-engine consumer expects a Delta table but source is plain Iceberg and engineers assume identical mutation semantics. Its targeted response is: Choose and document a supported format and catalog integration with explicit read/write compatibility tests. The current case is governed more directly by: SCD Type 2 preserves historical attribute versions rather than overwriting the prior business state.
Question 714
The team chooses: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. Its observed issue is: A company needs to review table-owner changes and permissions after organizational restructuring. What is the strongest technical basis?
- Object governance is ongoing and must follow organizational role and service identity changes.
- Permission reviews should follow actual securable objects and their dependencies rather than name assumptions.
- Security governance requires attributable administrative activity and durable evidence.
- Automatic lineage visibility has collection boundaries and does not imply every real-world dependency is recorded.
Explanation
Correct Answer
A:The decisive mechanism is: Object governance is ongoing and must follow organizational role and service identity changes. That explains the selected action: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. In the original scenario: A company needs to review table-owner changes and permissions after organizational restructuring. The specific unmanaged risk is: Accumulated historical grants may give former project teams access to unrelated data products. Validate with: The recertification report identifies owners, changed grants and approved remediation evidence.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. Its targeted response is: Reconcile catalog object identity, lineage and current grants after schema or owner changes. The current case is governed more directly by: Object governance is ongoing and must follow organizational role and service identity changes.
C:This principle concerns a separate data-engineering condition: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. Its targeted response is: Configure supported Databricks audit logging and route relevant events to a secured retention destination. The current case is governed more directly by: Object governance is ongoing and must follow organizational role and service identity changes.
D:This principle concerns a separate data-engineering condition: A lineage graph shows no relationship for data loaded outside the monitored platform and the team assumes the dataset has no upstream dependency. Its targeted response is: Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance. The current case is governed more directly by: Object governance is ongoing and must follow organizational role and service identity changes.
Question 715
A platform architect adopts: Use idempotent deployment methods or reconcile existing resource IDs before creating replacements. For this requirement: A REST deployment script creates duplicate jobs every time CI reruns after a timeout. Which rationale MOST directly supports it?
- Reviewed changes with required status checks reduce uncontrolled production configuration drift.
- Infrastructure automation must tolerate retries without multiplying the intended target resources.
- Reproducible deployments require versioned execution dependencies as well as application code.
- Syntax checks do not validate business semantics or interaction with external tables.
Explanation
Correct Answer
B:The decisive mechanism is: Infrastructure automation must tolerate retries without multiplying the intended target resources. That explains the selected action: Use idempotent deployment methods or reconcile existing resource IDs before creating replacements. In the original scenario: A REST deployment script creates duplicate jobs every time CI reruns after a timeout. The specific unmanaged risk is: Duplicate jobs may run on the same schedule and load data twice. Validate with: Two identical deployment executions leave exactly one intended job with approved settings.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A release process merges unreviewed notebook changes directly into the main branch minutes before a production run. Its targeted response is: Protect the main branch with peer review, required tests and controlled promotion windows. The current case is governed more directly by: Infrastructure automation must tolerate retries without multiplying the intended target resources.
C:This principle concerns a separate data-engineering condition: A team cannot reproduce a prior release because package versions are resolved dynamically during deployment. Its targeted response is: Pin package and runtime versions in the governed release artifact and record its dependency manifest. The current case is governed more directly by: Infrastructure automation must tolerate retries without multiplying the intended target resources.
D:This principle concerns a separate data-engineering condition: A release modifies transformation logic but tests only whether Python files compile. Its targeted response is: Add representative unit and integration tests asserting transformation results and schema contracts. The current case is governed more directly by: Infrastructure automation must tolerate retries without multiplying the intended target resources.
Question 716
An operator introduces: Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model. The situation is: A data product needs to copy a supported Azure Data Factory pipeline output into governed Databricks tables. Which validation should be required before signoff?
- A sampled bronze row links to the expected stream partition and source event time.
- After a restart, already committed files are not duplicated and newly arrived files are ingested.
- ADF completion evidence and Databricks job dependencies show an end-to-end successful load.
- A seed file loads the exact expected columns and invalid rows are reported rather than silently accepted.
Explanation
Correct Answer
C:The strongest acceptance proof is: ADF completion evidence and Databricks job dependencies show an end-to-end successful load. It specifically verifies: Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model. The original issue was: A data product needs to copy a supported Azure Data Factory pipeline output into governed Databricks tables. The underlying mechanism is: An external orchestrator can trigger Databricks processing while governance and failure handling remain explicit. Without it, uncoordinated retries can run transformations before ingestion finishes or under the wrong identity.
Incorrect Answers
A:This result would validate a different measure: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay. That is relevant to the distinct problem: A pipeline ingests Event Hubs messages into a bronze table but never captures the partition, offset or event timestamp. Here the acceptance criterion is: ADF completion evidence and Databricks job dependencies show an end-to-end successful load.
B:This result would validate a different measure: Use Auto Loader with durable checkpointing and an appropriate discovery mode to ingest new files incrementally. That is relevant to the distinct 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. Here the acceptance criterion is: ADF completion evidence and Databricks job dependencies show an end-to-end successful load.
D:This result would validate a different measure: Specify the correct input delimiter, header and schema and validate parsing on a representative file. That is relevant to the distinct problem: An overnight load reads tab-separated files but an engineer assumes comma separators and casts malformed columns to null. Here the acceptance criterion is: ADF completion evidence and Databricks job dependencies show an end-to-end successful load.
Question 717
The recommended measure is: Use an incremental append pattern with suitable deduplication when source events cannot change. The operational context is: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. Which data engineering concept applies?
- Append is generally simpler for immutable events than key-by-key mutation logic.
- Pivoting transposes category values into columns but requires stable categories and aggregation semantics.
- MERGE combines inserts and updates atomically against a keyed target.
- SQL NULL indicates absent or unknown values while numeric zero is a valid value.
Explanation
Correct Answer
A:The decisive mechanism is: Append is generally simpler for immutable events than key-by-key mutation logic. That explains the selected action: Use an incremental append pattern with suitable deduplication when source events cannot change. In the original scenario: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. The specific unmanaged risk is: Unnecessary MERGE operations can add substantial cost and contention without correctness benefit. Validate with: A timed append comparison meets the freshness and duplicate controls with lower compute consumption.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A quality report needs one column for each product status category but stores status as separate rows. Its targeted response is: Apply a controlled pivot with a defined set of expected categories and aggregation rule. The current case is governed more directly by: Append is generally simpler for immutable events than key-by-key mutation logic.
C:This principle concerns a separate data-engineering condition: A product catalog receives corrections for existing SKUs plus entirely new items on each incremental load. Its targeted response is: Use a Delta MERGE keyed by SKU with appropriate matched-update and not-matched-insert logic. The current case is governed more directly by: Append is generally simpler for immutable events than key-by-key mutation logic.
D:This principle concerns a separate data-engineering condition: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. Its targeted response is: Implement explicit null predicates rather than treating zero and null as equivalent. The current case is governed more directly by: Append is generally simpler for immutable events than key-by-key mutation logic.
Question 718
An operator introduces: Record and pin supported package versions in the workload deployment specification and test reproducibility. The situation is: A notebook workflow imports a Python package without pinning its version, producing different results after an environment update. Which validation should be required before signoff?
- Permission tests show approved analysts run their notebooks while unauthorized cluster policy edits and installs fail.
- A forced restart of interactive compute leaves the scheduled production task unaffected.
- Clean-environment executions install the approved versions and return matching deterministic results.
- Identical data and query workloads yield reconciled outputs and a recorded improvement in elapsed time per unit cost.
Explanation
Correct Answer
C:The strongest acceptance proof is: Clean-environment executions install the approved versions and return matching deterministic results. It specifically verifies: Record and pin supported package versions in the workload deployment specification and test reproducibility. The original issue was: A notebook workflow imports a Python package without pinning its version, producing different results after an environment update. The underlying mechanism is: Reproducible dependencies avoid unintentional behavior changes across cluster restarts and deployments. Without it, implicit latest-version resolution can introduce breaking API changes into unchanged pipeline code.
Incorrect Answers
A:This result would validate a different measure: Apply suitable compute access modes, policies and entitlements that restrict who can attach or modify shared compute. That is relevant to the distinct problem: A multi-team interactive cluster permits users to attach arbitrary unapproved libraries and run notebooks under broad shared privileges. Here the acceptance criterion is: Clean-environment executions install the approved versions and return matching deterministic results.
B:This result would validate a different measure: Define a job-owned execution identity and eligible task compute separate from ad hoc analyst cluster lifecycle. That is relevant to the distinct problem: A scheduled ETL run uses shared analyst compute and fails whenever the cluster owner restarts a notebook session. Here the acceptance criterion is: Clean-environment executions install the approved versions and return matching deterministic results.
D:This result would validate a different measure: Benchmark Photon on a supported runtime with representative queries and compare cost, latency and correctness. That is relevant to the distinct 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. Here the acceptance criterion is: Clean-environment executions install the approved versions and return matching deterministic results.
Question 719
The design team proposes: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. The situation is: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. Which technical principle justifies the decision?
- Message-bus streams require offset progress tracking and a durable state boundary.
- Managed ingestion connectors can simplify source synchronization when their coverage fits the source.
- Watermarks define the tolerated late-event horizon for stateful stream processing.
- Data pipeline completeness requires tracking arrivals rather than assuming an exact wall-clock boundary.
Explanation
Correct Answer
A:The decisive mechanism is: Message-bus streams require offset progress tracking and a durable state boundary. That explains the selected action: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. In the original scenario: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. The specific unmanaged risk is: An uncheckpointed consumer can replay or omit events after a restart. Validate with: An event batch survives a controlled consumer restart and downstream totals match the expected sample.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A batch integration needs a connector-managed path from a supported operational source into the lakehouse. Its targeted response is: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction. The current case is governed more directly by: Message-bus streams require offset progress tracking and a durable state boundary.
C:This principle concerns a separate data-engineering condition: A stream must group clicks into five-minute event-time windows while some mobile devices transmit data several minutes late. Its targeted response is: Configure event-time windowing and an appropriate watermark based on observed lateness. The current case is governed more directly by: Message-bus streams require offset progress tracking and a durable state boundary.
D:This principle concerns a separate data-engineering condition: A Databricks job receives daily structured extracts but an upstream schedule occasionally delivers files late. Its targeted response is: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark. The current case is governed more directly by: Message-bus streams require offset progress tracking and a durable state boundary.
Question 720
A production data team leaves out: Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported. Its scenario is: A data compliance team needs consistent redaction of columns tagged as personal data across hundreds of catalog tables. Which failure mode is MOST relevant?
- A copied notebook may leak storage access keys beyond the intended data-processing environment.
- Confusing catalog visibility with data authorization can lead to unnecessary sensitive table access.
- Manual per-table rules can miss newly created columns and expose sensitive values.
- Fixing only Azure IAM may leave catalog object access denied while broad grants increase risk.
Explanation
Correct Answer
C:The direct residual exposure is: Manual per-table rules can miss newly created columns and expose sensitive values. The triggering condition is: A data compliance team needs consistent redaction of columns tagged as personal data across hundreds of catalog tables. The omitted safeguard is: Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported. This matters because: Attribute-based policies can apply common decisions at scale rather than managing every table individually. A corrective test would show: A new tagged test column receives the required masking behavior without a separate manual table exception.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. Its preventative action would be: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. The most direct exposure in the current scenario is: Manual per-table rules can miss newly created columns and expose sensitive values.
B:This failure mode belongs mainly to another situation: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. Its preventative action would be: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. The most direct exposure in the current scenario is: Manual per-table rules can miss newly created columns and expose sensitive values.
D:This failure mode belongs mainly to another situation: A managed identity can read a storage container but a newly created external table is denied in Databricks. Its preventative action would be: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges. The most direct exposure in the current scenario is: Manual per-table rules can miss newly created columns and expose sensitive values.