Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 86
Question 850
For this Microsoft DP-750 case: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. Which design or operational response BEST fits?
- Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs.
- Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again.
- Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling.
- Run supported OPTIMIZE or predictive optimization and validate file-size distribution and query cost.
Explanation
Correct Answer
A:The most appropriate action is: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. It addresses the stated condition: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. The technical basis is: VACUUM removes old physical files, so aggressive cleanup can break valid historical references. Without this control, premature deletion may invalidate time travel or a lagging reader's file references. A direct acceptance check is: A permitted historical query succeeds before and after approved housekeeping within its retention boundary.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A warehouse query remains slow even after larger compute is allocated and the profile reports scanning nearly every file. The corresponding measure there would be: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again. The stated situation instead calls for: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs.
C:This alternative primarily addresses a different Azure Databricks problem: A streaming pipeline's throughput falls although event arrival increases and its input backlog grows over time. The corresponding measure there would be: Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling. The stated situation instead calls for: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs.
D:This alternative primarily addresses a different Azure Databricks problem: A Delta table contains millions of tiny files after frequent microbatch updates and SQL scans spend time opening files. The corresponding measure there would be: Run supported OPTIMIZE or predictive optimization and validate file-size distribution and query cost. The stated situation instead calls for: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs.
Question 851
The recommended measure is: Compare table-level masks against centrally governed ABAC coverage and identify missing assignments. The operational context is: A user creates a column mask on a single table and assumes all tables with the same field name are protected. Which data engineering concept applies?
- Row filters can restrict query results without maintaining separate physical copies by region.
- Governance depends on maintained object ownership as teams and responsibilities change.
- Per-table fine-grained policies do not automatically propagate to unrelated objects.
- Object governance is ongoing and must follow organizational role and service identity changes.
Explanation
Correct Answer
C:The decisive mechanism is: Per-table fine-grained policies do not automatically propagate to unrelated objects. That explains the selected action: Compare table-level masks against centrally governed ABAC coverage and identify missing assignments. In the original scenario: A user creates a column mask on a single table and assumes all tables with the same field name are protected. The specific unmanaged risk is: An identically named confidential field in a new table could be exposed. Validate with: A governance test finds masked behavior across all intended tagged objects and detects any unprotected table.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A shared customer table needs dynamic per-region row restrictions but the business refuses duplicating physical datasets. Its targeted response is: Use row-filter policies on the governed table and test permitted region entitlements. The current case is governed more directly by: Per-table fine-grained policies do not automatically propagate to unrelated objects.
B:This principle concerns a separate data-engineering condition: An audit asks who owns a catalog table but object ownership still points to an inactive employee. Its targeted response is: Transfer ownership through approved governance workflow and review grants after reassignment. The current case is governed more directly by: Per-table fine-grained policies do not automatically propagate to unrelated objects.
D:This principle concerns a separate data-engineering condition: A company needs to review table-owner changes and permissions after organizational restructuring. Its targeted response is: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. The current case is governed more directly by: Per-table fine-grained policies do not automatically propagate to unrelated objects.
Question 852
An Azure Databricks architect reviews the following problem: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. What should the team implement FIRST?
- Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle.
- Define and validate environment-specific catalog, workspace and identity targets in deployment configuration.
- Use idempotent deployment methods or reconcile existing resource IDs before creating replacements.
- Store deployment source in Git with reviewed branches and pull requests before promoting changes.
Explanation
Correct Answer
D:The most appropriate action is: Store deployment source in Git with reviewed branches and pull requests before promoting changes. It addresses the stated condition: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. The technical basis is: Version control and code review establish provenance and repeatable release history. Without this control, unreviewed direct edits can break jobs without a reproducible rollback commit. A direct acceptance check is: A production run references an approved immutable commit and a prior version can be restored.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. The corresponding measure there would be: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. The stated situation instead calls for: Store deployment source in Git with reviewed branches and pull requests before promoting changes.
B:This alternative primarily addresses a different Azure Databricks problem: A multi-environment setup uses the same catalog for test and production because bundle target variables were omitted. The corresponding measure there would be: Define and validate environment-specific catalog, workspace and identity targets in deployment configuration. The stated situation instead calls for: Store deployment source in Git with reviewed branches and pull requests before promoting changes.
C:This alternative primarily addresses a different Azure Databricks problem: A REST deployment script creates duplicate jobs every time CI reruns after a timeout. The corresponding measure there would be: Use idempotent deployment methods or reconcile existing resource IDs before creating replacements. The stated situation instead calls for: Store deployment source in Git with reviewed branches and pull requests before promoting changes.
Question 853
The team chooses: Add bounded retries with exponential backoff and observable failure after the retry budget. Its observed issue is: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. What is the strongest technical basis?
- Portable pipelines should separate code logic from environment-specific configuration.
- Retryable transient failures should be distinguished from permanent data or permission errors.
- A recoverable pipeline should produce the same logical state after an equivalent retry.
- Task-level repair reduces unnecessary recomputation while preserving dependency correctness.
Explanation
Correct Answer
B:The decisive mechanism is: Retryable transient failures should be distinguished from permanent data or permission errors. That explains the selected action: Add bounded retries with exponential backoff and observable failure after the retry budget. In the original scenario: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. The specific unmanaged risk is: Immediate permanent failure on a brief service outage can miss a delivery SLA. Validate with: An injected transient 503 recovers within the retry budget while repeated failures produce actionable alerts.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A multi-team notebook uses hard-coded workspace names and credentials, making the same pipeline fail in staging. Its targeted response is: Parameterize environment-specific paths, catalogs and identities through governed deployment configuration. The current case is governed more directly by: Retryable transient failures should be distinguished from permanent data or permission errors.
C:This principle concerns a separate data-engineering condition: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. Its targeted response is: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. The current case is governed more directly by: Retryable transient failures should be distinguished from permanent data or permission errors.
D:This principle concerns a separate data-engineering condition: A bulk repair executes all pipeline tasks again even when only the final reporting notebook failed. Its targeted response is: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid. The current case is governed more directly by: Retryable transient failures should be distinguished from permanent data or permission errors.
Question 854
The design team proposes: Design a separate failure-handling or completion branch with the supported run-if logic for alerts and cleanup. The situation is: A source task fails yet the monitoring task never executes because all downstream tasks require upstream success. Which technical principle justifies the decision?
- Retryable transient failures should be distinguished from permanent data or permission errors.
- A correct pipeline graph enables safe execution order and impact analysis.
- Quality gates must precede trusted publication, not merely log errors afterwards.
- Orchestration may need error paths that execute regardless of normal success dependencies.
Explanation
Correct Answer
D:The decisive mechanism is: Orchestration may need error paths that execute regardless of normal success dependencies. That explains the selected action: Design a separate failure-handling or completion branch with the supported run-if logic for alerts and cleanup. In the original scenario: A source task fails yet the monitoring task never executes because all downstream tasks require upstream success. The specific unmanaged risk is: An upstream failure can remain invisible and leave temporary resources without cleanup. Validate with: A staged failure triggers the documented alert and cleanup while skipping dependent publication.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. Its targeted response is: Add bounded retries with exponential backoff and observable failure after the retry budget. The current case is governed more directly by: Orchestration may need error paths that execute regardless of normal success dependencies.
B:This principle concerns a separate data-engineering condition: A declarative pipeline transforms several datasets but its source names are ambiguous and a data team cannot reconstruct dependencies. Its targeted response is: Declare consistent table names and dependencies and validate the generated pipeline graph. The current case is governed more directly by: Orchestration may need error paths that execute regardless of normal success dependencies.
C:This principle concerns a separate data-engineering condition: A workflow writes to production tables before a validation task examines null keys and duplicates. Its targeted response is: Place validations before publishing and use an atomic cutover or controlled target write. The current case is governed more directly by: Orchestration may need error paths that execute regardless of normal success dependencies.
Question 855
A Databricks engineer recommends: Normalize time zone semantics before extracting business-local reporting dates. It responds to: A date field mixes UTC timestamps and local store times but a pipeline groups all values by the raw date string. What underlying mechanism BEST explains why?
- Time zone conversion and calendar boundary choice affect the grouping of events.
- Union operations concatenate rows and require aligned column meanings.
- Append is generally simpler for immutable events than key-by-key mutation logic.
- Set difference helps identify migration gaps without retrieving matched records.
Explanation
Correct Answer
A:The decisive mechanism is: Time zone conversion and calendar boundary choice affect the grouping of events. That explains the selected action: Normalize time zone semantics before extracting business-local reporting dates. In the original scenario: A date field mixes UTC timestamps and local store times but a pipeline groups all values by the raw date string. The specific unmanaged risk is: Orders near midnight may be reported under the wrong business day. Validate with: Known events around midnight map to the intended store-local date and correct UTC instant.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. Its targeted response is: Align compatible schemas and use name-based union semantics with explicit type checks. The current case is governed more directly by: Time zone conversion and calendar boundary choice affect the grouping of events.
C:This principle concerns a separate data-engineering condition: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. Its targeted response is: Use an incremental append pattern with suitable deduplication when source events cannot change. The current case is governed more directly by: Time zone conversion and calendar boundary choice affect the grouping of events.
D:This principle concerns a separate data-engineering condition: An analyst must find records present in the source system but absent in a target migration. Its targeted response is: Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics. The current case is governed more directly by: Time zone conversion and calendar boundary choice affect the grouping of events.
Question 856
An implementation skips: Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance. Engineers are observing: A lineage graph shows no relationship for data loaded outside the monitored platform and the team assumes the dataset has no upstream dependency. What consequence is MOST likely?
- Long-lived shared storage credentials may expose unrelated files or survive contract termination.
- Consumers can use incorrectly labeled confidential fields without recognizing their sensitivity.
- Uncaptured external ingestion may lead to incomplete impact analysis and unsafe upstream changes.
- Old cleanup tasks can destroy files that the revised retention requirement still protects.
Explanation
Correct Answer
C:The direct residual exposure is: Uncaptured external ingestion may lead to incomplete impact analysis and unsafe upstream changes. The triggering condition is: A lineage graph shows no relationship for data loaded outside the monitored platform and the team assumes the dataset has no upstream dependency. The omitted safeguard is: Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance. This matters because: Automatic lineage visibility has collection boundaries and does not imply every real-world dependency is recorded. A corrective test would show: A provenance review identifies both captured Databricks edges and documented external system dependencies.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A data-sharing project emails storage keys to an external partner for reading curated Delta results. Its preventative action would be: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. The most direct exposure in the current scenario is: Uncaptured external ingestion may lead to incomplete impact analysis and unsafe upstream changes.
B:This failure mode belongs mainly to another situation: A central repository contains schemas with missing column owners and no sensitivity classifications. Its preventative action would be: Implement a catalog stewardship process to review metadata and governed tags at dataset publication. The most direct exposure in the current scenario is: Uncaptured external ingestion may lead to incomplete impact analysis and unsafe upstream changes.
D:This failure mode belongs mainly to another situation: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. Its preventative action would be: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. The most direct exposure in the current scenario is: Uncaptured external ingestion may lead to incomplete impact analysis and unsafe upstream changes.
Question 857
A Databricks engineer recommends: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality. It responds to: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. What underlying mechanism BEST explains why?
- CTAS populates a table at execution time and does not imply continuous synchronization with source.
- Layered lakehouse processing separates source fidelity from approved business transformations.
- Data models balance redundancy and query simplicity according to workload requirements.
- High-cardinality partition columns can fragment file layout and increase metadata overhead.
Explanation
Correct Answer
D:The decisive mechanism is: High-cardinality partition columns can fragment file layout and increase metadata overhead. That explains the selected action: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality. In the original scenario: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. The specific unmanaged risk is: Excessive partitions create small files and poor query planning without useful pruning. Validate with: File-count and query-profile comparisons show fewer fragments and faster targeted scans.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A pipeline uses CREATE TABLE AS SELECT for a one-time derived dataset but later assumes the result refreshes automatically. Its targeted response is: Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh. The current case is governed more directly by: High-cardinality partition columns can fragment file layout and increase metadata overhead.
B: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: High-cardinality partition columns can fragment file layout and increase metadata overhead.
C:This principle concerns a separate data-engineering condition: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. Its targeted response is: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. The current case is governed more directly by: High-cardinality partition columns can fragment file layout and increase metadata overhead.
Question 858
A production data platform experiences this condition: A team copies Databricks notebooks manually between three workspaces and each uses different hardcoded identifiers. Which targeted measure should be selected?
- Resolve Git merge conflicts with tests and reviewed integration before merging the release branch.
- Include performance and end-to-end tests using representative scale and data distributions.
- Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging.
- Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI.
Explanation
Correct Answer
D:The most appropriate action is: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI. It addresses the stated condition: A team copies Databricks notebooks manually between three workspaces and each uses different hardcoded identifiers. The technical basis is: Declarative bundle definitions can make job and pipeline deployments repeatable across environments. Without this control, manual workspace copying can omit task settings and point production at development tables. A direct acceptance check is: A staging and production deployment use one versioned definition but distinct approved parameters.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: Two engineers change the same ingestion function on separate branches and one silently overwrites the other's fix. The corresponding measure there would be: Resolve Git merge conflicts with tests and reviewed integration before merging the release branch. The stated situation instead calls for: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI.
B:This alternative primarily addresses a different Azure Databricks problem: An engineering test suite passes on miniature in-memory data yet fails in production on skewed billion-row joins. The corresponding measure there would be: Include performance and end-to-end tests using representative scale and data distributions. The stated situation instead calls for: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI.
C:This alternative primarily addresses a different Azure Databricks problem: A new pipeline passes unit tests but production fails because the service principal lacks a catalog grant. The corresponding measure there would be: Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging. The stated situation instead calls for: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI.
Question 859
For this Azure Databricks issue: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. Engineers choose: Apply type, nullability and range expectations before promoting bronze rows into the silver target. What acceptance evidence is BEST?
- A simulated type change is rejected or rescued with an actionable alert and no corrupted curated output.
- Injected critical and noncritical bad rows follow their respective approved actions and emit metrics.
- A sample of valid UTC timestamps passes and known ambiguous strings produce the expected exception record.
- A controlled malformed amount is detected and excluded from published silver while legitimate zero values remain.
Explanation
Correct Answer
D:The strongest acceptance proof is: A controlled malformed amount is detected and excluded from published silver while legitimate zero values remain. It specifically verifies: Apply type, nullability and range expectations before promoting bronze rows into the silver target. The original issue was: A product data contract requires every transaction amount to use nonnegative decimal values but new raw files include quoted text strings. The underlying mechanism is: Layered quality gates prevent malformed source values from contaminating trusted downstream tables. Without it, invalid amounts may silently convert to null and skew revenue aggregates.
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: A controlled malformed amount is detected and excluded from published silver while legitimate zero values remain.
B:This result would validate a different measure: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity. That is relevant to the distinct problem: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. Here the acceptance criterion is: A controlled malformed amount is detected and excluded from published silver while legitimate zero values remain.
C: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: A controlled malformed amount is detected and excluded from published silver while legitimate zero values remain.
Question 860
An implementation skips: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. Engineers are observing: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. What consequence is MOST likely?
- An environment-default schema can route production data definitions into an incorrect catalog.
- An unreviewed semantic instruction can return a plausible but incorrect business measure.
- Assuming full DDL or mutation support may cause failed deployments or inadvertent source changes.
- Users may query raw unvalidated records as though they were approved curated metrics.
Explanation
Correct Answer
C:The direct residual exposure is: Assuming full DDL or mutation support may cause failed deployments or inadvertent source changes. The triggering condition is: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. The omitted safeguard is: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. This matters because: Foreign catalog semantics and connector capabilities differ from native managed Delta table operations. A corrective test would show: A capability test documents supported query and write operations and prevents unsupported mutations.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. Its preventative action would be: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks. The most direct exposure in the current scenario is: Assuming full DDL or mutation support may cause failed deployments or inadvertent source changes.
B:This failure mode belongs mainly to another situation: An AI/BI Genie space is configured with ambiguous metric terminology and produces misleading natural-language interpretations. Its preventative action would be: Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics. The most direct exposure in the current scenario is: Assuming full DDL or mutation support may cause failed deployments or inadvertent source changes.
D: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: Assuming full DDL or mutation support may cause failed deployments or inadvertent source changes.