Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 16
Question 150
The team implements: Use a suitable COPY INTO or supported batch ingestion statement with validated format and path options. The original problem is: An integration performs a one-off initial import of an existing CSV folder into a Delta table. Which test MOST convincingly demonstrates correctness?
- The import reads the intended input files once and reconciles the expected row count and schema.
- A test source update appears in the target with correct keys and measurable ingestion lag.
- A shuffled CDC test results in the correct highest-version value after replay.
- Injected duplicate and malformed source samples follow the intended dedupe or quarantine rules.
Explanation
Correct Answer
A:The strongest acceptance proof is: The import reads the intended input files once and reconciles the expected row count and schema. It specifically verifies: Use a suitable COPY INTO or supported batch ingestion statement with validated format and path options. The original issue was: An integration performs a one-off initial import of an existing CSV folder into a Delta table. The underlying mechanism is: One-time or incremental file loading can be expressed with SQL ingestion commands without building a persistent streaming service. Without it, A bespoke long-running stream for a one-time load adds complexity and idle cost.
Incorrect Answers
B:This result would validate a different measure: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction. That is relevant to the distinct problem: A batch integration needs a connector-managed path from a supported operational source into the lakehouse. Here the acceptance criterion is: The import reads the intended input files once and reconciles the expected row count and schema.
C:This result would validate a different measure: Apply ordered CDC sequencing using source change version or timestamp and consistent delete handling. That is relevant to the distinct problem: A transactional feed produces out-of-order CDC events and a naive MERGE overwrites a newer status with an older update. Here the acceptance criterion is: The import reads the intended input files once and reconciles the expected row count and schema.
D:This result would validate a different measure: Define Lakeflow Spark Declarative Pipelines source options, incremental behavior and expectations with a durable target. That is relevant to the distinct problem: A declarative pipeline loads cloud object files continuously but its configuration omits how duplicate files and bad records are handled. Here the acceptance criterion is: The import reads the intended input files once and reconciles the expected row count and schema.
Question 151
The team implements: Protect the main branch with peer review, required tests and controlled promotion windows. The original problem is: A release process merges unreviewed notebook changes directly into the main branch minutes before a production run. Which test MOST convincingly demonstrates correctness?
- An unauthorized direct push is rejected and a reviewed pull request completes all required gates.
- Deployment plans show the intended trigger for each target and a test job fires at the correct interval.
- Two identical deployment executions leave exactly one intended job with approved settings.
- A product owner signs off a sample report and its reconciled acceptance criteria before rollout.
Explanation
Correct Answer
A:The strongest acceptance proof is: An unauthorized direct push is rejected and a reviewed pull request completes all required gates. It specifically verifies: Protect the main branch with peer review, required tests and controlled promotion windows. The original issue was: A release process merges unreviewed notebook changes directly into the main branch minutes before a production run. The underlying mechanism is: Reviewed changes with required status checks reduce uncontrolled production configuration drift. Without it, A faulty last-minute edit can create an untested release with no accountable reviewer.
Incorrect Answers
B: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: An unauthorized direct push is rejected and a reviewed pull request completes all required gates.
C:This result would validate a different measure: Use idempotent deployment methods or reconcile existing resource IDs before creating replacements. That is relevant to the distinct problem: A REST deployment script creates duplicate jobs every time CI reruns after a timeout. Here the acceptance criterion is: An unauthorized direct push is rejected and a reviewed pull request completes all required gates.
D:This result would validate a different measure: Add user acceptance tests for the relevant reporting contract before production promotion. That is relevant to the distinct problem: A developer changes a transformation with a user-visible business effect but omits acceptance testing by the data product owner. Here the acceptance criterion is: An unauthorized direct push is rejected and a reviewed pull request completes all required gates.
Question 152
A pipeline owner declines the action: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges. The business situation is: A managed identity can read a storage container but a newly created external table is denied in Databricks. What specific failure can follow?
- Fixing only Azure IAM may leave catalog object access denied while broad grants increase risk.
- Manual per-table rules can miss newly created columns and expose sensitive values.
- Unnecessary modification rights can let a compromised analyst alter financial records.
- Giving all analysts write rights merely to repair one pipeline expands accidental corruption risk.
Explanation
Correct Answer
A:The direct residual exposure is: Fixing only Azure IAM may leave catalog object access denied while broad grants increase risk. The triggering condition is: A managed identity can read a storage container but a newly created external table is denied in Databricks. The omitted safeguard is: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges. This matters because: Cloud IAM and Unity Catalog are complementary authorization layers that must both permit the intended operation. A corrective test would show: A storage access test and catalog grant review both pass for the designated service principal.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A data compliance team needs consistent redaction of columns tagged as personal data across hundreds of catalog tables. Its preventative action would be: Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported. The most direct exposure in the current scenario is: Fixing only Azure IAM may leave catalog object access denied while broad grants increase risk.
C:This failure mode belongs mainly to another situation: A finance analyst must read an approved table but was granted broad MODIFY rights at the schema level. Its preventative action would be: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants. The most direct exposure in the current scenario is: Fixing only Azure IAM may leave catalog object access denied while broad grants increase risk.
D:This failure mode belongs mainly to another situation: An engineering pipeline attempts to insert records into a production Delta table using an account with SELECT only. Its preventative action would be: Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants. The most direct exposure in the current scenario is: Fixing only Azure IAM may leave catalog object access denied while broad grants increase risk.
Question 153
A platform architect adopts: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. For this requirement: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. Which rationale MOST directly supports it?
- Compute isolation reduces interference between unrelated application environments and execution libraries.
- Auto-termination choices must reflect continuously running streams differently from one-shot notebooks.
- Concurrency queuing is separate from a single-query execution performance problem.
- Ephemeral task-oriented compute can avoid idle capacity costs while retaining reproducible batch execution.
Explanation
Correct Answer
B:The decisive mechanism is: Auto-termination choices must reflect continuously running streams differently from one-shot notebooks. That explains the selected action: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. In the original scenario: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. The specific unmanaged risk is: A stream may stop unexpectedly and leave event consumption behind its permitted freshness objective. Validate with: A quiet-period rehearsal retains the required streaming operation and subsequent events process without missed offsets.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A notebook pipeline uses a shared cluster with unstable third-party dependencies while a critical finance job needs controlled isolation. Its targeted response is: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions. The current case is governed more directly by: Auto-termination choices must reflect continuously running streams differently from one-shot notebooks.
C:This principle concerns a separate data-engineering condition: A BI warehouse repeatedly slows during morning sign-in peaks even though a single analyst query runs quickly. Its targeted response is: Tune supported SQL warehouse capacity and concurrency scaling based on simultaneous production query measurements. The current case is governed more directly by: Auto-termination choices must reflect continuously running streams differently from one-shot notebooks.
D:This principle concerns a separate data-engineering condition: A nightly batch transformation uses a continuously running all-purpose cluster even though no analyst interacts with the workload between runs. Its targeted response is: Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution. The current case is governed more directly by: Auto-termination choices must reflect continuously running streams differently from one-shot notebooks.
Question 154
A production data team leaves out: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles. Its scenario is: A customer service dashboard must show the last four digits of account identifiers but never full account values. Which failure mode is MOST relevant?
- Direct-path writes can bypass registration and leave unowned storage artifacts.
- An attacker obtaining the repository could invoke Databricks APIs with a broad personal identity.
- Granting SELECT without masking may expose full account identifiers to unauthorized readers.
- Fixing only Azure IAM may leave catalog object access denied while broad grants increase risk.
Explanation
Correct Answer
C:The direct residual exposure is: Granting SELECT without masking may expose full account identifiers to unauthorized readers. The triggering condition is: A customer service dashboard must show the last four digits of account identifiers but never full account values. The omitted safeguard is: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles. This matters because: Column masking can transform sensitive values at query time according to the querying principal. A corrective test would show: Role-based sample queries show masked values for support and exact values only for approved security operators.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A user is granted CREATE TABLE but cannot create an external table at an unregistered cloud path. Its preventative action would be: Configure a supported external location and specific creation privileges rather than bypassing the catalog to write directly. The most direct exposure in the current scenario is: Granting SELECT without masking may expose full account identifiers to unauthorized readers.
B:This failure mode belongs mainly to another situation: A production workload uses a personal access token stored in Git for Databricks REST calls. Its preventative action would be: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. The most direct exposure in the current scenario is: Granting SELECT without masking may expose full account identifiers to unauthorized readers.
D:This failure mode belongs mainly to another situation: A managed identity can read a storage container but a newly created external table is denied in Databricks. Its preventative action would be: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges. The most direct exposure in the current scenario is: Granting SELECT without masking may expose full account identifiers to unauthorized readers.
Question 155
The team chooses: Implement explicit null predicates rather than treating zero and null as equivalent. Its observed issue is: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. What is the strongest technical basis?
- Unpivoting converts a wide repeated-measure structure into a normalized row representation.
- SQL NULL indicates absent or unknown values while numeric zero is a valid value.
- Append is generally simpler for immutable events than key-by-key mutation logic.
- Aggregation alone cannot distinguish valid repeat enrollments from accidental duplicates.
Explanation
Correct Answer
B:The decisive mechanism is: SQL NULL indicates absent or unknown values while numeric zero is a valid value. That explains the selected action: Implement explicit null predicates rather than treating zero and null as equivalent. In the original scenario: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. The specific unmanaged risk is: Conflating zero with missing data hides legitimate stockouts and distorts service metrics. Validate with: A seeded dataset retains zero-quantity items while rows with null quantities follow the documented rule.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A large orders dataset has one column per month but a dashboard expects month-value rows for filtering and grouping. Its targeted response is: Use a compatible unpivot or stack transformation with explicit month and amount columns. The current case is governed more directly by: SQL NULL indicates absent or unknown values while numeric zero is a valid value.
C:This principle concerns a separate data-engineering condition: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. Its targeted response is: Use an incremental append pattern with suitable deduplication when source events cannot change. The current case is governed more directly by: SQL NULL indicates absent or unknown values while numeric zero is a valid value.
D:This principle concerns a separate data-engineering condition: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. Its targeted response is: Validate business keys and choose a deterministic latest-enrollment record before aggregation. The current case is governed more directly by: SQL NULL indicates absent or unknown values while numeric zero is a valid value.
Question 156
During a lakehouse implementation review, engineers observe: A central security team manually adds row masking rules to every department table and new datasets repeatedly lack protection. What is the BEST next action?
- Run a scheduled ownership and grant recertification process using catalog metadata and audit events.
- Transfer ownership through approved governance workflow and review grants after reassignment.
- Create compatible central ABAC policies based on governed classifications and verify inherited coverage.
- Develop an approved role-aware column mask and test its outputs across supported query clients.
Explanation
Correct Answer
C:The most appropriate action is: Create compatible central ABAC policies based on governed classifications and verify inherited coverage. It addresses the stated condition: A central security team manually adds row masking rules to every department table and new datasets repeatedly lack protection. The technical basis is: ABAC can scale consistent data protection across tables matching policy attributes. Without this control, manual protection drift can expose fields on newly created tables before a review. A direct acceptance check is: A newly classified test table receives the prescribed mask and an authorized exception is documented.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A company needs to review table-owner changes and permissions after organizational restructuring. The corresponding measure there would be: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. The stated situation instead calls for: Create compatible central ABAC policies based on governed classifications and verify inherited coverage.
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: Create compatible central ABAC policies based on governed classifications and verify inherited coverage.
D:This alternative primarily addresses a different Azure Databricks problem: A data product stores PII in a shared Delta table but several reports require different masking for each audience. The corresponding measure there would be: Develop an approved role-aware column mask and test its outputs across supported query clients. The stated situation instead calls for: Create compatible central ABAC policies based on governed classifications and verify inherited coverage.
Question 157
An Azure Databricks architect reviews the following problem: A stream writes into an external sink without stable batch identities and causes duplicate side effects on retry. What should the team implement FIRST?
- Use supported streaming or sufficiently frequent incremental CDC with measured end-to-end latency.
- Use a suitable COPY INTO or supported batch ingestion statement with validated format and path options.
- Use Spark-native distributed read and transformation APIs or partition-safe processing.
- Implement idempotent foreachBatch or compatible transactional sink logic keyed by epoch or business identity.
Explanation
Correct Answer
D:The most appropriate action is: Implement idempotent foreachBatch or compatible transactional sink logic keyed by epoch or business identity. It addresses the stated condition: A stream writes into an external sink without stable batch identities and causes duplicate side effects on retry. The technical basis is: Structured Streaming may retry microbatches, so external effects need idempotency. Without this control, retries can duplicate invoices or notifications even if the source checkpoint is correct. A direct acceptance check is: Replaying the same microbatch produces one target effect per business key.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A team selects batch processing for customer account changes though downstream applications require minute-scale freshness. The corresponding measure there would be: Use supported streaming or sufficiently frequent incremental CDC with measured end-to-end latency. The stated situation instead calls for: Implement idempotent foreachBatch or compatible transactional sink logic keyed by epoch or business identity.
B:This alternative primarily addresses a different Azure Databricks problem: An integration performs a one-off initial import of an existing CSV folder into a Delta table. The corresponding measure there would be: Use a suitable COPY INTO or supported batch ingestion statement with validated format and path options. The stated situation instead calls for: Implement idempotent foreachBatch or compatible transactional sink logic keyed by epoch or business identity.
C:This alternative primarily addresses a different Azure Databricks problem: A Python notebook reads a massive table into pandas on the driver before processing data intended for Spark executors. The corresponding measure there would be: Use Spark-native distributed read and transformation APIs or partition-safe processing. The stated situation instead calls for: Implement idempotent foreachBatch or compatible transactional sink logic keyed by epoch or business identity.
Question 158
A Databricks engineer recommends: Use row-filter policies on the governed table and test permitted region entitlements. It responds to: A shared customer table needs dynamic per-region row restrictions but the business refuses duplicating physical datasets. What underlying mechanism BEST explains why?
- Governed descriptive metadata reduces ambiguity and supports correct analytical interpretation.
- Row filters can restrict query results without maintaining separate physical copies by region.
- Column mask policies can enforce context-dependent presentation without duplicating raw PII.
- ABAC can scale consistent data protection across tables matching policy attributes.
Explanation
Correct Answer
B:The decisive mechanism is: Row filters can restrict query results without maintaining separate physical copies by region. That explains the selected action: Use row-filter policies on the governed table and test permitted region entitlements. In the original scenario: A shared customer table needs dynamic per-region row restrictions but the business refuses duplicating physical datasets. The specific unmanaged risk is: Duplicated datasets can diverge or escape synchronized retention and correction policies. Validate with: Queries from two test regions return only their eligible rows from the same table.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A business glossary has table names but no indication of which field is net revenue versus gross sales. Its targeted response is: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. The current case is governed more directly by: Row filters can restrict query results without maintaining separate physical copies by region.
C:This principle concerns a separate data-engineering condition: A data product stores PII in a shared Delta table but several reports require different masking for each audience. Its targeted response is: Develop an approved role-aware column mask and test its outputs across supported query clients. The current case is governed more directly by: Row filters can restrict query results without maintaining separate physical copies by region.
D:This principle concerns a separate data-engineering condition: A central security team manually adds row masking rules to every department table and new datasets repeatedly lack protection. Its targeted response is: Create compatible central ABAC policies based on governed classifications and verify inherited coverage. The current case is governed more directly by: Row filters can restrict query results without maintaining separate physical copies by region.
Question 159
A pipeline owner declines the action: Maintain table and column descriptions in Unity Catalog metadata at creation and during schema changes. The business situation is: Analysts create tables without column comments and the data steward cannot explain monetary units or null semantics. What specific failure can follow?
- Users can unknowingly consume stale aggregates if refresh ownership and schedule are unspecified.
- An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts.
- An ownerless shared view may expose unreviewed columns or become impossible to maintain safely.
- Poorly described fields lead to incorrect joins, unit conversions or disclosure decisions.
Explanation
Correct Answer
D:The direct residual exposure is: Poorly described fields lead to incorrect joins, unit conversions or disclosure decisions. The triggering condition is: Analysts create tables without column comments and the data steward cannot explain monetary units or null semantics. The omitted safeguard is: Maintain table and column descriptions in Unity Catalog metadata at creation and during schema changes. This matters because: Discoverability requires human-readable business metadata in addition to schema types. A corrective test would show: Catalog Explorer shows reviewed descriptions and a sample consumer can identify the column's intended units.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A BI group needs to query a materialized aggregate while the source transaction Delta table changes hourly. Its preventative action would be: Create an eligible materialized view or managed derived table with appropriate refresh and access rules. The most direct exposure in the current scenario is: Poorly described fields lead to incorrect joins, unit conversions or disclosure decisions.
B: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: Poorly described fields lead to incorrect joins, unit conversions or disclosure decisions.
C: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: Poorly described fields lead to incorrect joins, unit conversions or disclosure decisions.
Question 160
A production data platform experiences this condition: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. Which targeted measure should be selected?
- Restrict governed-tag administration and audit changes to protected metadata.
- Configure supported Databricks audit logging and route relevant events to a secured retention destination.
- Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage.
- Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation.
Explanation
Correct Answer
A:The most appropriate action is: Restrict governed-tag administration and audit changes to protected metadata. It addresses the stated condition: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. The technical basis is: Tag-based access control relies on trusted management of the tags themselves. Without this control, unauthorized retagging may neutralize masking or row restrictions on sensitive information. A direct acceptance check is: A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. The corresponding measure there would be: Configure supported Databricks audit logging and route relevant events to a secured retention destination. The stated situation instead calls for: Restrict governed-tag administration and audit changes to protected metadata.
C:This alternative primarily addresses a different Azure Databricks problem: An analyst wants to know which upstream pipeline produced a metric displayed in a board dashboard. The corresponding measure there would be: Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage. The stated situation instead calls for: Restrict governed-tag administration and audit changes to protected metadata.
D:This alternative primarily addresses a different Azure Databricks problem: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. The corresponding measure there would be: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. The stated situation instead calls for: Restrict governed-tag administration and audit changes to protected metadata.