Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 2
Question 10
For this Azure Databricks issue: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. Engineers choose: Create an authorized connection and supported foreign catalog for the external source. What acceptance evidence is BEST?
- A restricted query through the foreign catalog returns current permitted rows and honors source connectivity limits.
- An architecture test proves the selected object's refresh and query cost meet defined needs.
- An analyst can query approved tables but cannot create a schema without a separate grant.
- Approved regional workspaces access their catalogs while a disallowed workspace fails its access test.
Explanation
Correct Answer
A:The strongest acceptance proof is: A restricted query through the foreign catalog returns current permitted rows and honors source connectivity limits. It specifically verifies: Create an authorized connection and supported foreign catalog for the external source. The original issue was: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. The underlying mechanism is: Lakehouse Federation lets governed queries access supported external systems through a connection abstraction. Without it, copying the whole remote source for a narrow lookup can create unnecessary latency, duplication and privacy exposure.
Incorrect Answers
B: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: A restricted query through the foreign catalog returns current permitted rows and honors source connectivity limits.
C: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 restricted query through the foreign catalog returns current permitted rows and honors source connectivity limits.
D:This result would validate a different measure: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings. That is relevant to the distinct problem: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. Here the acceptance criterion is: A restricted query through the foreign catalog returns current permitted rows and honors source connectivity limits.
Question 11
A data product owner adopts: Pin package and runtime versions in the governed release artifact and record its dependency manifest. The reason is: A team cannot reproduce a prior release because package versions are resolved dynamically during deployment. What observed result BEST proves effectiveness?
- A rehearsed rollback restores a prior tested bundle and recovers the expected job definitions.
- Rebuilding the prior release resolves identical pinned versions and passes the saved regression suite.
- Deployment plans show the intended trigger for each target and a test job fires at the correct interval.
- A test UI change is flagged and the approved deployment restores the intended configuration.
Explanation
Correct Answer
B:The strongest acceptance proof is: Rebuilding the prior release resolves identical pinned versions and passes the saved regression suite. It specifically verifies: Pin package and runtime versions in the governed release artifact and record its dependency manifest. The original issue was: A team cannot reproduce a prior release because package versions are resolved dynamically during deployment. The underlying mechanism is: Reproducible deployments require versioned execution dependencies as well as application code. Without it, the same Git commit may run differently after a dependency's incompatible update.
Incorrect Answers
A:This result would validate a different measure: Tag and retain approved bundle releases and document a verified redeploy or rollback procedure. That is relevant to the distinct problem: An operations group wants to roll back a broken Lakeflow workflow but keeps no previous package version. Here the acceptance criterion is: Rebuilding the prior release resolves identical pinned versions and passes the saved regression suite.
C:This result would validate a different measure: Validate per-target bundle variable resolution and compare rendered job definitions before deployment. That is relevant to the distinct problem: A data engineer updates a bundled job trigger but another environment's deployment silently uses the wrong schedule. Here the acceptance criterion is: Rebuilding the prior release resolves identical pinned versions and passes the saved regression suite.
D:This result would validate a different measure: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. That is relevant to the distinct problem: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. Here the acceptance criterion is: Rebuilding the prior release resolves identical pinned versions and passes the saved regression suite.
Question 12
A team omits the recommended measure: Choose incremental append or merge based on immutable versus mutable source behavior. Its environment shows: A raw event lake contains append-only records but a developer chooses daily full overwrite of the curated Delta table. What is the MOST direct residual risk?
- Duplicate dimension keys can inflate sums when each fact joins more than one dimension row.
- Poorly chosen keys increase full scans and maintenance overhead as traffic grows.
- Directly rewriting CSV in place can expose partial updates and inconsistent reader results.
- Unnecessary overwrites increase compute cost and can cause data loss during partial reruns.
Explanation
Correct Answer
D:The direct residual exposure is: Unnecessary overwrites increase compute cost and can cause data loss during partial reruns. The triggering condition is: A raw event lake contains append-only records but a developer chooses daily full overwrite of the curated Delta table. The omitted safeguard is: Choose incremental append or merge based on immutable versus mutable source behavior. This matters because: Ingestion strategy should match whether source records can be corrected or deleted. A corrective test would show: Two successive batches load only new records while preserved history and counts reconcile.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A finance dashboard needs monthly revenue by customer and must join customer dimensions without multiplying facts. Its preventative action would be: Design a conformed star schema with explicit fact grain and unique dimension keys. The most direct exposure in the current scenario is: Unnecessary overwrites increase compute cost and can cause data loss during partial reruns.
B:This failure mode belongs mainly to another situation: A query repeatedly filters by customer, date and product but the physical data design was selected without query-profile evidence. Its preventative action would be: Compare selective filter patterns and data-skipping statistics before committing partition and clustering keys. The most direct exposure in the current scenario is: Unnecessary overwrites increase compute cost and can cause data loss during partial reruns.
C:This failure mode belongs mainly to another situation: A reporting team stores frequent updates in raw CSV files and expects atomic MERGE and historical time travel. Its preventative action would be: Use a managed Delta table for transactional updates and controlled schema evolution. The most direct exposure in the current scenario is: Unnecessary overwrites increase compute cost and can cause data loss during partial reruns.
Question 13
The team implements: Develop an approved role-aware column mask and test its outputs across supported query clients. The original problem is: A data product stores PII in a shared Delta table but several reports require different masking for each audience. Which test MOST convincingly demonstrates correctness?
- Authorized privacy reviewers see full test values while ordinary report roles see only permitted redactions.
- The recertification report identifies owners, changed grants and approved remediation evidence.
- A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
- A simulated cleanup retains protected history and an audit maps the new duration to approved settings.
Explanation
Correct Answer
A:The strongest acceptance proof is: Authorized privacy reviewers see full test values while ordinary report roles see only permitted redactions. It specifically verifies: Develop an approved role-aware column mask and test its outputs across supported query clients. The original issue was: A data product stores PII in a shared Delta table but several reports require different masking for each audience. The underlying mechanism is: Column mask policies can enforce context-dependent presentation without duplicating raw PII. Without it, independent report-level masking may be bypassed by direct SQL access to the source.
Incorrect Answers
B:This result would validate a different measure: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. That is relevant to the distinct problem: A company needs to review table-owner changes and permissions after organizational restructuring. Here the acceptance criterion is: Authorized privacy reviewers see full test values while ordinary report roles see only permitted redactions.
C:This result would validate a different measure: Restrict governed-tag administration and audit changes to protected metadata. That is relevant to the distinct problem: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. Here the acceptance criterion is: Authorized privacy reviewers see full test values while ordinary report roles see only permitted redactions.
D:This result would validate a different measure: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. That is relevant to the distinct problem: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. Here the acceptance criterion is: Authorized privacy reviewers see full test values while ordinary report roles see only permitted redactions.
Question 14
The team implements: Pin a supported Databricks Runtime version and validate application libraries against it before deployment. The original problem is: A developer selects a new Databricks Runtime version for production despite an untested JDBC driver dependency. Which test MOST convincingly demonstrates correctness?
- A staging run on the proposed runtime loads the required JDBC driver and reproduces validated output.
- A representative run measures total cost and elapsed time, including initialization, and meets the freshness budget.
- Clean-environment executions install the approved versions and return matching deterministic results.
- Load tests for normal and month-end volumes satisfy runtime targets without exceeding the approved worker ceiling.
Explanation
Correct Answer
A:The strongest acceptance proof is: A staging run on the proposed runtime loads the required JDBC driver and reproduces validated output. It specifically verifies: Pin a supported Databricks Runtime version and validate application libraries against it before deployment. The original issue was: A developer selects a new Databricks Runtime version for production despite an untested JDBC driver dependency. The underlying mechanism is: Spark and runtime upgrades can change supported APIs, dependency versions and execution behavior. Without it, an unverified runtime switch may break a previously working production ingestion notebook.
Incorrect Answers
B:This result would validate a different measure: Separate the small validation into an eligible lightweight or serverless task and measure total end-to-end runtime. That is relevant to the distinct problem: A data team uses a high-power job cluster for a low-volume data-quality check that spends most runtime starting the cluster. Here the acceptance criterion is: A staging run on the proposed runtime loads the required JDBC driver and reproduces validated output.
C:This result would validate a different measure: Record and pin supported package versions in the workload deployment specification and test reproducibility. That is relevant to the distinct problem: A notebook workflow imports a Python package without pinning its version, producing different results after an environment update. Here the acceptance criterion is: A staging run on the proposed runtime loads the required JDBC driver and reproduces validated output.
D:This result would validate a different measure: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. That is relevant to the distinct problem: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. Here the acceptance criterion is: A staging run on the proposed runtime loads the required JDBC driver and reproduces validated output.
Question 15
A production data team leaves out: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity. Its scenario is: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. Which failure mode is MOST relevant?
- Null business keys can enter Delta targets and make updates or joins nondeterministic.
- A seemingly successful load can conceal a growing upstream data-loss problem.
- Silently coercing a breaking type can erase measurable values while a job appears successful.
- Unclear expectation handling may allow financial errors to reach gold tables or stop all low-risk events unnecessarily.
Explanation
Correct Answer
D:The direct residual exposure is: Unclear expectation handling may allow financial errors to reach gold tables or stop all low-risk events unnecessarily. The triggering condition is: A Lakeflow pipeline has a quality rule but nobody has decided whether invalid transactions should stop publishing. The omitted safeguard is: Configure expectations with an explicit fail, drop or retention behavior aligned to business severity. This matters because: Quality rules require defined operational consequences, not only Boolean expressions. A corrective test would show: Injected critical and noncritical bad rows follow their respective approved actions and emit metrics.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An event pipeline must reject rows with a null transaction ID, but the data engineer checks only the row count after load. Its preventative action would be: Enforce a NOT NULL constraint or pipeline expectation on the transaction ID with a defined failure action. The most direct exposure in the current scenario is: Unclear expectation handling may allow financial errors to reach gold tables or stop all low-risk events unnecessarily.
B:This failure mode belongs mainly to another situation: A pipeline reports zero failed rows because bad records are silently dropped without any count of what was removed. Its preventative action would be: Collect expectation metrics and reconcile input, accepted, quarantined and rejected record counts. The most direct exposure in the current scenario is: Unclear expectation handling may allow financial errors to reach gold tables or stop all low-risk events unnecessarily.
C:This failure mode belongs mainly to another situation: A source API changes a quantity from integer to nested JSON and the pipeline silently produces nulls downstream. Its preventative action would be: Apply schema enforcement with explicit drift handling and alert on incompatible structural changes. The most direct exposure in the current scenario is: Unclear expectation handling may allow financial errors to reach gold tables or stop all low-risk events unnecessarily.
Question 16
A platform architect adopts: Create environment-specific Unity Catalog catalogs or schemas and enforce clear ownership and naming conventions. For this requirement: Production and development teams create identically named data objects in one catalog and accidentally overwrite test tables. Which rationale MOST directly supports it?
- Catalog and schema hierarchy can isolate environments while making object ownership and purpose explicit.
- The object type should reflect whether data is computed on read or persisted and maintained.
- Metadata definitions, locations and privileges must align after a table lifecycle transition.
- Abstraction views can separate a consumer-facing contract from internal physical table evolution.
Explanation
Correct Answer
A:The decisive mechanism is: Catalog and schema hierarchy can isolate environments while making object ownership and purpose explicit. That explains the selected action: Create environment-specific Unity Catalog catalogs or schemas and enforce clear ownership and naming conventions. In the original scenario: Production and development teams create identically named data objects in one catalog and accidentally overwrite test tables. The specific unmanaged risk is: An unqualified table reference may redirect a production job to a developer's test dataset. Validate with: Production jobs resolve fully qualified names and fail safely when pointed at a nonproduction catalog.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A data pipeline creates a physical table for a reporting transformation that would be better maintained as a query definition. Its targeted response is: Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities. The current case is governed more directly by: Catalog and schema hierarchy can isolate environments while making object ownership and purpose explicit.
C:This principle concerns a separate data-engineering condition: A managed Delta table is migrated to external storage but the team does not update table registration or grant scopes. Its targeted response is: Recreate or update supported external table registration using an approved location and correct access controls. The current case is governed more directly by: Catalog and schema hierarchy can isolate environments while making object ownership and purpose explicit.
D:This principle concerns a separate data-engineering condition: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. Its targeted response is: Define a stable contract through managed views and test compatibility before changing source objects. The current case is governed more directly by: Catalog and schema hierarchy can isolate environments while making object ownership and purpose explicit.
Question 17
The design team proposes: Maintain table and column descriptions in Unity Catalog metadata at creation and during schema changes. The situation is: Analysts create tables without column comments and the data steward cannot explain monetary units or null semantics. Which technical principle justifies the decision?
- Catalog separation and workspace access controls can help enforce organizational and geography boundaries.
- Discoverability requires human-readable business metadata in addition to schema types.
- Lakehouse Federation lets governed queries access supported external systems through a connection abstraction.
- Explicit namespace resolution makes deployment deterministic across different workspaces.
Explanation
Correct Answer
B:The decisive mechanism is: Discoverability requires human-readable business metadata in addition to schema types. That explains the selected action: Maintain table and column descriptions in Unity Catalog metadata at creation and during schema changes. In the original scenario: Analysts create tables without column comments and the data steward cannot explain monetary units or null semantics. The specific unmanaged risk is: Poorly described fields lead to incorrect joins, unit conversions or disclosure decisions. Validate with: Catalog Explorer shows reviewed descriptions and a sample consumer can identify the column's intended units.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. Its targeted response is: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings. The current case is governed more directly by: Discoverability requires human-readable business metadata in addition to schema types.
C:This principle concerns a separate data-engineering condition: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. Its targeted response is: Create an authorized connection and supported foreign catalog for the external source. The current case is governed more directly by: Discoverability requires human-readable business metadata in addition to schema types.
D:This principle concerns a separate data-engineering condition: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. Its targeted response is: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks. The current case is governed more directly by: Discoverability requires human-readable business metadata in addition to schema types.
Question 18
The recommended measure is: Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh. The operational context is: A pipeline uses CREATE TABLE AS SELECT for a one-time derived dataset but later assumes the result refreshes automatically. Which data engineering concept applies?
- A star schema separates measurable events from descriptive dimensions and controls join cardinality.
- Data models balance redundancy and query simplicity according to workload requirements.
- Type 1 dimensions replace nonhistorical descriptive attributes without retaining obsolete versions.
- CTAS populates a table at execution time and does not imply continuous synchronization with source.
Explanation
Correct Answer
D:The decisive mechanism is: CTAS populates a table at execution time and does not imply continuous synchronization with source. That explains the selected action: Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh. In the original scenario: A pipeline uses CREATE TABLE AS SELECT for a one-time derived dataset but later assumes the result refreshes automatically. The specific unmanaged risk is: Dashboards can become stale when an initial table snapshot is mistaken for a live derived view. Validate with: A source update changes the target only through the planned refresh mechanism and produces a recorded watermark.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A finance dashboard needs monthly revenue by customer and must join customer dimensions without multiplying facts. Its targeted response is: Design a conformed star schema with explicit fact grain and unique dimension keys. The current case is governed more directly by: CTAS populates a table at execution time and does not imply continuous synchronization with source.
B: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: CTAS populates a table at execution time and does not imply continuous synchronization with source.
C:This principle concerns a separate data-engineering condition: A reference table stores only the latest airport name and business users explicitly do not need historical values. Its targeted response is: Implement the required SCD Type 1 overwrite with stable business keys and validated updates. The current case is governed more directly by: CTAS populates a table at execution time and does not imply continuous synchronization with source.
Question 19
A data product owner adopts: Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution. The reason is: A nightly batch transformation uses a continuously running all-purpose cluster even though no analyst interacts with the workload between runs. What observed result BEST proves effectiveness?
- A forced restart of interactive compute leaves the scheduled production task unaffected.
- The scheduled job completes within its service objective and compute billing shows no unattended idle cluster hours.
- Permission tests show approved analysts run their notebooks while unauthorized cluster policy edits and installs fail.
- A test upgrade on the interactive cluster does not change the isolated finance job's dependency versions or results.
Explanation
Correct Answer
B:The strongest acceptance proof is: The scheduled job completes within its service objective and compute billing shows no unattended idle cluster hours. It specifically verifies: Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution. The original issue was: A nightly batch transformation uses a continuously running all-purpose cluster even though no analyst interacts with the workload between runs. The underlying mechanism is: Ephemeral task-oriented compute can avoid idle capacity costs while retaining reproducible batch execution. Without it, leaving an interactive cluster running around the clock accumulates charges unrelated to completed pipeline work.
Incorrect Answers
A:This result would validate a different measure: Define a job-owned execution identity and eligible task compute separate from ad hoc analyst cluster lifecycle. That is relevant to the distinct problem: A scheduled ETL run uses shared analyst compute and fails whenever the cluster owner restarts a notebook session. Here the acceptance criterion is: The scheduled job completes within its service objective and compute billing shows no unattended idle cluster hours.
C:This result would validate a different measure: Apply suitable compute access modes, policies and entitlements that restrict who can attach or modify shared compute. That is relevant to the distinct problem: A multi-team interactive cluster permits users to attach arbitrary unapproved libraries and run notebooks under broad shared privileges. Here the acceptance criterion is: The scheduled job completes within its service objective and compute billing shows no unattended idle cluster hours.
D:This result would validate a different measure: Run the finance job on dedicated supported job compute with its own pinned libraries and permissions. That is relevant to the distinct problem: A notebook pipeline uses a shared cluster with unstable third-party dependencies while a critical finance job needs controlled isolation. Here the acceptance criterion is: The scheduled job completes within its service objective and compute billing shows no unattended idle cluster hours.
Question 20
A team omits the recommended measure: Implement explicit null predicates rather than treating zero and null as equivalent. Its environment shows: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. What is the MOST direct residual risk?
- Blindly broadcasting a large table can exhaust executor memory while unnecessary shuffles slow joins.
- Blind append creates multiple current versions and breaks consumer joins.
- Refund amounts treated as sales inflate net revenue even when record counts match.
- Conflating zero with missing data hides legitimate stockouts and distorts service metrics.
Explanation
Correct Answer
D:The direct residual exposure is: Conflating zero with missing data hides legitimate stockouts and distorts service metrics. The triggering condition is: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. The omitted safeguard is: Implement explicit null predicates rather than treating zero and null as equivalent. This matters because: SQL NULL indicates absent or unknown values while numeric zero is a valid value. A corrective test would show: A seeded dataset retains zero-quantity items while rows with null quantities follow the documented rule.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A pipeline joins a huge fact table with a tiny dimension and a normal shuffle join creates excessive network traffic. Its preventative action would be: Evaluate a suitable broadcast join based on measured dimension size and Spark execution plans. The most direct exposure in the current scenario is: Conflating zero with missing data hides legitimate stockouts and distorts service metrics.
B:This failure mode belongs mainly to another situation: A product catalog receives corrections for existing SKUs plus entirely new items on each incremental load. Its preventative action would be: Use a Delta MERGE keyed by SKU with appropriate matched-update and not-matched-insert logic. The most direct exposure in the current scenario is: Conflating zero with missing data hides legitimate stockouts and distorts service metrics.
C:This failure mode belongs mainly to another situation: A daily revenue report double-counts refunds because both debit and credit rows are summed as positive numbers. Its preventative action would be: Normalize transaction sign semantics before grouping by business date and customer. The most direct exposure in the current scenario is: Conflating zero with missing data hides legitimate stockouts and distorts service metrics.