Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 60
Question 590
A team omits the recommended measure: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. Its environment shows: A company needs to review table-owner changes and permissions after organizational restructuring. What is the MOST direct residual risk?
- An identically named confidential field in a new table could be exposed.
- Accumulated historical grants may give former project teams access to unrelated data products.
- Analysts may combine incompatible metrics and deliver unreliable reports.
- Long-lived shared storage credentials may expose unrelated files or survive contract termination.
Explanation
Correct Answer
B:The direct residual exposure is: Accumulated historical grants may give former project teams access to unrelated data products. The triggering condition is: A company needs to review table-owner changes and permissions after organizational restructuring. The omitted safeguard is: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. This matters because: Object governance is ongoing and must follow organizational role and service identity changes. A corrective test would show: The recertification report identifies owners, changed grants and approved remediation evidence.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A user creates a column mask on a single table and assumes all tables with the same field name are protected. Its preventative action would be: Compare table-level masks against centrally governed ABAC coverage and identify missing assignments. The most direct exposure in the current scenario is: Accumulated historical grants may give former project teams access to unrelated data products.
C:This failure mode belongs mainly to another situation: A business glossary has table names but no indication of which field is net revenue versus gross sales. Its preventative action would be: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. The most direct exposure in the current scenario is: Accumulated historical grants may give former project teams access to unrelated data products.
D: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: Accumulated historical grants may give former project teams access to unrelated data products.
Question 591
A production data team leaves out: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention. Its scenario is: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. Which failure mode is MOST relevant?
- Overprovisioning creates higher spend when stages are not parallelizable.
- A critical SLA may depend on unrelated teams' scheduling and resource usage.
- Restarting a healthy compute resource cannot repair a denied storage credential or table grant.
- A failed cluster can disappear before operators gather evidence of its root cause.
Explanation
Correct Answer
D:The direct residual exposure is: A failed cluster can disappear before operators gather evidence of its root cause. The triggering condition is: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. The omitted safeguard is: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention. This matters because: Centralized telemetry supports durable troubleshooting when ephemeral compute terminates. A corrective test would show: A simulated failure leaves accessible run logs and correlation identifiers in the approved monitoring destination.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A pipeline experiences escalating costs after a team increases node counts but execution duration barely changes. Its preventative action would be: Use run-level compute utilization, cost and stage metrics to identify unused capacity. The most direct exposure in the current scenario is: A failed cluster can disappear before operators gather evidence of its root cause.
B:This failure mode belongs mainly to another situation: A production notebook intermittently times out only when many other jobs share the same classic cluster. Its preventative action would be: Compare workload contention and resource reservations, then isolate or resize the critical job compute. The most direct exposure in the current scenario is: A failed cluster can disappear before operators gather evidence of its root cause.
C:This failure mode belongs mainly to another situation: An operations team sees Dataflow-like ingestion failures but cannot identify whether the problem is a Unity Catalog grant or a Spark stage. Its preventative action would be: Correlate error messages, job run IDs, catalog authorization logs and Spark execution evidence before remediation. The most direct exposure in the current scenario is: A failed cluster can disappear before operators gather evidence of its root cause.
Question 592
During a lakehouse implementation review, engineers observe: A managed identity can read a storage container but a newly created external table is denied in Databricks. What is the BEST next action?
- Review and revoke stale grants and any linked service credentials, preserving required internal ownership.
- Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges.
- Configure a tested Unity Catalog row filter or suitable ABAC policy based on the authorized identity.
- Replace broad grants with documented minimum creation and use privileges in a dedicated schema.
Explanation
Correct Answer
B:The most appropriate action is: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges. It addresses the stated condition: A managed identity can read a storage container but a newly created external table is denied in Databricks. The technical basis is: Cloud IAM and Unity Catalog are complementary authorization layers that must both permit the intended operation. Without this control, fixing only Azure IAM may leave catalog object access denied while broad grants increase risk. A direct acceptance check is: A storage access test and catalog grant review both pass for the designated service principal.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A vendor's service principal was granted global access for a one-month integration and the project ended. The corresponding measure there would be: Review and revoke stale grants and any linked service credentials, preserving required internal ownership. The stated situation instead calls for: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges.
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: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges.
D: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: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges.
Question 593
The team implements: Validate API status and returned resource identifiers, then use bounded retries only for transient failures. The original problem is: An automation job uses Databricks REST APIs but omits response-code checks and assumes every HTTP request succeeded. Which test MOST convincingly demonstrates correctness?
- A production run references an approved immutable commit and a prior version can be restored.
- An integration fixture with historical updates yields exactly the intended target versions.
- An injected API rejection makes CI fail with a traceable error and leaves production unchanged.
- A product owner signs off a sample report and its reconciled acceptance criteria before rollout.
Explanation
Correct Answer
C:The strongest acceptance proof is: An injected API rejection makes CI fail with a traceable error and leaves production unchanged. It specifically verifies: Validate API status and returned resource identifiers, then use bounded retries only for transient failures. The original issue was: An automation job uses Databricks REST APIs but omits response-code checks and assumes every HTTP request succeeded. The underlying mechanism is: Deployment APIs can reject requests even when the calling script continues to run. Without it, A failed job update can be silently treated as a successful release.
Incorrect Answers
A:This result would validate a different measure: Store deployment source in Git with reviewed branches and pull requests before promoting changes. That is relevant to the distinct problem: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. Here the acceptance criterion is: An injected API rejection makes CI fail with a traceable error and leaves production unchanged.
B:This result would validate a different measure: Include an integration test using actual Delta table semantics and representative source changes. That is relevant to the distinct problem: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. Here the acceptance criterion is: An injected API rejection makes CI fail with a traceable error and leaves production unchanged.
D:This result would validate a different measure: Add user acceptance tests for the relevant reporting contract before production promotion. That is relevant to the distinct problem: A developer changes a transformation with a user-visible business effect but omits acceptance testing by the data product owner. Here the acceptance criterion is: An injected API rejection makes CI fail with a traceable error and leaves production unchanged.
Question 594
An Azure Databricks architect reviews the following problem: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. What should the team implement FIRST?
- Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies.
- Define validated job parameters and propagate them through supported task parameter bindings.
- Configure bounded restarts and alerting with root-cause investigation for repeated failures.
- Set task and job timeout limits with notifications and a documented retry and recovery route.
Explanation
Correct Answer
A:The most appropriate action is: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. It addresses the stated condition: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. The technical basis is: Repair runs and per-task retries address different recovery granularities. Without this control, replaying an entire DAG without need can duplicate side effects and increase cost. A direct acceptance check is: A failed downstream task is repaired without repeating successful non-idempotent upstream work.
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: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies.
C:This alternative primarily addresses a different Azure Databricks problem: A continuously running pipeline is scheduled to restart automatically but restart storms consume a growing compute budget. The corresponding measure there would be: Configure bounded restarts and alerting with root-cause investigation for repeated failures. The stated situation instead calls for: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies.
D:This alternative primarily addresses a different Azure Databricks problem: A long-running job occasionally hangs but there is no configured runtime ceiling or escalation. The corresponding measure there would be: Set task and job timeout limits with notifications and a documented retry and recovery route. The stated situation instead calls for: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies.
Question 595
A platform architect adopts: Use caching only for beneficial reuse and release persisted state when no longer needed. For this requirement: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. Which rationale MOST directly supports it?
- Maintenance operations themselves consume compute and should correspond to data growth and read patterns.
- Full scans caused by poor layout require data organization or predicate changes rather than only more compute.
- Caching trades execution time for memory and may increase pressure when datasets are not reused.
- Scheduling cannot guarantee freshness when actual execution exceeds the interval.
Explanation
Correct Answer
C:The decisive mechanism is: Caching trades execution time for memory and may increase pressure when datasets are not reused. That explains the selected action: Use caching only for beneficial reuse and release persisted state when no longer needed. In the original scenario: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. The specific unmanaged risk is: Unused cached data can cause eviction, spilling and unexpected failures for later stages. Validate with: Spark storage metrics show released cache and unchanged correctness with improved total runtime.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A new Delta table maintenance job combines repeated OPTIMIZE and VACUUM at every microbatch even though changes are tiny. Its targeted response is: Set a measured maintenance cadence or evaluate supported predictive optimization for eligible managed tables. The current case is governed more directly by: Caching trades execution time for memory and may increase pressure when datasets are not reused.
B:This principle concerns a separate data-engineering condition: A warehouse query remains slow even after larger compute is allocated and the profile reports scanning nearly every file. Its targeted response is: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again. The current case is governed more directly by: Caching trades execution time for memory and may increase pressure when datasets are not reused.
D:This principle concerns a separate data-engineering condition: A job scheduled each hour starts running for 80 minutes and overlaps the next run. Its targeted response is: Investigate stage runtime growth and enforce appropriate concurrency policy before raising frequency. The current case is governed more directly by: Caching trades execution time for memory and may increase pressure when datasets are not reused.
Question 596
The design team proposes: Use run-level compute utilization, cost and stage metrics to identify unused capacity. The situation is: A pipeline experiences escalating costs after a team increases node counts but execution duration barely changes. Which technical principle justifies the decision?
- Alert quality depends on actionable thresholds and distinguishing transient variation from sustained failure.
- Wide aggregations redistribute data and can create memory-intensive hot partitions.
- Cost optimization requires throughput per resource rather than simply maximizing available workers.
- Severe key skew causes uneven task work even with many executors.
Explanation
Correct Answer
C:The decisive mechanism is: Cost optimization requires throughput per resource rather than simply maximizing available workers. That explains the selected action: Use run-level compute utilization, cost and stage metrics to identify unused capacity. In the original scenario: A pipeline experiences escalating costs after a team increases node counts but execution duration barely changes. The specific unmanaged risk is: Overprovisioning creates higher spend when stages are not parallelizable. Validate with: A smaller tested configuration completes within SLA at a lower measured cost.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: An alert triggers on every harmless microbatch delay while real hour-long ingestion stalls go unnoticed. Its targeted response is: Define meaningful latency, error and backlog thresholds with alert routing based on the business SLO. The current case is governed more directly by: Cost optimization requires throughput per resource rather than simply maximizing available workers.
B:This principle concerns a separate data-engineering condition: A Spark workload repeatedly fails with executor out-of-memory errors on a high-cardinality groupBy. Its targeted response is: Profile aggregation key distribution, shuffle partitions and executor memory before choosing a targeted change. The current case is governed more directly by: Cost optimization requires throughput per resource rather than simply maximizing available workers.
D:This principle concerns a separate data-engineering condition: A DataFrame join spills heavily because a single join key occurs in most rows. Its targeted response is: Use query-profile evidence and a supported skew mitigation such as adaptive execution or key-aware repartitioning. The current case is governed more directly by: Cost optimization requires throughput per resource rather than simply maximizing available workers.
Question 597
For this Microsoft DP-750 case: An analyst must find records present in the source system but absent in a target migration. Which design or operational response BEST fits?
- Use an incremental append pattern with suitable deduplication when source events cannot change.
- Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics.
- Apply a deterministic deduplication rule based on stable order identity and source version before aggregation.
- Use a compatible unpivot or stack transformation with explicit month and amount columns.
Explanation
Correct Answer
B:The most appropriate action is: Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics. It addresses the stated condition: An analyst must find records present in the source system but absent in a target migration. The technical basis is: Set difference helps identify migration gaps without retrieving matched records. Without this control, an inner join hides precisely the missing records the reconciliation needs to surface. A direct acceptance check is: The gap report returns seeded source-only records and excludes matched records.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. The corresponding measure there would be: Use an incremental append pattern with suitable deduplication when source events cannot change. The stated situation instead calls for: Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics.
C: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 a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics.
D: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: Use a left anti-join or EXCEPT operation with aligned schemas and explicit null semantics.
Question 598
A production data platform experiences this condition: A Databricks job receives daily structured extracts but an upstream schedule occasionally delivers files late. Which targeted measure should be selected?
- Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark.
- Deduplicate by stable event identity and business time using documented state and watermark rules.
- Configure supported schema evolution or rescued-data handling with explicit compatibility review.
- Use Auto Loader with durable checkpointing and an appropriate discovery mode to ingest new files incrementally.
Explanation
Correct Answer
A:The most appropriate action is: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark. It addresses the stated condition: A Databricks job receives daily structured extracts but an upstream schedule occasionally delivers files late. The technical basis is: Data pipeline completeness requires tracking arrivals rather than assuming an exact wall-clock boundary. Without this control, A fixed midnight file list can omit valid delayed uploads. A direct acceptance check is: A deliberately delayed file is ingested exactly once within the allowed arrival window.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: An ingestion pipeline reads cloud events with at-least-once delivery and assumes every event ID appears only once. The corresponding measure there would be: Deduplicate by stable event identity and business time using documented state and watermark rules. The stated situation instead calls for: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark.
C:This alternative primarily addresses a different Azure Databricks problem: A file feed introduces an unexpected optional column and the stream fails after the first changed file. The corresponding measure there would be: Configure supported schema evolution or rescued-data handling with explicit compatibility review. The stated situation instead calls for: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark.
D: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: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark.
Question 599
For this Microsoft DP-750 case: A batch integration needs a connector-managed path from a supported operational source into the lakehouse. Which design or operational response BEST fits?
- Choose a controlled CREATE OR REPLACE TABLE or compatible atomic table-replacement strategy and validate schema/permissions.
- Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model.
- Persist necessary source metadata and checkpoint lineage for troubleshooting and replay.
- Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction.
Explanation
Correct Answer
D:The most appropriate action is: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction. It addresses the stated condition: A batch integration needs a connector-managed path from a supported operational source into the lakehouse. The technical basis is: Managed ingestion connectors can simplify source synchronization when their coverage fits the source. Without this control, custom polling without checkpoint or schema handling may miss updates and require fragile maintenance. A direct acceptance check is: A test source update appears in the target with correct keys and measurable ingestion lag.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An existing table must be rebuilt from corrected historical files while its readers require a consistent atomic replacement. The corresponding measure there would be: Choose a controlled CREATE OR REPLACE TABLE or compatible atomic table-replacement strategy and validate schema/permissions. The stated situation instead calls for: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction.
B:This alternative primarily addresses a different Azure Databricks problem: A data product needs to copy a supported Azure Data Factory pipeline output into governed Databricks tables. The corresponding measure there would be: Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model. The stated situation instead calls for: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction.
C:This alternative primarily addresses a different Azure Databricks problem: A pipeline ingests Event Hubs messages into a bronze table but never captures the partition, offset or event timestamp. The corresponding measure there would be: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay. The stated situation instead calls for: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction.
Question 600
During a lakehouse implementation review, engineers observe: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. What is the BEST next action?
- Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements.
- Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation.
- Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access.
- Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery.
Explanation
Correct Answer
B:The most appropriate action is: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. It addresses the stated condition: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. The technical basis is: Data sharing scope should minimize disclosed fields and rows and specify a refresh contract. Without this control, sharing raw transaction tables can disclose protected customer attributes unnecessarily. A direct acceptance check is: A test recipient reads the expected daily aggregate and cannot enumerate underlying detailed transaction records.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. The corresponding measure there would be: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. The stated situation instead calls for: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation.
C:This alternative primarily addresses a different Azure Databricks problem: A Delta Sharing recipient must stop receiving future updates after an agreement expires. The corresponding measure there would be: Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access. The stated situation instead calls for: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation.
D:This alternative primarily addresses a different Azure Databricks problem: A business glossary has table names but no indication of which field is net revenue versus gross sales. The corresponding measure there would be: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. The stated situation instead calls for: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation.