Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 22
Question 210
An implementation skips: Configure a tested Unity Catalog row filter or suitable ABAC policy based on the authorized identity. Engineers are observing: A user must see only the East region rows of a common sales table while managers see all territories. What consequence is MOST likely?
- An employee departure or password rotation can unexpectedly break critical production ingestion.
- A copied notebook may leak storage access keys beyond the intended data-processing environment.
- A retired vendor workload can continue reading business data through unchanged credentials.
- A user could retrieve other regions by querying the table without an application filter.
Explanation
Correct Answer
D:The direct residual exposure is: A user could retrieve other regions by querying the table without an application filter. The triggering condition is: A user must see only the East region rows of a common sales table while managers see all territories. The omitted safeguard is: Configure a tested Unity Catalog row filter or suitable ABAC policy based on the authorized identity. This matters because: Row-level security evaluates access rules at query time rather than relying on users to remember a WHERE clause. A corrective test would show: An East-region identity cannot read West-region test rows while the approved manager has the intended view.
Incorrect Answers
A: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 user could retrieve other regions by querying the table without an application filter.
B:This failure mode belongs mainly to another situation: A scheduled cloud-data ingestion needs an Azure storage identity but engineers embed a reusable account key inside notebooks. Its preventative action would be: Use a supported Azure managed identity and Unity Catalog storage credential or equivalent approved access path. The most direct exposure in the current scenario is: A user could retrieve other regions by querying the table without an application filter.
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: A user could retrieve other regions by querying the table without an application filter.
Question 211
A Databricks engineer recommends: Create a team-specific schema with ownership or delegated creation grants limited to that namespace. It responds to: A newly onboarded product team wants to create its own tables but should not have administration rights over every catalog. What underlying mechanism BEST explains why?
- Delegating within a governed schema supports self-service without tenant-wide administrative access.
- Foreign catalog semantics and connector capabilities differ from native managed Delta table operations.
- A view can define a query abstraction without requiring a second physical copy of source data.
- Reading a governed object does not imply permission to create or administer peer objects.
Explanation
Correct Answer
A:The decisive mechanism is: Delegating within a governed schema supports self-service without tenant-wide administrative access. That explains the selected action: Create a team-specific schema with ownership or delegated creation grants limited to that namespace. In the original scenario: A newly onboarded product team wants to create its own tables but should not have administration rights over every catalog. The specific unmanaged risk is: Global privileges may allow a team to alter or remove other products' data assets. Validate with: The product service principal creates in its own schema and fails the same operation in unrelated schemas.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. Its targeted response is: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. The current case is governed more directly by: Delegating within a governed schema supports self-service without tenant-wide administrative access.
C:This principle concerns a separate data-engineering condition: An analyst wants to expose a filtered projection of a governed table without copying sensitive source rows. Its targeted response is: Create a Unity Catalog view with approved permissions and verify underlying access semantics. The current case is governed more directly by: Delegating within a governed schema supports self-service without tenant-wide administrative access.
D:This principle concerns a separate data-engineering condition: A team expects every analyst to CREATE SCHEMA simply because they can SELECT tables in an existing catalog. Its targeted response is: Grant precise container-use and object-creation privileges based on actual job roles. The current case is governed more directly by: Delegating within a governed schema supports self-service without tenant-wide administrative access.
Question 212
A Databricks engineer recommends: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay. It responds to: A pipeline ingests Event Hubs messages into a bronze table but never captures the partition, offset or event timestamp. What underlying mechanism BEST explains why?
- Input extraction semantics determine whether repeated rows are new events or refreshed state.
- Managed ingestion connectors can simplify source synchronization when their coverage fits the source.
- Streaming source metadata supports provenance and exact-range incident investigation.
- CDC propagates source mutations without duplicating full snapshots.
Explanation
Correct Answer
C:The decisive mechanism is: Streaming source metadata supports provenance and exact-range incident investigation. That explains the selected action: Persist necessary source metadata and checkpoint lineage for troubleshooting and replay. In the original scenario: A pipeline ingests Event Hubs messages into a bronze table but never captures the partition, offset or event timestamp. The specific unmanaged risk is: A failed data-quality rule cannot be traced back to the event-bus record that produced it. Validate with: A sampled bronze row links to the expected stream partition and source event time.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A daily file load uses append-only mode for periodic snapshots of the same full inventory. Its targeted response is: Use a snapshot replacement or keyed MERGE strategy instead of appending every full snapshot as new records. The current case is governed more directly by: Streaming source metadata supports provenance and exact-range incident investigation.
B:This principle concerns a separate data-engineering condition: A batch integration needs a connector-managed path from a supported operational source into the lakehouse. Its targeted response is: Evaluate supported Lakeflow Connect ingestion rather than hardcoding ad hoc database extraction. The current case is governed more directly by: Streaming source metadata supports provenance and exact-range incident investigation.
D: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: Streaming source metadata supports provenance and exact-range incident investigation.
Question 213
The team chooses: Create an eligible materialized view or managed derived table with appropriate refresh and access rules. Its observed issue is: A BI group needs to query a materialized aggregate while the source transaction Delta table changes hourly. What is the strongest technical basis?
- Materialized views can persist derived query results, but refresh behavior must match freshness expectations.
- Consistent identifiers reduce accidental parsing and namespace resolution differences.
- Metadata definitions, locations and privileges must align after a table lifecycle transition.
- Managed versus external tables differ in who manages data paths and deletion behavior.
Explanation
Correct Answer
A:The decisive mechanism is: Materialized views can persist derived query results, but refresh behavior must match freshness expectations. That explains the selected action: Create an eligible materialized view or managed derived table with appropriate refresh and access rules. In the original scenario: A BI group needs to query a materialized aggregate while the source transaction Delta table changes hourly. The specific unmanaged risk is: Users can unknowingly consume stale aggregates if refresh ownership and schedule are unspecified. Validate with: A source update followed by the documented refresh produces reconciled aggregate totals.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: An ingestion team creates a table with a reserved or inconsistent name and automation fails in one environment. Its targeted response is: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers. The current case is governed more directly by: Materialized views can persist derived query results, but refresh behavior must match freshness expectations.
C:This principle concerns a separate data-engineering condition: A managed Delta table is migrated to external storage but the team does not update table registration or grant scopes. Its targeted response is: Recreate or update supported external table registration using an approved location and correct access controls. The current case is governed more directly by: Materialized views can persist derived query results, but refresh behavior must match freshness expectations.
D: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: Materialized views can persist derived query results, but refresh behavior must match freshness expectations.
Question 214
The team implements: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. The original problem is: A business glossary has table names but no indication of which field is net revenue versus gross sales. Which test MOST convincingly demonstrates correctness?
- Authorized privacy reviewers see full test values while ordinary report roles see only permitted redactions.
- A normal reader cannot remove the governed tag while approved stewards' edits produce audit evidence.
- A simulated cleanup retains protected history and an audit maps the new duration to approved settings.
- A data steward can find the certified revenue definition and verify the correct field in Catalog Explorer.
Explanation
Correct Answer
D:The strongest acceptance proof is: A data steward can find the certified revenue definition and verify the correct field in Catalog Explorer. It specifically verifies: Add reviewed Unity Catalog table and column comments, owners and business definitions for consumer discovery. The original issue was: A business glossary has table names but no indication of which field is net revenue versus gross sales. The underlying mechanism is: Governed descriptive metadata reduces ambiguity and supports correct analytical interpretation. Without it, analysts may combine incompatible metrics and deliver unreliable reports.
Incorrect Answers
A:This result would validate a different measure: Develop an approved role-aware column mask and test its outputs across supported query clients. That is relevant to the distinct problem: A data product stores PII in a shared Delta table but several reports require different masking for each audience. Here the acceptance criterion is: A data steward can find the certified revenue definition and verify the correct field in Catalog Explorer.
B: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: A data steward can find the certified revenue definition and verify the correct field in Catalog Explorer.
C:This result would validate a different measure: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. That is relevant to the distinct problem: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. Here the acceptance criterion is: A data steward can find the certified revenue definition and verify the correct field in Catalog Explorer.
Question 215
A solution applies: Create compatible central ABAC policies based on governed classifications and verify inherited coverage. It addresses: A central security team manually adds row masking rules to every department table and new datasets repeatedly lack protection. Which operational outcome MOST directly verifies success?
- A newly classified test table receives the prescribed mask and an authorized exception is documented.
- A hold rehearsal retrieves the original protected records and documents preservation scope and access.
- A seeded transformation appears with its expected upstream source and downstream target in lineage.
- A test recipient reads the expected daily aggregate and cannot enumerate underlying detailed transaction records.
Explanation
Correct Answer
A:The strongest acceptance proof is: A newly classified test table receives the prescribed mask and an authorized exception is documented. It specifically verifies: Create compatible central ABAC policies based on governed classifications and verify inherited coverage. The original issue was: A central security team manually adds row masking rules to every department table and new datasets repeatedly lack protection. The underlying mechanism is: ABAC can scale consistent data protection across tables matching policy attributes. Without it, manual protection drift can expose fields on newly created tables before a review.
Incorrect Answers
B:This result would validate a different measure: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. That is relevant to the distinct problem: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. Here the acceptance criterion is: A newly classified test table receives the prescribed mask and an authorized exception is documented.
C:This result would validate a different measure: Inspect Unity Catalog data lineage and table history in Catalog Explorer, checking actual supported capture coverage. That is relevant to the distinct problem: An analyst wants to know which upstream pipeline produced a metric displayed in a board dashboard. Here the acceptance criterion is: A newly classified test table receives the prescribed mask and an authorized exception is documented.
D:This result would validate a different measure: Publish a restricted derived dataset through Delta Sharing after privacy and freshness validation. That is relevant to the distinct problem: A customer wants to share only a daily refreshed aggregate, not raw personally identifiable transactions. Here the acceptance criterion is: A newly classified test table receives the prescribed mask and an authorized exception is documented.
Question 216
A Databricks engineer recommends: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. It responds to: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. What underlying mechanism BEST explains why?
- Creating an external table requires governed location and storage authorization beyond a generic schema creation grant.
- Security of a view depends on the complete authorization path, not merely its SELECT projection.
- Object discovery or BROWSE is not a grant to read its underlying data.
- Separation of duties requires independent decisions for object administration, data modification and read access.
Explanation
Correct Answer
B:The decisive mechanism is: Security of a view depends on the complete authorization path, not merely its SELECT projection. That explains the selected action: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. In the original scenario: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. The specific unmanaged risk is: A user may bypass the masked presentation by reading the unmasked source table. Validate with: Direct source queries are denied for analysts while the governed view produces the approved masked data.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A user is granted CREATE TABLE but cannot create an external table at an unregistered cloud path. Its targeted response is: Configure a supported external location and specific creation privileges rather than bypassing the catalog to write directly. The current case is governed more directly by: Security of a view depends on the complete authorization path, not merely its SELECT projection.
C:This principle concerns a separate data-engineering condition: An analyst can view the names of confidential tables and assumes browsing metadata implies permission to query records. Its targeted response is: Separate discoverability privileges from USE and SELECT privileges in the catalog permissions model. The current case is governed more directly by: Security of a view depends on the complete authorization path, not merely its SELECT projection.
D:This principle concerns a separate data-engineering condition: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. Its targeted response is: Replace broad grants with documented minimum creation and use privileges in a dedicated schema. The current case is governed more directly by: Security of a view depends on the complete authorization path, not merely its SELECT projection.
Question 217
A platform architect adopts: Collect expectation metrics and reconcile input, accepted, quarantined and rejected record counts. For this requirement: A pipeline reports zero failed rows because bad records are silently dropped without any count of what was removed. Which rationale MOST directly supports it?
- Schema governance must span all ingestion paths that write to a common table.
- Primary business-key uniqueness is a semantic data-quality invariant even without enforced physical primary keys.
- Valid data type does not guarantee semantic range correctness.
- Measurable quality controls need observable outcomes and accounting for rejected data.
Explanation
Correct Answer
D:The decisive mechanism is: Measurable quality controls need observable outcomes and accounting for rejected data. That explains the selected action: Collect expectation metrics and reconcile input, accepted, quarantined and rejected record counts. In the original scenario: A pipeline reports zero failed rows because bad records are silently dropped without any count of what was removed. The specific unmanaged risk is: A seemingly successful load can conceal a growing upstream data-loss problem. Validate with: Each run reports complete input-to-output reconciliation and alerts when rejected fraction exceeds its SLO.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: An engineer changes the expected file schema in one notebook but forgets to update the Lakeflow pipeline definition. Its targeted response is: Maintain a governed schema contract and integration tests across both notebook and declarative pipeline paths. The current case is governed more directly by: Measurable quality controls need observable outcomes and accounting for rejected data.
B:This principle concerns a separate data-engineering condition: A curated account table accidentally contains multiple rows per supposedly unique current account ID. Its targeted response is: Run a supported uniqueness or cardinality validation during the transformation and surface violations. The current case is governed more directly by: Measurable quality controls need observable outcomes and accounting for rejected data.
C:This principle concerns a separate data-engineering condition: A bronze stream sometimes includes ages below zero or above 120 yet the transformation casts every value to integer. Its targeted response is: Define a range expectation with metrics and the approved drop, fail or quarantine disposition. The current case is governed more directly by: Measurable quality controls need observable outcomes and accounting for rejected data.
Question 218
For this Azure Databricks issue: A department wants a self-service sandbox but must prevent users from creating huge unrestricted clusters. Engineers choose: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users. What acceptance evidence is BEST?
- Clean-environment executions install the approved versions and return matching deterministic results.
- An ordinary user can start an approved small cluster but cannot exceed policy size or runtime limits.
- A load rehearsal meets dashboard p95 response targets while notebook resource spikes do not affect query service.
- Load tests for normal and month-end volumes satisfy runtime targets without exceeding the approved worker ceiling.
Explanation
Correct Answer
B:The strongest acceptance proof is: An ordinary user can start an approved small cluster but cannot exceed policy size or runtime limits. It specifically verifies: Create compute policies with approved node types, worker limits, tags and idle settings for the permitted users. The original issue was: A department wants a self-service sandbox but must prevent users from creating huge unrestricted clusters. The underlying mechanism is: Compute policies provide governance boundaries for permissible resource configurations. Without it, unrestricted cluster creation can create unpredictable spending and inconsistent operational standards.
Incorrect Answers
A:This result would validate a different measure: Record and pin supported package versions in the workload deployment specification and test reproducibility. That is relevant to the distinct problem: A notebook workflow imports a Python package without pinning its version, producing different results after an environment update. Here the acceptance criterion is: An ordinary user can start an approved small cluster but cannot exceed policy size or runtime limits.
C:This result would validate a different measure: Use an appropriately sized SQL warehouse with workload isolation and measured concurrency for dashboard queries. That is relevant to the distinct problem: Analysts run short SQL dashboard queries against a shared lakehouse but their notebooks share a general-purpose Spark cluster with training experiments. Here the acceptance criterion is: An ordinary user can start an approved small cluster but cannot exceed policy size or runtime limits.
D:This result would validate a different measure: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. That is relevant to the distinct problem: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. Here the acceptance criterion is: An ordinary user can start an approved small cluster but cannot exceed policy size or runtime limits.
Question 219
A pipeline owner declines the action: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers. The business situation is: An ingestion team creates a table with a reserved or inconsistent name and automation fails in one environment. What specific failure can follow?
- An ownerless shared view may expose unreviewed columns or become impossible to maintain safely.
- An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts.
- Users may query raw unvalidated records as though they were approved curated metrics.
- Global privileges may allow a team to alter or remove other products' data assets.
Explanation
Correct Answer
B:The direct residual exposure is: An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts. The triggering condition is: An ingestion team creates a table with a reserved or inconsistent name and automation fails in one environment. The omitted safeguard is: Adopt a portable naming and quoting convention compatible with Unity Catalog SQL identifiers. This matters because: Consistent identifiers reduce accidental parsing and namespace resolution differences. A corrective test would show: Automated DDL completes in both staging and production under the same naming rules.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A central team creates global views that hide source objects but forgets to document ownership and access grants. Its preventative action would be: Assign view ownership and narrowly scoped permissions under the appropriate Unity Catalog schema. The most direct exposure in the current scenario is: An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts.
C:This failure mode belongs mainly to another situation: Multiple data products put raw, refined and curated assets into a single schema with confusing table names. Its preventative action would be: Define a consistent schema and naming architecture separating layers and business domains by purpose. The most direct exposure in the current scenario is: An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts.
D:This failure mode belongs mainly to another situation: A newly onboarded product team wants to create its own tables but should not have administration rights over every catalog. Its preventative action would be: Create a team-specific schema with ownership or delegated creation grants limited to that namespace. The most direct exposure in the current scenario is: An inconsistent identifier forces manual quoting and breaks repeatable deployment scripts.
Question 220
A Databricks engineer recommends: Investigate stage runtime growth and enforce appropriate concurrency policy before raising frequency. It responds to: A job scheduled each hour starts running for 80 minutes and overlaps the next run. What underlying mechanism BEST explains why?
- Scheduling cannot guarantee freshness when actual execution exceeds the interval.
- A single hot partition can dominate a distributed stage despite idle executor capacity.
- Task-level repair can reduce replay cost while preserving successful work.
- Centralized telemetry supports durable troubleshooting when ephemeral compute terminates.
Explanation
Correct Answer
A:The decisive mechanism is: Scheduling cannot guarantee freshness when actual execution exceeds the interval. That explains the selected action: Investigate stage runtime growth and enforce appropriate concurrency policy before raising frequency. In the original scenario: A job scheduled each hour starts running for 80 minutes and overlaps the next run. The specific unmanaged risk is: Overlapping backlogs can amplify compute consumption and create conflicting writes. Validate with: Load testing shows completion within the target window and queued runs do not overlap unsafely.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: A production Spark query is slow and its stage graph shows one task running far longer than all peers. Its targeted response is: Inspect the Spark UI DAG and skewed-key distribution before changing cluster size. The current case is governed more directly by: Scheduling cannot guarantee freshness when actual execution exceeds the interval.
C: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: Scheduling cannot guarantee freshness when actual execution exceeds the interval.
D:This principle concerns a separate data-engineering condition: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. Its targeted response is: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention. The current case is governed more directly by: Scheduling cannot guarantee freshness when actual execution exceeds the interval.