Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 17
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.
Question 161
An operator introduces: Register supported external locations and storage credentials, then define governed external tables. The situation is: A legacy external Delta table points at a cloud location with an unmanaged storage credential stored in notebook text. Which validation should be required before signoff?
- The same deployment command creates objects only in its designated staging or production namespace.
- A restricted query through the foreign catalog returns current permitted rows and honors source connectivity limits.
- Contract tests continue to select documented columns through the published view after a staged schema change.
- A credential audit shows approved external access and no user-readable storage secret in notebook source.
Explanation
Correct Answer
D:The strongest acceptance proof is: A credential audit shows approved external access and no user-readable storage secret in notebook source. It specifically verifies: Register supported external locations and storage credentials, then define governed external tables. The original issue was: A legacy external Delta table points at a cloud location with an unmanaged storage credential stored in notebook text. The underlying mechanism is: External table metadata can be governed even when the underlying object files remain in external storage. Without it, credentials embedded in notebooks can be copied and used outside the intended catalog authorization.
Incorrect Answers
A:This result would validate a different measure: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks. That is relevant to the distinct problem: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. Here the acceptance criterion is: A credential audit shows approved external access and no user-readable storage secret in notebook source.
B:This result would validate a different measure: Create an authorized connection and supported foreign catalog for the external source. That is relevant to the distinct problem: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. Here the acceptance criterion is: A credential audit shows approved external access and no user-readable storage secret in notebook source.
C:This result would validate a different measure: Define a stable contract through managed views and test compatibility before changing source objects. That is relevant to the distinct problem: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. Here the acceptance criterion is: A credential audit shows approved external access and no user-readable storage secret in notebook source.
Question 162
A data engineering team faces this Azure Databricks requirement: A multi-step notebook workflow handles source extraction and final reporting in one cell sequence with no recoverable checkpoints. Which action is MOST appropriate?
- Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution.
- Place validations before publishing and use an atomic cutover or controlled target write.
- Split ingestion, validation and publishing into explicit orchestrated tasks with durable intermediate outputs.
- Write to a staging target, validate row totals and invariants, then perform the approved publication step.
Explanation
Correct Answer
C:The most appropriate action is: Split ingestion, validation and publishing into explicit orchestrated tasks with durable intermediate outputs. It addresses the stated condition: A multi-step notebook workflow handles source extraction and final reporting in one cell sequence with no recoverable checkpoints. The technical basis is: Separating pipeline stages creates observable failure boundaries and supports targeted recovery. Without this control, one late-stage error may force a costly replay of all preceding successful processing. A direct acceptance check is: A simulated final-task failure can be repaired without rerunning already validated upstream ingestion.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. The corresponding measure there would be: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. The stated situation instead calls for: Split ingestion, validation and publishing into explicit orchestrated tasks with durable intermediate outputs.
B:This alternative primarily addresses a different Azure Databricks problem: A workflow writes to production tables before a validation task examines null keys and duplicates. The corresponding measure there would be: Place validations before publishing and use an atomic cutover or controlled target write. The stated situation instead calls for: Split ingestion, validation and publishing into explicit orchestrated tasks with durable intermediate outputs.
D:This alternative primarily addresses a different Azure Databricks problem: A finance transformation writes its output directly into a published table before reconciling totals against the source. The corresponding measure there would be: Write to a staging target, validate row totals and invariants, then perform the approved publication step. The stated situation instead calls for: Split ingestion, validation and publishing into explicit orchestrated tasks with durable intermediate outputs.
Question 163
The design team proposes: Run a supported uniqueness or cardinality validation during the transformation and surface violations. The situation is: A curated account table accidentally contains multiple rows per supposedly unique current account ID. Which technical principle justifies the decision?
- Measurable quality controls need observable outcomes and accounting for rejected data.
- Primary business-key uniqueness is a semantic data-quality invariant even without enforced physical primary keys.
- Valid data type does not guarantee semantic range correctness.
- Quality rules require defined operational consequences, not only Boolean expressions.
Explanation
Correct Answer
B:The decisive mechanism is: Primary business-key uniqueness is a semantic data-quality invariant even without enforced physical primary keys. That explains the selected action: Run a supported uniqueness or cardinality validation during the transformation and surface violations. In the original scenario: A curated account table accidentally contains multiple rows per supposedly unique current account ID. The specific unmanaged risk is: Duplicate current accounts can multiply joins and financial balances. Validate with: A seeded repeated account ID is detected before the curated dataset is marked ready.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A pipeline reports zero failed rows because bad records are silently dropped without any count of what was removed. Its targeted response is: Collect expectation metrics and reconcile input, accepted, quarantined and rejected record counts. The current case is governed more directly by: Primary business-key uniqueness is a semantic data-quality invariant even without enforced physical primary keys.
C:This principle concerns a separate data-engineering condition: A bronze stream sometimes includes ages below zero or above 120 yet the transformation casts every value to integer. Its targeted response is: Define a range expectation with metrics and the approved drop, fail or quarantine disposition. The current case is governed more directly by: Primary business-key uniqueness is a semantic data-quality invariant even without enforced physical primary keys.
D:This principle concerns a separate data-engineering condition: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. Its targeted response is: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity. The current case is governed more directly by: Primary business-key uniqueness is a semantic data-quality invariant even without enforced physical primary keys.
Question 164
The team chooses: Check required parent catalog and schema usage privileges alongside the table SELECT grant. Its observed issue is: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. What is the strongest technical basis?
- Object access can require permission to traverse its parent hierarchy as well as read the child.
- Least privilege includes removing access when the business purpose expires.
- Data access delegation need not transfer administrative ownership of data objects.
- Automation authentication should be auditable, nonpersonal and resistant to repository exposure.
Explanation
Correct Answer
A:The decisive mechanism is: Object access can require permission to traverse its parent hierarchy as well as read the child. That explains the selected action: Check required parent catalog and schema usage privileges alongside the table SELECT grant. In the original scenario: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. The specific unmanaged risk is: Granting SELECT alone may not make a catalog object usable and lead to excessive troubleshooting grants. Validate with: A privilege inspection shows the narrow parent usage grants and the contractor can query only the intended table.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A vendor's service principal was granted global access for a one-month integration and the project ended. Its targeted response is: Review and revoke stale grants and any linked service credentials, preserving required internal ownership. The current case is governed more directly by: Object access can require permission to traverse its parent hierarchy as well as read the child.
C:This principle concerns a separate data-engineering condition: A data steward wants to grant temporary read access without handing over Unity Catalog ownership of a schema. Its targeted response is: Issue time-bounded group membership or an approved scoped SELECT grant with an access review. The current case is governed more directly by: Object access can require permission to traverse its parent hierarchy as well as read the child.
D:This principle concerns a separate data-engineering condition: A production workload uses a personal access token stored in Git for Databricks REST calls. Its targeted response is: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. The current case is governed more directly by: Object access can require permission to traverse its parent hierarchy as well as read the child.
Question 165
A data engineering team faces this Azure Databricks requirement: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. Which action is MOST appropriate?
- Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution.
- Parameterize environment-specific paths, catalogs and identities through governed deployment configuration.
- Design a separate failure-handling or completion branch with the supported run-if logic for alerts and cleanup.
- Add bounded retries with exponential backoff and observable failure after the retry budget.
Explanation
Correct Answer
A:The most appropriate action is: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. It addresses the stated condition: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. The technical basis is: A recoverable pipeline should produce the same logical state after an equivalent retry. Without this control, at-least-once task execution can duplicate side effects when outputs are append-only. A direct acceptance check is: Two executions of the same input batch yield one approved current record per order.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A multi-team notebook uses hard-coded workspace names and credentials, making the same pipeline fail in staging. The corresponding measure there would be: Parameterize environment-specific paths, catalogs and identities through governed deployment configuration. The stated situation instead calls for: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution.
C:This alternative primarily addresses a different Azure Databricks problem: A source task fails yet the monitoring task never executes because all downstream tasks require upstream success. The corresponding measure there would be: Design a separate failure-handling or completion branch with the supported run-if logic for alerts and cleanup. The stated situation instead calls for: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution.
D:This alternative primarily addresses a different Azure Databricks problem: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. The corresponding measure there would be: Add bounded retries with exponential backoff and observable failure after the retry budget. The stated situation instead calls for: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution.
Question 166
The recommended measure is: Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported. The operational context is: A data compliance team needs consistent redaction of columns tagged as personal data across hundreds of catalog tables. Which data engineering concept applies?
- Attribute-based policies can apply common decisions at scale rather than managing every table individually.
- Workload identities separate automated access from a person's employment and session lifecycle.
- Workspace access scope and principal privileges enforce different aspects of authorization.
- Data access delegation need not transfer administrative ownership of data objects.
Explanation
Correct Answer
A:The decisive mechanism is: Attribute-based policies can apply common decisions at scale rather than managing every table individually. That explains the selected action: Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported. In the original scenario: A data compliance team needs consistent redaction of columns tagged as personal data across hundreds of catalog tables. The specific unmanaged risk is: Manual per-table rules can miss newly created columns and expose sensitive values. Validate with: A new tagged test column receives the required masking behavior without a separate manual table exception.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: An ETL service principal is granted permissions through a personal employee account that will leave the company. Its targeted response is: Use a dedicated service principal with scoped Unity Catalog grants and governed credential lifecycle. The current case is governed more directly by: Attribute-based policies can apply common decisions at scale rather than managing every table individually.
C:This principle concerns a separate data-engineering condition: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. Its targeted response is: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. The current case is governed more directly by: Attribute-based policies can apply common decisions at scale rather than managing every table individually.
D:This principle concerns a separate data-engineering condition: A data steward wants to grant temporary read access without handing over Unity Catalog ownership of a schema. Its targeted response is: Issue time-bounded group membership or an approved scoped SELECT grant with an access review. The current case is governed more directly by: Attribute-based policies can apply common decisions at scale rather than managing every table individually.
Question 167
A Databricks engineer recommends: Write to a staging target, validate row totals and invariants, then perform the approved publication step. It responds to: A finance transformation writes its output directly into a published table before reconciling totals against the source. What underlying mechanism BEST explains why?
- Staging plus validation separates construction of data from its declaration as trusted.
- Retryable transient failures should be distinguished from permanent data or permission errors.
- Notebooks and declarative pipelines serve different orchestration and transformation patterns.
- A recoverable pipeline should produce the same logical state after an equivalent retry.
Explanation
Correct Answer
A:The decisive mechanism is: Staging plus validation separates construction of data from its declaration as trusted. That explains the selected action: Write to a staging target, validate row totals and invariants, then perform the approved publication step. In the original scenario: A finance transformation writes its output directly into a published table before reconciling totals against the source. The specific unmanaged risk is: A bad transformation may make a broken dataset immediately visible to consumers. Validate with: A seeded mismatch prevents cutover and the prior certified table remains queryable.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. Its targeted response is: Add bounded retries with exponential backoff and observable failure after the retry budget. The current case is governed more directly by: Staging plus validation separates construction of data from its declaration as trusted.
C:This principle concerns a separate data-engineering condition: An ad hoc machine-learning preparation task has complex custom Python orchestration and no declarative table graph. Its targeted response is: Select a notebook task within Lakeflow Jobs when procedural control and custom libraries fit the requirements. The current case is governed more directly by: Staging plus validation separates construction of data from its declaration as trusted.
D:This principle concerns a separate data-engineering condition: A nightly pipeline rerun appends the same orders to the target and doubles totals after an operator presses Retry. Its targeted response is: Use idempotent writes or MERGE keyed by stable order identity for repeatable task execution. The current case is governed more directly by: Staging plus validation separates construction of data from its declaration as trusted.
Question 168
During a lakehouse implementation review, engineers observe: A curated account table accidentally contains multiple rows per supposedly unique current account ID. What is the BEST next action?
- Apply schema enforcement with explicit drift handling and alert on incompatible structural changes.
- Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action.
- Run a supported uniqueness or cardinality validation during the transformation and surface violations.
- Configure expectations with an explicit fail, drop or retention behavior aligned to business severity.
Explanation
Correct Answer
C:The most appropriate action is: Run a supported uniqueness or cardinality validation during the transformation and surface violations. It addresses the stated condition: A curated account table accidentally contains multiple rows per supposedly unique current account ID. The technical basis is: Primary business-key uniqueness is a semantic data-quality invariant even without enforced physical primary keys. Without this control, duplicate current accounts can multiply joins and financial balances. A direct acceptance check is: A seeded repeated account ID is detected before the curated dataset is marked ready.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A source API changes a quantity from integer to nested JSON and the pipeline silently produces nulls downstream. The corresponding measure there would be: Apply schema enforcement with explicit drift handling and alert on incompatible structural changes. The stated situation instead calls for: Run a supported uniqueness or cardinality validation during the transformation and surface violations.
B:This alternative primarily addresses a different Azure Databricks problem: An event pipeline must reject rows with a null transaction ID, but the data engineer checks only the row count after load. The corresponding measure there would be: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action. The stated situation instead calls for: Run a supported uniqueness or cardinality validation during the transformation and surface violations.
D:This alternative primarily addresses a different Azure Databricks problem: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. The corresponding measure there would be: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity. The stated situation instead calls for: Run a supported uniqueness or cardinality validation during the transformation and surface violations.
Question 169
A production data platform experiences this condition: An administrator attaches a row-filter function that returns errors for unauthorized query contexts and treats the issue as data corruption. Which targeted measure should be selected?
- Replace committed personal credentials with supported workload authentication and revoke exposed tokens.
- Use a dedicated service principal with scoped Unity Catalog grants and governed credential lifecycle.
- Revoke inappropriate base-table access and publish only the authorized view or policy-governed object.
- Test the identity-aware filter function, its permissions and supported execution context on representative queries.
Explanation
Correct Answer
D:The most appropriate action is: Test the identity-aware filter function, its permissions and supported execution context on representative queries. It addresses the stated condition: An administrator attaches a row-filter function that returns errors for unauthorized query contexts and treats the issue as data corruption. The technical basis is: Fine-grained security functions are part of the query execution path and can affect availability. Without this control, A broken policy function may deny intended users or expose inconsistent query results if bypassed. A direct acceptance check is: Approved and disallowed identities receive the expected records without filter execution errors.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A production workload uses a personal access token stored in Git for Databricks REST calls. The corresponding measure there would be: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. The stated situation instead calls for: Test the identity-aware filter function, its permissions and supported execution context on representative queries.
B: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: Test the identity-aware filter function, its permissions and supported execution context on representative queries.
C:This alternative primarily addresses a different Azure Databricks problem: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. The corresponding measure there would be: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. The stated situation instead calls for: Test the identity-aware filter function, its permissions and supported execution context on representative queries.
Question 170
A platform architect adopts: Specify the stream watermark and an explicit closeout readiness condition before running downstream aggregation. For this requirement: A streaming process depends on a downstream batch closeout but no one defines whether it should wait for the latest watermark. Which rationale MOST directly supports it?
- Orchestration may need error paths that execute regardless of normal success dependencies.
- Task-level repair reduces unnecessary recomputation while preserving dependency correctness.
- Stream progress is not synonymous with completeness for a business reporting interval.
- Declarative pipelines express table dependencies and data quality rules without bespoke notebook orchestration.
Explanation
Correct Answer
C:The decisive mechanism is: Stream progress is not synonymous with completeness for a business reporting interval. That explains the selected action: Specify the stream watermark and an explicit closeout readiness condition before running downstream aggregation. In the original scenario: A streaming process depends on a downstream batch closeout but no one defines whether it should wait for the latest watermark. The specific unmanaged risk is: A downstream report can close before late but permitted events are incorporated. Validate with: A controlled late-event test updates the interval before its approved closeout and leaves later events for correction.
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: Stream progress is not synonymous with completeness for a business reporting interval.
B:This principle concerns a separate data-engineering condition: A bulk repair executes all pipeline tasks again even when only the final reporting notebook failed. Its targeted response is: Separate tasks and use the supported repair-run workflow at the failed stage when dependencies remain valid. The current case is governed more directly by: Stream progress is not synonymous with completeness for a business reporting interval.
D:This principle concerns a separate data-engineering condition: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. Its targeted response is: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. The current case is governed more directly by: Stream progress is not synonymous with completeness for a business reporting interval.