Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 67
Question 660
A production data team leaves out: Choose one compatible data layout strategy based on table format, platform support and query evidence. Its scenario is: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. Which failure mode is MOST relevant?
- Duplicating physical dimensions can leave teams on inconsistent updates or retention periods.
- Poorly chosen keys increase full scans and maintenance overhead as traffic grows.
- Mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations.
- Assuming every engine can use every feature can result in invalid writes or unreadable metadata.
Explanation
Correct Answer
C:The direct residual exposure is: Mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations. The triggering condition is: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. The omitted safeguard is: Choose one compatible data layout strategy based on table format, platform support and query evidence. This matters because: Liquid clustering and traditional ZORDER/partitioning have compatibility constraints and different maintenance paths. A corrective test would show: A supported optimization command completes and query plans show the chosen layout works.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A data product creates multiple physical copies of a curated dimension because teams need different column names. Its preventative action would be: Expose stable SQL views over a governed base table when only presentation aliases differ. The most direct exposure in the current scenario is: Mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations.
B:This failure mode belongs mainly to another situation: A query repeatedly filters by customer, date and product but the physical data design was selected without query-profile evidence. Its preventative action would be: Compare selective filter patterns and data-skipping statistics before committing partition and clustering keys. The most direct exposure in the current scenario is: Mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations.
D:This failure mode belongs mainly to another situation: A cross-engine consumer expects a Delta table but source is plain Iceberg and engineers assume identical mutation semantics. Its preventative action would be: Choose and document a supported format and catalog integration with explicit read/write compatibility tests. The most direct exposure in the current scenario is: Mixing incompatible layout mechanisms can fail operations or leave the team relying on nonexistent optimizations.
Question 661
A data engineering team faces this Azure Databricks requirement: A notebook workflow imports a Python package without pinning its version, producing different results after an environment update. Which action is MOST appropriate?
- Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data.
- Tune supported SQL warehouse capacity and concurrency scaling based on simultaneous production query measurements.
- Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior.
- Record and pin supported package versions in the workload deployment specification and test reproducibility.
Explanation
Correct Answer
D:The most appropriate action is: Record and pin supported package versions in the workload deployment specification and test reproducibility. It addresses the stated condition: A notebook workflow imports a Python package without pinning its version, producing different results after an environment update. The technical basis is: Reproducible dependencies avoid unintentional behavior changes across cluster restarts and deployments. Without this control, implicit latest-version resolution can introduce breaking API changes into unchanged pipeline code. A direct acceptance check is: Clean-environment executions install the approved versions and return matching deterministic results.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A team turns on every performance setting for a workload without benchmarking whether disk spills or network shuffle dominate runtime. The corresponding measure there would be: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data. The stated situation instead calls for: Record and pin supported package versions in the workload deployment specification and test reproducibility.
B:This alternative primarily addresses a different Azure Databricks problem: A BI warehouse repeatedly slows during morning sign-in peaks even though a single analyst query runs quickly. The corresponding measure there would be: Tune supported SQL warehouse capacity and concurrency scaling based on simultaneous production query measurements. The stated situation instead calls for: Record and pin supported package versions in the workload deployment specification and test reproducibility.
C:This alternative primarily addresses a different Azure Databricks problem: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. The corresponding measure there would be: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. The stated situation instead calls for: Record and pin supported package versions in the workload deployment specification and test reproducibility.
Question 662
A Databricks engineer recommends: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. It responds to: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. What underlying mechanism BEST explains why?
- Least privilege includes removing access when the business purpose expires.
- Unity Catalog privileges are scoped to securable objects and can be inherited from containers.
- Workspace access scope and principal privileges enforce different aspects of authorization.
- Read and write operations require distinct Unity Catalog privileges and operating identities.
Explanation
Correct Answer
C:The decisive mechanism is: Workspace access scope and principal privileges enforce different aspects of authorization. That explains the selected action: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. In the original scenario: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. The specific unmanaged risk is: An object may be available to overprivileged identities in unintended contexts if either boundary is ignored. Validate with: A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A vendor's service principal was granted global access for a one-month integration and the project ended. Its targeted response is: Review and revoke stale grants and any linked service credentials, preserving required internal ownership. The current case is governed more directly by: Workspace access scope and principal privileges enforce different aspects of authorization.
B:This principle concerns a separate data-engineering condition: A finance analyst must read an approved table but was granted broad MODIFY rights at the schema level. Its targeted response is: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants. The current case is governed more directly by: Workspace access scope and principal privileges enforce different aspects of authorization.
D:This principle concerns a separate data-engineering condition: An engineering pipeline attempts to insert records into a production Delta table using an account with SELECT only. Its targeted response is: Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants. The current case is governed more directly by: Workspace access scope and principal privileges enforce different aspects of authorization.
Question 663
The team implements: Compare table-level masks against centrally governed ABAC coverage and identify missing assignments. The original problem is: A user creates a column mask on a single table and assumes all tables with the same field name are protected. Which test MOST convincingly demonstrates correctness?
- A seeded transformation appears with its expected upstream source and downstream target in lineage.
- A governance test finds masked behavior across all intended tagged objects and detects any unprotected table.
- The partner reads only the approved shared table and fails to access a nonshared table.
- A controlled historical read succeeds within the mandated window and approved cleanup starts only afterwards.
Explanation
Correct Answer
B:The strongest acceptance proof is: A governance test finds masked behavior across all intended tagged objects and detects any unprotected table. It specifically verifies: Compare table-level masks against centrally governed ABAC coverage and identify missing assignments. The original issue was: A user creates a column mask on a single table and assumes all tables with the same field name are protected. The underlying mechanism is: Per-table fine-grained policies do not automatically propagate to unrelated objects. Without it, an identically named confidential field in a new table could be exposed.
Incorrect Answers
A: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 governance test finds masked behavior across all intended tagged objects and detects any unprotected table.
C: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 governance test finds masked behavior across all intended tagged objects and detects any unprotected table.
D: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 governance test finds masked behavior across all intended tagged objects and detects any unprotected table.
Question 664
A data product owner adopts: Collect expectation metrics and reconcile input, accepted, quarantined and rejected record counts. The reason is: A pipeline reports zero failed rows because bad records are silently dropped without any count of what was removed. What observed result BEST proves effectiveness?
- A simulated type change is rejected or rescued with an actionable alert and no corrupted curated output.
- A sample of valid UTC timestamps passes and known ambiguous strings produce the expected exception record.
- Quality dashboards separate optional-null rates from prohibited null keys and meet agreed thresholds.
- Each run reports complete input-to-output reconciliation and alerts when rejected fraction exceeds its SLO.
Explanation
Correct Answer
D:The strongest acceptance proof is: Each run reports complete input-to-output reconciliation and alerts when rejected fraction exceeds its SLO. It specifically verifies: Collect expectation metrics and reconcile input, accepted, quarantined and rejected record counts. The original issue was: A pipeline reports zero failed rows because bad records are silently dropped without any count of what was removed. The underlying mechanism is: Measurable quality controls need observable outcomes and accounting for rejected data. Without it, A seemingly successful load can conceal a growing upstream data-loss problem.
Incorrect Answers
A:This result would validate a different measure: Apply schema enforcement with explicit drift handling and alert on incompatible structural changes. That is relevant to the distinct problem: A source API changes a quantity from integer to nested JSON and the pipeline silently produces nulls downstream. Here the acceptance criterion is: Each run reports complete input-to-output reconciliation and alerts when rejected fraction exceeds its SLO.
B:This result would validate a different measure: Validate timezone-aware timestamp types and quarantine ambiguous or unparseable event values. That is relevant to the distinct problem: A regulated dataset requires all timestamps to parse as UTC but several rows have ambiguous local values. Here the acceptance criterion is: Each run reports complete input-to-output reconciliation and alerts when rejected fraction exceeds its SLO.
C:This result would validate a different measure: Profile source missingness and define field-specific required versus optional expectations. That is relevant to the distinct problem: A new customer feed is missing optional contact information for 8% of rows and the team treats every null as pipeline failure. Here the acceptance criterion is: Each run reports complete input-to-output reconciliation and alerts when rejected fraction exceeds its SLO.
Question 665
A data engineering team faces this Azure Databricks requirement: A long-running job occasionally hangs but there is no configured runtime ceiling or escalation. Which action is MOST appropriate?
- Define validated job parameters and propagate them through supported task parameter bindings.
- Set task and job timeout limits with notifications and a documented retry and recovery route.
- Wait for or explicitly verify required external or asynchronous work before reporting task success.
- Review explicit dependency and run-if settings and validate skip behavior through a staged failure.
Explanation
Correct Answer
B:The most appropriate action is: Set task and job timeout limits with notifications and a documented retry and recovery route. It addresses the stated condition: A long-running job occasionally hangs but there is no configured runtime ceiling or escalation. The technical basis is: Timeouts and incident routing bound the cost and impact of stalled workflow execution. Without this control, A hung task can consume cluster hours indefinitely and prevent expected downstream refresh. A direct acceptance check is: A simulated stall exceeds the threshold, stops correctly and alerts the support team.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A workflow needs to pass a date parameter from a scheduled trigger into all its downstream notebook tasks. The corresponding measure there would be: Define validated job parameters and propagate them through supported task parameter bindings. The stated situation instead calls for: Set task and job timeout limits with notifications and a documented retry and recovery route.
C:This alternative primarily addresses a different Azure Databricks problem: A job is successful in the orchestrator but the business target is not updated because the notebook returns before async work completes. The corresponding measure there would be: Wait for or explicitly verify required external or asynchronous work before reporting task success. The stated situation instead calls for: Set task and job timeout limits with notifications and a documented retry and recovery route.
D:This alternative primarily addresses a different Azure Databricks problem: A job owner cannot explain why a task skipped execution after a predecessor failed. The corresponding measure there would be: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. The stated situation instead calls for: Set task and job timeout limits with notifications and a documented retry and recovery route.
Question 666
An operator introduces: Write to a staging target, validate row totals and invariants, then perform the approved publication step. The situation is: A finance transformation writes its output directly into a published table before reconciling totals against the source. Which validation should be required before signoff?
- An injected transient 503 recovers within the retry budget while repeated failures produce actionable alerts.
- A delayed-ingestion test prevents gold refresh until bronze and silver are completed successfully.
- A seeded mismatch prevents cutover and the prior certified table remains queryable.
- Invalid input blocks publication while the previous approved dataset remains available.
Explanation
Correct Answer
C:The strongest acceptance proof is: A seeded mismatch prevents cutover and the prior certified table remains queryable. It specifically verifies: Write to a staging target, validate row totals and invariants, then perform the approved publication step. The original issue was: A finance transformation writes its output directly into a published table before reconciling totals against the source. The underlying mechanism is: Staging plus validation separates construction of data from its declaration as trusted. Without it, A bad transformation may make a broken dataset immediately visible to consumers.
Incorrect Answers
A:This result would validate a different measure: Add bounded retries with exponential backoff and observable failure after the retry budget. That is relevant to the distinct problem: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. Here the acceptance criterion is: A seeded mismatch prevents cutover and the prior certified table remains queryable.
B:This result would validate a different measure: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed. That is relevant to the distinct problem: A sales pipeline aggregates gold metrics before the bronze ingestion task finishes and occasionally reports incomplete totals. Here the acceptance criterion is: A seeded mismatch prevents cutover and the prior certified table remains queryable.
D:This result would validate a different measure: Place validations before publishing and use an atomic cutover or controlled target write. That is relevant to the distinct problem: A workflow writes to production tables before a validation task examines null keys and duplicates. Here the acceptance criterion is: A seeded mismatch prevents cutover and the prior certified table remains queryable.
Question 667
A production data platform experiences this condition: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. Which targeted measure should be selected?
- Replace broad grants with documented minimum creation and use privileges in a dedicated schema.
- Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model.
- Configure a tested Unity Catalog row filter or suitable ABAC policy based on the authorized identity.
- Check required parent catalog and schema usage privileges alongside the table SELECT grant.
Explanation
Correct Answer
D:The most appropriate action is: Check required parent catalog and schema usage privileges alongside the table SELECT grant. It addresses the stated condition: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. The technical basis is: Object access can require permission to traverse its parent hierarchy as well as read the child. Without this control, granting SELECT alone may not make a catalog object usable and lead to excessive troubleshooting grants. A direct acceptance check is: A privilege inspection shows the narrow parent usage grants and the contractor can query only the intended table.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. The corresponding measure there would be: Replace broad grants with documented minimum creation and use privileges in a dedicated schema. The stated situation instead calls for: Check required parent catalog and schema usage privileges alongside the table SELECT grant.
B:This alternative primarily addresses a different Azure Databricks problem: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. The corresponding measure there would be: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. The stated situation instead calls for: Check required parent catalog and schema usage privileges alongside the table SELECT grant.
C:This alternative primarily addresses a different Azure Databricks problem: A user must see only the East region rows of a common sales table while managers see all territories. The corresponding measure there would be: Configure a tested Unity Catalog row filter or suitable ABAC policy based on the authorized identity. The stated situation instead calls for: Check required parent catalog and schema usage privileges alongside the table SELECT grant.
Question 668
A production data platform experiences this condition: A file feed introduces an unexpected optional column and the stream fails after the first changed file. Which targeted measure should be selected?
- Use Auto Loader with durable checkpointing and an appropriate discovery mode to ingest new files incrementally.
- Configure supported schema evolution or rescued-data handling with explicit compatibility review.
- Implement idempotent foreachBatch or compatible transactional sink logic keyed by epoch or business identity.
- Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction.
Explanation
Correct Answer
B:The most appropriate action is: Configure supported schema evolution or rescued-data handling with explicit compatibility review. It addresses the stated condition: A file feed introduces an unexpected optional column and the stream fails after the first changed file. The technical basis is: Schema drift must be classified as an acceptable extension or a breaking contract change. Without this control, ignoring changed source structures can halt ingestion or silently lose fields. A direct acceptance check is: A controlled extra-column event is either safely evolved or quarantined with an explicit notification.
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: Configure supported schema evolution or rescued-data handling with explicit compatibility review.
C:This alternative primarily addresses a different Azure Databricks problem: A stream writes into an external sink without stable batch identities and causes duplicate side effects on retry. The corresponding measure there would be: Implement idempotent foreachBatch or compatible transactional sink logic keyed by epoch or business identity. The stated situation instead calls for: Configure supported schema evolution or rescued-data handling with explicit compatibility review.
D: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: Configure supported schema evolution or rescued-data handling with explicit compatibility review.
Question 669
A production data platform experiences this condition: A department wants a self-service sandbox but must prevent users from creating huge unrestricted clusters. Which targeted measure should be selected?
- Tune supported SQL warehouse capacity and concurrency scaling based on simultaneous production query measurements.
- Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users.
- Pin a supported Databricks Runtime version and validate application libraries against it before deployment.
- Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution.
Explanation
Correct Answer
B:The most appropriate action is: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users. It addresses the stated condition: A department wants a self-service sandbox but must prevent users from creating huge unrestricted clusters. The technical basis is: Compute policies provide governance boundaries for permissible resource configurations. Without this control, unrestricted cluster creation can create unpredictable spending and inconsistent operational standards. A direct acceptance check is: An ordinary user can start an approved small cluster but cannot exceed policy size or runtime limits.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A BI warehouse repeatedly slows during morning sign-in peaks even though a single analyst query runs quickly. The corresponding measure there would be: Tune supported SQL warehouse capacity and concurrency scaling based on simultaneous production query measurements. The stated situation instead calls for: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users.
C:This alternative primarily addresses a different Azure Databricks problem: A developer selects a new Databricks Runtime version for production despite an untested JDBC driver dependency. The corresponding measure there would be: Pin a supported Databricks Runtime version and validate application libraries against it before deployment. The stated situation instead calls for: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users.
D:This alternative primarily addresses a different Azure Databricks problem: A nightly batch transformation uses a continuously running all-purpose cluster even though no analyst interacts with the workload between runs. The corresponding measure there would be: Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution. The stated situation instead calls for: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users.
Question 670
A production data platform experiences this condition: A daily revenue report double-counts refunds because both debit and credit rows are summed as positive numbers. Which targeted measure should be selected?
- Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics.
- Define field-specific missing-value rules and quarantine or enrich unknown values before assigning business meaning.
- Use a compatible unpivot or stack transformation with explicit month and amount columns.
- Normalize transaction sign semantics before grouping by business date and customer.
Explanation
Correct Answer
D:The most appropriate action is: Normalize transaction sign semantics before grouping by business date and customer. It addresses the stated condition: A daily revenue report double-counts refunds because both debit and credit rows are summed as positive numbers. The technical basis is: Aggregations require correctly modeled financial direction and data types. Without this control, refund amounts treated as sales inflate net revenue even when record counts match. A direct acceptance check is: A test invoice with a linked refund produces the approved net amount.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An analyst must find records present in the source system but absent in a target migration. The corresponding measure there would be: Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics. The stated situation instead calls for: Normalize transaction sign semantics before grouping by business date and customer.
B:This alternative primarily addresses a different Azure Databricks problem: A customer reference dataset has missing country codes but a pipeline replaces every null with an arbitrary default country. The corresponding measure there would be: Define field-specific missing-value rules and quarantine or enrich unknown values before assigning business meaning. The stated situation instead calls for: Normalize transaction sign semantics before grouping by business date and customer.
C:This alternative primarily addresses a different Azure Databricks problem: A large orders dataset has one column per month but a dashboard expects month-value rows for filtering and grouping. The corresponding measure there would be: Use a compatible unpivot or stack transformation with explicit month and amount columns. The stated situation instead calls for: Normalize transaction sign semantics before grouping by business date and customer.