Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 57
Question 560
A data engineering team faces this Azure Databricks requirement: A newly onboarded product team wants to create its own tables but should not have administration rights over every catalog. Which action is MOST appropriate?
- Create environment-specific Unity Catalog catalogs or schemas and enforce clear ownership and naming conventions.
- Use fully qualified names and a controlled default namespace in deployment SQL and notebooks.
- Create a team-specific schema with ownership or delegated creation grants limited to that namespace.
- Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers.
Explanation
Correct Answer
C:The most appropriate action is: Create a team-specific schema with ownership or delegated creation grants limited to that namespace. It addresses the stated condition: A newly onboarded product team wants to create its own tables but should not have administration rights over every catalog. The technical basis is: Delegating within a governed schema supports self-service without tenant-wide administrative access. Without this control, global privileges may allow a team to alter or remove other products' data assets. A direct acceptance check is: The product service principal creates in its own schema and fails the same operation in unrelated schemas.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: Production and development teams create identically named data objects in one catalog and accidentally overwrite test tables. The corresponding measure there would be: Create environment-specific Unity Catalog catalogs or schemas and enforce clear ownership and naming conventions. The stated situation instead calls for: Create a team-specific schema with ownership or delegated creation grants limited to that namespace.
B:This alternative primarily addresses a different Azure Databricks problem: An automation pipeline issues CREATE TABLE without qualifying the target catalog and schema. The corresponding measure there would be: Use fully qualified names and a controlled default namespace in deployment SQL and notebooks. The stated situation instead calls for: Create a team-specific schema with ownership or delegated creation grants limited to that namespace.
D:This alternative primarily addresses a different Azure Databricks problem: An ingestion team creates a table with a reserved or inconsistent name and automation fails in one environment. The corresponding measure there would be: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers. The stated situation instead calls for: Create a team-specific schema with ownership or delegated creation grants limited to that namespace.
Question 561
The design team proposes: Choose a controlled CREATE OR REPLACE TABLE or compatible atomic table-replacement strategy and validate schema/permissions. The situation is: An existing table must be rebuilt from corrected historical files while its readers require a consistent atomic replacement. Which technical principle justifies the decision?
- Atomic table replacement can avoid exposing a partially loaded intermediate table.
- CDC propagates source mutations without duplicating full snapshots.
- Freshness requirements should determine batch versus streaming design.
- Message-bus streams require offset progress tracking and a durable state boundary.
Explanation
Correct Answer
A:The decisive mechanism is: Atomic table replacement can avoid exposing a partially loaded intermediate table. That explains the selected action: Choose a controlled CREATE OR REPLACE TABLE or compatible atomic table-replacement strategy and validate schema/permissions. In the original scenario: An existing table must be rebuilt from corrected historical files while its readers require a consistent atomic replacement. The specific unmanaged risk is: Dropping then recreating tables may interrupt readers and lose associated governance settings. Validate with: Readers observe a complete validated target before or after cutover, not partial data.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A SaaS database updates and deletes customer records but a pipeline appends every nightly full extract to a Delta table. Its targeted response is: Use a supported change-data-capture feed and apply insert, update and delete semantics to the target. The current case is governed more directly by: Atomic table replacement can avoid exposing a partially loaded intermediate table.
C:This principle concerns a separate data-engineering condition: A team selects batch processing for customer account changes though downstream applications require minute-scale freshness. Its targeted response is: Use supported streaming or sufficiently frequent incremental CDC with measured end-to-end latency. The current case is governed more directly by: Atomic table replacement can avoid exposing a partially loaded intermediate table.
D:This principle concerns a separate data-engineering condition: A product emits append-only telemetry to Azure Event Hubs and dashboards need near-real-time processing. Its targeted response is: Use a supported Spark Structured Streaming or Lakeflow streaming source with an Event Hubs connection and checkpoint. The current case is governed more directly by: Atomic table replacement can avoid exposing a partially loaded intermediate table.
Question 562
An implementation skips: Configure event-time windowing and an appropriate watermark based on observed lateness. Engineers are observing: A stream must group clicks into five-minute event-time windows while some mobile devices transmit data several minutes late. What consequence is MOST likely?
- Misparsed columns can populate nulls while the batch appears to complete successfully.
- A bespoke long-running stream for a one-time load adds complexity and idle cost.
- Too-short watermark drops legitimate delayed events; too-long state retention may exhaust memory.
- Out-of-order events can regress a target from its latest state to a stale state.
Explanation
Correct Answer
C:The direct residual exposure is: Too-short watermark drops legitimate delayed events; too-long state retention may exhaust memory. The triggering condition is: A stream must group clicks into five-minute event-time windows while some mobile devices transmit data several minutes late. The omitted safeguard is: Configure event-time windowing and an appropriate watermark based on observed lateness. This matters because: Watermarks define the tolerated late-event horizon for stateful stream processing. A corrective test would show: Events arriving within the allowed lateness update the intended window and older events follow documented handling.
Incorrect Answers
A:This failure mode belongs mainly to another situation: An overnight load reads tab-separated files but an engineer assumes comma separators and casts malformed columns to null. Its preventative action would be: Specify the correct input delimiter, header and schema and validate parsing on a representative file. The most direct exposure in the current scenario is: Too-short watermark drops legitimate delayed events; too-long state retention may exhaust memory.
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: Too-short watermark drops legitimate delayed events; too-long state retention may exhaust memory.
D: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: Too-short watermark drops legitimate delayed events; too-long state retention may exhaust memory.
Question 563
A platform architect adopts: Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access. For this requirement: A Delta Sharing recipient must stop receiving future updates after an agreement expires. Which rationale MOST directly supports it?
- Data lineage links producers, transformations and consumers where observed activity is supported.
- Row filters can restrict query results without maintaining separate physical copies by region.
- External sharing must include explicit revocation and monitoring, not only initial provisioning.
- Tag-based access control relies on trusted management of the tags themselves.
Explanation
Correct Answer
C:The decisive mechanism is: External sharing must include explicit revocation and monitoring, not only initial provisioning. That explains the selected action: Revoke or disable the relevant Delta Sharing recipient/share permissions and verify subsequent access. In the original scenario: A Delta Sharing recipient must stop receiving future updates after an agreement expires. The specific unmanaged risk is: Expired partners may retain ongoing data access despite a terminated agreement. Validate with: A partner query fails after revocation while internal consumers remain able to read the dataset.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: An analyst wants to know which upstream pipeline produced a metric displayed in a board dashboard. Its targeted response is: Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage. The current case is governed more directly by: External sharing must include explicit revocation and monitoring, not only initial provisioning.
B:This principle concerns a separate data-engineering condition: A shared customer table needs dynamic per-region row restrictions but the business refuses duplicating physical datasets. Its targeted response is: Use row-filter policies on the governed table and test permitted region entitlements. The current case is governed more directly by: External sharing must include explicit revocation and monitoring, not only initial provisioning.
D:This principle concerns a separate data-engineering condition: A governance team tags columns as restricted but anyone can remove the tag to bypass attached policies. Its targeted response is: Restrict governed-tag administration and audit changes to protected metadata. The current case is governed more directly by: External sharing must include explicit revocation and monitoring, not only initial provisioning.
Question 564
For this Azure Databricks issue: An operations group wants to roll back a broken Lakeflow workflow but keeps no previous package version. Engineers choose: Tag and retain approved bundle releases and document a verified redeploy or rollback procedure. What acceptance evidence is BEST?
- An injected API rejection makes CI fail with a traceable error and leaves production unchanged.
- A rendered staging plan references only staging catalogs and refuses production resource paths.
- A rehearsed rollback restores a prior tested bundle and recovers the expected job definitions.
- A product owner signs off a sample report and its reconciled acceptance criteria before rollout.
Explanation
Correct Answer
C:The strongest acceptance proof is: A rehearsed rollback restores a prior tested bundle and recovers the expected job definitions. It specifically verifies: Tag and retain approved bundle releases and document a verified redeploy or rollback procedure. The original issue was: An operations group wants to roll back a broken Lakeflow workflow but keeps no previous package version. The underlying mechanism is: Immutable release versions enable controlled recovery of pipeline configuration and code. Without it, without versioned artifacts, recovery may require reconstructing past settings by memory.
Incorrect Answers
A:This result would validate a different measure: Validate API status and returned resource identifiers, then use bounded retries only for transient failures. That is relevant to the distinct problem: An automation job uses Databricks REST APIs but omits response-code checks and assumes every HTTP request succeeded. Here the acceptance criterion is: A rehearsed rollback restores a prior tested bundle and recovers the expected job definitions.
B:This result would validate a different measure: Define and validate environment-specific catalog, workspace and identity targets in deployment configuration. That is relevant to the distinct problem: A multi-environment setup uses the same catalog for test and production because bundle target variables were omitted. Here the acceptance criterion is: A rehearsed rollback restores a prior tested bundle and recovers the expected job definitions.
D:This result would validate a different measure: Add user acceptance tests for the relevant reporting contract before production promotion. That is relevant to the distinct problem: A developer changes a transformation with a user-visible business effect but omits acceptance testing by the data product owner. Here the acceptance criterion is: A rehearsed rollback restores a prior tested bundle and recovers the expected job definitions.
Question 565
The team chooses: Keep a governed raw or bronze representation before applying irreversible cleansing into silver and gold. Its observed issue is: A bronze ingestion layer stores only final transformed values and loses raw source fields needed for incident replay. What is the strongest technical basis?
- Data models balance redundancy and query simplicity according to workload requirements.
- A star schema separates measurable events from descriptive dimensions and controls join cardinality.
- Layered lakehouse processing separates source fidelity from approved business transformations.
- CTAS populates a table at execution time and does not imply continuous synchronization with source.
Explanation
Correct Answer
C:The decisive mechanism is: Layered lakehouse processing separates source fidelity from approved business transformations. That explains the selected action: Keep a governed raw or bronze representation before applying irreversible cleansing into silver and gold. In the original scenario: A bronze ingestion layer stores only final transformed values and loses raw source fields needed for incident replay. The specific unmanaged risk is: Without recoverable raw inputs the team cannot replay a transformation after discovering a rule defect. Validate with: A replay from a preserved source batch reproduces the expected silver and gold data after a code fix.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A customer table includes both region hierarchy and customers; teams disagree whether to snowflake descriptive attributes. Its targeted response is: Evaluate dimensional normalization against query complexity, maintenance and expected cardinality. The current case is governed more directly by: Layered lakehouse processing separates source fidelity from approved business transformations.
B: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: Layered lakehouse processing separates source fidelity from approved business transformations.
D:This principle concerns a separate data-engineering condition: A pipeline uses CREATE TABLE AS SELECT for a one-time derived dataset but later assumes the result refreshes automatically. Its targeted response is: Select CTAS for an explicitly materialized snapshot or a scheduled pipeline for ongoing refresh. The current case is governed more directly by: Layered lakehouse processing separates source fidelity from approved business transformations.
Question 566
A data engineering team faces this Azure Databricks requirement: A production notebook intermittently times out only when many other jobs share the same classic cluster. Which action is MOST appropriate?
- Compare workload contention and resource reservations, then isolate or resize the critical job compute.
- Use run-level compute utilization, cost and stage metrics to identify unused capacity.
- Profile aggregation key distribution, shuffle partitions and executor memory before choosing a targeted change.
- Use caching only for beneficial reuse and release persisted state when no longer needed.
Explanation
Correct Answer
A:The most appropriate action is: Compare workload contention and resource reservations, then isolate or resize the critical job compute. It addresses the stated condition: A production notebook intermittently times out only when many other jobs share the same classic cluster. The technical basis is: Shared compute competition can cause unpredictable task latency independent of input correctness. Without this control, A critical SLA may depend on unrelated teams' scheduling and resource usage. A direct acceptance check is: The isolated benchmark meets its percentile duration under simultaneous unrelated workload pressure.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A pipeline experiences escalating costs after a team increases node counts but execution duration barely changes. The corresponding measure there would be: Use run-level compute utilization, cost and stage metrics to identify unused capacity. The stated situation instead calls for: Compare workload contention and resource reservations, then isolate or resize the critical job compute.
C: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: Compare workload contention and resource reservations, then isolate or resize the critical job compute.
D:This alternative primarily addresses a different Azure Databricks problem: A team enables Spark cache for a one-time ETL dataset and never unpersists it before processing the next large table. The corresponding measure there would be: Use caching only for beneficial reuse and release persisted state when no longer needed. The stated situation instead calls for: Compare workload contention and resource reservations, then isolate or resize the critical job compute.
Question 567
The design team proposes: Compare selective filter patterns and data-skipping statistics before committing partition and clustering keys. The situation is: A query repeatedly filters by customer, date and product but the physical data design was selected without query-profile evidence. Which technical principle justifies the decision?
- Efficient layout keys are driven by actual access patterns and file statistics.
- Physical layout should match selective consumer predicates rather than convenience of ingestion.
- Ingestion strategy should match whether source records can be corrected or deleted.
- Data models balance redundancy and query simplicity according to workload requirements.
Explanation
Correct Answer
A:The decisive mechanism is: Efficient layout keys are driven by actual access patterns and file statistics. That explains the selected action: Compare selective filter patterns and data-skipping statistics before committing partition and clustering keys. In the original scenario: A query repeatedly filters by customer, date and product but the physical data design was selected without query-profile evidence. The specific unmanaged risk is: Poorly chosen keys increase full scans and maintenance overhead as traffic grows. Validate with: A measured workload benchmark shows scan reduction across the highest-value query templates.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: An event stream is partitioned by ingestion day but analysts constantly filter by event timestamp ranges crossing midnight. Its targeted response is: Reevaluate data layout using representative event-time filters and a suitable clustering key. The current case is governed more directly by: Efficient layout keys are driven by actual access patterns and file statistics.
C:This principle concerns a separate data-engineering condition: A raw event lake contains append-only records but a developer chooses daily full overwrite of the curated Delta table. Its targeted response is: Choose incremental append or merge based on immutable versus mutable source behavior. The current case is governed more directly by: Efficient layout keys are driven by actual access patterns and file statistics.
D: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: Efficient layout keys are driven by actual access patterns and file statistics.
Question 568
A solution applies: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger. It addresses: An ingestion job requires a one-time backfill without changing the future daily production schedule. Which operational outcome MOST directly verifies success?
- The historical batch completes with reconciled counts and next daily scheduled run remains unchanged.
- Run history records one intended business date and every task publishes that same interval.
- A scheduled run succeeds under the named service principal after the former owner account is disabled.
- A staged predecessor failure shows the approved downstream skip and cleanup path in run history.
Explanation
Correct Answer
A:The strongest acceptance proof is: The historical batch completes with reconciled counts and next daily scheduled run remains unchanged. It specifically verifies: Run a controlled parameterized manual invocation for the historical interval while retaining the regular trigger. The original issue was: An ingestion job requires a one-time backfill without changing the future daily production schedule. The underlying mechanism is: Backfills should be separated from ordinary schedules to avoid accidental duplicate processing. Without it, temporarily editing the main schedule may skip normal deliveries or replay wrong dates.
Incorrect Answers
B:This result would validate a different measure: Define validated job parameters and propagate them through supported task parameter bindings. That is relevant to the distinct problem: A workflow needs to pass a date parameter from a scheduled trigger into all its downstream notebook tasks. Here the acceptance criterion is: The historical batch completes with reconciled counts and next daily scheduled run remains unchanged.
C:This result would validate a different measure: Assign a dedicated run-as identity with durable scoped grants and an ownership review. That is relevant to the distinct problem: A job uses a service principal that loses access to the destination schema when an employee leaves. Here the acceptance criterion is: The historical batch completes with reconciled counts and next daily scheduled run remains unchanged.
D:This result would validate a different measure: Review explicit dependency and run-if settings and validate skip behavior through a staged failure. That is relevant to the distinct problem: A job owner cannot explain why a task skipped execution after a predecessor failed. Here the acceptance criterion is: The historical batch completes with reconciled counts and next daily scheduled run remains unchanged.
Question 569
For this Microsoft DP-750 case: A production workload uses a personal access token stored in Git for Databricks REST calls. Which design or operational response BEST fits?
- Replace committed personal credentials with supported workload authentication and revoke exposed tokens.
- Replace broad grants with documented minimum creation and use privileges in a dedicated schema.
- Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported.
- Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model.
Explanation
Correct Answer
A:The most appropriate action is: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. It addresses the stated condition: A production workload uses a personal access token stored in Git for Databricks REST calls. The technical basis is: Automation authentication should be auditable, nonpersonal and resistant to repository exposure. Without this control, an attacker obtaining the repository could invoke Databricks APIs with a broad personal identity. A direct acceptance check is: The pipeline executes under a scoped service identity and the old token is revoked and rejected.
Incorrect Answers
B:This alternative primarily addresses a different Azure Databricks problem: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. The corresponding measure there would be: Replace broad grants with documented minimum creation and use privileges in a dedicated schema. The stated situation instead calls for: Replace committed personal credentials with supported workload authentication and revoke exposed tokens.
C:This alternative primarily addresses a different Azure Databricks problem: A data compliance team needs consistent redaction of columns tagged as personal data across hundreds of catalog tables. The corresponding measure there would be: Use centrally governed tags and compatible Unity Catalog ABAC masking policies where supported. The stated situation instead calls for: Replace committed personal credentials with supported workload authentication and revoke exposed tokens.
D:This alternative primarily addresses a different Azure Databricks problem: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. The corresponding measure there would be: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. The stated situation instead calls for: Replace committed personal credentials with supported workload authentication and revoke exposed tokens.
Question 570
The recommended measure is: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. The operational context is: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. Which data engineering concept applies?
- Logical deletes can leave physical layout and scan behavior needing maintenance.
- Sustained source-to-sink throughput below arrival rate causes accumulating data freshness debt.
- VACUUM removes old physical files, so aggressive cleanup can break valid historical references.
- Task-level repair can reduce replay cost while preserving successful work.
Explanation
Correct Answer
C:The decisive mechanism is: VACUUM removes old physical files, so aggressive cleanup can break valid historical references. That explains the selected action: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. In the original scenario: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. The specific unmanaged risk is: Premature deletion may invalidate time travel or a lagging reader's file references. Validate with: A permitted historical query succeeds before and after approved housekeeping within its retention boundary.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A query on a Delta table slows after a small percentage of rows are deleted but data files are not optimized. Its targeted response is: Review deletion-vector behavior, table layout and suitable optimization for the supported runtime. The current case is governed more directly by: VACUUM removes old physical files, so aggressive cleanup can break valid historical references.
B:This principle concerns a separate data-engineering condition: A streaming pipeline's throughput falls although event arrival increases and its input backlog grows over time. Its targeted response is: Compare incoming event rate, processed records, watermark progress and state-store metrics before scaling. The current case is governed more directly by: VACUUM removes old physical files, so aggressive cleanup can break valid historical references.
D: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: VACUUM removes old physical files, so aggressive cleanup can break valid historical references.