Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 24
Question 230
The team implements: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention. The original problem is: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. Which test MOST convincingly demonstrates correctness?
- Post-mitigation stage durations are balanced and joined row counts remain correct.
- Spark storage metrics show released cache and unchanged correctness with improved total runtime.
- A selective query reads fewer files and meets latency targets after a controlled layout improvement.
- A simulated failure leaves accessible run logs and correlation identifiers in the approved monitoring destination.
Explanation
Correct Answer
D:The strongest acceptance proof is: A simulated failure leaves accessible run logs and correlation identifiers in the approved monitoring destination. It specifically verifies: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention. The original issue was: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. The underlying mechanism is: Centralized telemetry supports durable troubleshooting when ephemeral compute terminates. Without it, A failed cluster can disappear before operators gather evidence of its root cause.
Incorrect Answers
A:This result would validate a different measure: Use query-profile evidence and a supported skew mitigation such as adaptive execution or key-aware repartitioning. That is relevant to the distinct problem: A DataFrame join spills heavily because a single join key occurs in most rows. Here the acceptance criterion is: A simulated failure leaves accessible run logs and correlation identifiers in the approved monitoring destination.
B:This result would validate a different measure: Use caching only for beneficial reuse and release persisted state when no longer needed. That is relevant to the distinct problem: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. Here the acceptance criterion is: A simulated failure leaves accessible run logs and correlation identifiers in the approved monitoring destination.
C:This result would validate a different measure: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again. That is relevant to the distinct problem: A warehouse query remains slow even after larger compute is allocated and the profile reports scanning nearly every file. Here the acceptance criterion is: A simulated failure leaves accessible run logs and correlation identifiers in the approved monitoring destination.
Question 231
A production data team leaves out: Use Unity Catalog volumes with suitable schema and file privileges for supported non-tabular files. Its scenario is: A departmental data owner stores raw file attachments inside ad hoc DBFS directories instead of a governable data space. Which failure mode is MOST relevant?
- An environment-default schema can route production data definitions into an incorrect catalog.
- An ownerless shared view may expose unreviewed columns or become impossible to maintain safely.
- Users may query raw unvalidated records as though they were approved curated metrics.
- Unregistered working files can bypass object discovery and authorization reviews.
Explanation
Correct Answer
D:The direct residual exposure is: Unregistered working files can bypass object discovery and authorization reviews. The triggering condition is: A departmental data owner stores raw file attachments inside ad hoc DBFS directories instead of a governable data space. The omitted safeguard is: Use Unity Catalog volumes with suitable schema and file privileges for supported non-tabular files. This matters because: Volumes bring file-based assets into a governed catalog namespace distinct from SQL table records. A corrective test would show: Authorized principals list and read a governed volume path while unrelated roles receive denied access.
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: Unregistered working files can bypass object discovery and authorization reviews.
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: Unregistered working files can bypass object discovery and authorization reviews.
C: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: Unregistered working files can bypass object discovery and authorization reviews.
Question 232
A data engineering team faces this Azure Databricks requirement: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. Which action is MOST appropriate?
- Replace committed personal credentials with supported workload authentication and revoke exposed tokens.
- Review and revoke stale grants and any linked service credentials, preserving required internal ownership.
- Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension.
- Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path.
Explanation
Correct Answer
D:The most appropriate action is: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. It addresses the stated condition: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. The technical basis is: Managed identity authentication avoids exposing reusable static secrets and ties authorization to a governed identity. Without this control, A copied notebook may leak storage access keys beyond the intended data-processing environment. A direct acceptance check is: The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A production workload uses a personal access token stored in Git for Databricks REST calls. The corresponding measure there would be: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. The stated situation instead calls for: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path.
B: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: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path.
C:This alternative primarily addresses a different Azure Databricks problem: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. The corresponding measure there would be: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. The stated situation instead calls for: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path.
Question 233
For this Microsoft DP-750 case: A workflow writes to production tables before a validation task examines null keys and duplicates. Which design or operational response BEST fits?
- Propagate nonrecoverable exceptions to Lakeflow Jobs and attach actionable error metadata.
- Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph.
- Place validations before publishing and use an atomic cutover or controlled target write.
- Design a compatible atomic publication or versioned readiness contract so consumers see consistent results.
Explanation
Correct Answer
C:The most appropriate action is: Place validations before publishing and use an atomic cutover or controlled target write. It addresses the stated condition: A workflow writes to production tables before a validation task examines null keys and duplicates. The technical basis is: Quality gates must precede trusted publication, not merely log errors afterwards. Without this control, consumers can query invalid data during the interval before quality checks finish. A direct acceptance check is: Invalid input blocks publication while the previous approved dataset remains available.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A workflow uses a notebook task that catches exceptions and returns success even when a write step fails. The corresponding measure there would be: Propagate nonrecoverable exceptions to Lakeflow Jobs and attach actionable error metadata. The stated situation instead calls for: Place validations before publishing and use an atomic cutover or controlled target write.
B:This alternative primarily addresses a different Azure Databricks problem: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. The corresponding measure there would be: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. The stated situation instead calls for: Place validations before publishing and use an atomic cutover or controlled target write.
D:This alternative primarily addresses a different Azure Databricks problem: A regulated pipeline needs consistent transaction boundaries across multiple table writes but updates are published one at a time. The corresponding measure there would be: Design a compatible atomic publication or versioned readiness contract so consumers see consistent results. The stated situation instead calls for: Place validations before publishing and use an atomic cutover or controlled target write.
Question 234
A data product owner adopts: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. The reason is: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. What observed result BEST proves effectiveness?
- A quiet-period rehearsal retains the required streaming operation and subsequent events process without missed offsets.
- A controlled instance-family comparison achieves the same results with improved stage time and total execution cost.
- A representative run measures total cost and elapsed time, including initialization, and meets the freshness budget.
- Before-after measurements report comparable inputs, stage timings, spills and total cost.
Explanation
Correct Answer
A:The strongest acceptance proof is: A quiet-period rehearsal retains the required streaming operation and subsequent events process without missed offsets. It specifically verifies: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. The original issue was: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. The underlying mechanism is: Auto-termination choices must reflect continuously running streams differently from one-shot notebooks. Without it, A stream may stop unexpectedly and leave event consumption behind its permitted freshness objective.
Incorrect Answers
B:This result would validate a different measure: Choose node families and driver/worker sizes using CPU, memory, shuffle and workload profile evidence. That is relevant to the distinct problem: A new job uses a large memory-optimized node merely because its source data is large, although profiling shows compute-bound transforms. Here the acceptance criterion is: A quiet-period rehearsal retains the required streaming operation and subsequent events process without missed offsets.
C:This result would validate a different measure: Separate the small validation into an eligible lightweight or serverless task and measure total end-to-end runtime. That is relevant to the distinct problem: A data team uses a high-power job cluster for a low-volume data-quality check that spends most runtime starting the cluster. Here the acceptance criterion is: A quiet-period rehearsal retains the required streaming operation and subsequent events process without missed offsets.
D:This result would validate a different measure: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data. That is relevant to the distinct problem: A team turns on every performance setting for a workload without benchmarking whether disk spills or network shuffle dominate runtime. Here the acceptance criterion is: A quiet-period rehearsal retains the required streaming operation and subsequent events process without missed offsets.
Question 235
A pipeline owner declines the action: Recreate or update supported external table registration using an approved location and correct access controls. The business situation is: A managed Delta table is migrated to external storage but the team does not update table registration or grant scopes. What specific failure can follow?
- An unreviewed semantic instruction can return a plausible but incorrect business measure.
- Data may remain readable by direct path while the intended catalog table fails authorization.
- An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts.
- Poorly described fields lead to incorrect joins, unit conversions or disclosure decisions.
Explanation
Correct Answer
B:The direct residual exposure is: Data may remain readable by direct path while the intended catalog table fails authorization. The triggering condition is: A managed Delta table is migrated to external storage but the team does not update table registration or grant scopes. The omitted safeguard is: Recreate or update supported external table registration using an approved location and correct access controls. This matters because: Metadata definitions, locations and privileges must align after a table lifecycle transition. A corrective test would show: Catalog lookup and controlled read work from the registered target while unapproved principals cannot bypass it.
Incorrect Answers
A: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: Data may remain readable by direct path while the intended catalog table fails authorization.
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: Data may remain readable by direct path while the intended catalog table fails authorization.
D:This failure mode belongs mainly to another situation: Analysts create tables without column comments and the data steward cannot explain monetary units or null semantics. Its preventative action would be: Maintain table and column descriptions in Unity Catalog metadata at creation and during schema changes. The most direct exposure in the current scenario is: Data may remain readable by direct path while the intended catalog table fails authorization.
Question 236
The recommended measure is: Grant precise container-use and object-creation privileges based on actual job roles. The operational context is: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. Which data engineering concept applies?
- External table metadata can be governed even when the underlying object files remain in external storage.
- Reading a governed object does not imply permission to create or administer peer objects.
- Volumes bring file-based assets into a governed catalog namespace distinct from SQL table records.
- Governance of views includes ownership, discovery and authorization just as for tables.
Explanation
Correct Answer
B:The decisive mechanism is: Reading a governed object does not imply permission to create or administer peer objects. That explains the selected action: Grant precise container-use and object-creation privileges based on actual job roles. In the original scenario: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. The specific unmanaged risk is: Overbroad catalog privileges can let ordinary readers create misleading or unauthorized data products. Validate with: An analyst can query approved tables but cannot create a schema without a separate grant.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A legacy external Delta table points at a cloud location with an unmanaged storage credential stored in notebook text. Its targeted response is: Register supported external locations and storage credentials, then define governed external tables. The current case is governed more directly by: Reading a governed object does not imply permission to create or administer peer objects.
C:This principle concerns a separate data-engineering condition: A departmental data owner stores raw file attachments inside ad hoc DBFS directories instead of a governable data space. Its targeted response is: Use Unity Catalog volumes with suitable schema and file privileges for supported non-tabular files. The current case is governed more directly by: Reading a governed object does not imply permission to create or administer peer objects.
D:This principle concerns a separate data-engineering condition: A central team creates global views that hide source objects but forgets to document ownership and access grants. Its targeted response is: Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema. The current case is governed more directly by: Reading a governed object does not imply permission to create or administer peer objects.
Question 237
A data product owner adopts: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. The reason is: A lakehouse receives sensor observations with event timestamps that arrive out of order. What observed result BEST proves effectiveness?
- A supported optimization command completes and query plans show the chosen layout works.
- A controlled late event appears in the correct historical period according to the approved policy.
- A source update changes the target only through the planned refresh mechanism and produces a recorded watermark.
- A backdated invoice joins to the address valid on its transaction date while the current record shows the latest address.
Explanation
Correct Answer
B:The strongest acceptance proof is: A controlled late event appears in the correct historical period according to the approved policy. It specifically verifies: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. The original issue was: A lakehouse receives sensor observations with event timestamps that arrive out of order. The underlying mechanism is: Event time and processing time represent different facts and affect historical interpretation. Without it, treating arrival order as occurrence order may miscalculate event windows and temporal joins.
Incorrect Answers
A:This result would validate a different measure: Choose one compatible data layout strategy based on table format, platform support and query evidence. That is relevant to the distinct problem: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. Here the acceptance criterion is: A controlled late event appears in the correct historical period according to the approved policy.
C:This result would validate a different measure: Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh. That is relevant to the distinct problem: A pipeline uses CREATE TABLE AS SELECT for a one-time derived dataset but later assumes the result refreshes automatically. Here the acceptance criterion is: A controlled late event appears in the correct historical period according to the approved policy.
D:This result would validate a different measure: Model a slowly changing dimension Type 2 with effective dates, current flags and correctly managed surrogate keys. That is relevant to the distinct problem: A retail customer table changes delivery address repeatedly but analysts must reconstruct the address known at any prior invoice date. Here the acceptance criterion is: A controlled late event appears in the correct historical period according to the approved policy.
Question 238
A platform architect adopts: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. For this requirement: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. Which rationale MOST directly supports it?
- Concurrency management prevents competing executions from corrupting shared mutable state.
- Timeouts and incident routing bound the cost and impact of stalled workflow execution.
- Repair runs and per-task retries address different recovery granularities.
- Retries cannot repair missing tables or invalid schema references without corrective action.
Explanation
Correct Answer
C:The decisive mechanism is: Repair runs and per-task retries address different recovery granularities. That explains the selected action: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. In the original scenario: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. The specific unmanaged risk is: Replaying an entire DAG without need can duplicate side effects and increase cost. Validate with: A failed downstream task is repaired without repeating successful non-idempotent upstream work.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A daily data job runs twice during an incident and both executions write to the same target. Its targeted response is: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap. The current case is governed more directly by: Repair runs and per-task retries address different recovery granularities.
B:This principle concerns a separate data-engineering condition: A long-running job occasionally hangs but there is no configured runtime ceiling or escalation. Its targeted response is: Set task and job timeout limits with notifications and a documented retry and recovery route. The current case is governed more directly by: Repair runs and per-task retries address different recovery granularities.
D:This principle concerns a separate data-engineering condition: A job's retry policy restarts a deterministic bad SQL query six times even though the table is missing. Its targeted response is: Limit retries to appropriate transient errors and set accountable failure handling for permanent logic problems. The current case is governed more directly by: Repair runs and per-task retries address different recovery granularities.
Question 239
A data engineering team faces this Azure Databricks requirement: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. Which action is MOST appropriate?
- Choose one compatible data layout strategy based on table format, platform support and query evidence.
- Reevaluate data layout using representative event-time filters and a suitable clustering key.
- Use an external Unity Catalog table with an approved registered location instead of assuming managed storage ownership.
- Design a conformed star schema with explicit fact grain and unique dimension keys.
Explanation
Correct Answer
B:The most appropriate action is: Reevaluate data layout using representative event-time filters and a suitable clustering key. It addresses the stated condition: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. The technical basis is: Physical layout should match selective consumer predicates rather than convenience of ingestion. Without this control, A mismatched partition scheme forces broad scans across unrelated arrival-day files. A direct acceptance check is: The top event-time queries show improved data skipping and reconciled row counts.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. The corresponding measure there would be: Choose one compatible data layout strategy based on table format, platform support and query evidence. The stated situation instead calls for: Reevaluate data layout using representative event-time filters and a suitable clustering key.
C:This alternative primarily addresses a different Azure Databricks problem: A dataset has a strict requirement that Azure storage ownership and lifecycle remain under a separate platform team. The corresponding measure there would be: Use an external Unity Catalog table with an approved registered location instead of assuming managed storage ownership. The stated situation instead calls for: Reevaluate data layout using representative event-time filters and a suitable clustering key.
D:This alternative primarily addresses a different Azure Databricks problem: A finance dashboard needs monthly revenue by customer and must join customer dimensions without multiplying facts. The corresponding measure there would be: Design a conformed star schema with explicit fact grain and unique dimension keys. The stated situation instead calls for: Reevaluate data layout using representative event-time filters and a suitable clustering key.
Question 240
A team omits the recommended measure: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. Its environment shows: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. What is the MOST direct residual risk?
- Skew and memory limits may remain invisible until a full-scale run misses its SLA.
- A faulty last-minute edit can create an untested release with no accountable reviewer.
- Duplicate jobs may run on the same schedule and load data twice.
- Manual post-deployment edits can bypass review and silently change retry or security settings.
Explanation
Correct Answer
D:The direct residual exposure is: Manual post-deployment edits can bypass review and silently change retry or security settings. The triggering condition is: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. The omitted safeguard is: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. This matters because: Source control only provides operational truth when actual resource settings match the approved definition. A corrective test would show: A test UI change is flagged and the approved deployment restores the intended configuration.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An engineering test suite passes on miniature in-memory data yet fails in production on skewed billion-row joins. Its preventative action would be: Include performance and end-to-end tests using representative scale and data distributions. The most direct exposure in the current scenario is: Manual post-deployment edits can bypass review and silently change retry or security settings.
B:This failure mode belongs mainly to another situation: A release process merges unreviewed notebook changes directly into the main branch minutes before a production run. Its preventative action would be: Protect the main branch with peer review, required tests and controlled promotion windows. The most direct exposure in the current scenario is: Manual post-deployment edits can bypass review and silently change retry or security settings.
C: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: Manual post-deployment edits can bypass review and silently change retry or security settings.