Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 88
Question 870
A platform architect adopts: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. For this requirement: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. Which rationale MOST directly supports it?
- Foreign catalog semantics and connector capabilities differ from native managed Delta table operations.
- The object type should reflect whether data is computed on read or persisted and maintained.
- Managed versus external tables differ in who manages data paths and deletion behavior.
- Governance of views includes ownership, discovery and authorization just as for tables.
Explanation
Correct Answer
A:The decisive mechanism is: Foreign catalog semantics and connector capabilities differ from native managed Delta table operations. That explains the selected action: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. In the original scenario: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. The specific unmanaged risk is: Assuming full DDL or mutation support may cause failed deployments or inadvertent source changes. Validate with: A capability test documents supported query and write operations and prevents unsupported mutations.
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: Foreign catalog semantics and connector capabilities differ from native managed Delta table operations.
C:This principle concerns a separate data-engineering condition: A team expects dropping a managed table to preserve all physical data as though it were an external table. Its targeted response is: Select managed or external Unity Catalog table ownership intentionally and verify lifecycle semantics. The current case is governed more directly by: Foreign catalog semantics and connector capabilities differ from native managed Delta table operations.
D:This principle concerns a separate data-engineering condition: A central team creates global views that hide source objects but forgets to document ownership and access grants. Its targeted response is: Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema. The current case is governed more directly by: Foreign catalog semantics and connector capabilities differ from native managed Delta table operations.
Question 871
For this Azure Databricks issue: A company needs to review table-owner changes and permissions after organizational restructuring. Engineers choose: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. What acceptance evidence is BEST?
- A data steward can find the certified revenue definition and verify the correct field in Catalog Explorer.
- A partner query fails after revocation while internal consumers remain able to read the dataset.
- A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
- The recertification report identifies owners, changed grants and approved remediation evidence.
Explanation
Correct Answer
D:The strongest acceptance proof is: The recertification report identifies owners, changed grants and approved remediation evidence. It specifically verifies: Run a scheduled ownership and grant recertification process using catalog metadata and audit events. The original issue was: A company needs to review table-owner changes and permissions after organizational restructuring. The underlying mechanism is: Object governance is ongoing and must follow organizational role and service identity changes. Without it, accumulated historical grants may give former project teams access to unrelated data products.
Incorrect Answers
A:This result would validate a different measure: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. That is relevant to the distinct problem: A business glossary has table names but no indication of which field is net revenue versus gross sales. Here the acceptance criterion is: The recertification report identifies owners, changed grants and approved remediation evidence.
B:This result would validate a different measure: Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access. That is relevant to the distinct problem: A Delta Sharing recipient must stop receiving future updates after an agreement expires. Here the acceptance criterion is: The recertification report identifies owners, changed grants and approved remediation evidence.
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: The recertification report identifies owners, changed grants and approved remediation evidence.
Question 872
A production data platform experiences this condition: A feature-engineering notebook requires GPU libraries but the data cleaning jobs never use accelerators. Which targeted measure should be selected?
- Separate the small validation into an eligible lightweight or serverless task and measure total end-to-end runtime.
- Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations.
- Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met.
- Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior.
Explanation
Correct Answer
B:The most appropriate action is: Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations. It addresses the stated condition: A feature-engineering notebook requires GPU libraries but the data cleaning jobs never use accelerators. The technical basis is: GPU resources are specialized and do not automatically accelerate every Spark or SQL transformation. Without this control, A default GPU cluster may charge premium rates while most tasks leave accelerators unused. A direct acceptance check is: Resource telemetry shows accelerator use where needed and CPU jobs satisfy their SLA at lower cost.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A data team uses a high-power job cluster for a low-volume data-quality check that spends most runtime starting the cluster. The corresponding measure there would be: Separate the small validation into an eligible lightweight or serverless task and measure total end-to-end runtime. The stated situation instead calls for: Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations.
C:This alternative primarily addresses a different Azure Databricks problem: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. The corresponding measure there would be: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. The stated situation instead calls for: Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations.
D:This alternative primarily addresses a different Azure Databricks problem: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. The corresponding measure there would be: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. The stated situation instead calls for: Assign GPU-capable compute only to supported GPU workloads and use CPU compute for ordinary transformations.
Question 873
A pipeline owner declines the action: Specify the correct input delimiter, header and schema and validate parsing on a representative file. The business situation is: An overnight load reads tab-separated files but an engineer assumes comma separators and casts malformed columns to null. What specific failure can follow?
- Retries can duplicate invoices or notifications even if the source checkpoint is correct.
- A bespoke long-running stream for a one-time load adds complexity and idle cost.
- Out-of-order events can regress a target from its latest state to a stale state.
- Misparsed columns can populate nulls while the batch appears to complete successfully.
Explanation
Correct Answer
D:The direct residual exposure is: Misparsed columns can populate nulls while the batch appears to complete successfully. The triggering condition is: An overnight load reads tab-separated files but an engineer assumes comma separators and casts malformed columns to null. The omitted safeguard is: Specify the correct input delimiter, header and schema and validate parsing on a representative file. This matters because: Text ingestion options are part of the data contract and affect parsing correctness. A corrective test would show: A seed file loads the exact expected columns and invalid rows are reported rather than silently accepted.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A stream writes into an external sink without stable batch identities and causes duplicate side effects on retry. Its preventative action would be: Implement idempotent foreachBatch or compatible transactional sink logic keyed by epoch or business identity. The most direct exposure in the current scenario is: Misparsed columns can populate nulls while the batch appears to complete successfully.
B:This failure mode belongs mainly to another situation: An integration performs a one-off initial import of an existing CSV folder into a Delta table. Its preventative action would be: Use a suitable COPY INTO or supported batch ingestion statement with validated format and path options. The most direct exposure in the current scenario is: Misparsed columns can populate nulls while the batch appears to complete successfully.
C:This failure mode belongs mainly to another situation: A transactional feed produces out-of-order CDC events and a naive MERGE overwrites a newer status with an older update. Its preventative action would be: Apply ordered CDC sequencing using source change version or timestamp and consistent delete handling. The most direct exposure in the current scenario is: Misparsed columns can populate nulls while the batch appears to complete successfully.
Question 874
A production data platform experiences this condition: A warehouse query remains slow even after larger compute is allocated and the profile reports scanning nearly every file. Which targeted measure should be selected?
- Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again.
- Keep large results distributed and replace driver collection with bounded sampling or distributed writes.
- Analyze concurrent query load and scaling policies rather than selecting capacity from daily averages.
- Use Lakeflow Jobs repair at the failed task when dependency outputs remain valid.
Explanation
Correct Answer
A:The most appropriate action is: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again. It addresses the stated condition: A warehouse query remains slow even after larger compute is allocated and the profile reports scanning nearly every file. The technical basis is: Full scans caused by poor layout require data organization or predicate changes rather than only more compute. Without this control, scaling a query against irrelevant files can increase cost without proportional performance gains. A direct acceptance check is: A selective query reads fewer files and meets latency targets after a controlled layout improvement.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A Spark join reads large inputs but the driver reports failures after an analyst calls collect() on the result. The corresponding measure there would be: Keep large results distributed and replace driver collection with bounded sampling or distributed writes. The stated situation instead calls for: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again.
C:This alternative primarily addresses a different Azure Databricks problem: An interactive warehouse has high query queues during the morning but low CPU utilization after lunch. The corresponding measure there would be: Analyze concurrent query load and scaling policies rather than selecting capacity from daily averages. The stated situation instead calls for: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again.
D:This alternative primarily addresses a different Azure Databricks problem: A job fails during a temporary Azure storage outage but operators rerun every successful upstream task. The corresponding measure there would be: Use Lakeflow Jobs repair at the failed task when dependency outputs remain valid. The stated situation instead calls for: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again.
Question 875
A pipeline owner declines the action: Create compatible central ABAC policies based on governed classifications and verify inherited coverage. The business situation is: A central security team manually adds row masking rules to every department table and new datasets repeatedly lack protection. What specific failure can follow?
- A migrated table can retain unintended access or lose required controls after namespace changes.
- Manual protection drift can expose fields on newly created tables before a review.
- Accumulated historical grants may give former project teams access to unrelated data products.
- Analysts may combine incompatible metrics and deliver unreliable reports.
Explanation
Correct Answer
B:The direct residual exposure is: Manual protection drift can expose fields on newly created tables before a review. The triggering condition is: A central security team manually adds row masking rules to every department table and new datasets repeatedly lack protection. The omitted safeguard is: Create compatible central ABAC policies based on governed classifications and verify inherited coverage. This matters because: ABAC can scale consistent data protection across tables matching policy attributes. A corrective test would show: A newly classified test table receives the prescribed mask and an authorized exception is documented.
Incorrect Answers
A: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: Manual protection drift can expose fields on newly created tables before a review.
C: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: Manual protection drift can expose fields on newly created tables before a review.
D:This failure mode belongs mainly to another situation: A business glossary has table names but no indication of which field is net revenue versus gross sales. Its preventative action would be: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. The most direct exposure in the current scenario is: Manual protection drift can expose fields on newly created tables before a review.
Question 876
An Azure Databricks architect reviews the following problem: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. What should the team implement FIRST?
- Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again.
- Preserve diagnostic events and Spark UI stage evidence before restart where possible.
- Use caching only for beneficial reuse and release persisted state when no longer needed.
- Compare workload contention and resource reservations, then isolate or resize the critical job compute.
Explanation
Correct Answer
C:The most appropriate action is: Use caching only for beneficial reuse and release persisted state when no longer needed. It addresses the stated condition: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. The technical basis is: Caching trades execution time for memory and may increase pressure when datasets are not reused. Without this control, unused cached data can cause eviction, spilling and unexpected failures for later stages. A direct acceptance check is: Spark storage metrics show released cache and unchanged correctness with improved total runtime.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A warehouse query remains slow even after larger compute is allocated and the profile reports scanning nearly every file. The corresponding measure there would be: Inspect query predicates and Delta data skipping or clustering layout before increasing warehouse size again. The stated situation instead calls for: Use caching only for beneficial reuse and release persisted state when no longer needed.
B:This alternative primarily addresses a different Azure Databricks problem: An operator restarts a failed Databricks cluster before collecting the Spark executor and driver logs. The corresponding measure there would be: Preserve diagnostic events and Spark UI stage evidence before restart where possible. The stated situation instead calls for: Use caching only for beneficial reuse and release persisted state when no longer needed.
D:This alternative primarily addresses a different Azure Databricks problem: A production notebook intermittently times out only when many other jobs share the same classic cluster. The corresponding measure there would be: Compare workload contention and resource reservations, then isolate or resize the critical job compute. The stated situation instead calls for: Use caching only for beneficial reuse and release persisted state when no longer needed.
Question 877
A solution applies: Inspect driver collection and query planning behavior before simply enlarging every worker. It addresses: A SQL transformation consumes large amounts of memory on the driver despite executor tasks processing most source partitions. Which operational outcome MOST directly verifies success?
- The scheduled job completes within its service objective and compute billing shows no unattended idle cluster hours.
- A forced restart of interactive compute leaves the scheduled production task unaffected.
- Permission tests show approved analysts run their notebooks while unauthorized cluster policy edits and installs fail.
- Spark UI and driver metrics show bounded driver memory after correcting the collection pattern.
Explanation
Correct Answer
D:The strongest acceptance proof is: Spark UI and driver metrics show bounded driver memory after correcting the collection pattern. It specifically verifies: Inspect driver collection and query planning behavior before simply enlarging every worker. The original issue was: A SQL transformation consumes large amounts of memory on the driver despite executor tasks processing most source partitions. The underlying mechanism is: Driver-side collection and planning bottlenecks cannot be corrected solely by scaling executor count. Without it, blindly increasing worker nodes leaves driver out-of-memory failures unchanged and increases cost.
Incorrect Answers
A: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: Spark UI and driver metrics show bounded driver memory after correcting the collection pattern.
B: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: Spark UI and driver metrics show bounded driver memory after correcting the collection pattern.
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: Spark UI and driver metrics show bounded driver memory after correcting the collection pattern.
Question 878
A data product owner adopts: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. The reason is: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. What observed result BEST proves effectiveness?
- A controlled late-event test updates the interval before its approved closeout and leaves later events for correction.
- A delayed-ingestion test prevents gold refresh until bronze and silver are completed successfully.
- A pipeline run updates tables in valid dependency order and records expectation outcomes.
- A seeded mismatch prevents cutover and the prior certified table remains queryable.
Explanation
Correct Answer
C:The strongest acceptance proof is: A pipeline run updates tables in valid dependency order and records expectation outcomes. It specifically verifies: Evaluate Lakeflow Spark Declarative Pipelines for the compatible streaming and transformation graph. The original issue was: A continuous feed creates and refreshes tables with consistent declarative dependencies but developers manually chain notebooks. The underlying mechanism is: Declarative pipelines express table dependencies and data quality rules without bespoke notebook orchestration. Without it, hand-built ordering can drift from the actual dependency graph as tables are added.
Incorrect Answers
A:This result would validate a different measure: Specify the stream watermark and an explicit closeout readiness condition before running downstream aggregation. That is relevant to the distinct problem: A streaming process depends on a downstream batch closeout but no one defines whether it should wait for the latest watermark. Here the acceptance criterion is: A pipeline run updates tables in valid dependency order and records expectation outcomes.
B:This result would validate a different measure: Define explicit Lakeflow Jobs task dependencies so silver and gold steps run only after their required predecessors succeed. That is relevant to the distinct problem: A sales pipeline aggregates gold metrics before the bronze ingestion task finishes and occasionally reports incomplete totals. Here the acceptance criterion is: A pipeline run updates tables in valid dependency order and records expectation outcomes.
D:This result would validate a different measure: Write to a staging target, validate row totals and invariants, then perform the approved publication step. That is relevant to the distinct problem: A finance transformation writes its output directly into a published table before reconciling totals against the source. Here the acceptance criterion is: A pipeline run updates tables in valid dependency order and records expectation outcomes.
Question 879
A platform architect adopts: Store deployment source in Git with reviewed branches and pull requests before promoting changes. For this requirement: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. Which rationale MOST directly supports it?
- Correctness under small inputs does not establish workload performance at production cardinality.
- Reproducible deployments require versioned execution dependencies as well as application code.
- Technical tests cannot replace business approval of the reported meaning of data.
- Version control and code review establish provenance and repeatable release history.
Explanation
Correct Answer
D:The decisive mechanism is: Version control and code review establish provenance and repeatable release history. That explains the selected action: Store deployment source in Git with reviewed branches and pull requests before promoting changes. In the original scenario: Engineers edit production notebooks directly and lose the ability to identify which code change broke a pipeline. The specific unmanaged risk is: Unreviewed direct edits can break jobs without a reproducible rollback commit. Validate with: A production run references an approved immutable commit and a prior version can be restored.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: An engineering test suite passes on miniature in-memory data yet fails in production on skewed billion-row joins. Its targeted response is: Include performance and end-to-end tests using representative scale and data distributions. The current case is governed more directly by: Version control and code review establish provenance and repeatable release history.
B:This principle concerns a separate data-engineering condition: A team cannot reproduce a prior release because package versions are resolved dynamically during deployment. Its targeted response is: Pin package and runtime versions in the governed release artifact and record its dependency manifest. The current case is governed more directly by: Version control and code review establish provenance and repeatable release history.
C:This principle concerns a separate data-engineering condition: A developer changes a transformation with a user-visible business effect but omits acceptance testing by the data product owner. Its targeted response is: Add user acceptance tests for the relevant reporting contract before production promotion. The current case is governed more directly by: Version control and code review establish provenance and repeatable release history.
Question 880
During a lakehouse implementation review, engineers observe: A long-running job using an unsupported custom system dependency is moved to serverless without checking feature compatibility. What is the BEST next action?
- Record and pin supported package versions in the workload deployment specification and test reproducibility.
- Review current serverless limitations and select compatible classic jobs compute when necessary.
- Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior.
- Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met.
Explanation
Correct Answer
B:The most appropriate action is: Review current serverless limitations and select compatible classic jobs compute when necessary. It addresses the stated condition: A long-running job using an unsupported custom system dependency is moved to serverless without checking feature compatibility. The technical basis is: Serverless and classic compute have different configuration surfaces and supported dependency patterns. Without this control, A serverless migration may fail when a required library or environment customization cannot be installed. A direct acceptance check is: A compatibility matrix and staging execution demonstrate every necessary dependency on the chosen compute.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A notebook workflow imports a Python package without pinning its version, producing different results after an environment update. The corresponding measure there would be: Record and pin supported package versions in the workload deployment specification and test reproducibility. The stated situation instead calls for: Review current serverless limitations and select compatible classic jobs compute when necessary.
C:This alternative primarily addresses a different Azure Databricks problem: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. The corresponding measure there would be: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. The stated situation instead calls for: Review current serverless limitations and select compatible classic jobs compute when necessary.
D:This alternative primarily addresses a different Azure Databricks problem: A long-running streaming pipeline is configured with aggressive auto-termination during brief periods without arriving events. The corresponding measure there would be: Select stream-appropriate compute and lifecycle settings so monitoring and availability targets are met. The stated situation instead calls for: Review current serverless limitations and select compatible classic jobs compute when necessary.