Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 44
Question 430
For this Microsoft DP-750 case: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. Which design or operational response BEST fits?
- Create an eligible materialized view or managed derived table with appropriate refresh and access rules.
- Check federation connector capabilities and distinguish read-only remote access from supported writable local tables.
- Grant precise container-use and object-creation privileges based on actual job roles.
- Maintain table and column descriptions in Unity Catalog metadata at creation and during schema changes.
Explanation
Correct Answer
C:The most appropriate action is: Grant precise container-use and object-creation privileges based on actual job roles. It addresses the stated condition: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. The technical basis is: Reading a governed object does not imply permission to create or administer peer objects. Without this control, overbroad catalog privileges can let ordinary readers create misleading or unauthorized data products. A direct acceptance check is: An analyst can query approved tables but cannot create a schema without a separate grant.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A BI group needs to query a materialized aggregate while the source transaction Delta table changes hourly. The corresponding measure there would be: Create an eligible materialized view or managed derived table with appropriate refresh and access rules. The stated situation instead calls for: Grant precise container-use and object-creation privileges based on actual job roles.
B:This alternative primarily addresses a different Azure Databricks problem: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. The corresponding measure there would be: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. The stated situation instead calls for: Grant precise container-use and object-creation privileges based on actual job roles.
D:This alternative primarily addresses a different Azure Databricks problem: Analysts create tables without column comments and the data steward cannot explain monetary units or null semantics. The corresponding measure there would be: Maintain table and column descriptions in Unity Catalog metadata at creation and during schema changes. The stated situation instead calls for: Grant precise container-use and object-creation privileges based on actual job roles.
Question 431
A platform architect adopts: Use controlled task-level timeouts and isolate unpredictable external calls from bounded transform stages. For this requirement: A scheduled notebook contains both transformation SQL and a long-running external API loop that occasionally hangs. Which rationale MOST directly supports it?
- Orchestration may need error paths that execute regardless of normal success dependencies.
- Quality gates must precede trusted publication, not merely log errors afterwards.
- Task boundaries make duration limits and operational ownership explicit.
- Separating pipeline stages creates observable failure boundaries and supports targeted recovery.
Explanation
Correct Answer
C:The decisive mechanism is: Task boundaries make duration limits and operational ownership explicit. That explains the selected action: Use controlled task-level timeouts and isolate unpredictable external calls from bounded transform stages. In the original scenario: A scheduled notebook contains both transformation SQL and a long-running external API loop that occasionally hangs. The specific unmanaged risk is: A stalled API call can hold an entire pipeline indefinitely and consume compute. Validate with: A simulated hung request times out, alerts the owner and avoids publishing incomplete data.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A source task fails yet the monitoring task never executes because all downstream tasks require upstream success. Its targeted response is: Design a separate failure-handling or completion branch with the supported run-if logic for alerts and cleanup. The current case is governed more directly by: Task boundaries make duration limits and operational ownership explicit.
B: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: Task boundaries make duration limits and operational ownership explicit.
D:This principle concerns a separate data-engineering condition: A multi-step notebook workflow handles source extraction and final reporting in one cell sequence with no recoverable checkpoints. Its targeted response is: Split ingestion, validation and publishing into explicit orchestrated tasks with durable intermediate outputs. The current case is governed more directly by: Task boundaries make duration limits and operational ownership explicit.
Question 432
The team chooses: Configure bounded restarts and alerting with root-cause investigation for repeated failures. Its observed issue is: A continuously running pipeline is scheduled to restart automatically but restart storms consume a growing compute budget. What is the strongest technical basis?
- Production job run identities must be stable and authorized independent of a human notebook editor.
- Repair runs and per-task retries address different recovery granularities.
- Job task state transitions follow dependency and conditional execution rules.
- Automatic recovery should be limited by failure budgets and should not hide persistent faults.
Explanation
Correct Answer
D:The decisive mechanism is: Automatic recovery should be limited by failure budgets and should not hide persistent faults. That explains the selected action: Configure bounded restarts and alerting with root-cause investigation for repeated failures. In the original scenario: A continuously running pipeline is scheduled to restart automatically but restart storms consume a growing compute budget. The specific unmanaged risk is: Unbounded restarts can amplify resource consumption while no useful records are processed. Validate with: Repeated injected failures hit the configured stop threshold and create a human-actionable incident.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A job uses a service principal that loses access to the destination schema when an employee leaves. Its targeted response is: Assign a dedicated run-as identity with durable scoped grants and an ownership review. The current case is governed more directly by: Automatic recovery should be limited by failure budgets and should not hide persistent faults.
B:This principle concerns a separate data-engineering condition: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. Its targeted response is: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. The current case is governed more directly by: Automatic recovery should be limited by failure budgets and should not hide persistent faults.
C:This principle concerns a separate data-engineering condition: A job owner cannot explain why a task skipped execution after a predecessor failed. Its targeted response is: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. The current case is governed more directly by: Automatic recovery should be limited by failure budgets and should not hide persistent faults.
Question 433
A solution applies: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed. It addresses: A sales pipeline aggregates gold metrics before the bronze ingestion task finishes and occasionally reports incomplete totals. Which operational outcome MOST directly verifies success?
- A pipeline run updates tables in valid dependency order and records expectation outcomes.
- A delayed-ingestion test prevents gold refresh until bronze and silver are completed successfully.
- A seeded mismatch prevents cutover and the prior certified table remains queryable.
- A reviewed graph lists every expected parent and a source change propagates to the correct targets.
Explanation
Correct Answer
B:The strongest acceptance proof is: A delayed-ingestion test prevents gold refresh until bronze and silver are completed successfully. It specifically verifies: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed. The original issue was: A sales pipeline aggregates gold metrics before the bronze ingestion task finishes and occasionally reports incomplete totals. The underlying mechanism is: DAG-based orchestration coordinates data readiness and avoids race conditions across dependent tasks. Without it, an early downstream task can publish partial business totals without raising an obvious failure.
Incorrect Answers
A:This result would validate a different measure: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. That is relevant to the distinct problem: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. Here the acceptance criterion is: A delayed-ingestion test prevents gold refresh until bronze and silver are completed successfully.
C:This result would validate a different measure: Write to a staging target, validate row totals and invariants, then perform the approved publication step. That is relevant to the distinct problem: A finance transformation writes its output directly into a published table before reconciling totals against the source. Here the acceptance criterion is: A delayed-ingestion test prevents gold refresh until bronze and silver are completed successfully.
D:This result would validate a different measure: Declare consistent table names and dependencies and validate the generated pipeline graph. That is relevant to the distinct problem: A declarative pipeline transforms several datasets but its source names are ambiguous and a data team cannot reconstruct dependencies. Here the acceptance criterion is: A delayed-ingestion test prevents gold refresh until bronze and silver are completed successfully.
Question 434
A solution applies: Use a snapshot replacement or keyed MERGE strategy instead of appending every full snapshot as new records. It addresses: A daily file load uses append-only mode for periodic snapshots of the same full inventory. Which operational outcome MOST directly verifies success?
- A sampled bronze row links to the expected stream partition and source event time.
- Readers observe a complete validated target before or after cutover, not partial data.
- Two full snapshots produce one current inventory row per item and expected updates.
- Insert-update-delete test events produce one correct current target record per key.
Explanation
Correct Answer
C:The strongest acceptance proof is: Two full snapshots produce one current inventory row per item and expected updates. It specifically verifies: Use a snapshot replacement or keyed MERGE strategy instead of appending every full snapshot as new records. The original issue was: A daily file load uses append-only mode for periodic snapshots of the same full inventory. The underlying mechanism is: Input extraction semantics determine whether repeated rows are new events or refreshed state. Without it, appending full inventories multiplies items and distorts on-hand quantities.
Incorrect Answers
A:This result would validate a different measure: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay. That is relevant to the distinct problem: A pipeline ingests Event Hubs messages into a bronze table but never captures the partition, offset or event timestamp. Here the acceptance criterion is: Two full snapshots produce one current inventory row per item and expected updates.
B:This result would validate a different measure: Choose a controlled CREATE OR REPLACE TABLE or compatible atomic table-replacement strategy and validate schema/permissions. That is relevant to the distinct problem: An existing table must be rebuilt from corrected historical files while its readers require a consistent atomic replacement. Here the acceptance criterion is: Two full snapshots produce one current inventory row per item and expected updates.
D:This result would validate a different measure: Use a supported change-data-capture feed and apply insert, update and delete semantics to the target. That is relevant to the distinct problem: A SaaS database updates and deletes customer records but a pipeline appends every nightly full extract to a Delta table. Here the acceptance criterion is: Two full snapshots produce one current inventory row per item and expected updates.
Question 435
The team implements: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant. The original problem is: A business report must refresh daily at 06:00 in a defined local time zone but a developer schedules it in UTC without conversion. Which test MOST convincingly demonstrates correctness?
- A test file arrives and starts one valid job run without repeated empty polling.
- A failed downstream task is repaired without repeating successful non-idempotent upstream work.
- Run history shows the job starts at the agreed local times across representative date transitions.
- A missing-table test stops with the expected error while a transient failure recovers according to policy.
Explanation
Correct Answer
C:The strongest acceptance proof is: Run history shows the job starts at the agreed local times across representative date transitions. It specifically verifies: Configure the Lakeflow Job schedule with the intended time zone and verify daylight-saving behavior where relevant. The original issue was: 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 underlying mechanism is: Scheduler time zone semantics affect when recurring business windows run. Without it, an implicit UTC schedule can cause delivery an hour or more away from the required business cutover.
Incorrect Answers
A:This result would validate a different measure: Use a supported file-arrival trigger where its prerequisites and source location are compatible. That is relevant to the distinct problem: A cloud file feed needs a job triggered by arriving files instead of polling every minute. Here the acceptance criterion is: Run history shows the job starts at the agreed local times across representative date transitions.
B:This result would validate a different measure: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. That is relevant to the distinct problem: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. Here the acceptance criterion is: Run history shows the job starts at the agreed local times across representative date transitions.
D:This result would validate a different measure: Limit retries to appropriate transient errors and set accountable failure handling for permanent logic problems. That is relevant to the distinct problem: A job's retry policy restarts a deterministic bad SQL query six times even though the table is missing. Here the acceptance criterion is: Run history shows the job starts at the agreed local times across representative date transitions.
Question 436
A data engineering team faces this Azure Databricks requirement: A shared table includes an old regulated field and the business needs reproducible evidence of when it was removed. Which action is MOST appropriate?
- Use appropriate table history, schema change records and approved retention/audit evidence rather than relying on memory.
- Transfer ownership through approved governance workflow and review grants after reassignment.
- Reconcile catalog object identity, lineage and current grants after schema or owner changes.
- Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access.
Explanation
Correct Answer
A:The most appropriate action is: Use appropriate table history, schema change records and approved retention/audit evidence rather than relying on memory. It addresses the stated condition: A shared table includes an old regulated field and the business needs reproducible evidence of when it was removed. The technical basis is: Metadata history and audit trails can support investigation of structure and access changes. Without this control, deleting a field without documented change history can leave unanswerable regulatory questions. A direct acceptance check is: The change record ties the removed column to an authorized deployment and preserved evidence.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: An audit asks who owns a catalog table but object ownership still points to an inactive employee. The corresponding measure there would be: Transfer ownership through approved governance workflow and review grants after reassignment. The stated situation instead calls for: Use appropriate table history, schema change records and approved retention/audit evidence rather than relying on memory.
C:This alternative primarily addresses a different Azure Databricks problem: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. The corresponding measure there would be: Reconcile catalog object identity, lineage and current grants after schema or owner changes. The stated situation instead calls for: Use appropriate table history, schema change records and approved retention/audit evidence rather than relying on memory.
D: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: Use appropriate table history, schema change records and approved retention/audit evidence rather than relying on memory.
Question 437
A Databricks engineer recommends: Register supported external locations and storage credentials, then define governed external tables. It responds to: A legacy external Delta table points at a cloud location with an unmanaged storage credential stored in notebook text. What underlying mechanism BEST explains why?
- Lakehouse Federation lets governed queries access supported external systems through a connection abstraction.
- A view can define a query abstraction without requiring a second physical copy of source data.
- Foreign catalog semantics and connector capabilities differ from native managed Delta table operations.
- External table metadata can be governed even when the underlying object files remain in external storage.
Explanation
Correct Answer
D:The decisive mechanism is: External table metadata can be governed even when the underlying object files remain in external storage. That explains the selected action: Register supported external locations and storage credentials, then define governed external tables. In the original scenario: A legacy external Delta table points at a cloud location with an unmanaged storage credential stored in notebook text. The specific unmanaged risk is: Credentials embedded in notebooks can be copied and used outside the intended catalog authorization. Validate with: A credential audit shows approved external access and no user-readable storage secret in notebook source.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. Its targeted response is: Create an authorized connection and supported foreign catalog for the external source. The current case is governed more directly by: External table metadata can be governed even when the underlying object files remain in external storage.
B:This principle concerns a separate data-engineering condition: An analyst wants to expose a filtered projection of a governed table without copying sensitive source rows. Its targeted response is: Create a Unity Catalog view with approved permissions and verify underlying access semantics. The current case is governed more directly by: External table metadata can be governed even when the underlying object files remain in external storage.
C:This principle concerns a separate data-engineering condition: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. Its targeted response is: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. The current case is governed more directly by: External table metadata can be governed even when the underlying object files remain in external storage.
Question 438
An operator introduces: Use Lakeflow Jobs repair at the failed task when dependency outputs remain valid. The situation is: A job fails during a temporary Azure storage outage but operators rerun every successful upstream task. Which validation should be required before signoff?
- The job writes results through distributed output and driver memory stays below the approved threshold.
- A controlled transient outage is repaired without rerunning completed expensive ingestion.
- A dashboard highlights task and stage regressions before the total job breaches its SLA.
- Load testing shows completion within the target window and queued runs do not overlap unsafely.
Explanation
Correct Answer
B:The strongest acceptance proof is: A controlled transient outage is repaired without rerunning completed expensive ingestion. It specifically verifies: Use Lakeflow Jobs repair at the failed task when dependency outputs remain valid. The original issue was: A job fails during a temporary Azure storage outage but operators rerun every successful upstream task. The underlying mechanism is: Task-level repair can reduce replay cost while preserving successful work. Without it, unnecessary replay may duplicate writes and extend incident recovery time.
Incorrect Answers
A:This result would validate a different measure: Keep large results distributed and replace driver collection with bounded sampling or distributed writes. That is relevant to the distinct problem: A Spark join reads large inputs but the driver reports failures after an analyst calls collect() on the result. Here the acceptance criterion is: A controlled transient outage is repaired without rerunning completed expensive ingestion.
C:This result would validate a different measure: Collect job timing, task duration and relevant Spark stage metrics in a monitored baseline. That is relevant to the distinct problem: A job's duration doubles but an administrator sees only its final success status with no phase-level metrics. Here the acceptance criterion is: A controlled transient outage is repaired without rerunning completed expensive ingestion.
D:This result would validate a different measure: Investigate stage runtime growth and enforce appropriate concurrency policy before raising frequency. That is relevant to the distinct problem: A job scheduled each hour starts running for 80 minutes and overlaps the next run. Here the acceptance criterion is: A controlled transient outage is repaired without rerunning completed expensive ingestion.
Question 439
A data engineering team faces this Azure Databricks requirement: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. Which action is MOST appropriate?
- Define a deliberate unknown-member or late-dimension reconciliation pattern without silently dropping facts.
- Keep a governed raw or bronze representation before applying irreversible cleansing into silver and gold.
- Define fact-table grain at the required transaction or line-item level before aggregation.
- Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality.
Explanation
Correct Answer
D:The most appropriate action is: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality. It addresses the stated condition: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. The technical basis is: High-cardinality partition columns can fragment file layout and increase metadata overhead. Without this control, excessive partitions create small files and poor query planning without useful pruning. A direct acceptance check is: File-count and query-profile comparisons show fewer fragments and faster targeted scans.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A late-arriving purchase refers to a customer identifier whose dimension record has not yet been ingested. The corresponding measure there would be: Define a deliberate unknown-member or late-dimension reconciliation pattern without silently dropping facts. The stated situation instead calls for: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality.
B:This alternative primarily addresses a different Azure Databricks problem: A bronze ingestion layer stores only final transformed values and loses raw source fields needed for incident replay. The corresponding measure there would be: Keep a governed raw or bronze representation before applying irreversible cleansing into silver and gold. The stated situation instead calls for: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality.
C:This alternative primarily addresses a different Azure Databricks problem: A facts table groups product sales at daily level although auditors must inspect individual transaction adjustments. The corresponding measure there would be: Define fact-table grain at the required transaction or line-item level before aggregation. The stated situation instead calls for: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality.
Question 440
For this Azure Databricks issue: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. Engineers choose: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. What acceptance evidence is BEST?
- Representative business queries return consistent region totals with an acceptable plan.
- The top event-time queries show improved data skipping and reconciled row counts.
- The platform team retains approved storage lifecycle authority while Databricks queries the registered data.
- A controlled late event appears in the correct historical period according to the approved policy.
Explanation
Correct Answer
A:The strongest acceptance proof is: Representative business queries return consistent region totals with an acceptable plan. It specifically verifies: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. The original issue was: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. The underlying mechanism is: Data models balance redundancy and query simplicity according to workload requirements. Without it, unneeded normalization can add joins while denormalization without governance can produce inconsistent descriptions.
Incorrect Answers
B:This result would validate a different measure: Reevaluate data layout using representative event-time filters and a suitable clustering key. That is relevant to the distinct problem: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. Here the acceptance criterion is: Representative business queries return consistent region totals with an acceptable plan.
C:This result would validate a different measure: Use an external Unity Catalog table with an approved registered location instead of assuming managed storage ownership. That is relevant to the distinct problem: A dataset has a strict requirement that Azure storage ownership and lifecycle remain under a separate platform team. Here the acceptance criterion is: Representative business queries return consistent region totals with an acceptable plan.
D:This result would validate a different measure: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. That is relevant to the distinct problem: A lakehouse receives sensor observations with event timestamps that arrive out of order. Here the acceptance criterion is: Representative business queries return consistent region totals with an acceptable plan.