Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 35
Question 340
The team chooses: Test the identity-aware filter function, its permissions and supported execution context on representative queries. Its observed issue is: An administrator attaches a row-filter function that returns errors for unauthorized query contexts and treats the issue as data corruption. What is the strongest technical basis?
- Central data-plane access rules reduce reliance on every application path applying tenant filtering.
- Row-level security evaluates access rules at query time rather than relying on users to remember a WHERE clause.
- Object access can require permission to traverse its parent hierarchy as well as read the child.
- Fine-grained security functions are part of the query execution path and can affect availability.
Explanation
Correct Answer
D:The decisive mechanism is: Fine-grained security functions are part of the query execution path and can affect availability. That explains the selected action: Test the identity-aware filter function, its permissions and supported execution context on representative queries. In the original scenario: An administrator attaches a row-filter function that returns errors for unauthorized query contexts and treats the issue as data corruption. The specific unmanaged risk is: A broken policy function may deny intended users or expose inconsistent query results if bypassed. Validate with: Approved and disallowed identities receive the expected records without filter execution errors.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A multi-tenant analytics table relies on application code to append customer_id filtering. Its targeted response is: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. The current case is governed more directly by: Fine-grained security functions are part of the query execution path and can affect availability.
B:This principle concerns a separate data-engineering condition: A user must see only the East region rows of a common sales table while managers see all territories. Its targeted response is: Configure a tested Unity Catalog row filter or suitable ABAC policy based on the authorized identity. The current case is governed more directly by: Fine-grained security functions are part of the query execution path and can affect availability.
C:This principle concerns a separate data-engineering condition: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. Its targeted response is: Check required parent catalog and schema usage privileges alongside the table SELECT grant. The current case is governed more directly by: Fine-grained security functions are part of the query execution path and can affect availability.
Question 341
An operator introduces: Align compatible schemas and use name-based union semantics with explicit type checks. The situation is: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. Which validation should be required before signoff?
- A sample includes all approved categories and status totals reconcile to source rows.
- The merged dataset preserves typed values and column names from both input feeds.
- A test invoice with a linked refund produces the approved net amount.
- A seeded dataset retains zero-quantity items while rows with null quantities follow the documented rule.
Explanation
Correct Answer
B:The strongest acceptance proof is: The merged dataset preserves typed values and column names from both input feeds. It specifically verifies: Align compatible schemas and use name-based union semantics with explicit type checks. The original issue was: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. The underlying mechanism is: Union operations concatenate rows and require aligned column meanings. Without it, position-based union may quietly corrupt data when column positions differ.
Incorrect Answers
A:This result would validate a different measure: Apply a controlled pivot with a defined set of expected categories and aggregation rule. That is relevant to the distinct problem: A quality report needs one column for each product status category but stores status as separate rows. Here the acceptance criterion is: The merged dataset preserves typed values and column names from both input feeds.
C:This result would validate a different measure: Normalize transaction sign semantics before grouping by business date and customer. That is relevant to the distinct problem: A daily revenue report double-counts refunds because both debit and credit rows are summed as positive numbers. Here the acceptance criterion is: The merged dataset preserves typed values and column names from both input feeds.
D:This result would validate a different measure: Implement explicit null predicates rather than treating zero and null as equivalent. That is relevant to the distinct problem: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. Here the acceptance criterion is: The merged dataset preserves typed values and column names from both input feeds.
Question 342
A solution applies: Define and test consistent trimming, Unicode normalization and case comparison for the business key. It addresses: A customer-name cleansing script uses an arbitrary lowercase conversion without preserving Unicode and leading/trailing whitespace rules. Which operational outcome MOST directly verifies success?
- Known events around midnight map to the intended store-local date and correct UTC instant.
- The unpivoted output contains exactly one row per original item-month and preserves totals.
- A timed append comparison meets the freshness and duplicate controls with lower compute consumption.
- Mixed-case, whitespace and non-ASCII test records resolve according to the documented mapping policy.
Explanation
Correct Answer
D:The strongest acceptance proof is: Mixed-case, whitespace and non-ASCII test records resolve according to the documented mapping policy. It specifically verifies: Define and test consistent trimming, Unicode normalization and case comparison for the business key. The original issue was: A customer-name cleansing script uses an arbitrary lowercase conversion without preserving Unicode and leading/trailing whitespace rules. The underlying mechanism is: Text normalization must be deterministic and tailored to identifier semantics. Without it, inconsistent name normalization can create duplicate customers or merge distinct identities incorrectly.
Incorrect Answers
A:This result would validate a different measure: Normalize time zone semantics before extracting business-local reporting dates. That is relevant to the distinct problem: A date field mixes UTC timestamps and local store times but a pipeline groups all values by the raw date string. Here the acceptance criterion is: Mixed-case, whitespace and non-ASCII test records resolve according to the documented mapping policy.
B:This result would validate a different measure: Use a compatible unpivot or stack transformation with explicit month and amount columns. That is relevant to the distinct problem: A large orders dataset has one column per month but a dashboard expects month-value rows for filtering and grouping. Here the acceptance criterion is: Mixed-case, whitespace and non-ASCII test records resolve according to the documented mapping policy.
C:This result would validate a different measure: Use an incremental append pattern with suitable deduplication when source events cannot change. That is relevant to the distinct problem: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. Here the acceptance criterion is: Mixed-case, whitespace and non-ASCII test records resolve according to the documented mapping policy.
Question 343
During a lakehouse implementation review, engineers observe: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. What is the BEST next action?
- Use a dedicated service principal with scoped Unity Catalog grants and governed credential lifecycle.
- Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges.
- Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants.
- Replace broad grants with documented minimum creation and use privileges in a dedicated schema.
Explanation
Correct Answer
D:The most appropriate action is: Replace broad grants with documented minimum creation and use privileges in a dedicated schema. It addresses the stated condition: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. The technical basis is: Separation of duties requires independent decisions for object administration, data modification and read access. Without this control, A compromised job principal could alter data products unrelated to its intended table. A direct acceptance check is: An access test creates the required table only inside the approved job schema and denies other catalogs.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An ETL service principal is granted permissions through a personal employee account that will leave the company. The corresponding measure there would be: Use a dedicated service principal with scoped Unity Catalog grants and governed credential lifecycle. The stated situation instead calls for: Replace broad grants with documented minimum creation and use privileges in a dedicated schema.
B:This alternative primarily addresses a different Azure Databricks problem: A managed identity can read a storage container but a newly created external table is denied in Databricks. The corresponding measure there would be: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges. The stated situation instead calls for: Replace broad grants with documented minimum creation and use privileges in a dedicated schema.
C:This alternative primarily addresses a different Azure Databricks problem: A finance analyst must read an approved table but was granted broad MODIFY rights at the schema level. The corresponding measure there would be: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants. The stated situation instead calls for: Replace broad grants with documented minimum creation and use privileges in a dedicated schema.
Question 344
A team omits the recommended measure: Configure supported schema evolution or rescued-data handling with explicit compatibility review. Its environment shows: A file feed introduces an unexpected optional column and the stream fails after the first changed file. What is the MOST direct residual risk?
- Custom polling without checkpoint or schema handling may miss updates and require fragile maintenance.
- A stream can write duplicate or malformed records into curated output without policy.
- Ignoring changed source structures can halt ingestion or silently lose fields.
- A failed data-quality rule cannot be traced back to the event-bus record that produced it.
Explanation
Correct Answer
C:The direct residual exposure is: Ignoring changed source structures can halt ingestion or silently lose fields. The triggering condition is: A file feed introduces an unexpected optional column and the stream fails after the first changed file. The omitted safeguard is: Configure supported schema evolution or rescued-data handling with explicit compatibility review. This matters because: Schema drift must be classified as an acceptable extension or a breaking contract change. A corrective test would show: A controlled extra-column event is either safely evolved or quarantined with an explicit notification.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A batch integration needs a connector-managed path from a supported operational source into the lakehouse. Its preventative action would be: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction. The most direct exposure in the current scenario is: Ignoring changed source structures can halt ingestion or silently lose fields.
B:This failure mode belongs mainly to another situation: A declarative pipeline loads cloud object files continuously but its configuration omits how duplicate files and bad records are handled. Its preventative action would be: Define Lakeflow Spark Declarative Pipelines source options, incremental behavior and expectations with a durable target. The most direct exposure in the current scenario is: Ignoring changed source structures can halt ingestion or silently lose fields.
D:This failure mode belongs mainly to another situation: A pipeline ingests Event Hubs messages into a bronze table but never captures the partition, offset or event timestamp. Its preventative action would be: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay. The most direct exposure in the current scenario is: Ignoring changed source structures can halt ingestion or silently lose fields.
Question 345
A data product owner adopts: Use an appropriate intersect or semi-join operation based on set and duplicate requirements. The reason is: A team wants only customer IDs present in both systems but uses an inner join that multiplies repeated rows. What observed result BEST proves effectiveness?
- A controlled source sample produces exactly the permitted group keys and reconciled sums.
- A sample includes all approved categories and status totals reconcile to source rows.
- A test with repeated IDs produces the expected unique or multiset intersection by policy.
- A controlled money sample matches expected exact decimal totals and rejects malformed amounts.
Explanation
Correct Answer
C:The strongest acceptance proof is: A test with repeated IDs produces the expected unique or multiset intersection by policy. It specifically verifies: Use an appropriate intersect or semi-join operation based on set and duplicate requirements. The original issue was: A team wants only customer IDs present in both systems but uses an inner join that multiplies repeated rows. The underlying mechanism is: Set operations and joins differ in duplicate behavior and result cardinality. Without it, an unrestricted join can multiply keys and exaggerate customer counts.
Incorrect Answers
A:This result would validate a different measure: Apply the required filters and join conditions before aggregation and validate authorized output groups. That is relevant to the distinct problem: An analyst calculates total revenue grouped by country but a join includes countries not approved for reporting. Here the acceptance criterion is: A test with repeated IDs produces the expected unique or multiset intersection by policy.
B:This result would validate a different measure: Apply a controlled pivot with a defined set of expected categories and aggregation rule. That is relevant to the distinct problem: A quality report needs one column for each product status category but stores status as separate rows. Here the acceptance criterion is: A test with repeated IDs produces the expected unique or multiset intersection by policy.
D:This result would validate a different measure: Parse and cast monetary values to a suitable decimal type with invalid-value handling. That is relevant to the distinct problem: A finance field arrives as a string with currency symbols and the team aggregates it lexicographically. Here the acceptance criterion is: A test with repeated IDs produces the expected unique or multiset intersection by policy.
Question 346
A Databricks engineer recommends: Reevaluate data layout using representative event-time filters and a suitable clustering key. It responds to: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. What underlying mechanism BEST explains why?
- High-cardinality partition columns can fragment file layout and increase metadata overhead.
- Event time and processing time represent different facts and affect historical interpretation.
- Physical layout should match selective consumer predicates rather than convenience of ingestion.
- Delta version history can provide auditable historical snapshots while underlying files are retained.
Explanation
Correct Answer
C:The decisive mechanism is: Physical layout should match selective consumer predicates rather than convenience of ingestion. That explains the selected action: Reevaluate data layout using representative event-time filters and a suitable clustering key. In the original scenario: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. The specific unmanaged risk is: A mismatched partition scheme forces broad scans across unrelated arrival-day files. Validate with: The top event-time queries show improved data skipping and reconciled row counts.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: An event table is partitioned by the unique transaction identifier and creates millions of tiny partitions. Its targeted response is: Use coarse suitable partitioning or liquid clustering selected from filter patterns and cardinality. The current case is governed more directly by: Physical layout should match selective consumer predicates rather than convenience of ingestion.
B:This principle concerns a separate data-engineering condition: A lakehouse receives sensor observations with event timestamps that arrive out of order. Its targeted response is: Design event-time fields, ingestion timestamps and late-data behavior suited to replay and temporal queries. The current case is governed more directly by: Physical layout should match selective consumer predicates rather than convenience of ingestion.
D:This principle concerns a separate data-engineering condition: A business needs to compare two point-in-time table versions during a financial reconciliation. Its targeted response is: Use supported Delta table version history and time travel within the documented retention window. The current case is governed more directly by: Physical layout should match selective consumer predicates rather than convenience of ingestion.
Question 347
A data product owner adopts: Use caching only for beneficial reuse and release persisted state when no longer needed. The reason is: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. What observed result BEST proves effectiveness?
- A representative run shows reduced spill bytes and matching aggregate results with improved runtime.
- A dashboard highlights task and stage regressions before the total job breaches its SLA.
- Spark storage metrics show released cache and unchanged correctness with improved total runtime.
- The isolated benchmark meets its percentile duration under simultaneous unrelated workload pressure.
Explanation
Correct Answer
C:The strongest acceptance proof is: Spark storage metrics show released cache and unchanged correctness with improved total runtime. It specifically verifies: Use caching only for beneficial reuse and release persisted state when no longer needed. The original issue was: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. The underlying mechanism is: Caching trades execution time for memory and may increase pressure when datasets are not reused. Without it, unused cached data can cause eviction, spilling and unexpected failures for later stages.
Incorrect Answers
A:This result would validate a different measure: Examine shuffle metrics, memory pressure and partition sizing to target the spilling stage. That is relevant to the distinct problem: A large aggregation has repeated shuffle spills to disk even though source scans finish quickly. Here the acceptance criterion is: Spark storage metrics show released cache and unchanged correctness with improved total runtime.
B: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: Spark storage metrics show released cache and unchanged correctness with improved total runtime.
D:This result would validate a different measure: Compare workload contention and resource reservations, then isolate or resize the critical job compute. That is relevant to the distinct problem: A production notebook intermittently times out only when many other jobs share the same classic cluster. Here the acceptance criterion is: Spark storage metrics show released cache and unchanged correctness with improved total runtime.
Question 348
A team omits the recommended measure: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions. Its environment shows: A notebook pipeline uses a shared cluster with unstable third-party dependencies while a critical finance job needs controlled isolation. What is the MOST direct residual risk?
- An analyst restart or entitlement change can interrupt a production data delivery.
- An upgrade or runaway task on the shared cluster can compromise finance pipeline availability.
- A shared notebook cluster can cause dashboards to stall when unrelated Spark notebooks consume executors.
- A default GPU cluster may charge premium rates while most tasks leave accelerators unused.
Explanation
Correct Answer
B:The direct residual exposure is: An upgrade or runaway task on the shared cluster can compromise finance pipeline availability. The triggering condition is: A notebook pipeline uses a shared cluster with unstable third-party dependencies while a critical finance job needs controlled isolation. The omitted safeguard is: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions. This matters because: Compute isolation reduces interference between unrelated application environments and execution libraries. A corrective test would show: A test upgrade on the interactive cluster does not change the isolated finance job's dependency versions or results.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A scheduled ETL run uses shared analyst compute and fails whenever the cluster owner restarts a notebook session. Its preventative action would be: Define a job-owned execution identity and eligible task compute separate from ad hoc analyst cluster lifecycle. The most direct exposure in the current scenario is: An upgrade or runaway task on the shared cluster can compromise finance pipeline availability.
C:This failure mode belongs mainly to another situation: Analysts run short SQL dashboard queries against a shared lakehouse but their notebooks share a general-purpose Spark cluster with training experiments. Its preventative action would be: Use an appropriately sized SQL warehouse with workload isolation and measured concurrency for dashboard queries. The most direct exposure in the current scenario is: An upgrade or runaway task on the shared cluster can compromise finance pipeline availability.
D:This failure mode belongs mainly to another situation: A feature-engineering notebook requires GPU libraries but the data cleaning jobs never use accelerators. Its preventative action would be: Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations. The most direct exposure in the current scenario is: An upgrade or runaway task on the shared cluster can compromise finance pipeline availability.
Question 349
For this Microsoft DP-750 case: Two engineers change the same ingestion function on separate branches and one silently overwrites the other's fix. Which design or operational response BEST fits?
- Resolve Git merge conflicts with tests and reviewed integration before merging the release branch.
- Add user acceptance tests for the relevant reporting contract before production promotion.
- Add representative unit and integration tests asserting transformation results and schema contracts.
- Include performance and end-to-end tests using representative scale and data distributions.
Explanation
Correct Answer
A:The most appropriate action is: Resolve Git merge conflicts with tests and reviewed integration before merging the release branch. It addresses the stated condition: Two engineers change the same ingestion function on separate branches and one silently overwrites the other's fix. The technical basis is: Conflict resolution must preserve intended behavior from both change sets. Without this control, unreviewed overwrites can remove validation or idempotency logic from the deployed pipeline. A direct acceptance check is: A merged branch passes regression tests for both bug fixes and shows reviewed conflict decisions.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A developer changes a transformation with a user-visible business effect but omits acceptance testing by the data product owner. The corresponding measure there would be: Add user acceptance tests for the relevant reporting contract before production promotion. The stated situation instead calls for: Resolve Git merge conflicts with tests and reviewed integration before merging the release branch.
C:This alternative primarily addresses a different Azure Databricks problem: A release modifies transformation logic but tests only whether Python files compile. The corresponding measure there would be: Add representative unit and integration tests asserting transformation results and schema contracts. The stated situation instead calls for: Resolve Git merge conflicts with tests and reviewed integration before merging the release branch.
D:This alternative primarily addresses a different Azure Databricks problem: An engineering test suite passes on miniature in-memory data yet fails in production on skewed billion-row joins. The corresponding measure there would be: Include performance and end-to-end tests using representative scale and data distributions. The stated situation instead calls for: Resolve Git merge conflicts with tests and reviewed integration before merging the release branch.
Question 350
A platform architect adopts: Reconcile catalog object identity, lineage and current grants after schema or owner changes. For this requirement: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. Which rationale MOST directly supports it?
- Object governance is ongoing and must follow organizational role and service identity changes.
- Automatic lineage visibility has collection boundaries and does not imply every real-world dependency is recorded.
- Governance depends on maintained object ownership as teams and responsibilities change.
- Permission reviews should follow actual securable objects and their dependencies rather than name assumptions.
Explanation
Correct Answer
D:The decisive mechanism is: Permission reviews should follow actual securable objects and their dependencies rather than name assumptions. That explains the selected action: Reconcile catalog object identity, lineage and current grants after schema or owner changes. In the original scenario: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. The specific unmanaged risk is: A migrated table can retain unintended access or lose required controls after namespace changes. Validate with: An access matrix tests current schema objects and verifies intended principals after migration.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A company needs to review table-owner changes and permissions after organizational restructuring. Its targeted response is: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. The current case is governed more directly by: Permission reviews should follow actual securable objects and their dependencies rather than name assumptions.
B:This principle concerns a separate data-engineering condition: A lineage graph shows no relationship for data loaded outside the monitored platform and the team assumes the dataset has no upstream dependency. Its targeted response is: Validate Unity Catalog lineage capture coverage and supplement unsupported external steps with documented provenance. The current case is governed more directly by: Permission reviews should follow actual securable objects and their dependencies rather than name assumptions.
C:This principle concerns a separate data-engineering condition: An audit asks who owns a catalog table but object ownership still points to an inactive employee. Its targeted response is: Transfer ownership through approved governance workflow and review grants after reassignment. The current case is governed more directly by: Permission reviews should follow actual securable objects and their dependencies rather than name assumptions.