Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 8
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.
Question 71
A production data platform experiences this condition: A data steward wants to grant temporary read access without handing over Unity Catalog ownership of a schema. Which targeted measure should be selected?
- Check required parent catalog and schema usage privileges alongside the table SELECT grant.
- Replace committed personal credentials with supported workload authentication and revoke exposed tokens.
- Use supported Databricks secret access with least-privilege scope access and remove secret values from logs.
- Issue time-bounded group membership or an approved scoped SELECT grant with an access review.
Explanation
Correct Answer
D:The most appropriate action is: Issue time-bounded group membership or an approved scoped SELECT grant with an access review. It addresses the stated condition: A data steward wants to grant temporary read access without handing over Unity Catalog ownership of a schema. The technical basis is: Data access delegation need not transfer administrative ownership of data objects. Without this control, changing table owner for short-term access can unintentionally enable grant management and destructive changes. A direct acceptance check is: The visiting user reads the designated dataset before expiry and loses access afterwards without ownership changes.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A contractor receives SELECT on a table yet gets an access-denied error when querying with a three-part name. The corresponding measure there would be: Check required parent catalog and schema usage privileges alongside the table SELECT grant. The stated situation instead calls for: Issue time-bounded group membership or an approved scoped SELECT grant with an access review.
B:This alternative primarily addresses a different Azure Databricks problem: A production workload uses a personal access token stored in Git for Databricks REST calls. The corresponding measure there would be: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. The stated situation instead calls for: Issue time-bounded group membership or an approved scoped SELECT grant with an access review.
C:This alternative primarily addresses a different Azure Databricks problem: An application uses an external Azure Key Vault secret scope but a notebook prints the secret into task logs. The corresponding measure there would be: Use supported Databricks secret access with least-privilege scope access and remove secret values from logs. The stated situation instead calls for: Issue time-bounded group membership or an approved scoped SELECT grant with an access review.
Question 72
A data engineering team faces this Azure Databricks requirement: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. Which action is MOST appropriate?
- Include an integration test using actual Delta table semantics and representative source changes.
- Resolve Git merge conflicts with tests and reviewed integration before merging the release branch.
- Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle.
- Add representative unit and integration tests asserting transformation results and schema contracts.
Explanation
Correct Answer
A:The most appropriate action is: Include an integration test using actual Delta table semantics and representative source changes. It addresses the stated condition: A test harness mocks out Delta writes but the real job uses MERGE and unexpectedly changes historical rows. The technical basis is: Storage-layer transaction behavior must be tested in addition to pure function outputs. Without this control, unverified MERGE conditions can overwrite valid history despite passing mocked unit tests. A direct acceptance check is: An integration fixture with historical updates yields exactly the intended target versions.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: Two engineers change the same ingestion function on separate branches and one silently overwrites the other's fix. The corresponding measure there would be: Resolve Git merge conflicts with tests and reviewed integration before merging the release branch. The stated situation instead calls for: Include an integration test using actual Delta table semantics and representative source changes.
C:This alternative primarily addresses a different Azure Databricks problem: A Databricks bundle deployment differs from what appears in the repository because someone edits the job in the UI afterward. The corresponding measure there would be: Use drift detection or a release reconciliation that compares deployed objects against the versioned bundle. The stated situation instead calls for: Include an integration test using actual Delta table semantics and representative source changes.
D:This alternative primarily addresses a different Azure Databricks problem: A release modifies transformation logic but tests only whether Python files compile. The corresponding measure there would be: Add representative unit and integration tests asserting transformation results and schema contracts. The stated situation instead calls for: Include an integration test using actual Delta table semantics and representative source changes.
Question 73
A Databricks engineer recommends: Examine shuffle metrics, memory pressure and partition sizing to target the spilling stage. It responds to: A large aggregation has repeated shuffle spills to disk even though source scans finish quickly. What underlying mechanism BEST explains why?
- Maintenance operations themselves consume compute and should correspond to data growth and read patterns.
- Task-level repair can reduce replay cost while preserving successful work.
- Shuffle spills indicate data exceeded available in-memory execution resources for a stage.
- Concurrent demand peaks can drive queue delays independently of average compute utilization.
Explanation
Correct Answer
C:The decisive mechanism is: Shuffle spills indicate data exceeded available in-memory execution resources for a stage. That explains the selected action: Examine shuffle metrics, memory pressure and partition sizing to target the spilling stage. In the original scenario: A large aggregation has repeated shuffle spills to disk even though source scans finish quickly. The specific unmanaged risk is: Ignoring heavy spills can cause cascading I/O latency and missed pipeline deadlines. Validate with: A representative run shows reduced spill bytes and matching aggregate results with improved runtime.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A new Delta table maintenance job combines repeated OPTIMIZE and VACUUM at every microbatch even though changes are tiny. Its targeted response is: Set a measured maintenance cadence or evaluate supported predictive optimization for eligible managed tables. The current case is governed more directly by: Shuffle spills indicate data exceeded available in-memory execution resources for a stage.
B:This principle concerns a separate data-engineering condition: A job fails during a temporary Azure storage outage but operators rerun every successful upstream task. Its targeted response is: Use Lakeflow Jobs repair at the failed task when dependency outputs remain valid. The current case is governed more directly by: Shuffle spills indicate data exceeded available in-memory execution resources for a stage.
D:This principle concerns a separate data-engineering condition: An interactive warehouse has high query queues during the morning but low CPU utilization after lunch. Its targeted response is: Analyze concurrent query load and scaling policies rather than selecting capacity from daily averages. The current case is governed more directly by: Shuffle spills indicate data exceeded available in-memory execution resources for a stage.
Question 74
The following control has NOT been implemented: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. In this case: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. Which exposure remains?
- One missing tenant predicate can expose another customer’s records.
- A compromised job principal could alter data products unrelated to its intended table.
- A copied notebook may leak storage access keys beyond the intended data-processing environment.
- An employee departure or password rotation can unexpectedly break critical production ingestion.
Explanation
Correct Answer
C:The direct residual exposure is: A copied notebook may leak storage access keys beyond the intended data-processing environment. The triggering condition is: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. The omitted safeguard is: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. This matters because: Managed identity authentication avoids exposing reusable static secrets and ties authorization to a governed identity. A corrective test would show: The scheduled job reads its approved storage path while no plaintext credential exists in source or logs.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A multi-tenant analytics table relies on application code to append customer_id filtering. Its preventative action would be: Implement a Unity Catalog row filter with deterministic identity-to-tenant mapping and test negative cases. The most direct exposure in the current scenario is: A copied notebook may leak storage access keys beyond the intended data-processing environment.
B:This failure mode belongs mainly to another situation: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. Its preventative action would be: Replace broad grants with documented minimum creation and use privileges in a dedicated schema. The most direct exposure in the current scenario is: A copied notebook may leak storage access keys beyond the intended data-processing environment.
D:This failure mode belongs mainly to another situation: An ETL service principal is granted permissions through a personal employee account that will leave the company. Its preventative action would be: Use a dedicated service principal with scoped Unity Catalog grants and governed credential lifecycle. The most direct exposure in the current scenario is: A copied notebook may leak storage access keys beyond the intended data-processing environment.
Question 75
An operator introduces: Investigate stage runtime growth and enforce appropriate concurrency policy before raising frequency. The situation is: A job scheduled each hour starts running for 80 minutes and overlaps the next run. Which validation should be required before signoff?
- A selective query reads fewer files and meets latency targets after a controlled layout improvement.
- A peak-load rehearsal stabilizes backlog and keeps end-to-end event age within target.
- A dashboard highlights task and stage regressions before the total job breaches its SLA.
- Load testing shows completion within the target window and queued runs do not overlap unsafely.
Explanation
Correct Answer
D:The strongest acceptance proof is: Load testing shows completion within the target window and queued runs do not overlap unsafely. It specifically verifies: Investigate stage runtime growth and enforce appropriate concurrency policy before raising frequency. The original issue was: A job scheduled each hour starts running for 80 minutes and overlaps the next run. The underlying mechanism is: Scheduling cannot guarantee freshness when actual execution exceeds the interval. Without it, overlapping backlogs can amplify compute consumption and create conflicting writes.
Incorrect Answers
A:This result would validate a different measure: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again. That is relevant to the distinct problem: A warehouse query remains slow even after larger compute is allocated and the profile reports scanning nearly every file. Here the acceptance criterion is: Load testing shows completion within the target window and queued runs do not overlap unsafely.
B:This result would validate a different measure: Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling. That is relevant to the distinct problem: A streaming pipeline's throughput falls although event arrival increases and its input backlog grows over time. Here the acceptance criterion is: Load testing shows completion within the target window and queued runs do not overlap unsafely.
C:This result would validate a different measure: Collect job timing, task duration and relevant Spark stage metrics in a monitored baseline. That is relevant to the distinct problem: A job's duration doubles but an administrator sees only its final success status with no phase-level metrics. Here the acceptance criterion is: Load testing shows completion within the target window and queued runs do not overlap unsafely.
Question 76
The team implements: Use Unity Catalog volumes with suitable schema and file privileges for supported non-tabular files. The original problem is: A departmental data owner stores raw file attachments inside ad hoc DBFS directories instead of a governable data space. Which test MOST convincingly demonstrates correctness?
- A controlled MERGE and SQL query succeed against the governed Delta table with expected records.
- Authorized principals list and read a governed volume path while unrelated roles receive denied access.
- Catalog lookup and controlled read work from the registered target while unapproved principals cannot bypass it.
- The product service principal creates in its own schema and fails the same operation in unrelated schemas.
Explanation
Correct Answer
B:The strongest acceptance proof is: Authorized principals list and read a governed volume path while unrelated roles receive denied access. It specifically verifies: Use Unity Catalog volumes with suitable schema and file privileges for supported non-tabular files. The original issue was: A departmental data owner stores raw file attachments inside ad hoc DBFS directories instead of a governable data space. The underlying mechanism is: Volumes bring file-based assets into a governed catalog namespace distinct from SQL table records. Without it, unregistered working files can bypass object discovery and authorization reviews.
Incorrect Answers
A: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: Authorized principals list and read a governed volume path while unrelated roles receive denied access.
C:This result would validate a different measure: Recreate or update supported external table registration using an approved location and correct access controls. That is relevant to the distinct problem: A managed Delta table is migrated to external storage but the team does not update table registration or grant scopes. Here the acceptance criterion is: Authorized principals list and read a governed volume path while unrelated roles receive denied access.
D:This result would validate a different measure: Create a team-specific schema with ownership or delegated creation grants limited to that namespace. That is relevant to the distinct problem: A newly onboarded product team wants to create its own tables but should not have administration rights over every catalog. Here the acceptance criterion is: Authorized principals list and read a governed volume path while unrelated roles receive denied access.
Question 77
A solution applies: Correlate error messages, job run IDs, catalog authorization logs and Spark execution evidence before remediation. It addresses: An operations team sees Dataflow-like ingestion failures but cannot identify whether the problem is a Unity Catalog grant or a Spark stage. Which operational outcome MOST directly verifies success?
- An injected permission failure maps to the relevant principal and grant while compute remains healthy.
- A controlled transient outage is repaired without rerunning completed expensive ingestion.
- A controlled representative load finishes without OOM and output group counts reconcile.
- Load testing shows completion within the target window and queued runs do not overlap unsafely.
Explanation
Correct Answer
A:The strongest acceptance proof is: An injected permission failure maps to the relevant principal and grant while compute remains healthy. It specifically verifies: Correlate error messages, job run IDs, catalog authorization logs and Spark execution evidence before remediation. The original issue was: An operations team sees Dataflow-like ingestion failures but cannot identify whether the problem is a Unity Catalog grant or a Spark stage. The underlying mechanism is: Different failure layers require different diagnostic paths instead of generic cluster restarts. Without it, restarting a healthy compute resource cannot repair a denied storage credential or table grant.
Incorrect Answers
B:This result would validate a different measure: Use Lakeflow Jobs repair at the failed task when dependency outputs remain valid. That is relevant to the distinct problem: A job fails during a temporary Azure storage outage but operators rerun every successful upstream task. Here the acceptance criterion is: An injected permission failure maps to the relevant principal and grant while compute remains healthy.
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: An injected permission failure maps to the relevant principal and grant while compute remains healthy.
D:This result would validate a different measure: Investigate stage runtime growth and enforce appropriate concurrency policy before raising frequency. That is relevant to the distinct problem: A job scheduled each hour starts running for 80 minutes and overlaps the next run. Here the acceptance criterion is: An injected permission failure maps to the relevant principal and grant while compute remains healthy.
Question 78
A team omits the recommended measure: Create an authorized connection and supported foreign catalog for the external source. Its environment shows: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. What is the MOST direct residual risk?
- An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts.
- A broadly shared catalog can expose regulated data to unintended region workspaces.
- Replicated extracts may fall outside the original source's governance and retention controls.
- Copying the whole remote source for a narrow lookup can create unnecessary latency, duplication and privacy exposure.
Explanation
Correct Answer
D:The direct residual exposure is: Copying the whole remote source for a narrow lookup can create unnecessary latency, duplication and privacy exposure. The triggering condition is: A workspace needs to query a foreign transactional source without first loading every row into a Delta table. The omitted safeguard is: Create an authorized connection and supported foreign catalog for the external source. This matters because: Lakehouse Federation lets governed queries access supported external systems through a connection abstraction. A corrective test would show: A restricted query through the foreign catalog returns current permitted rows and honors source connectivity limits.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An ingestion team creates a table with a reserved or inconsistent name and automation fails in one environment. Its preventative action would be: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers. The most direct exposure in the current scenario is: Copying the whole remote source for a narrow lookup can create unnecessary latency, duplication and privacy exposure.
B:This failure mode belongs mainly to another situation: A platform architect creates one catalog for subsidiaries with incompatible regional data-residency permissions. Its preventative action would be: Split catalogs or governance boundaries along residency and ownership requirements and validate workspace bindings. The most direct exposure in the current scenario is: Copying the whole remote source for a narrow lookup can create unnecessary latency, duplication and privacy exposure.
C:This failure mode belongs mainly to another situation: An analyst wants to expose a filtered projection of a governed table without copying sensitive source rows. Its preventative action would be: Create a Unity Catalog view with approved permissions and verify underlying access semantics. The most direct exposure in the current scenario is: Copying the whole remote source for a narrow lookup can create unnecessary latency, duplication and privacy exposure.
Question 79
For this Microsoft DP-750 case: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. Which design or operational response BEST fits?
- Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs.
- Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention.
- Examine shuffle metrics, memory pressure and partition sizing to target the spilling stage.
- Set a measured maintenance cadence or evaluate supported predictive optimization for eligible managed tables.
Explanation
Correct Answer
B:The most appropriate action is: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention. It addresses the stated condition: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. The technical basis is: Centralized telemetry supports durable troubleshooting when ephemeral compute terminates. Without this control, A failed cluster can disappear before operators gather evidence of its root cause. A direct acceptance check is: A simulated failure leaves accessible run logs and correlation identifiers in the approved monitoring destination.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. The corresponding measure there would be: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. The stated situation instead calls for: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention.
C:This alternative primarily addresses a different Azure Databricks problem: A large aggregation has repeated shuffle spills to disk even though source scans finish quickly. The corresponding measure there would be: Examine shuffle metrics, memory pressure and partition sizing to target the spilling stage. The stated situation instead calls for: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention.
D:This alternative primarily addresses a different Azure Databricks problem: A new Delta table maintenance job combines repeated OPTIMIZE and VACUUM at every microbatch even though changes are tiny. The corresponding measure there would be: Set a measured maintenance cadence or evaluate supported predictive optimization for eligible managed tables. The stated situation instead calls for: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention.
Question 80
The team implements: Use an appropriately sized SQL warehouse with workload isolation and measured concurrency for dashboard queries. The original problem is: Analysts run short SQL dashboard queries against a shared lakehouse but their notebooks share a general-purpose Spark cluster with training experiments. Which test MOST convincingly demonstrates correctness?
- A load rehearsal meets dashboard p95 response targets while notebook resource spikes do not affect query service.
- An ordinary user can start an approved small cluster but cannot exceed policy size or runtime limits.
- The scheduled job completes within its service objective and compute billing shows no unattended idle cluster hours.
- Before-after measurements report comparable inputs, stage timings, spills and total cost.
Explanation
Correct Answer
A:The strongest acceptance proof is: A load rehearsal meets dashboard p95 response targets while notebook resource spikes do not affect query service. It specifically verifies: Use an appropriately sized SQL warehouse with workload isolation and measured concurrency for dashboard queries. The original issue was: Analysts run short SQL dashboard queries against a shared lakehouse but their notebooks share a general-purpose Spark cluster with training experiments. The underlying mechanism is: SQL warehouses are optimized for SQL analytics and isolate query serving from other compute activities. Without it, A shared notebook cluster can cause dashboards to stall when unrelated Spark notebooks consume executors.
Incorrect Answers
B:This result would validate a different measure: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users. That is relevant to the distinct problem: A department wants a self-service sandbox but must prevent users from creating huge unrestricted clusters. Here the acceptance criterion is: A load rehearsal meets dashboard p95 response targets while notebook resource spikes do not affect query service.
C:This result would validate a different measure: Move the scheduled transformation to appropriately configured jobs compute or supported serverless jobs and release resources after execution. That is relevant to the distinct problem: A nightly batch transformation uses a continuously running all-purpose cluster even though no analyst interacts with the workload between runs. Here the acceptance criterion is: A load rehearsal meets dashboard p95 response targets while notebook resource spikes do not affect query service.
D:This result would validate a different measure: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data. That is relevant to the distinct problem: A team turns on every performance setting for a workload without benchmarking whether disk spills or network shuffle dominate runtime. Here the acceptance criterion is: A load rehearsal meets dashboard p95 response targets while notebook resource spikes do not affect query service.