Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 7
Question 60
An operator introduces: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings. The situation is: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. Which validation should be required before signoff?
- Approved regional workspaces access their catalogs while a disallowed workspace fails its access test.
- Catalog Explorer shows reviewed descriptions and a sample consumer can identify the column's intended units.
- An architecture test proves the selected object's refresh and query cost meet defined needs.
- A controlled MERGE and SQL query succeed against the governed Delta table with expected records.
Explanation
Correct Answer
A:The strongest acceptance proof is: Approved regional workspaces access their catalogs while a disallowed workspace fails its access test. It specifically verifies: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings. The original issue was: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. The underlying mechanism is: Catalog separation and workspace access controls can help enforce organizational and geography boundaries. Without it, A broadly shared catalog can expose regulated data to unintended region workspaces.
Incorrect Answers
B:This result would validate a different measure: Maintain table and column descriptions in Unity Catalog metadata at creation and during schema changes. That is relevant to the distinct problem: Analysts create tables without column comments and the data steward cannot explain monetary units or null semantics. Here the acceptance criterion is: Approved regional workspaces access their catalogs while a disallowed workspace fails its access test.
C:This result would validate a different measure: Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities. That is relevant to the distinct problem: A data pipeline creates a physical table for a reporting transformation that would be better maintained as a query definition. Here the acceptance criterion is: Approved regional workspaces access their catalogs while a disallowed workspace fails its access test.
D:This result would validate a different measure: Register the structured dataset as an appropriate managed Delta table rather than treating the volume itself as a SQL table. That is relevant to the distinct problem: A team exposes structured transaction data as files in a volume but wants SQL analytics and ACID MERGE behavior. Here the acceptance criterion is: Approved regional workspaces access their catalogs while a disallowed workspace fails its access test.
Question 61
An implementation skips: Preserve diagnostic events and Spark UI stage evidence before restart where possible. Engineers are observing: An operator restarts a failed Databricks cluster before collecting the Spark executor and driver logs. What consequence is MOST likely?
- Increasing source throughput without repairing processing bottlenecks can worsen queue age.
- Unobserved performance drift can cause the pipeline to miss future delivery windows.
- Restarting a healthy compute resource cannot repair a denied storage credential or table grant.
- A recurring failure may never be diagnosed if its only logs are destroyed repeatedly.
Explanation
Correct Answer
D:The direct residual exposure is: A recurring failure may never be diagnosed if its only logs are destroyed repeatedly. The triggering condition is: An operator restarts a failed Databricks cluster before collecting the Spark executor and driver logs. The omitted safeguard is: Preserve diagnostic events and Spark UI stage evidence before restart where possible. This matters because: Transient cluster restarts can remove evidence necessary to distinguish dependency, data and resource failures. A corrective test would show: A simulated failure yields archived logs, failed stage IDs and a documented root-cause path.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A streaming pipeline's throughput falls although event arrival increases and its input backlog grows over time. Its preventative action would be: Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling. The most direct exposure in the current scenario is: A recurring failure may never be diagnosed if its only logs are destroyed repeatedly.
B:This failure mode belongs mainly to another situation: A job's duration doubles but an administrator sees only its final success status with no phase-level metrics. Its preventative action would be: Collect job timing, task duration and relevant Spark stage metrics in a monitored baseline. The most direct exposure in the current scenario is: A recurring failure may never be diagnosed if its only logs are destroyed repeatedly.
C:This failure mode belongs mainly to another situation: An operations team sees Dataflow-like ingestion failures but cannot identify whether the problem is a Unity Catalog grant or a Spark stage. Its preventative action would be: Correlate error messages, job run IDs, catalog authorization logs and Spark execution evidence before remediation. The most direct exposure in the current scenario is: A recurring failure may never be diagnosed if its only logs are destroyed repeatedly.
Question 62
The team implements: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. The original problem is: A production workload uses a personal access token stored in Git for Databricks REST calls. Which test MOST convincingly demonstrates correctness?
- An approved DDL operation creates the external table at a registered location and an arbitrary path is rejected.
- The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
- Role-based sample queries show masked values for support and exact values only for approved security operators.
- The pipeline executes under a scoped service identity and the old token is revoked and rejected.
Explanation
Correct Answer
D:The strongest acceptance proof is: The pipeline executes under a scoped service identity and the old token is revoked and rejected. It specifically verifies: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. The original issue was: A production workload uses a personal access token stored in Git for Databricks REST calls. The underlying mechanism is: Automation authentication should be auditable, nonpersonal and resistant to repository exposure. Without it, an attacker obtaining the repository could invoke Databricks APIs with a broad personal identity.
Incorrect Answers
A:This result would validate a different measure: Configure a supported external location and specific creation privileges rather than bypassing the catalog to write directly. That is relevant to the distinct problem: A user is granted CREATE TABLE but cannot create an external table at an unregistered cloud path. Here the acceptance criterion is: The pipeline executes under a scoped service identity and the old token is revoked and rejected.
B:This result would validate a different measure: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. That is relevant to the distinct problem: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. Here the acceptance criterion is: The pipeline executes under a scoped service identity and the old token is revoked and rejected.
C:This result would validate a different measure: Apply a supported column mask or ABAC masking rule to the sensitive field and test different roles. That is relevant to the distinct problem: A customer service dashboard must show the last four digits of account identifiers but never full account values. Here the acceptance criterion is: The pipeline executes under a scoped service identity and the old token is revoked and rejected.
Question 63
A platform architect adopts: Expose stable SQL views over a governed base table when only presentation aliases differ. For this requirement: A data product creates multiple physical copies of a curated dimension because teams need different column names. Which rationale MOST directly supports it?
- Data models balance redundancy and query simplicity according to workload requirements.
- Late facts and missing dimension keys require explicit referential handling.
- Views can provide different consumer contracts without unnecessary data duplication.
- Ingestion strategy should match whether source records can be corrected or deleted.
Explanation
Correct Answer
C:The decisive mechanism is: Views can provide different consumer contracts without unnecessary data duplication. That explains the selected action: Expose stable SQL views over a governed base table when only presentation aliases differ. In the original scenario: A data product creates multiple physical copies of a curated dimension because teams need different column names. The specific unmanaged risk is: Duplicating physical dimensions can leave teams on inconsistent updates or retention periods. Validate with: Two views return consistent key rows while their documented alias columns remain stable.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. Its targeted response is: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. The current case is governed more directly by: Views can provide different consumer contracts without unnecessary data duplication.
B:This principle concerns a separate data-engineering condition: A late-arriving purchase refers to a customer identifier whose dimension record has not yet been ingested. Its targeted response is: Define a deliberate unknown-member or late-dimension reconciliation pattern without silently dropping facts. The current case is governed more directly by: Views can provide different consumer contracts without unnecessary data duplication.
D:This principle concerns a separate data-engineering condition: A raw event lake contains append-only records but a developer chooses daily full overwrite of the curated Delta table. Its targeted response is: Choose incremental append or merge based on immutable versus mutable source behavior. The current case is governed more directly by: Views can provide different consumer contracts without unnecessary data duplication.
Question 64
The team chooses: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. Its observed issue is: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. What is the strongest technical basis?
- Object governance is ongoing and must follow organizational role and service identity changes.
- Delta Sharing can provide governed data access without distributing underlying storage account keys.
- Retention policy must account for physical file cleanup as well as logical table content.
- Per-table fine-grained policies do not automatically propagate to unrelated objects.
Explanation
Correct Answer
C:The decisive mechanism is: Retention policy must account for physical file cleanup as well as logical table content. That explains the selected action: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. In the original scenario: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. The specific unmanaged risk is: Premature removal of obsolete files can prevent required time travel or restore operations. Validate with: A controlled historical read succeeds within the mandated window and approved cleanup starts only afterwards.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A company needs to review table-owner changes and permissions after organizational restructuring. Its targeted response is: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. The current case is governed more directly by: Retention policy must account for physical file cleanup as well as logical table content.
B:This principle concerns a separate data-engineering condition: A data-sharing project emails storage keys to an external partner for reading curated Delta results. Its targeted response is: Use Delta Sharing with an authorized recipient, narrowly scoped shares and lifecycle management. The current case is governed more directly by: Retention policy must account for physical file cleanup as well as logical table content.
D: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: Retention policy must account for physical file cleanup as well as logical table content.
Question 65
A solution applies: Join historical dimension rows using business key and validity interval at event time. It addresses: A clickstream fact table is joined to a customer table with multiple status versions but no effective-date condition. Which operational outcome MOST directly verifies success?
- Sample events match exactly one dimension version valid at their event timestamp.
- A timed append comparison meets the freshness and duplicate controls with lower compute consumption.
- Test histories with retries and real re-enrollments produce the approved per-student count.
- Rows with absent country are flagged for resolution and approved true defaults are applied consistently.
Explanation
Correct Answer
A:The strongest acceptance proof is: Sample events match exactly one dimension version valid at their event timestamp. It specifically verifies: Join historical dimension rows using business key and validity interval at event time. The original issue was: A clickstream fact table is joined to a customer table with multiple status versions but no effective-date condition. The underlying mechanism is: Temporal join predicates are needed when a dimension contains multiple valid versions per business key. Without it, A simple key join duplicates click events and misattributes prior users.
Incorrect Answers
B:This result would validate a different measure: Use an incremental append pattern with suitable deduplication when source events cannot change. That is relevant to the distinct problem: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. Here the acceptance criterion is: Sample events match exactly one dimension version valid at their event timestamp.
C:This result would validate a different measure: Validate business keys and choose a deterministic latest-enrollment record before aggregation. That is relevant to the distinct problem: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. Here the acceptance criterion is: Sample events match exactly one dimension version valid at their event timestamp.
D:This result would validate a different measure: Define field-specific missing-value rules and quarantine or enrich unknown values before assigning business meaning. That is relevant to the distinct problem: A customer reference dataset has missing country codes but a pipeline replaces every null with an arbitrary default country. Here the acceptance criterion is: Sample events match exactly one dimension version valid at their event timestamp.
Question 66
A platform architect adopts: Apply the required filters and join conditions before aggregation and validate authorized output groups. For this requirement: An analyst calculates total revenue grouped by country but a join includes countries not approved for reporting. Which rationale MOST directly supports it?
- Deduplication should use meaningful business keys, not arbitrary full-row equality alone.
- Filter placement and join predicates determine which rows contribute to a grouped measure.
- Union operations concatenate rows and require aligned column meanings.
- SQL NULL indicates absent or unknown values while numeric zero is a valid value.
Explanation
Correct Answer
B:The decisive mechanism is: Filter placement and join predicates determine which rows contribute to a grouped measure. That explains the selected action: Apply the required filters and join conditions before aggregation and validate authorized output groups. In the original scenario: An analyst calculates total revenue grouped by country but a join includes countries not approved for reporting. The specific unmanaged risk is: Aggregating unauthorized or irrelevant rows can disclose or distort regional totals. Validate with: A controlled source sample produces exactly the permitted group keys and reconciled sums.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: An incoming orders table contains repeated order IDs because a vendor retransmits the same daily extract. Its targeted response is: Apply a deterministic deduplication rule based on stable order identity and source version before aggregation. The current case is governed more directly by: Filter placement and join predicates determine which rows contribute to a grouped measure.
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: Filter placement and join predicates determine which rows contribute to a grouped measure.
D:This principle concerns a separate data-engineering condition: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. Its targeted response is: Implement explicit null predicates rather than treating zero and null as equivalent. The current case is governed more directly by: Filter placement and join predicates determine which rows contribute to a grouped measure.
Question 67
A production data platform experiences this condition: A daily data job runs twice during an incident and both executions write to the same target. Which targeted measure should be selected?
- Use a supported file-arrival trigger where its prerequisites and source location are compatible.
- Configure appropriate maximum concurrent runs and idempotent target writes to control overlap.
- Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies.
- Configure bounded restarts and alerting with root-cause investigation for repeated failures.
Explanation
Correct Answer
B:The most appropriate action is: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap. It addresses the stated condition: A daily data job runs twice during an incident and both executions write to the same target. The technical basis is: Concurrency management prevents competing executions from corrupting shared mutable state. Without this control, overlapping runs may race to overwrite outputs or duplicate appended records. A direct acceptance check is: A controlled dual-trigger test respects the run limit and produces one correct final target.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A cloud file feed needs a job triggered by arriving files instead of polling every minute. The corresponding measure there would be: Use a supported file-arrival trigger where its prerequisites and source location are compatible. The stated situation instead calls for: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap.
C:This alternative primarily addresses a different Azure Databricks problem: A team assumes that automatic job retries are the same as recovering a failed multi-step run at its last unsuccessful task. The corresponding measure there would be: Choose the appropriate retry and repair-run functionality based on failed-task state and valid dependencies. The stated situation instead calls for: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap.
D:This alternative primarily addresses a different Azure Databricks problem: A continuously running pipeline is scheduled to restart automatically but restart storms consume a growing compute budget. The corresponding measure there would be: Configure bounded restarts and alerting with root-cause investigation for repeated failures. The stated situation instead calls for: Configure appropriate maximum concurrent runs and idempotent target writes to control overlap.
Question 68
A pipeline owner declines the action: Design a task DAG with parallel independent ingestion and an aggregation dependency after both complete. The business situation is: A pipeline uses a single notebook to read four sources sequentially even though two can be processed independently. What specific failure can follow?
- Consumers can query invalid data during the interval before quality checks finish.
- Unnecessary serial execution can extend the critical path beyond the freshness target.
- An early downstream task can publish partial business totals without raising an obvious failure.
- Immediate permanent failure on a brief service outage can miss a delivery SLA.
Explanation
Correct Answer
B:The direct residual exposure is: Unnecessary serial execution can extend the critical path beyond the freshness target. The triggering condition is: A pipeline uses a single notebook to read four sources sequentially even though two can be processed independently. The omitted safeguard is: Design a task DAG with parallel independent ingestion and an aggregation dependency after both complete. This matters because: Parallelism is safe when tasks have no mutual data dependency and the join point is explicit. A corrective test would show: Timing evidence shows independent branches run concurrently and the merge waits for both results.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A workflow writes to production tables before a validation task examines null keys and duplicates. Its preventative action would be: Place validations before publishing and use an atomic cutover or controlled target write. The most direct exposure in the current scenario is: Unnecessary serial execution can extend the critical path beyond the freshness target.
C:This failure mode belongs mainly to another situation: A sales pipeline aggregates gold metrics before the bronze ingestion task finishes and occasionally reports incomplete totals. Its preventative action would be: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed. The most direct exposure in the current scenario is: Unnecessary serial execution can extend the critical path beyond the freshness target.
D:This failure mode belongs mainly to another situation: A batch enrichment task downloads a remote file and sometimes receives transient HTTP 503 responses. Its preventative action would be: Add bounded retries with exponential backoff and observable failure after the retry budget. The most direct exposure in the current scenario is: Unnecessary serial execution can extend the critical path beyond the freshness target.
Question 69
A pipeline owner declines the action: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. The business situation is: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. What specific failure can follow?
- Historical evidence may be lost even when the latest dataset remains complete.
- Accumulated historical grants may give former project teams access to unrelated data products.
- Duplicated datasets can diverge or escape synchronized retention and correction policies.
- An orphaned ownership chain can delay access review or emergency remediation.
Explanation
Correct Answer
A:The direct residual exposure is: Historical evidence may be lost even when the latest dataset remains complete. The triggering condition is: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. The omitted safeguard is: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. This matters because: Ordinary table replacement does not automatically constitute defensible preservation of historical legal records. A corrective test would show: A hold rehearsal retrieves the original protected records and documents preservation scope and access.
Incorrect Answers
B:This failure mode belongs mainly to another situation: A company needs to review table-owner changes and permissions after organizational restructuring. Its preventative action would be: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. The most direct exposure in the current scenario is: Historical evidence may be lost even when the latest dataset remains complete.
C:This failure mode belongs mainly to another situation: A shared customer table needs dynamic per-region row restrictions but the business refuses duplicating physical datasets. Its preventative action would be: Use row-filter policies on the governed table and test permitted region entitlements. The most direct exposure in the current scenario is: Historical evidence may be lost even when the latest dataset remains complete.
D:This failure mode belongs mainly to another situation: An audit asks who owns a catalog table but object ownership still points to an inactive employee. Its preventative action would be: Transfer ownership through approved governance workflow and review grants after reassignment. The most direct exposure in the current scenario is: Historical evidence may be lost even when the latest dataset remains complete.
Question 70
A data product owner adopts: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. The reason is: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. What observed result BEST proves effectiveness?
- An analyst can query approved tables but cannot create a schema without a separate grant.
- Contract tests continue to select documented columns through the published view after a staged schema change.
- A capability test documents supported query and write operations and prevents unsupported mutations.
- A restricted query through the foreign catalog returns current permitted rows and honors source connectivity limits.
Explanation
Correct Answer
C:The strongest acceptance proof is: A capability test documents supported query and write operations and prevents unsupported mutations. It specifically verifies: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. The original issue was: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. The underlying mechanism is: Foreign catalog semantics and connector capabilities differ from native managed Delta table operations. Without it, assuming full DDL or mutation support may cause failed deployments or inadvertent source changes.
Incorrect Answers
A:This result would validate a different measure: Grant precise container-use and object-creation privileges based on actual job roles. That is relevant to the distinct problem: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. Here the acceptance criterion is: A capability test documents supported query and write operations and prevents unsupported mutations.
B: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 capability test documents supported query and write operations and prevents unsupported mutations.
D: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 capability test documents supported query and write operations and prevents unsupported mutations.