Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 82
Question 810
An operator introduces: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. The situation is: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. Which validation should be required before signoff?
- A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
- An access test creates the required table only inside the approved job schema and denies other catalogs.
- The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
- A test account from tenant A cannot retrieve tenant B records through SQL, notebooks or the approved BI route.
Explanation
Correct Answer
A:The strongest acceptance proof is: A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails. It specifically verifies: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. The original issue was: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. The underlying mechanism is: Workspace access scope and principal privileges enforce different aspects of authorization. Without it, an object may be available to overprivileged identities in unintended contexts if either boundary is ignored.
Incorrect Answers
B:This result would validate a different measure: Replace broad grants with documented minimum creation and use privileges in a dedicated schema. That is relevant to the distinct problem: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. Here the acceptance criterion is: A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
C:This result would validate a different measure: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. That is relevant to the distinct problem: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. Here the acceptance criterion is: A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
D:This result would validate a different measure: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. That is relevant to the distinct problem: A multi-tenant analytics table relies on application code to append customer_id filtering. Here the acceptance criterion is: A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
Question 811
For this Microsoft DP-750 case: A pipeline uses CREATE TABLE AS SELECT for a one-time derived dataset but later assumes the result refreshes automatically. Which design or operational response BEST fits?
- Choose one compatible data layout strategy based on table format, platform support and query evidence.
- Implement the required SCD Type 1 overwrite with stable business keys and validated updates.
- Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh.
- Define fact-table grain at the required transaction or line-item level before aggregation.
Explanation
Correct Answer
C:The most appropriate action is: Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh. It addresses the stated condition: A pipeline uses CREATE TABLE AS SELECT for a one-time derived dataset but later assumes the result refreshes automatically. The technical basis is: CTAS populates a table at execution time and does not imply continuous synchronization with source. Without this control, dashboards can become stale when an initial table snapshot is mistaken for a live derived view. A direct acceptance check is: A source update changes the target only through the planned refresh mechanism and produces a recorded watermark.
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: Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh.
B:This alternative primarily addresses a different Azure Databricks problem: A reference table stores only the latest airport name and business users explicitly do not need historical values. The corresponding measure there would be: Implement the required SCD Type 1 overwrite with stable business keys and validated updates. The stated situation instead calls for: Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh.
D: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: Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh.
Question 812
A pipeline owner declines the action: Design a separate failure-handling or completion branch with the supported run-if logic for alerts and cleanup. The business situation is: A source task fails yet the monitoring task never executes because all downstream tasks require upstream success. What specific failure can follow?
- An upstream failure can remain invisible and leave temporary resources without cleanup.
- Hard-coded development resources can cause a production job to read or overwrite the wrong data.
- Full reruns can repeat expensive historical ingestion and duplicate side effects.
- Readers can combine incompatible versions when related tables update independently.
Explanation
Correct Answer
A:The direct residual exposure is: An upstream failure can remain invisible and leave temporary resources without cleanup. The triggering condition is: A source task fails yet the monitoring task never executes because all downstream tasks require upstream success. The omitted safeguard is: Design a separate failure-handling or completion branch with the supported run-if logic for alerts and cleanup. This matters because: Orchestration may need error paths that execute regardless of normal success dependencies. A corrective test would show: A staged failure triggers the documented alert and cleanup while skipping dependent publication.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A multi-team notebook uses hard-coded workspace names and credentials, making the same pipeline fail in staging. Its preventative action would be: Parameterize environment-specific paths, catalogs and identities through governed deployment configuration. The most direct exposure in the current scenario is: An upstream failure can remain invisible and leave temporary resources without cleanup.
C:This failure mode belongs mainly to another situation: A bulk repair executes all pipeline tasks again even when only the final reporting notebook failed. Its preventative action would be: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid. The most direct exposure in the current scenario is: An upstream failure can remain invisible and leave temporary resources without cleanup.
D:This failure mode belongs mainly to another situation: A regulated pipeline needs consistent transaction boundaries across multiple table writes but updates are published one at a time. Its preventative action would be: Design a compatible atomic publication or versioned readiness contract so consumers see consistent results. The most direct exposure in the current scenario is: An upstream failure can remain invisible and leave temporary resources without cleanup.
Question 813
An Azure Databricks architect reviews the following problem: A multi-tenant analytics table relies on application code to append customer_id filtering. What should the team implement FIRST?
- Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants.
- Use supported Databricks secret access with least-privilege scope access and remove secret values from logs.
- Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported.
- Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases.
Explanation
Correct Answer
D:The most appropriate action is: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. It addresses the stated condition: A multi-tenant analytics table relies on application code to append customer_id filtering. The technical basis is: Central data-plane access rules reduce reliance on every application path applying tenant filtering. Without this control, one missing tenant predicate can expose another customer’s records. A direct acceptance check is: A test account from tenant A cannot retrieve tenant B records through SQL, notebooks or the approved BI route.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An engineering pipeline attempts to insert records into a production Delta table using an account with SELECT only. The corresponding measure there would be: Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants. The stated situation instead calls for: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases.
B:This alternative primarily addresses a different Azure Databricks problem: An application uses an external Azure Key Vault secret scope but a notebook prints the secret into task logs. The corresponding measure there would be: Use supported Databricks secret access with least-privilege scope access and remove secret values from logs. The stated situation instead calls for: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases.
C:This alternative primarily addresses a different Azure Databricks problem: A data compliance team needs consistent redaction of columns tagged as personal data across hundreds of catalog tables. The corresponding measure there would be: Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported. The stated situation instead calls for: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases.
Question 814
An operator introduces: Add user acceptance tests for the relevant reporting contract before production promotion. The situation is: A developer changes a transformation with a user-visible business effect but omits acceptance testing by the data product owner. Which validation should be required before signoff?
- An unauthorized direct push is rejected and a reviewed pull request completes all required gates.
- An integration fixture with historical updates yields exactly the intended target versions.
- Deployment plans show the intended trigger for each target and a test job fires at the correct interval.
- A product owner signs off a sample report and its reconciled acceptance criteria before rollout.
Explanation
Correct Answer
D:The strongest acceptance proof is: A product owner signs off a sample report and its reconciled acceptance criteria before rollout. It specifically verifies: Add user acceptance tests for the relevant reporting contract before production promotion. The original issue was: A developer changes a transformation with a user-visible business effect but omits acceptance testing by the data product owner. The underlying mechanism is: Technical tests cannot replace business approval of the reported meaning of data. Without it, A numerically correct but semantically changed field can mislead business users.
Incorrect Answers
A:This result would validate a different measure: Protect the main branch with peer review, required tests and controlled promotion windows. That is relevant to the distinct problem: A release process merges unreviewed notebook changes directly into the main branch minutes before a production run. Here the acceptance criterion is: A product owner signs off a sample report and its reconciled acceptance criteria before rollout.
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: A product owner signs off a sample report and its reconciled acceptance criteria before rollout.
C:This result would validate a different measure: Validate per-target bundle variable resolution and compare rendered job definitions before deployment. That is relevant to the distinct problem: A data engineer updates a bundled job trigger but another environment's deployment silently uses the wrong schedule. Here the acceptance criterion is: A product owner signs off a sample report and its reconciled acceptance criteria before rollout.
Question 815
The team chooses: Validate business keys and choose a deterministic latest-enrollment record before aggregation. Its observed issue is: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. What is the strongest technical basis?
- Aggregation alone cannot distinguish valid repeat enrollments from accidental duplicates.
- Union operations concatenate rows and require aligned column meanings.
- Null remediation must preserve the difference between genuinely unknown data and a legitimate default.
- Time zone conversion and calendar boundary choice affect the grouping of events.
Explanation
Correct Answer
A:The decisive mechanism is: Aggregation alone cannot distinguish valid repeat enrollments from accidental duplicates. That explains the selected action: Validate business keys and choose a deterministic latest-enrollment record before aggregation. In the original scenario: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. The specific unmanaged risk is: Completion metrics may be inflated or undercounted when duplicate business events are not resolved. Validate with: Test histories with retries and real re-enrollments produce the approved per-student count.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: Two quarterly sales feeds have the same logical fields but different column ordering and a union shifts amounts into dates. Its targeted response is: Align compatible schemas and use name-based union semantics with explicit type checks. The current case is governed more directly by: Aggregation alone cannot distinguish valid repeat enrollments from accidental duplicates.
C:This principle concerns a separate data-engineering condition: A customer reference dataset has missing country codes but a pipeline replaces every null with an arbitrary default country. Its targeted response is: Define field-specific missing-value rules and quarantine or enrich unknown values before assigning business meaning. The current case is governed more directly by: Aggregation alone cannot distinguish valid repeat enrollments from accidental duplicates.
D:This principle concerns a separate data-engineering condition: A date field mixes UTC timestamps and local store times but a pipeline groups all values by the raw date string. Its targeted response is: Normalize time zone semantics before extracting business-local reporting dates. The current case is governed more directly by: Aggregation alone cannot distinguish valid repeat enrollments from accidental duplicates.
Question 816
The following control has NOT been implemented: Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model. In this case: A data product needs to copy a supported Azure Data Factory pipeline output into governed Databricks tables. Which exposure remains?
- Appending full inventories multiplies items and distorts on-hand quantities.
- A failed data-quality rule cannot be traced back to the event-bus record that produced it.
- A fixed midnight file list can omit valid delayed uploads.
- Uncoordinated retries can run transformations before ingestion finishes or under the wrong identity.
Explanation
Correct Answer
D:The direct residual exposure is: Uncoordinated retries can run transformations before ingestion finishes or under the wrong identity. The triggering condition is: A data product needs to copy a supported Azure Data Factory pipeline output into governed Databricks tables. The omitted safeguard is: Coordinate ADF orchestration with the appropriate Databricks task and Unity Catalog access model. This matters because: An external orchestrator can trigger Databricks processing while governance and failure handling remain explicit. A corrective test would show: ADF completion evidence and Databricks job dependencies show an end-to-end successful load.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A daily file load uses append-only mode for periodic snapshots of the same full inventory. Its preventative action would be: Use a snapshot replacement or keyed MERGE strategy instead of appending every full snapshot as new records. The most direct exposure in the current scenario is: Uncoordinated retries can run transformations before ingestion finishes or under the wrong identity.
B: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: Uncoordinated retries can run transformations before ingestion finishes or under the wrong identity.
C:This failure mode belongs mainly to another situation: A Databricks job receives daily structured extracts but an upstream schedule occasionally delivers files late. Its preventative action would be: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark. The most direct exposure in the current scenario is: Uncoordinated retries can run transformations before ingestion finishes or under the wrong identity.
Question 817
A team omits the recommended measure: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI. Its environment shows: A team copies Databricks notebooks manually between three workspaces and each uses different hardcoded identifiers. What is the MOST direct residual risk?
- A deployment may succeed while the first production job cannot access its storage or schema.
- Manual workspace copying can omit task settings and point production at development tables.
- 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.
Explanation
Correct Answer
B:The direct residual exposure is: Manual workspace copying can omit task settings and point production at development tables. The triggering condition is: A team copies Databricks notebooks manually between three workspaces and each uses different hardcoded identifiers. The omitted safeguard is: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI. This matters because: Declarative bundle definitions can make job and pipeline deployments repeatable across environments. A corrective test would show: A staging and production deployment use one versioned definition but distinct approved parameters.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A new pipeline passes unit tests but production fails because the service principal lacks a catalog grant. Its preventative action would be: Include integration tests of identity, Unity Catalog permissions and destination connectivity in staging. The most direct exposure in the current scenario is: Manual workspace copying can omit task settings and point production at development tables.
C: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 workspace copying can omit task settings and point production at development tables.
D:This failure mode belongs mainly to another situation: A REST deployment script creates duplicate jobs every time CI reruns after a timeout. Its preventative action would be: Use idempotent deployment methods or reconcile existing resource IDs before creating replacements. The most direct exposure in the current scenario is: Manual workspace copying can omit task settings and point production at development tables.
Question 818
A production data team leaves out: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. Its scenario is: A business glossary has table names but no indication of which field is net revenue versus gross sales. Which failure mode is MOST relevant?
- Premature removal of obsolete files can prevent required time travel or restore operations.
- Analysts may combine incompatible metrics and deliver unreliable reports.
- Sharing raw transaction tables can disclose protected customer attributes unnecessarily.
- Without lineage the team may repair the wrong pipeline after a metric regression.
Explanation
Correct Answer
B:The direct residual exposure is: Analysts may combine incompatible metrics and deliver unreliable reports. The triggering condition is: A business glossary has table names but no indication of which field is net revenue versus gross sales. The omitted safeguard is: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. This matters because: Governed descriptive metadata reduces ambiguity and supports correct analytical interpretation. A corrective test would show: A data steward can find the certified revenue definition and verify the correct field in Catalog Explorer.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. Its preventative action would be: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. The most direct exposure in the current scenario is: Analysts may combine incompatible metrics and deliver unreliable reports.
C:This failure mode belongs mainly to another situation: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. Its preventative action would be: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. The most direct exposure in the current scenario is: Analysts may combine incompatible metrics and deliver unreliable reports.
D:This failure mode belongs mainly to another situation: An analyst wants to know which upstream pipeline produced a metric displayed in a board dashboard. Its preventative action would be: Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage. The most direct exposure in the current scenario is: Analysts may combine incompatible metrics and deliver unreliable reports.
Question 819
A data engineering team faces this Azure Databricks requirement: A new job uses a large memory-optimized node merely because its source data is large, although profiling shows compute-bound transforms. Which action is MOST appropriate?
- Inspect driver collection and query planning behavior before simply enlarging every worker.
- Evaluate compatible instance pools or supported serverless startup behavior rather than keeping unused all-purpose clusters awake.
- Pin a supported Databricks Runtime version and validate application libraries against it before deployment.
- Choose node families and driver/worker sizes using CPU, memory, shuffle and workload profile evidence.
Explanation
Correct Answer
D:The most appropriate action is: Choose node families and driver/worker sizes using CPU, memory, shuffle and workload profile evidence. It addresses the stated condition: A new job uses a large memory-optimized node merely because its source data is large, although profiling shows compute-bound transforms. The technical basis is: Workload bottlenecks rather than raw input size should drive Spark cluster shape and resource selection. Without this control, overspending on memory does not relieve a CPU-bound stage and may worsen the cost-performance ratio. A direct acceptance check is: A controlled instance-family comparison achieves the same results with improved stage time and total execution cost.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A SQL transformation consumes large amounts of memory on the driver despite executor tasks processing most source partitions. The corresponding measure there would be: Inspect driver collection and query planning behavior before simply enlarging every worker. The stated situation instead calls for: Choose node families and driver/worker sizes using CPU, memory, shuffle and workload profile evidence.
B:This alternative primarily addresses a different Azure Databricks problem: A scheduled workflow launches dozens of short-lived classic clusters and loses several minutes each time waiting for virtual machines. The corresponding measure there would be: Evaluate compatible instance pools or supported serverless startup behavior rather than keeping unused all-purpose clusters awake. The stated situation instead calls for: Choose node families and driver/worker sizes using CPU, memory, shuffle and workload profile evidence.
C:This alternative primarily addresses a different Azure Databricks problem: A developer selects a new Databricks Runtime version for production despite an untested JDBC driver dependency. The corresponding measure there would be: Pin a supported Databricks Runtime version and validate application libraries against it before deployment. The stated situation instead calls for: Choose node families and driver/worker sizes using CPU, memory, shuffle and workload profile evidence.
Question 820
For this Azure Databricks issue: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. Engineers choose: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. What acceptance evidence is BEST?
- A hold rehearsal retrieves the original protected records and documents preservation scope and access.
- A publish-time check rejects missing required descriptions, owners and classification tags.
- A simulated cleanup retains protected history and an audit maps the new duration to approved settings.
- A controlled historical read succeeds within the mandated window and approved cleanup starts only afterwards.
Explanation
Correct Answer
D:The strongest acceptance proof is: A controlled historical read succeeds within the mandated window and approved cleanup starts only afterwards. It specifically verifies: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. The original issue was: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. The underlying mechanism is: Retention policy must account for physical file cleanup as well as logical table content. Without it, premature removal of obsolete files can prevent required time travel or restore operations.
Incorrect Answers
A:This result would validate a different measure: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. That is relevant to the distinct problem: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. Here the acceptance criterion is: A controlled historical read succeeds within the mandated window and approved cleanup starts only afterwards.
B:This result would validate a different measure: Implement a catalog stewardship process to review metadata and governed tags at dataset publication. That is relevant to the distinct problem: A central repository contains schemas with missing column owners and no sensitivity classifications. Here the acceptance criterion is: A controlled historical read succeeds within the mandated window and approved cleanup starts only afterwards.
C:This result would validate a different measure: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. That is relevant to the distinct problem: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. Here the acceptance criterion is: A controlled historical read succeeds within the mandated window and approved cleanup starts only afterwards.