Free DP-750 Exam Braindumps
Implementing Data Engineering Solutions Using Azure Databricks Questions 3–7 (page: 11)

Updated On: 3-Nov-2026
View Related Case Study

You have an Azure Databricks workspace that uses serverless compute.
New records must be processed as soon as they become available.
You need to ingest data by using Lakeflow Jobs.
Which type of job trigger should you use for the ingestion?

  1. manual
  2. file arrival
  3. scheduled
  4. continuous

Answer(s): D

Explanation:

The best trigger type for this scenario is the Continuous trigger.
Immediate Processing: The Continuous trigger mode processes new records as soon as they arrive at the configured data sources. This matches your requirement to ingest and process records without waiting for an artificial time interval.
Native Serverless Support: When paired with serverless compute, Lakeflow Jobs efficiently manage resources by automatically scaling up or down according to the real-time stream volume.
Built-in Fault Tolerance: Continuous pipelines on Databricks automatically handle failures by retrying with an exponential backoff policy, keeping your automated ingestion operational 24/7 without manual intervention.


Reference:

https://docs.databricks.com/aws/en/jobs/continuous



View Related Case Study

You have an Azure Databricks workspace that is enabled for Unity Catalog and contains a managed Delta table named Sales.
Sales stores transaction data and contains the following columns:
-transaction_id (string)
-transaction_date (date)
-amount (decimal)
You need to implement the following data quality requirements by using table-level data quality enforcement:
-amount must be greater than 0.
-transaction_id must never be null.
-Invalid records must be rejected when data is written to the Sales table.
What should you do?

  1. Use a SELECT statement with WHERE conditions to validate the data before querying.
  2. Create a view that filters out rows where transaction_id is null or amount is less than or equal to 0.
  3. Add a NOT NULL constraint to transaction_id and a CHECK constraint to amount.
  4. Configure row-level security (RLS) where transaction_id is null or amount is less than or equal to 0.

Answer(s): C

Explanation:

To enforce these table-level data quality rules and automatically reject any invalid write operations in Azure Databricks, you must configure NOT NULL and CHECK constraints on the Delta table using standard SQL commands.
In Delta Lake, these constraints are enforced instantly on write. If an incoming record violates any of them, the entire transaction fails, and the invalid records are rejected.
1. Enforce transaction_id Cannot Be Null
Add a NOT NULL constraint to the transaction_id column. This blocks any write attempt containing a null identifier.
ALTER TABLE sales_data ALTER COLUMN transaction_id SET NOT NULL;
2. Enforce amount Must Be Greater Than 0
Add a CHECK constraint to the table to validate that the amount values strictly exceed zero.
ALTER TABLE sales_data ADD CONSTRAINT check_amount_positive CHECK (amount > 0);


Reference:

https://docs.databricks.com/aws/en/tables/constraints



View Related Case Study

You have an Azure Databricks workspace that is enabled for Unity Catalog and contains two Delta tables named Table1 and Table2 of the same data type.
Table1 contains a column named Column1. Table2 contains a column named Column2.
You run the following query.
SELECT Colum1
FROM Table1
GROUP BY Column1
HAVING COUNT(*) > 1
INTERSECT
SELECT Column2
FROM Table2
GROUP BY Column2
HAVING COUNT(*) > 1;
What occurs when you run the query?

  1. Values appear in both tables more than once.
  2. Values appear in either table more than once.
  3. Values appear in Table2 but NOT Table1.
  4. Values appear in Table1 more than once.

Answer(s): A

Explanation:

The query will output a single column containing only the values that are duplicated within Table1 and also duplicated within Table2.
Duplicates Isolated First: The GROUP BY and HAVING COUNT(*) > 1 clauses filter each table independently to find only their duplicate rows.
Matching Values Found: The INTERSECT operator compares the filtered results of both tables.
Shared Values Returned: Only values that exist in both filtered datasets are included in the final output.
Automatic Distinct Filtering: INTERSECT automatically removes any duplicate values from the final result set, ensuring each matching value appears exactly once.
Column Naming: The output column will inherit its name from the first SELECT statement (Column1).


Reference:

https://quizlet.com/study-guides/inf3707-chapter-4-data-retrieval-from-2-or-more-tables-6ec17b26-76a8-4c33-8fa7-18d64154512d



View Related Case Study

You have an Azure Databricks workspace that is enabled for Unity Catalog and contains two managed Delta tables named sales.schema1.table1 and sales.schema1.table2.
sales.schema1.table1 contains sales data from the current year.
sales.schema1.table2 contains historical data.
You need to load all the rows from sales.schema1.table1 into sales.schema1.table2. The solution must preserve any existing data in sales.schema1.table2 and minimize processing effort.
Which command should you run?

  1. INSERT OVERWRITE sales.schema1.table2 SELECT * FROM sales.schema1.table1;
  2. CREATE TABLE sales.schema1.table2 AS SELECT * FROM sales.schema1.table1;
  3. INSERT INTO sales.schema1.table2 SELECT * FROM sales.schema1.table1;
  4. CREATE OR REPLACE TABLE sales.schema1.table2 AS SELECT * FROM sales.schema1.table1;

Answer(s): C

Explanation:

To load all rows from one table into the other while preserving existing data and minimizing processing effort, you should use the SQL INSERT INTO statement.
Preserves Data: INSERT INTO appends new rows to the target table without modifying or deleting the existing data.
Lowest Processing Effort: It performs a direct data append at the storage level. Unlike MERGE INTO, it does not scan the target table for matches, saving significant compute time and costs.
Delta Lake Optimization: Because these are Delta tables, appending data simply writes new parquet files and commits them to the transaction log, making the operation fast and efficient.


Reference:

https://medium.com/@gema.correa/handling-schema-evolution-and-schema-compensation-in-databricks-lesso ns-from-the-field-7af8d915beef



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure Databricks workspace that is enabled for Unity Catalog.
You plan to run the following PySpark code.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Yes
Yes - New columns from the incoming JSON payload will be added automatically to the target Delta table.
New columns from the incoming JSON payload will be added automatically to the target Delta table.
Schema Evolution: The .option("MergeSchema", "true") configuration explicitly tells Delta Lake to update the target table's schema when it encounters new columns.
Auto-Detection: Spark automatically infers the structure of the incoming streaming dataframe (df) and merges any novel attributes into the Bronze table during the write operation.
Box 2: Yes
Yes - Previously processed data will not be reprocessed if the pipeline fails.
Previously processed data will not be reprocessed if the pipeline fails, provided the checkpoint directory is not deleted or corrupted.
Checkpoint tracking: Spark streams use the checkpoint location to record exactly which files and offsets have been successfully processed.
Idempotency: When the failed pipeline restarts, Spark reads the checkpoint metadata to resume precisely where it left off.
Trigger status: The availableNow=True trigger respects these checkpoints, only processing new data arrived since the last successful batch.
Box 3: No
No - Each new batch of telemetry data will overwrite the existing data in the target Delta table.
Each new batch of telemetry data will not overwrite the existing data in the target Delta table.
Output Mode: The code explicitly sets .outputMode("append").
Behavior: This mode only adds new incoming rows to the existing table.
Delta Integration: Delta Lake safely commits these new files without touching older data.


Reference:

https://shahrukh0603.medium.com/day-33-of-databrickster-42f97477af35
https://medium.com/@devhoode/streaming-changes-from-postgresql-to-databricks-lakehouse-using-structured -streaming-c65769d65ca7



Viewing page 11 of 23
Viewing questions 51 - 55 out of 108 questions


Post your Comments and Discuss Microsoft DP-750 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!