Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 80
Question 790
A team omits the recommended measure: Set a measured maintenance cadence or evaluate supported predictive optimization for eligible managed tables. Its environment shows: A new Delta table maintenance job combines repeated OPTIMIZE and VACUUM at every microbatch even though changes are tiny. What is the MOST direct residual risk?
- Scaling a query against irrelevant files can increase cost without proportional performance gains.
- Over-maintenance can spend more resources rewriting files than it saves in queries.
- Unused cached data can cause eviction, spilling and unexpected failures for later stages.
- Collecting billions of rows can crash the driver despite idle executors.
Explanation
Correct Answer
B:The direct residual exposure is: Over-maintenance can spend more resources rewriting files than it saves in queries. The triggering condition is: A new Delta table maintenance job combines repeated OPTIMIZE and VACUUM at every microbatch even though changes are tiny. The omitted safeguard is: Set a measured maintenance cadence or evaluate supported predictive optimization for eligible managed tables. This matters because: Maintenance operations themselves consume compute and should correspond to data growth and read patterns. A corrective test would show: A benchmark shows lower total maintenance-plus-query cost without compromising retention.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A warehouse query remains slow even after larger compute is allocated and the profile reports scanning nearly every file. Its preventative action would be: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again. The most direct exposure in the current scenario is: Over-maintenance can spend more resources rewriting files than it saves in queries.
C:This failure mode belongs mainly to another situation: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. Its preventative action would be: Use caching only for beneficial reuse and release persisted state when no longer needed. The most direct exposure in the current scenario is: Over-maintenance can spend more resources rewriting files than it saves in queries.
D:This failure mode belongs mainly to another situation: A Spark join reads large inputs but the driver reports failures after an analyst calls collect() on the result. Its preventative action would be: Keep large results distributed and replace driver collection with bounded sampling or distributed writes. The most direct exposure in the current scenario is: Over-maintenance can spend more resources rewriting files than it saves in queries.
Question 791
A pipeline owner declines the action: Use a compatible unpivot or stack transformation with explicit month and amount columns. The business situation is: A large orders dataset has one column per month but a dashboard expects month-value rows for filtering and grouping. What specific failure can follow?
- Unnecessary MERGE operations can add substantial cost and contention without correctness benefit.
- Directly summing mismatched month columns can produce fragile and incomplete queries.
- Duplicate orders inflate sales totals and can trigger incorrect downstream payouts.
- Completion metrics may be inflated or undercounted when duplicate business events are not resolved.
Explanation
Correct Answer
B:The direct residual exposure is: Directly summing mismatched month columns can produce fragile and incomplete queries. The triggering condition is: A large orders dataset has one column per month but a dashboard expects month-value rows for filtering and grouping. The omitted safeguard is: Use a compatible unpivot or stack transformation with explicit month and amount columns. This matters because: Unpivoting converts a wide repeated-measure structure into a normalized row representation. A corrective test would show: The unpivoted output contains exactly one row per original item-month and preserves totals.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An append-only telemetry feed includes newly observed events but engineers use MERGE with expensive full-table scans on every insert. Its preventative action would be: Use an incremental append pattern with suitable deduplication when source events cannot change. The most direct exposure in the current scenario is: Directly summing mismatched month columns can produce fragile and incomplete queries.
C:This failure mode belongs mainly to another situation: An incoming orders table contains repeated order IDs because a vendor retransmits the same daily extract. Its preventative action would be: Apply a deterministic deduplication rule based on stable order identity and source version before aggregation. The most direct exposure in the current scenario is: Directly summing mismatched month columns can produce fragile and incomplete queries.
D:This failure mode belongs mainly to another situation: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. Its preventative action would be: Validate business keys and choose a deterministic latest-enrollment record before aggregation. The most direct exposure in the current scenario is: Directly summing mismatched month columns can produce fragile and incomplete queries.
Question 792
A team omits the recommended measure: Validate business keys and choose a deterministic latest-enrollment record before aggregation. Its environment shows: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. What is the MOST direct residual risk?
- An unrestricted join can multiply keys and exaggerate customer counts.
- Completion metrics may be inflated or undercounted when duplicate business events are not resolved.
- Conflating zero with missing data hides legitimate stockouts and distorts service metrics.
- Refund amounts treated as sales inflate net revenue even when record counts match.
Explanation
Correct Answer
B:The direct residual exposure is: Completion metrics may be inflated or undercounted when duplicate business events are not resolved. The triggering condition is: A student dataset uses SQL GROUP BY with unhandled duplicate enrollment rows before reporting course completion. The omitted safeguard is: Validate business keys and choose a deterministic latest-enrollment record before aggregation. This matters because: Aggregation alone cannot distinguish valid repeat enrollments from accidental duplicates. A corrective test would show: Test histories with retries and real re-enrollments produce the approved per-student count.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A team wants only customer IDs present in both systems but uses an inner join that multiplies repeated rows. Its preventative action would be: Use an appropriate intersect or semi-join operation based on set and duplicate requirements. The most direct exposure in the current scenario is: Completion metrics may be inflated or undercounted when duplicate business events are not resolved.
C:This failure mode belongs mainly to another situation: A team filters out null quantities but needs to preserve rows with zero as valid inventory states. Its preventative action would be: Implement explicit null predicates rather than treating zero and null as equivalent. The most direct exposure in the current scenario is: Completion metrics may be inflated or undercounted when duplicate business events are not resolved.
D: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: Completion metrics may be inflated or undercounted when duplicate business events are not resolved.
Question 793
A team omits the recommended measure: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. Its environment shows: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. What is the MOST direct residual risk?
- Accumulated historical grants may give former project teams access to unrelated data products.
- A migrated table can retain unintended access or lose required controls after namespace changes.
- An identically named confidential field in a new table could be exposed.
- Premature removal of obsolete files can prevent required time travel or restore operations.
Explanation
Correct Answer
D:The direct residual exposure is: Premature removal of obsolete files can prevent required time travel or restore operations. The triggering condition is: A regulation requires keeping event records for 90 days but a job performs VACUUM after only a few hours. The omitted safeguard is: Coordinate Delta retention configuration, VACUUM safety settings and formal recovery requirements. This matters because: Retention policy must account for physical file cleanup as well as logical table content. A corrective test would show: A controlled historical read succeeds within the mandated window and approved cleanup starts only afterwards.
Incorrect Answers
A: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: Premature removal of obsolete files can prevent required time travel or restore operations.
B:This failure mode belongs mainly to another situation: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. Its preventative action would be: Reconcile catalog object identity, lineage and current grants after schema or owner changes. The most direct exposure in the current scenario is: Premature removal of obsolete files can prevent required time travel or restore operations.
C:This failure mode belongs mainly to another situation: A user creates a column mask on a single table and assumes all tables with the same field name are protected. Its preventative action would be: Compare table-level masks against centrally governed ABAC coverage and identify missing assignments. The most direct exposure in the current scenario is: Premature removal of obsolete files can prevent required time travel or restore operations.
Question 794
During a lakehouse implementation review, engineers observe: An operations team sees Dataflow-like ingestion failures but cannot identify whether the problem is a Unity Catalog grant or a Spark stage. What is the BEST next action?
- Review deletion-vector behavior, table layout and suitable optimization for the supported runtime.
- Profile aggregation key distribution, shuffle partitions and executor memory before choosing a targeted change.
- Correlate error messages, job run IDs, catalog authorization logs and Spark execution evidence before remediation.
- Inspect the Spark UI DAG and skewed-key distribution before changing cluster size.
Explanation
Correct Answer
C:The most appropriate action is: Correlate error messages, job run IDs, catalog authorization logs and Spark execution evidence before remediation. It addresses the stated condition: An operations team sees Dataflow-like ingestion failures but cannot identify whether the problem is a Unity Catalog grant or a Spark stage. The technical basis is: Different failure layers require different diagnostic paths instead of generic cluster restarts. Without this control, restarting a healthy compute resource cannot repair a denied storage credential or table grant. A direct acceptance check is: An injected permission failure maps to the relevant principal and grant while compute remains healthy.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A query on a Delta table slows after a small percentage of rows are deleted but data files are not optimized. The corresponding measure there would be: Review deletion-vector behavior, table layout and suitable optimization for the supported runtime. The stated situation instead calls for: Correlate error messages, job run IDs, catalog authorization logs and Spark execution evidence before remediation.
B:This alternative primarily addresses a different Azure Databricks problem: A Spark workload repeatedly fails with executor out-of-memory errors on a high-cardinality groupBy. The corresponding measure there would be: Profile aggregation key distribution, shuffle partitions and executor memory before choosing a targeted change. The stated situation instead calls for: Correlate error messages, job run IDs, catalog authorization logs and Spark execution evidence before remediation.
D:This alternative primarily addresses a different Azure Databricks problem: A production Spark query is slow and its stage graph shows one task running far longer than all peers. The corresponding measure there would be: Inspect the Spark UI DAG and skewed-key distribution before changing cluster size. The stated situation instead calls for: Correlate error messages, job run IDs, catalog authorization logs and Spark execution evidence before remediation.
Question 795
For this Microsoft DP-750 case: A developer selects a new Databricks Runtime version for production despite an untested JDBC driver dependency. Which design or operational response BEST fits?
- Benchmark Photon on a supported runtime with representative queries and compare cost, latency and correctness.
- Set appropriate auto-termination or idle controls for interactive compute while excluding workloads requiring continuous availability.
- Pin a supported Databricks Runtime version and validate application libraries against it before deployment.
- Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution.
Explanation
Correct Answer
C:The most appropriate action is: Pin a supported Databricks Runtime version and validate application libraries against it before deployment. It addresses the stated condition: A developer selects a new Databricks Runtime version for production despite an untested JDBC driver dependency. The technical basis is: Spark and runtime upgrades can change supported APIs, dependency versions and execution behavior. Without this control, an unverified runtime switch may break a previously working production ingestion notebook. A direct acceptance check is: A staging run on the proposed runtime loads the required JDBC driver and reproduces validated output.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A Spark SQL pipeline spends most of its time executing wide joins and aggregations but the team has not evaluated a compatible vectorized execution engine. The corresponding measure there would be: Benchmark Photon on a supported runtime with representative queries and compare cost, latency and correctness. The stated situation instead calls for: Pin a supported Databricks Runtime version and validate application libraries against it before deployment.
B:This alternative primarily addresses a different Azure Databricks problem: A newly created cluster remains available for hours after manual exploration even though the organization has a strict idle-cost policy. The corresponding measure there would be: Set appropriate auto-termination or idle controls for interactive compute while excluding workloads requiring continuous availability. The stated situation instead calls for: Pin a supported Databricks Runtime version and validate application libraries against it before deployment.
D:This alternative primarily addresses a different Azure Databricks problem: A nightly batch transformation uses a continuously running all-purpose cluster even though no analyst interacts with the workload between runs. The corresponding measure there would be: Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution. The stated situation instead calls for: Pin a supported Databricks Runtime version and validate application libraries against it before deployment.
Question 796
A data engineering team faces this Azure Databricks requirement: A release modifies transformation logic but tests only whether Python files compile. Which action is MOST appropriate?
- Add representative unit and integration tests asserting transformation results and schema contracts.
- Define and validate environment-specific catalog, workspace and identity targets in deployment configuration.
- Run end-to-end contract tests for dependent readers and obtain owner approval for breaking changes.
- Pin package and runtime versions in the governed release artifact and record its dependency manifest.
Explanation
Correct Answer
A:The most appropriate action is: Add representative unit and integration tests asserting transformation results and schema contracts. It addresses the stated condition: A release modifies transformation logic but tests only whether Python files compile. The technical basis is: Syntax checks do not validate business semantics or interaction with external tables. Without this control, A logically incorrect aggregation can pass compilation while corrupting metrics. A direct acceptance check is: A seeded test dataset returns documented expected outputs and intentionally bad inputs fail.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A multi-environment setup uses the same catalog for test and production because bundle target variables were omitted. The corresponding measure there would be: Define and validate environment-specific catalog, workspace and identity targets in deployment configuration. The stated situation instead calls for: Add representative unit and integration tests asserting transformation results and schema contracts.
C:This alternative primarily addresses a different Azure Databricks problem: A sensitive SQL view is renamed in the release but the team does not test downstream dashboards before promotion. The corresponding measure there would be: Run end-to-end contract tests for dependent readers and obtain owner approval for breaking changes. The stated situation instead calls for: Add representative unit and integration tests asserting transformation results and schema contracts.
D:This alternative primarily addresses a different Azure Databricks problem: A team cannot reproduce a prior release because package versions are resolved dynamically during deployment. The corresponding measure there would be: Pin package and runtime versions in the governed release artifact and record its dependency manifest. The stated situation instead calls for: Add representative unit and integration tests asserting transformation results and schema contracts.
Question 797
An operator introduces: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. The situation is: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. Which validation should be required before signoff?
- The pipeline executes under a scoped service identity and the old token is revoked and rejected.
- The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
- An auditor lists allowed table metadata without retrieving restricted row contents.
- Direct source queries are denied for analysts while the governed view produces the approved masked data.
Explanation
Correct Answer
B:The strongest acceptance proof is: The scheduled job reads its approved storage path while no plaintext credential exists in source or logs. It specifically verifies: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. The original issue was: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. The underlying mechanism is: Managed identity authentication avoids exposing reusable static secrets and ties authorization to a governed identity. Without it, A copied notebook may leak storage access keys beyond the intended data-processing environment.
Incorrect Answers
A:This result would validate a different measure: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. That is relevant to the distinct problem: A production workload uses a personal access token stored in Git for Databricks REST calls. Here the acceptance criterion is: The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
C:This result would validate a different measure: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. That is relevant to the distinct problem: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. Here the acceptance criterion is: The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
D:This result would validate a different measure: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. That is relevant to the distinct problem: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. Here the acceptance criterion is: The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
Question 798
During a lakehouse implementation review, engineers observe: An ingestion team creates a table with a reserved or inconsistent name and automation fails in one environment. What is the BEST next action?
- Create an authorized connection and supported foreign catalog for the external source.
- Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers.
- Define a stable contract through managed views and test compatibility before changing source objects.
- Select managed or external Unity Catalog table ownership intentionally and verify lifecycle semantics.
Explanation
Correct Answer
B:The most appropriate action is: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers. It addresses the stated condition: An ingestion team creates a table with a reserved or inconsistent name and automation fails in one environment. The technical basis is: Consistent identifiers reduce accidental parsing and namespace resolution differences. Without this control, an inconsistent identifier forces manual quoting and breaks repeatable deployment scripts. A direct acceptance check is: Automated DDL completes in both staging and production under the same naming rules.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. The corresponding measure there would be: Create an authorized connection and supported foreign catalog for the external source. The stated situation instead calls for: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers.
C:This alternative primarily addresses a different Azure Databricks problem: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. The corresponding measure there would be: Define a stable contract through managed views and test compatibility before changing source objects. The stated situation instead calls for: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers.
D:This alternative primarily addresses a different Azure Databricks problem: A team expects dropping a managed table to preserve all physical data as though it were an external table. The corresponding measure there would be: Select managed or external Unity Catalog table ownership intentionally and verify lifecycle semantics. The stated situation instead calls for: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers.
Question 799
During a lakehouse implementation review, engineers observe: A sales pipeline aggregates gold metrics before the bronze ingestion task finishes and occasionally reports incomplete totals. What is the BEST next action?
- Design a compatible atomic publication or versioned readiness contract so consumers see consistent results.
- Select a notebook task within Lakeflow Jobs when procedural control and custom libraries fit the requirements.
- Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed.
- Design a task DAG with parallel independent ingestion and an aggregation dependency after both complete.
Explanation
Correct Answer
C:The most appropriate action is: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed. It addresses the stated condition: A sales pipeline aggregates gold metrics before the bronze ingestion task finishes and occasionally reports incomplete totals. The technical basis is: DAG-based orchestration coordinates data readiness and avoids race conditions across dependent tasks. Without this control, an early downstream task can publish partial business totals without raising an obvious failure. A direct acceptance check is: A delayed-ingestion test prevents gold refresh until bronze and silver are completed successfully.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A regulated pipeline needs consistent transaction boundaries across multiple table writes but updates are published one at a time. The corresponding measure there would be: Design a compatible atomic publication or versioned readiness contract so consumers see consistent results. The stated situation instead calls for: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed.
B:This alternative primarily addresses a different Azure Databricks problem: An ad hoc machine-learning preparation task has complex custom Python orchestration and no declarative table graph. The corresponding measure there would be: Select a notebook task within Lakeflow Jobs when procedural control and custom libraries fit the requirements. The stated situation instead calls for: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed.
D:This alternative primarily addresses a different Azure Databricks problem: A pipeline uses a single notebook to read four sources sequentially even though two can be processed independently. The corresponding measure there would be: Design a task DAG with parallel independent ingestion and an aggregation dependency after both complete. The stated situation instead calls for: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed.
Question 800
An implementation skips: Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants. Engineers are observing: An engineering pipeline attempts to insert records into a production Delta table using an account with SELECT only. What consequence is MOST likely?
- Giving all analysts write rights merely to repair one pipeline expands accidental corruption risk.
- Granting SELECT without masking may expose full account identifiers to unauthorized readers.
- A retired vendor workload can continue reading business data through unchanged credentials.
- Manual per-table rules can miss newly created columns and expose sensitive values.
Explanation
Correct Answer
A:The direct residual exposure is: Giving all analysts write rights merely to repair one pipeline expands accidental corruption risk. The triggering condition is: An engineering pipeline attempts to insert records into a production Delta table using an account with SELECT only. The omitted safeguard is: Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants. This matters because: Read and write operations require distinct Unity Catalog privileges and operating identities. A corrective test would show: The writer inserts a validated test row and reader accounts are denied modification attempts.
Incorrect Answers
B: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: Giving all analysts write rights merely to repair one pipeline expands accidental corruption risk.
C:This failure mode belongs mainly to another situation: A vendor's service principal was granted global access for a one-month integration and the project ended. Its preventative action would be: Review and revoke stale grants and any linked service credentials, preserving required internal ownership. The most direct exposure in the current scenario is: Giving all analysts write rights merely to repair one pipeline expands accidental corruption risk.
D:This failure mode belongs mainly to another situation: A data compliance team needs consistent redaction of columns tagged as personal data across hundreds of catalog tables. Its preventative action would be: Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported. The most direct exposure in the current scenario is: Giving all analysts write rights merely to repair one pipeline expands accidental corruption risk.