Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 43
Question 420
A team omits the recommended measure: Check required parent catalog and schema usage privileges alongside the table SELECT grant. Its environment shows: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. What is the MOST direct residual risk?
- Granting SELECT alone may not make a catalog object usable and lead to excessive troubleshooting grants.
- An employee departure or password rotation can unexpectedly break critical production ingestion.
- Confusing catalog visibility with data authorization can lead to unnecessary sensitive table access.
- Granting SELECT without masking may expose full account identifiers to unauthorized readers.
Explanation
Correct Answer
A:The direct residual exposure is: Granting SELECT alone may not make a catalog object usable and lead to excessive troubleshooting grants. The triggering condition is: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. The omitted safeguard is: Check required parent catalog and schema usage privileges alongside the table SELECT grant. This matters because: Object access can require permission to traverse its parent hierarchy as well as read the child. A corrective test would show: A privilege inspection shows the narrow parent usage grants and the contractor can query only the intended table.
Incorrect Answers
B:This failure mode belongs mainly to another situation: An ETL service principal is granted permissions through a personal employee account that will leave the company. Its preventative action would be: Use a dedicated service principal with scoped Unity Catalog grants and governed credential lifecycle. The most direct exposure in the current scenario is: Granting SELECT alone may not make a catalog object usable and lead to excessive troubleshooting grants.
C:This failure mode belongs mainly to another situation: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. Its preventative action would be: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. The most direct exposure in the current scenario is: Granting SELECT alone may not make a catalog object usable and lead to excessive troubleshooting grants.
D:This failure mode belongs mainly to another situation: A customer service dashboard must show the last four digits of account identifiers but never full account values. Its preventative action would be: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles. The most direct exposure in the current scenario is: Granting SELECT alone may not make a catalog object usable and lead to excessive troubleshooting grants.
Question 421
For this Microsoft DP-750 case: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. Which design or operational response BEST fits?
- Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action.
- Configure expectations with an explicit fail, drop or retention behavior aligned to business severity.
- Define a range expectation with metrics and the approved drop, fail or quarantine disposition.
- Apply schema enforcement with explicit drift handling and alert on incompatible structural changes.
Explanation
Correct Answer
B:The most appropriate action is: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity. It addresses the stated condition: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. The technical basis is: Quality rules require defined operational consequences, not only Boolean expressions. Without this control, unclear expectation handling may allow financial errors to reach gold tables or stop all low-risk events unnecessarily. A direct acceptance check is: Injected critical and noncritical bad rows follow their respective approved actions and emit metrics.
Incorrect Answers
A: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: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity.
C:This alternative primarily addresses a different Azure Databricks problem: A bronze stream sometimes includes ages below zero or above 120 yet the transformation casts every value to integer. The corresponding measure there would be: Define a range expectation with metrics and the approved drop, fail or quarantine disposition. The stated situation instead calls for: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity.
D: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: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity.
Question 422
The recommended measure is: Review deletion-vector behavior, table layout and suitable optimization for the supported runtime. The operational context is: A query on a Delta table slows after a small percentage of rows are deleted but data files are not optimized. Which data engineering concept applies?
- VACUUM removes old physical files, so aggressive cleanup can break valid historical references.
- Concurrent demand peaks can drive queue delays independently of average compute utilization.
- Logical deletes can leave physical layout and scan behavior needing maintenance.
- Centralized telemetry supports durable troubleshooting when ephemeral compute terminates.
Explanation
Correct Answer
C:The decisive mechanism is: Logical deletes can leave physical layout and scan behavior needing maintenance. That explains the selected action: Review deletion-vector behavior, table layout and suitable optimization for the supported runtime. In the original scenario: A query on a Delta table slows after a small percentage of rows are deleted but data files are not optimized. The specific unmanaged risk is: Ignoring metadata and file-layout changes can increase latency even though row counts decline. Validate with: A supported optimization produces matching visible rows and a measured reduction in scanned data.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. Its targeted response is: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. The current case is governed more directly by: Logical deletes can leave physical layout and scan behavior needing maintenance.
B:This principle concerns a separate data-engineering condition: An interactive warehouse has high query queues during the morning but low CPU utilization after lunch. Its targeted response is: Analyze concurrent query load and scaling policies rather than selecting capacity from daily averages. The current case is governed more directly by: Logical deletes can leave physical layout and scan behavior needing maintenance.
D:This principle concerns a separate data-engineering condition: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. Its targeted response is: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention. The current case is governed more directly by: Logical deletes can leave physical layout and scan behavior needing maintenance.
Question 423
A team omits the recommended measure: Issue time-bounded group membership or an approved scoped SELECT grant with an access review. Its environment shows: A data steward wants to grant temporary read access without handing over Unity Catalog ownership of a schema. What is the MOST direct residual risk?
- An object may be available to overprivileged identities in unintended contexts if either boundary is ignored.
- Changing table owner for short-term access can unintentionally enable grant management and destructive changes.
- One missing tenant predicate can expose another customer’s records.
- Confusing catalog visibility with data authorization can lead to unnecessary sensitive table access.
Explanation
Correct Answer
B:The direct residual exposure is: Changing table owner for short-term access can unintentionally enable grant management and destructive changes. The triggering condition is: A data steward wants to grant temporary read access without handing over Unity Catalog ownership of a schema. The omitted safeguard is: Issue time-bounded group membership or an approved scoped SELECT grant with an access review. This matters because: Data access delegation need not transfer administrative ownership of data objects. A corrective test would show: The visiting user reads the designated dataset before expiry and loses access afterwards without ownership changes.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. Its preventative action would be: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. The most direct exposure in the current scenario is: Changing table owner for short-term access can unintentionally enable grant management and destructive changes.
C:This failure mode belongs mainly to another situation: A multi-tenant analytics table relies on application code to append customer_id filtering. Its preventative action would be: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. The most direct exposure in the current scenario is: Changing table owner for short-term access can unintentionally enable grant management and destructive changes.
D:This failure mode belongs mainly to another situation: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. Its preventative action would be: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. The most direct exposure in the current scenario is: Changing table owner for short-term access can unintentionally enable grant management and destructive changes.
Question 424
For this Azure Databricks issue: A file feed introduces an unexpected optional column and the stream fails after the first changed file. Engineers choose: Configure supported schema evolution or rescued-data handling with explicit compatibility review. What acceptance evidence is BEST?
- A controlled extra-column event is either safely evolved or quarantined with an explicit notification.
- A maintenance simulation retains the checkpoint and resumes ingestion from the expected offset.
- A shuffled CDC test results in the correct highest-version value after replay.
- An event batch survives a controlled consumer restart and downstream totals match the expected sample.
Explanation
Correct Answer
A:The strongest acceptance proof is: A controlled extra-column event is either safely evolved or quarantined with an explicit notification. It specifically verifies: Configure supported schema evolution or rescued-data handling with explicit compatibility review. The original issue was: A file feed introduces an unexpected optional column and the stream fails after the first changed file. The underlying mechanism is: Schema drift must be classified as an acceptable extension or a breaking contract change. Without it, ignoring changed source structures can halt ingestion or silently lose fields.
Incorrect Answers
B:This result would validate a different measure: Store checkpoint and schema tracking files in durable protected locations with retention matching the stream lifecycle. That is relevant to the distinct problem: A long-running ingestion job persists its checkpoint in the same temporary folder that daily cleanup deletes. Here the acceptance criterion is: A controlled extra-column event is either safely evolved or quarantined with an explicit notification.
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: A controlled extra-column event is either safely evolved or quarantined with an explicit notification.
D:This result would validate a different measure: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. That is relevant to the distinct problem: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. Here the acceptance criterion is: A controlled extra-column event is either safely evolved or quarantined with an explicit notification.
Question 425
An implementation skips: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. Engineers are observing: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. What consequence is MOST likely?
- Replaying an entire DAG without need can duplicate side effects and increase cost.
- A clock-only trigger can start before the dependency has produced the expected dataset.
- Premature success can start downstream tasks against incomplete writes.
- Unbounded restarts can amplify resource consumption while no useful records are processed.
Explanation
Correct Answer
A:The direct residual exposure is: Replaying an entire DAG without need can duplicate side effects and increase cost. The triggering condition is: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. The omitted safeguard is: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. This matters because: Repair runs and per-task retries address different recovery granularities. A corrective test would show: A failed downstream task is repaired without repeating successful non-idempotent upstream work.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A pipeline must run when an upstream Databricks table is updated but analysts have hardcoded a daily time estimate. Its preventative action would be: Evaluate supported table update triggers or a clear upstream job dependency based on actual availability. The most direct exposure in the current scenario is: Replaying an entire DAG without need can duplicate side effects and increase cost.
C:This failure mode belongs mainly to another situation: A job is successful in the orchestrator but the business target is not updated because the notebook returns before async work completes. Its preventative action would be: Wait for or explicitly verify required external or asynchronous work before reporting task success. The most direct exposure in the current scenario is: Replaying an entire DAG without need can duplicate side effects and increase cost.
D:This failure mode belongs mainly to another situation: A continuously running pipeline is scheduled to restart automatically but restart storms consume a growing compute budget. Its preventative action would be: Configure bounded restarts and alerting with root-cause investigation for repeated failures. The most direct exposure in the current scenario is: Replaying an entire DAG without need can duplicate side effects and increase cost.
Question 426
The following control has NOT been implemented: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. In this case: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. Which exposure remains?
- Confusing catalog visibility with data authorization can lead to unnecessary sensitive table access.
- Changing table owner for short-term access can unintentionally enable grant management and destructive changes.
- A user may bypass the masked presentation by reading the unmasked source table.
- Granting SELECT without masking may expose full account identifiers to unauthorized readers.
Explanation
Correct Answer
C:The direct residual exposure is: A user may bypass the masked presentation by reading the unmasked source table. The triggering condition is: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. The omitted safeguard is: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. This matters because: Security of a view depends on the complete authorization path, not merely its SELECT projection. A corrective test would show: Direct source queries are denied for analysts while the governed view produces the approved masked data.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. Its preventative action would be: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. The most direct exposure in the current scenario is: A user may bypass the masked presentation by reading the unmasked source table.
B:This failure mode belongs mainly to another situation: A data steward wants to grant temporary read access without handing over Unity Catalog ownership of a schema. Its preventative action would be: Issue time-bounded group membership or an approved scoped SELECT grant with an access review. The most direct exposure in the current scenario is: A user may bypass the masked presentation by reading the unmasked source table.
D:This failure mode belongs mainly to another situation: A customer service dashboard must show the last four digits of account identifiers but never full account values. Its preventative action would be: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles. The most direct exposure in the current scenario is: A user may bypass the masked presentation by reading the unmasked source table.
Question 427
A production data platform experiences this condition: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. Which targeted measure should be selected?
- Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI.
- Use idempotent deployment methods or reconcile existing resource IDs before creating replacements.
- Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle.
- Validate API status and returned resource identifiers, then use bounded retries only for transient failures.
Explanation
Correct Answer
C:The most appropriate action is: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. It addresses the stated condition: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. The technical basis is: Source control only provides operational truth when actual resource settings match the approved definition. Without this control, manual post-deployment edits can bypass review and silently change retry or security settings. A direct acceptance check is: A test UI change is flagged and the approved deployment restores the intended configuration.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A team copies Databricks notebooks manually between three workspaces and each uses different hardcoded identifiers. The corresponding measure there would be: Package declarative automation bundle configurations with environment-specific targets and deploy through the supported CLI. The stated situation instead calls for: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle.
B:This alternative primarily addresses a different Azure Databricks problem: A REST deployment script creates duplicate jobs every time CI reruns after a timeout. The corresponding measure there would be: Use idempotent deployment methods or reconcile existing resource IDs before creating replacements. The stated situation instead calls for: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle.
D:This alternative primarily addresses a different Azure Databricks problem: An automation job uses Databricks REST APIs but omits response-code checks and assumes every HTTP request succeeded. The corresponding measure there would be: Validate API status and returned resource identifiers, then use bounded retries only for transient failures. The stated situation instead calls for: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle.
Question 428
A Databricks engineer recommends: Use appropriate table history, schema change records and approved retention/audit evidence rather than relying on memory. It responds to: A shared table includes an old regulated field and the business needs reproducible evidence of when it was removed. What underlying mechanism BEST explains why?
- External sharing must include explicit revocation and monitoring, not only initial provisioning.
- Metadata history and audit trails can support investigation of structure and access changes.
- Security governance requires attributable administrative activity and durable evidence.
- Permission reviews should follow actual securable objects and their dependencies rather than name assumptions.
Explanation
Correct Answer
B:The decisive mechanism is: Metadata history and audit trails can support investigation of structure and access changes. That explains the selected action: Use appropriate table history, schema change records and approved retention/audit evidence rather than relying on memory. In the original scenario: A shared table includes an old regulated field and the business needs reproducible evidence of when it was removed. The specific unmanaged risk is: Deleting a field without documented change history can leave unanswerable regulatory questions. Validate with: The change record ties the removed column to an authorized deployment and preserved evidence.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A Delta Sharing recipient must stop receiving future updates after an agreement expires. Its targeted response is: Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access. The current case is governed more directly by: Metadata history and audit trails can support investigation of structure and access changes.
C:This principle concerns a separate data-engineering condition: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. Its targeted response is: Configure supported Databricks audit logging and route relevant events to a secured retention destination. The current case is governed more directly by: Metadata history and audit trails can support investigation of structure and access changes.
D:This principle concerns a separate data-engineering condition: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. Its targeted response is: Reconcile catalog object identity, lineage and current grants after schema or owner changes. The current case is governed more directly by: Metadata history and audit trails can support investigation of structure and access changes.
Question 429
A production data platform experiences this condition: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. Which targeted measure should be selected?
- Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements.
- Transfer ownership through approved governance workflow and review grants after reassignment.
- Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification.
- Use appropriate table history, schema change records and approved retention/audit evidence rather than relying on memory.
Explanation
Correct Answer
A:The most appropriate action is: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. It addresses the stated condition: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. The technical basis is: Retention policy must account for physical file cleanup as well as logical table content. Without this control, premature removal of obsolete files can prevent required time travel or restore operations. A direct acceptance check is: A controlled historical read succeeds within the mandated window and approved cleanup starts only afterwards.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: An audit asks who owns a catalog table but object ownership still points to an inactive employee. The corresponding measure there would be: Transfer ownership through approved governance workflow and review grants after reassignment. The stated situation instead calls for: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements.
C:This alternative primarily addresses a different Azure Databricks problem: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. The corresponding measure there would be: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. The stated situation instead calls for: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements.
D:This alternative primarily addresses a different Azure Databricks problem: A shared table includes an old regulated field and the business needs reproducible evidence of when it was removed. The corresponding measure there would be: Use appropriate table history, schema change records and approved retention/audit evidence rather than relying on memory. The stated situation instead calls for: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements.
Question 430
For this Microsoft DP-750 case: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. Which design or operational response BEST fits?
- Create an eligible materialized view or managed derived table with appropriate refresh and access rules.
- Check federation connector capabilities and distinguish read-only remote access from supported writable local tables.
- Grant precise container-use and object-creation privileges based on actual job roles.
- Maintain table and column descriptions in Unity Catalog metadata at creation and during schema changes.
Explanation
Correct Answer
C:The most appropriate action is: Grant precise container-use and object-creation privileges based on actual job roles. It addresses the stated condition: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. The technical basis is: Reading a governed object does not imply permission to create or administer peer objects. Without this control, overbroad catalog privileges can let ordinary readers create misleading or unauthorized data products. A direct acceptance check is: An analyst can query approved tables but cannot create a schema without a separate grant.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A BI group needs to query a materialized aggregate while the source transaction Delta table changes hourly. The corresponding measure there would be: Create an eligible materialized view or managed derived table with appropriate refresh and access rules. The stated situation instead calls for: Grant precise container-use and object-creation privileges based on actual job roles.
B:This alternative primarily addresses a different Azure Databricks problem: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. The corresponding measure there would be: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. The stated situation instead calls for: Grant precise container-use and object-creation privileges based on actual job roles.
D:This alternative primarily addresses a different Azure Databricks problem: Analysts create tables without column comments and the data steward cannot explain monetary units or null semantics. The corresponding measure there would be: Maintain table and column descriptions in Unity Catalog metadata at creation and during schema changes. The stated situation instead calls for: Grant precise container-use and object-creation privileges based on actual job roles.