Implementing Data Engineering Solutions Using Azure Databricks DP-750 Practice Test 5
Question 40
The team chooses: Choose incremental append or merge based on immutable versus mutable source behavior. Its observed issue is: A raw event lake contains append-only records but a developer chooses daily full overwrite of the curated Delta table. What is the strongest technical basis?
- Delta tables support transactional mutations and versioned metadata beyond raw delimiter files.
- Temporal tables describe the validity of state over time rather than only its latest value.
- Liquid clustering and traditional ZORDER/partitioning have compatibility constraints and different maintenance paths.
- Ingestion strategy should match whether source records can be corrected or deleted.
Explanation
Correct Answer
D:The decisive mechanism is: Ingestion strategy should match whether source records can be corrected or deleted. That explains the selected action: Choose incremental append or merge based on immutable versus mutable source behavior. In the original scenario: A raw event lake contains append-only records but a developer chooses daily full overwrite of the curated Delta table. The specific unmanaged risk is: Unnecessary overwrites increase compute cost and can cause data loss during partial reruns. Validate with: Two successive batches load only new records while preserved history and counts reconcile.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A reporting team stores frequent updates in raw CSV files and expects atomic MERGE and historical time travel. Its targeted response is: Use a managed Delta table for transactional updates and controlled schema evolution. The current case is governed more directly by: Ingestion strategy should match whether source records can be corrected or deleted.
B:This principle concerns a separate data-engineering condition: A historical compliance table must show how account status changed at precise effective intervals. Its targeted response is: Use a temporal history model with nonoverlapping effective-from and effective-to boundaries. The current case is governed more directly by: Ingestion strategy should match whether source records can be corrected or deleted.
C:This principle concerns a separate data-engineering condition: A team attempts to apply both ZORDER and liquid clustering to the same Delta table. Its targeted response is: Choose one compatible data layout strategy based on table format, platform support and query evidence. The current case is governed more directly by: Ingestion strategy should match whether source records can be corrected or deleted.
Question 41
An Azure Databricks architect reviews the following problem: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. What should the team implement FIRST?
- Select managed or external Unity Catalog table ownership intentionally and verify lifecycle semantics.
- Check federation connector capabilities and distinguish read-only remote access from supported writable local tables.
- Define a stable contract through managed views and test compatibility before changing source objects.
- Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities.
Explanation
Correct Answer
B:The most appropriate action is: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables. It addresses the stated condition: A foreign catalog is connected to a remote database but an analyst expects standard managed Delta writes against it. The technical basis is: Foreign catalog semantics and connector capabilities differ from native managed Delta table operations. Without this control, assuming full DDL or mutation support may cause failed deployments or inadvertent source changes. A direct acceptance check is: A capability test documents supported query and write operations and prevents unsupported mutations.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: A team expects dropping a managed table to preserve all physical data as though it were an external table. The corresponding measure there would be: Select managed or external Unity Catalog table ownership intentionally and verify lifecycle semantics. The stated situation instead calls for: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables.
C:This alternative primarily addresses a different Azure Databricks problem: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. The corresponding measure there would be: Define a stable contract through managed views and test compatibility before changing source objects. The stated situation instead calls for: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables.
D:This alternative primarily addresses a different Azure Databricks problem: A data pipeline creates a physical table for a reporting transformation that would be better maintained as a query definition. The corresponding measure there would be: Choose a view, materialized view or stored table based on freshness, cost and refresh responsibilities. The stated situation instead calls for: Check federation connector capabilities and distinguish read-only remote access from supported writable local tables.
Question 42
The recommended measure is: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. The operational context is: A production workload uses a personal access token stored in Git for Databricks REST calls. Which data engineering concept applies?
- Automation authentication should be auditable, nonpersonal and resistant to repository exposure.
- Read and write operations require distinct Unity Catalog privileges and operating identities.
- Security of a view depends on the complete authorization path, not merely its SELECT projection.
- Cloud IAM and Unity Catalog are complementary authorization layers that must both permit the intended operation.
Explanation
Correct Answer
A:The decisive mechanism is: Automation authentication should be auditable, nonpersonal and resistant to repository exposure. That explains the selected action: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. In the original scenario: A production workload uses a personal access token stored in Git for Databricks REST calls. The specific unmanaged risk is: An attacker obtaining the repository could invoke Databricks APIs with a broad personal identity. Validate with: The pipeline executes under a scoped service identity and the old token is revoked and rejected.
Incorrect Answers
B:This principle concerns a separate data-engineering condition: An engineering pipeline attempts to insert records into a production Delta table using an account with SELECT only. Its targeted response is: Grant a dedicated writer identity the minimum supported modification permissions and revoke broad user write grants. The current case is governed more directly by: Automation authentication should be auditable, nonpersonal and resistant to repository exposure.
C:This principle concerns a separate data-engineering condition: A data owner builds a masked view but analysts can still query the underlying sensitive table directly. Its targeted response is: Revoke inappropriate base-table access and publish only the authorized view or policy-governed object. The current case is governed more directly by: Automation authentication should be auditable, nonpersonal and resistant to repository exposure.
D:This principle concerns a separate data-engineering condition: A managed identity can read a storage container but a newly created external table is denied in Databricks. Its targeted response is: Align Azure storage role assignments with the registered Unity Catalog storage credential and external-location privileges. The current case is governed more directly by: Automation authentication should be auditable, nonpersonal and resistant to repository exposure.
Question 43
A solution applies: Replace broad grants with documented minimum creation and use privileges in a dedicated schema. It addresses: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. Which operational outcome MOST directly verifies success?
- The pipeline executes under a scoped service identity and the old token is revoked and rejected.
- An approved DDL operation creates the external table at a registered location and an arbitrary path is rejected.
- A permitted principal in the allowed workspace succeeds while an unauthorized user or workspace fails.
- An access test creates the required table only inside the approved job schema and denies other catalogs.
Explanation
Correct Answer
D:The strongest acceptance proof is: An access test creates the required table only inside the approved job schema and denies other catalogs. It specifically verifies: Replace broad grants with documented minimum creation and use privileges in a dedicated schema. The original issue was: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. The underlying mechanism is: Separation of duties requires independent decisions for object administration, data modification and read access. Without it, A compromised job principal could alter data products unrelated to its intended table.
Incorrect Answers
A:This result would validate a different measure: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. That is relevant to the distinct problem: A production workload uses a personal access token stored in Git for Databricks REST calls. Here the acceptance criterion is: An access test creates the required table only inside the approved job schema and denies other catalogs.
B:This result would validate a different measure: Configure a supported external location and specific creation privileges rather than bypassing the catalog to write directly. That is relevant to the distinct problem: A user is granted CREATE TABLE but cannot create an external table at an unregistered cloud path. Here the acceptance criterion is: An access test creates the required table only inside the approved job schema and denies other catalogs.
C:This result would validate a different measure: Apply both the workspace binding and appropriate Unity Catalog object grants, then test each dimension. That is relevant to the distinct problem: A team restricts access through a catalog-to-workspace binding but treats it as a replacement for data privileges. Here the acceptance criterion is: An access test creates the required table only inside the approved job schema and denies other catalogs.
Question 44
A solution applies: Use run-level compute utilization, cost and stage metrics to identify unused capacity. It addresses: A pipeline experiences escalating costs after a team increases node counts but execution duration barely changes. Which operational outcome MOST directly verifies success?
- A short benign delay does not page staff while a sustained backlog triggers the documented severity.
- A smaller tested configuration completes within SLA at a lower measured cost.
- A selective query reads fewer files and meets latency targets after a controlled layout improvement.
- Post-mitigation stage durations are balanced and joined row counts remain correct.
Explanation
Correct Answer
B:The strongest acceptance proof is: A smaller tested configuration completes within SLA at a lower measured cost. It specifically verifies: Use run-level compute utilization, cost and stage metrics to identify unused capacity. The original issue was: A pipeline experiences escalating costs after a team increases node counts but execution duration barely changes. The underlying mechanism is: Cost optimization requires throughput per resource rather than simply maximizing available workers. Without it, overprovisioning creates higher spend when stages are not parallelizable.
Incorrect Answers
A:This result would validate a different measure: Define meaningful latency, error and backlog thresholds with alert routing based on the business SLO. That is relevant to the distinct problem: An alert triggers on every harmless microbatch delay while real hour-long ingestion stalls go unnoticed. Here the acceptance criterion is: A smaller tested configuration completes within SLA at a lower measured cost.
C: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: A smaller tested configuration completes within SLA at a lower measured cost.
D:This result would validate a different measure: Use query-profile evidence and a supported skew mitigation such as adaptive execution or key-aware repartitioning. That is relevant to the distinct problem: A DataFrame join spills heavily because a single join key occurs in most rows. Here the acceptance criterion is: A smaller tested configuration completes within SLA at a lower measured cost.
Question 45
The recommended measure is: Define Lakeflow Spark Declarative Pipelines source options, incremental behavior and expectations with a durable target. The operational context is: A declarative pipeline loads cloud object files continuously but its configuration omits how duplicate files and bad records are handled. Which data engineering concept applies?
- Text ingestion options are part of the data contract and affect parsing correctness.
- Delivery guarantees alone do not remove duplicate producer or consumer events.
- Declarative ingestion still requires explicit quality and replay assumptions.
- Data pipeline completeness requires tracking arrivals rather than assuming an exact wall-clock boundary.
Explanation
Correct Answer
C:The decisive mechanism is: Declarative ingestion still requires explicit quality and replay assumptions. That explains the selected action: Define Lakeflow Spark Declarative Pipelines source options, incremental behavior and expectations with a durable target. In the original scenario: A declarative pipeline loads cloud object files continuously but its configuration omits how duplicate files and bad records are handled. The specific unmanaged risk is: A stream can write duplicate or malformed records into curated output without policy. Validate with: Injected duplicate and malformed source samples follow the intended dedupe or quarantine rules.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: An overnight load reads tab-separated files but an engineer assumes comma separators and casts malformed columns to null. Its targeted response is: Specify the correct input delimiter, header and schema and validate parsing on a representative file. The current case is governed more directly by: Declarative ingestion still requires explicit quality and replay assumptions.
B:This principle concerns a separate data-engineering condition: An ingestion pipeline reads cloud events with at-least-once delivery and assumes every event ID appears only once. Its targeted response is: Deduplicate by stable event identity and business time using documented state and watermark rules. The current case is governed more directly by: Declarative ingestion still requires explicit quality and replay assumptions.
D:This principle concerns a separate data-engineering condition: A Databricks job receives daily structured extracts but an upstream schedule occasionally delivers files late. Its targeted response is: Use incremental file ingestion with explicit late-arrival cutoffs and a measurable source-to-target watermark. The current case is governed more directly by: Declarative ingestion still requires explicit quality and replay assumptions.
Question 46
The recommended measure is: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention. The operational context is: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. Which data engineering concept applies?
- VACUUM removes old physical files, so aggressive cleanup can break valid historical references.
- Centralized telemetry supports durable troubleshooting when ephemeral compute terminates.
- Different failure layers require different diagnostic paths instead of generic cluster restarts.
- Scheduling cannot guarantee freshness when actual execution exceeds the interval.
Explanation
Correct Answer
B:The decisive mechanism is: Centralized telemetry supports durable troubleshooting when ephemeral compute terminates. That explains the selected action: Export relevant logs and metrics through a supported Log Analytics or Azure Monitor integration with controlled retention. In the original scenario: An Azure Databricks pipeline has recurring errors but its logs remain only in a short-lived cluster session. The specific unmanaged risk is: A failed cluster can disappear before operators gather evidence of its root cause. Validate with: A simulated failure leaves accessible run logs and correlation identifiers in the approved monitoring destination.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: An engineer runs VACUUM with a zero-hour retention on a shared Delta table used for historical audit queries. Its targeted response is: Respect documented safe retention windows and coordinate VACUUM with readers, streams and time-travel needs. The current case is governed more directly by: Centralized telemetry supports durable troubleshooting when ephemeral compute terminates.
C:This principle concerns a separate data-engineering condition: An operations team sees Dataflow-like ingestion failures but cannot identify whether the problem is a Unity Catalog grant or a Spark stage. Its targeted response is: Correlate error messages, job run IDs, catalog authorization logs and Spark execution evidence before remediation. The current case is governed more directly by: Centralized telemetry supports durable troubleshooting when ephemeral compute terminates.
D:This principle concerns a separate data-engineering condition: A job scheduled each hour starts running for 80 minutes and overlaps the next run. Its targeted response is: Investigate stage runtime growth and enforce appropriate concurrency policy before raising frequency. The current case is governed more directly by: Centralized telemetry supports durable troubleshooting when ephemeral compute terminates.
Question 47
A pipeline owner declines the action: Replace broad grants with documented minimum creation and use privileges in a dedicated schema. The business situation is: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. What specific failure can follow?
- A compromised job principal could alter data products unrelated to its intended table.
- An employee departure or password rotation can unexpectedly break critical production ingestion.
- An attacker obtaining the repository could invoke Databricks APIs with a broad personal identity.
- A protected secret can still leak through debug output or unrestricted notebook results.
Explanation
Correct Answer
A:The direct residual exposure is: A compromised job principal could alter data products unrelated to its intended table. The triggering condition is: A development team grants ALL PRIVILEGES on a catalog so that one job can create a temporary table. The omitted safeguard is: Replace broad grants with documented minimum creation and use privileges in a dedicated schema. This matters because: Separation of duties requires independent decisions for object administration, data modification and read access. A corrective test would show: An access test creates the required table only inside the approved job schema and denies other catalogs.
Incorrect Answers
B: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 compromised job principal could alter data products unrelated to its intended table.
C:This failure mode belongs mainly to another situation: A production workload uses a personal access token stored in Git for Databricks REST calls. Its preventative action would be: Replace committed personal credentials with supported workload authentication and revoke exposed tokens. The most direct exposure in the current scenario is: A compromised job principal could alter data products unrelated to its intended table.
D:This failure mode belongs mainly to another situation: An application uses an external Azure Key Vault secret scope but a notebook prints the secret into task logs. Its preventative action would be: Use supported Databricks secret access with least-privilege scope access and remove secret values from logs. The most direct exposure in the current scenario is: A compromised job principal could alter data products unrelated to its intended table.
Question 48
An Azure Databricks architect reviews the following problem: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. What should the team implement FIRST?
- Create a Unity Catalog view with approved permissions and verify underlying access semantics.
- Define a stable contract through managed views and test compatibility before changing source objects.
- Use Unity Catalog volumes with suitable schema and file privileges for supported non-tabular files.
- Recreate or update supported external table registration using an approved location and correct access controls.
Explanation
Correct Answer
B:The most appropriate action is: Define a stable contract through managed views and test compatibility before changing source objects. It addresses the stated condition: A reporting service needs to keep a stable presentation schema while underlying source columns are renamed by engineering. The technical basis is: Abstraction views can separate a consumer-facing contract from internal physical table evolution. Without this control, direct downstream table references can break when upstream columns are renamed. A direct acceptance check is: Contract tests continue to select documented columns through the published view after a staged schema change.
Incorrect Answers
A:This alternative primarily addresses a different Azure Databricks problem: An analyst wants to expose a filtered projection of a governed table without copying sensitive source rows. The corresponding measure there would be: Create a Unity Catalog view with approved permissions and verify underlying access semantics. The stated situation instead calls for: Define a stable contract through managed views and test compatibility before changing source objects.
C:This alternative primarily addresses a different Azure Databricks problem: A departmental data owner stores raw file attachments inside ad hoc DBFS directories instead of a governable data space. The corresponding measure there would be: Use Unity Catalog volumes with suitable schema and file privileges for supported non-tabular files. The stated situation instead calls for: Define a stable contract through managed views and test compatibility before changing source objects.
D:This alternative primarily addresses a different Azure Databricks problem: A managed Delta table is migrated to external storage but the team does not update table registration or grant scopes. The corresponding measure there would be: Recreate or update supported external table registration using an approved location and correct access controls. The stated situation instead calls for: Define a stable contract through managed views and test compatibility before changing source objects.
Question 49
The design team proposes: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. The situation is: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. Which technical principle justifies the decision?
- Technical retention settings and organizational policy need an auditable, consistent lifecycle.
- Ordinary table replacement does not automatically constitute defensible preservation of historical legal records.
- Permission reviews should follow actual securable objects and their dependencies rather than name assumptions.
- Security governance requires attributable administrative activity and durable evidence.
Explanation
Correct Answer
B:The decisive mechanism is: Ordinary table replacement does not automatically constitute defensible preservation of historical legal records. That explains the selected action: Design record-level retention and external legal-hold workflows appropriate to the applicable policy. In the original scenario: A product owner assumes a nightly Delta table overwrite meets a legal hold requirement for old records. The specific unmanaged risk is: Historical evidence may be lost even when the latest dataset remains complete. Validate with: A hold rehearsal retrieves the original protected records and documents preservation scope and access.
Incorrect Answers
A:This principle concerns a separate data-engineering condition: A regulated source dataset receives an updated retention period but storage cleanup still follows the obsolete policy. Its targeted response is: Align table retention properties, scheduled maintenance and legal ownership approvals with the current classification. The current case is governed more directly by: Ordinary table replacement does not automatically constitute defensible preservation of historical legal records.
C:This principle concerns a separate data-engineering condition: A governance team grants dataset access solely by a table's displayed name while records are moved to a new schema. Its targeted response is: Reconcile catalog object identity, lineage and current grants after schema or owner changes. The current case is governed more directly by: Ordinary table replacement does not automatically constitute defensible preservation of historical legal records.
D:This principle concerns a separate data-engineering condition: A compliance auditor requests a record of who changed Unity Catalog grants but audit logs are not collected. Its targeted response is: Configure supported Databricks audit logging and route relevant events to a secured retention destination. The current case is governed more directly by: Ordinary table replacement does not automatically constitute defensible preservation of historical legal records.
Question 50
A pipeline owner declines the action: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. The business situation is: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. What specific failure can follow?
- Unmeasured tuning changes can hide the original bottleneck or increase compute costs.
- A fixed undersized cluster misses month-end deadlines while an oversized fixed cluster wastes daily spend.
- Sizing from isolated benchmark queries can leave hundreds of dashboard viewers waiting in a query queue.
- Ignoring startup overhead can make small jobs miss a narrow delivery window even when their Spark tasks are fast.
Explanation
Correct Answer
B:The direct residual exposure is: A fixed undersized cluster misses month-end deadlines while an oversized fixed cluster wastes daily spend. The triggering condition is: A data engineering job sometimes requires twice its usual executor capacity during month-end loads while weekdays are much smaller. The omitted safeguard is: Configure bounded autoscaling using measured workload demand and verify maximum cost and startup behavior. This matters because: Autoscaling can adapt worker resources to changing parallel workload demand within a defined limit. A corrective test would show: Load tests for normal and month-end volumes satisfy runtime targets without exceeding the approved worker ceiling.
Incorrect Answers
A:This failure mode belongs mainly to another situation: A team turns on every performance setting for a workload without benchmarking whether disk spills or network shuffle dominate runtime. Its preventative action would be: Collect Spark stage profiles and test a targeted compute or Photon setting against comparable data. The most direct exposure in the current scenario is: A fixed undersized cluster misses month-end deadlines while an oversized fixed cluster wastes daily spend.
C:This failure mode belongs mainly to another situation: A BI warehouse repeatedly slows during morning sign-in peaks even though a single analyst query runs quickly. Its preventative action would be: Tune supported SQL warehouse capacity and concurrency scaling based on simultaneous production query measurements. The most direct exposure in the current scenario is: A fixed undersized cluster misses month-end deadlines while an oversized fixed cluster wastes daily spend.
D:This failure mode belongs mainly to another situation: A scheduled workflow launches dozens of short-lived classic clusters and loses several minutes each time waiting for virtual machines. Its preventative action would be: Evaluate compatible instance pools or supported serverless startup behavior rather than keeping unused all-purpose clusters awake. The most direct exposure in the current scenario is: A fixed undersized cluster misses month-end deadlines while an oversized fixed cluster wastes daily spend.