Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 11
Question 100
The design team proposes: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. The situation is: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. Which technical principle justifies the decision?
- Tag-based access control relies on trusted management of the tags themselves.
- Data sharing scope should minimize disclosed fields and rows and specify a refresh contract.
- Ordinary table replacement does not automatically constitute defensible preservation of historical legal records.
- Retention policy must account for physical file cleanup as well as logical table content.
Explanation
Correct Answer
B:The decisive mechanism is: Data sharing scope should minimize disclosed fields and rows and specify a refresh contract. That explains the selected action: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. In the original scenario: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. The specific unmanaged risk is: Sharing raw transaction tables can disclose protected customer attributes unnecessarily. Validate with: A test recipient reads the expected daily aggregate and cannot enumerate underlying detailed transaction records.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. Its targeted response is: Restrict governed-tag administration and audit changes to protected metadata. The current case is governed more directly by: Data sharing scope should minimize disclosed fields and rows and specify a refresh contract.
C:This principle concerns a separate data-engineering condition: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. Its targeted response is: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. The current case is governed more directly by: Data sharing scope should minimize disclosed fields and rows and specify a refresh contract.
D:This principle concerns a separate data-engineering condition: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. Its targeted response is: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. The current case is governed more directly by: Data sharing scope should minimize disclosed fields and rows and specify a refresh contract.
Question 101
The design team proposes: Join historical dimension rows using business key and validity interval at event time. The situation is: A clickstream fact table is joined to a customer table with multiple status versions but no effective-date condition. Which technical principle justifies the decision?
- Temporal join predicates are needed when a dimension contains multiple valid versions per business key.
- MERGE combines inserts and updates atomically against a keyed target.
- Union operations concatenate rows and require aligned column meanings.
- Aggregations require correctly modeled financial direction and data types.
Explanation
Correct Answer
A:The decisive mechanism is: Temporal join predicates are needed when a dimension contains multiple valid versions per business key. That explains the selected action: Join historical dimension rows using business key and validity interval at event time. In the original scenario: A clickstream fact table is joined to a customer table with multiple status versions but no effective-date condition. The specific unmanaged risk is: A simple key join duplicates click events and misattributes prior users. Validate with: Sample events match exactly one dimension version valid at their event timestamp.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A product catalog receives corrections for existing SKUs plus entirely new items on each incremental load. Its targeted response is: Use a Delta MERGE keyed by SKU with appropriate matched-update and not-matched-insert logic. The current case is governed more directly by: Temporal join predicates are needed when a dimension contains multiple valid versions per business key.
C: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: Temporal join predicates are needed when a dimension contains multiple valid versions per business key.
D:This principle concerns a separate data-engineering condition: A daily revenue report double-counts refunds because both debit and credit rows are summed as positive numbers. Its targeted response is: Normalize transaction sign semantics before grouping by business date and customer. The current case is governed more directly by: Temporal join predicates are needed when a dimension contains multiple valid versions per business key.
Question 102
The recommended measure is: Define validated job parameters and propagate them through supported task parameter bindings. The operational context is: A workflow needs to pass a date parameter from a scheduled trigger into all its downstream notebook tasks. Which data engineering concept applies?
- Task success must correspond to the completion of required data side effects, not just function invocation.
- Consistent parameter passing ensures dependent tasks operate on the same business interval.
- Automatic recovery should be limited by failure budgets and should not hide persistent faults.
- Job task state transitions follow dependency and conditional execution rules.
Explanation
Correct Answer
B:The decisive mechanism is: Consistent parameter passing ensures dependent tasks operate on the same business interval. That explains the selected action: Define validated job parameters and propagate them through supported task parameter bindings. In the original scenario: A workflow needs to pass a date parameter from a scheduled trigger into all its downstream notebook tasks. The specific unmanaged risk is: Mixed processing dates across tasks can create unreconciled reports and repeated records. Validate with: Run history records one intended business date and every task publishes that same interval.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A job is successful in the orchestrator but the business target is not updated because the notebook returns before async work completes. Its targeted response is: Wait for or explicitly verify required external or asynchronous work before reporting task success. The current case is governed more directly by: Consistent parameter passing ensures dependent tasks operate on the same business interval.
C:This principle concerns a separate data-engineering condition: A continuously running pipeline is scheduled to restart automatically but restart storms consume a growing compute budget. Its targeted response is: Configure bounded restarts and alerting with root-cause investigation for repeated failures. The current case is governed more directly by: Consistent parameter passing ensures dependent tasks operate on the same business interval.
D:This principle concerns a separate data-engineering condition: A job owner cannot explain why a task skipped execution after a predecessor failed. Its targeted response is: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. The current case is governed more directly by: Consistent parameter passing ensures dependent tasks operate on the same business interval.
Question 103
A production data platform experiences this condition: A reference table stores only the latest airport name and business users explicitly do not need historical values. Which targeted measure should be selected?
- Implement the required SCD Type 1 overwrite with stable business keys and validated updates.
- Use supported Delta table version history and time travel within the documented retention window.
- Enable supported liquid clustering with appropriate keys and run compatible optimization.
- Expose stable SQL views over a governed base table when only presentation aliases differ.
Explanation
Correct Answer
A:The most appropriate action is: Implement the required SCD Type 1 overwrite with stable business keys and validated updates. It addresses the stated condition: A reference table stores only the latest airport name and business users explicitly do not need historical values. The technical basis is: Type 1 dimensions replace nonhistorical descriptive attributes without retaining obsolete versions. Without this control, keeping unnecessary historical rows can produce multiple matches and incorrect lookup joins. A direct acceptance check is: The business key resolves to one current row after an update and no unintended duplicate joins occur.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A business needs to compare two point-in-time table versions during a financial reconciliation. The corresponding measure there would be: Use supported Delta table version history and time travel within the documented retention window. The stated situation instead calls for: Implement the required SCD Type 1 overwrite with stable business keys and validated updates.
C:This alternative primarily addresses a different Azure Databricks problem: A large Delta fact table is filtered primarily on high-cardinality account IDs with changing query patterns. The corresponding measure there would be: Enable supported liquid clustering with appropriate keys and run compatible optimization. The stated situation instead calls for: Implement the required SCD Type 1 overwrite with stable business keys and validated updates.
D:This alternative primarily addresses a different Azure Databricks problem: A data product creates multiple physical copies of a curated dimension because teams need different column names. The corresponding measure there would be: Expose stable SQL views over a governed base table when only presentation aliases differ. The stated situation instead calls for: Implement the required SCD Type 1 overwrite with stable business keys and validated updates.
Question 104
A data product owner adopts: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. The reason is: A multi-tenant analytics table relies on application code to append customer_id filtering. What observed result BEST proves effectiveness?
- The analyst can SELECT the authorized table but cannot UPDATE it or read an unrelated protected table.
- A test account from tenant A cannot retrieve tenant B records through SQL, notebooks or the approved BI route.
- After revocation the vendor principal cannot list or query protected objects while internal jobs remain healthy.
- A storage access test and catalog grant review both pass for the designated service principal.
Explanation
Correct Answer
B:The strongest acceptance proof is: A test account from tenant A cannot retrieve tenant B records through SQL, notebooks or the approved BI route. It specifically verifies: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. The original issue was: A multi-tenant analytics table relies on application code to append customer_id filtering. The underlying mechanism is: Central data-plane access rules reduce reliance on every application path applying tenant filtering. Without it, one missing tenant predicate can expose another customer’s records.
Incorrect Answers
A:This result would validate a different measure: Grant only the required USE and SELECT privileges to the analyst group and inspect inherited grants. That is relevant to the distinct problem: A finance analyst must read an approved table but was granted broad MODIFY rights at the schema level. Here the acceptance criterion is: A test account from tenant A cannot retrieve tenant B records through SQL, notebooks or the approved BI route.
C:This result would validate a different measure: Review and revoke stale grants and any linked service credentials, preserving required internal ownership. That is relevant to the distinct problem: A vendor's service principal was granted global access for a one-month integration and the project ended. Here the acceptance criterion is: A test account from tenant A cannot retrieve tenant B records through SQL, notebooks or the approved BI route.
D:This result would validate a different measure: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges. That is relevant to the distinct problem: A managed identity can read a storage container but a newly created external table is denied in Databricks. Here the acceptance criterion is: A test account from tenant A cannot retrieve tenant B records through SQL, notebooks or the approved BI route.
Question 105
The following control has NOT been implemented: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. In this case: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. Which exposure remains?
- An object may be available to overprivileged identities in unintended contexts if either boundary is ignored.
- A user may bypass the masked presentation by reading the unmasked source table.
- A protected secret can still leak through debug output or unrestricted notebook results.
- A user could retrieve other regions by querying the table without an application filter.
Explanation
Correct Answer
A:The direct residual exposure is: An object may be available to overprivileged identities in unintended contexts if either boundary is ignored. The triggering condition is: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. The omitted safeguard is: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. This matters because: Workspace access scope and principal privileges enforce different aspects of authorization. A corrective test would show: A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. Its preventative action would be: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. The most direct exposure in the current scenario is: An object may be available to overprivileged identities in unintended contexts if either boundary is ignored.
C:This failure mode belongs mainly to another situation: An application uses an external Azure Key Vault secret scope but a notebook prints the secret into task logs. Its preventative action would be: Use supported Databricks secret access with least-privilege scope access and remove secret values from logs. The most direct exposure in the current scenario is: An object may be available to overprivileged identities in unintended contexts if either boundary is ignored.
D:This failure mode belongs mainly to another situation: A user must see only the East region rows of a common sales table while managers see all territories. Its preventative action would be: Configure a tested Unity Catalog row filter or suitable ABAC policy based on the authorized identity. The most direct exposure in the current scenario is: An object may be available to overprivileged identities in unintended contexts if either boundary is ignored.
Question 106
The team chooses: Issue time-bounded group membership or an approved scoped SELECT grant with an access review. Its observed issue is: A data steward wants to grant temporary read access without handing over Unity Catalog ownership of a schema. What is the strongest technical basis?
- Central data-plane access rules reduce reliance on every application path applying tenant filtering.
- Security of a view depends on the complete authorization path, not merely its SELECT projection.
- Data access delegation need not transfer administrative ownership of data objects.
- Workload identities separate automated access from a person's employment and session lifecycle.
Explanation
Correct Answer
C:The decisive mechanism is: Data access delegation need not transfer administrative ownership of data objects. That explains the selected action: Issue time-bounded group membership or an approved scoped SELECT grant with an access review. In the original scenario: A data steward wants to grant temporary read access without handing over Unity Catalog ownership of a schema. The specific unmanaged risk is: Changing table owner for short-term access can unintentionally enable grant management and destructive changes. Validate with: The visiting user reads the designated dataset before expiry and loses access afterwards without ownership changes.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A multi-tenant analytics table relies on application code to append customer_id filtering. Its targeted response is: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. The current case is governed more directly by: Data access delegation need not transfer administrative ownership of data objects.
B:This principle concerns a separate data-engineering condition: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. Its targeted response is: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. The current case is governed more directly by: Data access delegation need not transfer administrative ownership of data objects.
D: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: Data access delegation need not transfer administrative ownership of data objects.
Question 107
A Databricks engineer recommends: Use supported Delta table version history and time travel within the documented retention window. It responds to: A business needs to compare two point-in-time table versions during a financial reconciliation. What underlying mechanism BEST explains why?
- CTAS populates a table at execution time and does not imply continuous synchronization with source.
- Delta version history can provide auditable historical snapshots while underlying files are retained.
- Physical layout should match selective consumer predicates rather than convenience of ingestion.
- Temporal tables describe the validity of state over time rather than only its latest value.
Explanation
Correct Answer
B:The decisive mechanism is: Delta version history can provide auditable historical snapshots while underlying files are retained. That explains the selected action: Use supported Delta table version history and time travel within the documented retention window. In the original scenario: A business needs to compare two point-in-time table versions during a financial reconciliation. The specific unmanaged risk is: Assuming indefinite history can fail once physical file retention expires. Validate with: A controlled historical version query returns the expected prior balance before maintenance removes eligible old files.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A pipeline uses CREATE TABLE AS SELECT for a one-time derived dataset but later assumes the result refreshes automatically. Its targeted response is: Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh. The current case is governed more directly by: Delta version history can provide auditable historical snapshots while underlying files are retained.
C:This principle concerns a separate data-engineering condition: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. Its targeted response is: Reevaluate data layout using representative event-time filters and a suitable clustering key. The current case is governed more directly by: Delta version history can provide auditable historical snapshots while underlying files are retained.
D:This principle concerns a separate data-engineering condition: A historical compliance table must show how account status changed at precise effective intervals. Its targeted response is: Use a temporal history model with nonoverlapping effective-from and effective-to boundaries. The current case is governed more directly by: Delta version history can provide auditable historical snapshots while underlying files are retained.
Question 108
A Databricks engineer recommends: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. It responds to: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. What underlying mechanism BEST explains why?
- Per-table fine-grained policies do not automatically propagate to unrelated objects.
- Governance metadata is useful only when ownership and classification are kept current.
- Technical retention settings and organizational policy need an auditable, consistent lifecycle.
- Permission reviews should follow actual securable objects and their dependencies rather than name assumptions.
Explanation
Correct Answer
C:The decisive mechanism is: Technical retention settings and organizational policy need an auditable, consistent lifecycle. That explains the selected action: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. In the original scenario: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. The specific unmanaged risk is: Old cleanup tasks can destroy files that the revised retention requirement still protects. Validate with: A simulated cleanup retains protected history and an audit maps the new duration to approved settings.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A user creates a column mask on a single table and assumes all tables with the same field name are protected. Its targeted response is: Compare table-level masks against centrally governed ABAC coverage and identify missing assignments. The current case is governed more directly by: Technical retention settings and organizational policy need an auditable, consistent lifecycle.
B:This principle concerns a separate data-engineering condition: A central repository contains schemas with missing column owners and no sensitivity classifications. Its targeted response is: Implement a catalog stewardship process to review metadata and governed tags at dataset publication. The current case is governed more directly by: Technical retention settings and organizational policy need an auditable, consistent lifecycle.
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: Technical retention settings and organizational policy need an auditable, consistent lifecycle.
Question 109
A solution applies: Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling. It addresses: A streaming pipeline's throughput falls although event arrival increases and its input backlog grows over time. Which operational outcome MOST directly verifies success?
- A peak-concurrency replay meets latency and queue targets with recorded cost.
- A representative run shows reduced spill bytes and matching aggregate results with improved runtime.
- A controlled representative load finishes without OOM and output group counts reconcile.
- A peak-load rehearsal stabilizes backlog and keeps end-to-end event age within target.
Explanation
Correct Answer
D:The strongest acceptance proof is: A peak-load rehearsal stabilizes backlog and keeps end-to-end event age within target. It specifically verifies: Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling. The original issue was: A streaming pipeline's throughput falls although event arrival increases and its input backlog grows over time. The underlying mechanism is: Sustained source-to-sink throughput below arrival rate causes accumulating data freshness debt. Without it, increasing source throughput without repairing processing bottlenecks can worsen queue age.
Incorrect Answers
A:This result would validate a different measure: Analyze concurrent query load and scaling policies rather than selecting capacity from daily averages. That is relevant to the distinct problem: An interactive warehouse has high query queues during the morning but low CPU utilization after lunch. Here the acceptance criterion is: A peak-load rehearsal stabilizes backlog and keeps end-to-end event age within target.
B:This result would validate a different measure: Examine shuffle metrics, memory pressure and partition sizing to target the spilling stage. That is relevant to the distinct problem: A large aggregation has repeated shuffle spills to disk even though source scans finish quickly. Here the acceptance criterion is: A peak-load rehearsal stabilizes backlog and keeps end-to-end event age within target.
C:This result would validate a different measure: Profile aggregation key distribution, shuffle partitions and executor memory before choosing a targeted change. That is relevant to the distinct problem: A Spark workload repeatedly fails with executor out-of-memory errors on a high-cardinality groupBy. Here the acceptance criterion is: A peak-load rehearsal stabilizes backlog and keeps end-to-end event age within target.
Question 110
A team omits the recommended measure: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users. Its environment shows: A department wants a self-service sandbox but must prevent users from creating huge unrestricted clusters. What is the MOST direct residual risk?
- An unverified runtime switch may break a previously working production ingestion notebook.
- Leaving an interactive cluster running around the clock accumulates charges unrelated to completed pipeline work.
- Unrestricted cluster creation can create unpredictable spending and inconsistent operational standards.
- An upgrade or runaway task on the shared cluster can compromise finance pipeline availability.
Explanation
Correct Answer
C:The direct residual exposure is: Unrestricted cluster creation can create unpredictable spending and inconsistent operational standards. The triggering condition is: A department wants a self-service sandbox but must prevent users from creating huge unrestricted clusters. The omitted safeguard is: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users. This matters because: Compute policies provide governance boundaries for permissible resource configurations. A corrective test would show: An ordinary user can start an approved small cluster but cannot exceed policy size or runtime limits.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A developer selects a new Databricks Runtime version for production despite an untested JDBC driver dependency. Its preventative action would be: Pin a supported Databricks Runtime version and validate application libraries against it before deployment. The most direct exposure in the current scenario is: Unrestricted cluster creation can create unpredictable spending and inconsistent operational standards.
B:This failure mode belongs mainly to another situation: A nightly batch transformation uses a continuously running all-purpose cluster even though no analyst interacts with the workload between runs. Its preventative action would be: Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution. The most direct exposure in the current scenario is: Unrestricted cluster creation can create unpredictable spending and inconsistent operational standards.
D:This failure mode belongs mainly to another situation: A notebook pipeline uses a shared cluster with unstable third-party dependencies while a critical finance job needs controlled isolation. Its preventative action would be: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions. The most direct exposure in the current scenario is: Unrestricted cluster creation can create unpredictable spending and inconsistent operational standards.