Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 63
Question 620
The following control has NOT been implemented: Include an integration test using actual Delta table semantics and representative source changes. In this case: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. Which exposure remains?
- The same Git commit may run differently after a dependency's incompatible update.
- Unverified MERGE conditions can overwrite valid history despite passing mocked unit tests.
- Manual post-deployment edits can bypass review and silently change retry or security settings.
- Duplicate jobs may run on the same schedule and load data twice.
Explanation
Correct Answer
B:The direct residual exposure is: Unverified MERGE conditions can overwrite valid history despite passing mocked unit tests. The triggering condition is: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. The omitted safeguard is: Include an integration test using actual Delta table semantics and representative source changes. This matters because: Storage-layer transaction behavior must be tested in addition to pure function outputs. A corrective test would show: An integration fixture with historical updates yields exactly the intended target versions.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A team cannot reproduce a prior release because package versions are resolved dynamically during deployment. Its preventative action would be: Pin package and runtime versions in the governed release artifact and record its dependency manifest. The most direct exposure in the current scenario is: Unverified MERGE conditions can overwrite valid history despite passing mocked unit tests.
C:This failure mode belongs mainly to another situation: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. Its preventative action would be: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. The most direct exposure in the current scenario is: Unverified MERGE conditions can overwrite valid history despite passing mocked unit tests.
D:This failure mode belongs mainly to another situation: A REST deployment script creates duplicate jobs every time CI reruns after a timeout. Its preventative action would be: Use idempotent deployment methods or reconcile existing resource IDs before creating replacements. The most direct exposure in the current scenario is: Unverified MERGE conditions can overwrite valid history despite passing mocked unit tests.
Question 621
For this Azure Databricks issue: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. Engineers choose: Implement explicit null predicates rather than treating zero and null as equivalent. What acceptance evidence is BEST?
- A seeded dataset retains zero-quantity items while rows with null quantities follow the documented rule.
- Sample events match exactly one dimension version valid at their event timestamp.
- The gap report returns seeded source-only records and excludes matched records.
- Mixed-case, whitespace and non-ASCII test records resolve according to the documented mapping policy.
Explanation
Correct Answer
A:The strongest acceptance proof is: A seeded dataset retains zero-quantity items while rows with null quantities follow the documented rule. It specifically verifies: Implement explicit null predicates rather than treating zero and null as equivalent. The original issue was: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. The underlying mechanism is: SQL NULL indicates absent or unknown values while numeric zero is a valid value. Without it, conflating zero with missing data hides legitimate stockouts and distorts service metrics.
Incorrect Answers
B:This result would validate a different measure: Join historical dimension rows using business key and validity interval at event time. That is relevant to the distinct problem: A clickstream fact table is joined to a customer table with multiple status versions but no effective-date condition. Here the acceptance criterion is: A seeded dataset retains zero-quantity items while rows with null quantities follow the documented rule.
C:This result would validate a different measure: Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics. That is relevant to the distinct problem: An analyst must find records present in the source system but absent in a target migration. Here the acceptance criterion is: A seeded dataset retains zero-quantity items while rows with null quantities follow the documented rule.
D:This result would validate a different measure: Define and test consistent trimming, Unicode normalization and case comparison for the business key. That is relevant to the distinct problem: A customer-name cleansing script uses an arbitrary lowercase conversion without preserving Unicode and leading/trailing whitespace rules. Here the acceptance criterion is: A seeded dataset retains zero-quantity items while rows with null quantities follow the documented rule.
Question 622
A Databricks engineer recommends: Set appropriate auto-termination or idle controls for interactive compute while excluding workloads requiring continuous availability. It responds to: A newly created cluster remains available for hours after manual exploration even though the organization has a strict idle-cost policy. What underlying mechanism BEST explains why?
- Interactive compute should have a governed idle lifecycle distinct from persistent services.
- Production job reliability benefits from stable identities and workload-specific compute ownership.
- Auto-termination choices must reflect continuously running streams differently from one-shot notebooks.
- Photon can accelerate many supported SQL and DataFrame operations but requires workload-specific measurements.
Explanation
Correct Answer
A:The decisive mechanism is: Interactive compute should have a governed idle lifecycle distinct from persistent services. That explains the selected action: Set appropriate auto-termination or idle controls for interactive compute while excluding workloads requiring continuous availability. In the original scenario: A newly created cluster remains available for hours after manual exploration even though the organization has a strict idle-cost policy. The specific unmanaged risk is: Forgotten development clusters can consume cloud resources long after the last useful notebook cell. Validate with: An inactive test cluster terminates after the configured interval and users can restart it when authorized.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A scheduled ETL run uses shared analyst compute and fails whenever the cluster owner restarts a notebook session. Its targeted response is: Define a job-owned execution identity and eligible task compute separate from ad hoc analyst cluster lifecycle. The current case is governed more directly by: Interactive compute should have a governed idle lifecycle distinct from persistent services.
C:This principle concerns a separate data-engineering condition: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. Its targeted response is: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. The current case is governed more directly by: Interactive compute should have a governed idle lifecycle distinct from persistent services.
D:This principle concerns a separate data-engineering condition: 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. Its targeted response is: Benchmark Photon on a supported runtime with representative queries and compare cost, latency and correctness. The current case is governed more directly by: Interactive compute should have a governed idle lifecycle distinct from persistent services.
Question 623
A pipeline owner declines the action: Use a dedicated service principal with scoped Unity Catalog grants and governed credential lifecycle. The business situation is: An ETL service principal is granted permissions through a personal employee account that will leave the company. What specific failure can follow?
- A user may bypass the masked presentation by reading the unmasked source table.
- One missing tenant predicate can expose another customer’s records.
- An employee departure or password rotation can unexpectedly break critical production ingestion.
- Unnecessary modification rights can let a compromised analyst alter financial records.
Explanation
Correct Answer
C:The direct residual exposure is: An employee departure or password rotation can unexpectedly break critical production ingestion. The triggering condition is: An ETL service principal is granted permissions through a personal employee account that will leave the company. The omitted safeguard is: Use a dedicated service principal with scoped Unity Catalog grants and governed credential lifecycle. This matters because: Workload identities separate automated access from a person's employment and session lifecycle. A corrective test would show: The pipeline authenticates using the designated service principal and operates after the employee account is disabled.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. Its preventative action would be: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. The most direct exposure in the current scenario is: An employee departure or password rotation can unexpectedly break critical production ingestion.
B:This failure mode belongs mainly to another situation: A multi-tenant analytics table relies on application code to append customer_id filtering. Its preventative action would be: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. The most direct exposure in the current scenario is: An employee departure or password rotation can unexpectedly break critical production ingestion.
D:This failure mode belongs mainly to another situation: A finance analyst must read an approved table but was granted broad MODIFY rights at the schema level. Its preventative action would be: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants. The most direct exposure in the current scenario is: An employee departure or password rotation can unexpectedly break critical production ingestion.
Question 624
The recommended measure is: Place validations before publishing and use an atomic cutover or controlled target write. The operational context is: A workflow writes to production tables before a validation task examines null keys and duplicates. Which data engineering concept applies?
- Stream progress is not synonymous with completeness for a business reporting interval.
- Task-level repair reduces unnecessary recomputation while preserving dependency correctness.
- Quality gates must precede trusted publication, not merely log errors afterwards.
- Idempotent retries are suitable for transient conditions, not unchanging invalid data.
Explanation
Correct Answer
C:The decisive mechanism is: Quality gates must precede trusted publication, not merely log errors afterwards. That explains the selected action: Place validations before publishing and use an atomic cutover or controlled target write. In the original scenario: A workflow writes to production tables before a validation task examines null keys and duplicates. The specific unmanaged risk is: Consumers can query invalid data during the interval before quality checks finish. Validate with: Invalid input blocks publication while the previous approved dataset remains available.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A streaming process depends on a downstream batch closeout but no one defines whether it should wait for the latest watermark. Its targeted response is: Specify the stream watermark and an explicit closeout readiness condition before running downstream aggregation. The current case is governed more directly by: Quality gates must precede trusted publication, not merely log errors afterwards.
B: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: Quality gates must precede trusted publication, not merely log errors afterwards.
D:This principle concerns a separate data-engineering condition: A pipeline automatically retries malformed source records indefinitely and consumes its entire compute budget. Its targeted response is: Route deterministic validation failures to quarantine rather than retrying them as transient infrastructure errors. The current case is governed more directly by: Quality gates must precede trusted publication, not merely log errors afterwards.
Question 625
The following control has NOT been implemented: Register the structured dataset as an appropriate managed Delta table rather than treating the volume itself as a SQL table. In this case: A team exposes structured transaction data as files in a volume but wants SQL analytics and ACID MERGE behavior. Which exposure remains?
- Copying the whole remote source for a narrow lookup can create unnecessary latency, duplication and privacy exposure.
- An unreviewed semantic instruction can return a plausible but incorrect business measure.
- An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts.
- File-only storage may lack table-level transactional update and discoverability semantics.
Explanation
Correct Answer
D:The direct residual exposure is: File-only storage may lack table-level transactional update and discoverability semantics. The triggering condition is: A team exposes structured transaction data as files in a volume but wants SQL analytics and ACID MERGE behavior. The omitted safeguard is: Register the structured dataset as an appropriate managed Delta table rather than treating the volume itself as a SQL table. This matters because: Volumes organize files, whereas Delta tables offer tabular metadata and transactional query operations. A corrective test would show: A controlled MERGE and SQL query succeed against the governed Delta table with expected records.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. Its preventative action would be: Create an authorized connection and supported foreign catalog for the external source. The most direct exposure in the current scenario is: File-only storage may lack table-level transactional update and discoverability semantics.
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: File-only storage may lack table-level transactional update and discoverability semantics.
C: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: File-only storage may lack table-level transactional update and discoverability semantics.
Question 626
A production data team leaves out: Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics. Its scenario is: An AI/BI Genie space is configured with ambiguous metric terminology and produces misleading natural-language interpretations. Which failure mode is MOST relevant?
- Unregistered working files can bypass object discovery and authorization reviews.
- An ownerless shared view may expose unreviewed columns or become impossible to maintain safely.
- An unreviewed semantic instruction can return a plausible but incorrect business measure.
- File-only storage may lack table-level transactional update and discoverability semantics.
Explanation
Correct Answer
C:The direct residual exposure is: An unreviewed semantic instruction can return a plausible but incorrect business measure. The triggering condition is: An AI/BI Genie space is configured with ambiguous metric terminology and produces misleading natural-language interpretations. The omitted safeguard is: Add reviewed Genie instructions, table descriptions and example questions consistent with trusted catalog semantics. This matters because: Natural-language discovery needs business context and governed metadata to disambiguate metrics. A corrective test would show: A set of known business prompts yields reconciled SQL and approved metric definitions.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A departmental data owner stores raw file attachments inside ad hoc DBFS directories instead of a governable data space. Its preventative action would be: Use Unity Catalog volumes with suitable schema and file privileges for supported non-tabular files. The most direct exposure in the current scenario is: An unreviewed semantic instruction can return a plausible but incorrect business measure.
B:This failure mode belongs mainly to another situation: A central team creates global views that hide source objects but forgets to document ownership and access grants. Its preventative action would be: Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema. The most direct exposure in the current scenario is: An unreviewed semantic instruction can return a plausible but incorrect business measure.
D: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: An unreviewed semantic instruction can return a plausible but incorrect business measure.
Question 627
For this Azure Databricks issue: A central team creates global views that hide source objects but forgets to document ownership and access grants. Engineers choose: Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema. What acceptance evidence is BEST?
- Discovery tests distinguish raw from certified curated objects and owners confirm their assigned namespaces.
- An access review identifies the view steward and confirms a prohibited reader cannot query it.
- Approved regional workspaces access their catalogs while a disallowed workspace fails its access test.
- Contract tests continue to select documented columns through the published view after a staged schema change.
Explanation
Correct Answer
B:The strongest acceptance proof is: An access review identifies the view steward and confirms a prohibited reader cannot query it. It specifically verifies: Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema. The original issue was: A central team creates global views that hide source objects but forgets to document ownership and access grants. The underlying mechanism is: Governance of views includes ownership, discovery and authorization just as for tables. Without it, an ownerless shared view may expose unreviewed columns or become impossible to maintain safely.
Incorrect Answers
A:This result would validate a different measure: Define a consistent schema and naming architecture separating layers and business domains by purpose. That is relevant to the distinct problem: Multiple data products put raw, refined and curated assets into a single schema with confusing table names. Here the acceptance criterion is: An access review identifies the view steward and confirms a prohibited reader cannot query it.
C:This result would validate a different measure: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings. That is relevant to the distinct problem: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. Here the acceptance criterion is: An access review identifies the view steward and confirms a prohibited reader cannot query it.
D:This result would validate a different measure: Define a stable contract through managed views and test compatibility before changing source objects. That is relevant to the distinct problem: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. Here the acceptance criterion is: An access review identifies the view steward and confirms a prohibited reader cannot query it.
Question 628
During a lakehouse implementation review, engineers observe: An ingestion job requires a one-time backfill without changing the future daily production schedule. What is the BEST next action?
- Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger.
- Define validated job parameters and propagate them through supported task parameter bindings.
- Configure appropriate maximum concurrent runs and idempotent target writes to control overlap.
- Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant.
Explanation
Correct Answer
A:The most appropriate action is: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger. It addresses the stated condition: An ingestion job requires a one-time backfill without changing the future daily production schedule. The technical basis is: Backfills should be separated from ordinary schedules to avoid accidental duplicate processing. Without this control, temporarily editing the main schedule may skip normal deliveries or replay wrong dates. A direct acceptance check is: The historical batch completes with reconciled counts and next daily scheduled run remains unchanged.
Incorrect Answers
B: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: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger.
C:This alternative primarily addresses a different Azure Databricks problem: A daily data job runs twice during an incident and both executions write to the same target. The corresponding measure there would be: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap. The stated situation instead calls for: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger.
D:This alternative primarily addresses a different Azure Databricks problem: 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 corresponding measure there would be: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant. The stated situation instead calls for: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger.
Question 629
An Azure Databricks architect reviews the following problem: A team wants only customer IDs present in both systems but uses an inner join that multiplies repeated rows. What should the team implement FIRST?
- Apply a deterministic deduplication rule based on stable order identity and source version before aggregation.
- Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics.
- Use an appropriate intersect or semi-join operation based on set and duplicate requirements.
- Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans.
Explanation
Correct Answer
C:The most appropriate action is: Use an appropriate intersect or semi-join operation based on set and duplicate requirements. It addresses the stated condition: A team wants only customer IDs present in both systems but uses an inner join that multiplies repeated rows. The technical basis is: Set operations and joins differ in duplicate behavior and result cardinality. Without this control, an unrestricted join can multiply keys and exaggerate customer counts. A direct acceptance check is: A test with repeated IDs produces the expected unique or multiset intersection by policy.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An incoming orders table contains repeated order IDs because a vendor retransmits the same daily extract. The corresponding measure there would be: Apply a deterministic deduplication rule based on stable order identity and source version before aggregation. The stated situation instead calls for: Use an appropriate intersect or semi-join operation based on set and duplicate requirements.
B: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: Use an appropriate intersect or semi-join operation based on set and duplicate requirements.
D:This alternative primarily addresses a different Azure Databricks problem: A pipeline joins a huge fact table with a tiny dimension and a normal shuffle join creates excessive network traffic. The corresponding measure there would be: Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans. The stated situation instead calls for: Use an appropriate intersect or semi-join operation based on set and duplicate requirements.
Question 630
An Azure Databricks architect reviews the following problem: An engineering test suite passes on miniature in-memory data yet fails in production on skewed billion-row joins. What should the team implement FIRST?
- Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle.
- Store deployment source in Git with reviewed branches and pull requests before promoting changes.
- Run end-to-end contract tests for dependent readers and obtain owner approval for breaking changes.
- Include performance and end-to-end tests using representative scale and data distributions.
Explanation
Correct Answer
D:The most appropriate action is: Include performance and end-to-end tests using representative scale and data distributions. It addresses the stated condition: An engineering test suite passes on miniature in-memory data yet fails in production on skewed billion-row joins. The technical basis is: Correctness under small inputs does not establish workload performance at production cardinality. Without this control, skew and memory limits may remain invisible until a full-scale run misses its SLA. A direct acceptance check is: A load test includes known hot keys and verifies latency, spills and output totals within targets.
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: Include performance and end-to-end tests using representative scale and data distributions.
B:This alternative primarily addresses a different Azure Databricks problem: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. The corresponding measure there would be: Store deployment source in Git with reviewed branches and pull requests before promoting changes. The stated situation instead calls for: Include performance and end-to-end tests using representative scale and data distributions.
C:This alternative primarily addresses a different Azure Databricks problem: A sensitive SQL view is renamed in the release but the team does not test downstream dashboards before promotion. The corresponding measure there would be: Run end-to-end contract tests for dependent readers and obtain owner approval for breaking changes. The stated situation instead calls for: Include performance and end-to-end tests using representative scale and data distributions.