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

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

You have an Azure Databricks workspace that is enabled for Unity Catalog.
You have an Apache Spark Structured Streaming job that writes data to a Delta table.
After the cluster restarts, the streaming job reprocesses previously ingested data.
You need to prevent the streaming job from reprocessing the data after the cluster restarts.
What should you do?

  1. Configure a checkpoint location for the streaming query.
  2. Increase the trigger interval of the streaming query.
  3. Enable change data feed (CDF) for the target table.
  4. Configure a watermark for the streaming query.

Answer(s): A

Explanation:

To prevent your Apache Spark Structured Streaming job from reprocessing previously ingested data after a cluster restart, you must configure a streaming checkpoint directory.
Core Solution
Enable Checkpointing: Define the checkpointLocation option in your streaming write configuration.
Track Progress: Spark uses this directory to save the exact offset ranges of processed data.
Automatic Recovery: Upon restart, the engine reads the checkpoint and resumes precisely where it left off.
Implementation Example in python
# Configure the streaming write with a checkpoint path
(df.writeStream
.format("delta")
.outputMode("append")
.option("checkpointLocation", "/Volumes/catalog/schema/volume_name/checkpoints/job_name") .toTable("catalog.schema.target_table"))


Reference:

https://medium.com/@salah.uddin_75300/architecture-of-a-streaming-machine-learning-data-pipeline-042200c 8e7ff



View Related Case Study

You have an Azure Databricks workspace that contains an all-purpose cluster named Cluster1.
You need to configure Cluster1 to meet the following requirements:
-Scale up automatically when workloads increase
-Scale down automatically when workloads decrease
-Minimize costs
The solution must minimize costs.
Which two actions should you perform? Each correct answer presents part of the solution.
Note: Each correct selection is worth one point.

  1. Disable Photon acceleration.
  2. Enable autoscaling for Cluster1.
  3. Apply a compute policy that enables users to manage the cluster settings.
  4. Specify a fixed number of workers.
  5. Configure Cluster1 to terminate after 30 minutes of inactivity.

Answer(s): B,E

Explanation:

Enabling autoscaling and setting a 30-minute auto-termination timeout is the correct configuration to meet the goals.
Autoscaling handles fluctuating workloads, while auto-termination prevents you from paying for idle compute resources.
Dynamic Scaling: Autoscaling automatically adds workers during high loads and removes them when demand drops.
Cost Control: The 30-minute termination window ensures the cluster shuts down completely if no jobs are running, stopping all compute charges.


Reference:

https://community.databricks.com/t5/get-started-discussions/cluster-auto-termination-best-practices/td-p/75826



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure Databricks workspace that contains a cluster named Cluster1.
Cluster1 has the following characteristics:
-Configured as a single node cluster
-Uses a general purpose virtual machine node type
The cluster runtime environment has the following configurations:
-Uses Databricks Runtime for Machine Learning (Databricks Runtime ML)
-Includes common machine learning libraries
-Supports Python workloads
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: No
No - Cluster1 can be used to train learning models that require GPU acceleration.
GPU Acceleration is not supported in Cluster1:
General Purpose VM: General purpose virtual machines (like Azure's Standard_D or Standard_E series) run on standard CPUs, not GPUs.
Missing Hardware: Deep learning frameworks (like PyTorch or TensorFlow) need physical GPU cores (Tensor Cores) to speed up model training.
Runtime Mismatch: The standard Databricks Runtime ML installs CPU versions of machine learning libraries unless a GPU-specific runtime version is selected.
Box 2: No
No - Cluster1 can distribute machine learning workloads across multiple nodes.
Why Distribution is Not Possible in Cluster1:
Single Node Architecture: A single node cluster operates entirely on one virtual machine.
No Worker Nodes: It contains only a driver node and zero worker nodes.
Local Execution Only: All computations, library executions, and Python workloads run locally on that single machine.
Box 3: Yes
Yes - Cluster1 can run Python workloads that rely on preinstalled machine learning libraries.
The setup perfectly aligns with the requirements for single-node machine learning workflows:
Databricks Runtime ML: This specialized runtime environment automatically packages and preinstalls popular open-source data science and machine learning packages. These include frameworks like scikit-learn, TensorFlow, PyTorch, and XGBoost, allowing Python workloads to run right out of the box without requiring manual package installations.
Single Node Configuration: In Azure Databricks, Single Node compute is specifically designed for light-duty data engineering or non-distributed machine learning libraries. It runs both the Spark driver and worker tasks on a single virtual machine node.
General Purpose VM Node Type: Standard general-purpose Azure virtual machines (such as D-series SKUs) are fully compatible with CPU-optimized ML workloads (e.g., scikit-learn models or CPU-based neural networks).


Reference:

https://learn.microsoft.com/en-us/azure/machine-learning/how-to-configure-environment?view=azureml-api-2



View Related Case Study

You manage Declarative Automation Bundles by using the Databricks CLI.
You run the following command in a terminal window.
databricks bundle init
What occurs when you run the command?

  1. The bundle configuration is validated.
  2. A new Declarative Automation Bundles project structure is created.
  3. Bundle-defined resources are deployed to the Databricks workspace.
  4. Jobs or pipelines defined in the bundle are run.

Answer(s): B

Explanation:

Running the databricks bundle init command initializes a new project directory based on a project template for Declarative Automation Bundles.


Reference:

https://docs.databricks.com/aws/en/dev-tools/bundles/jobs-tutorial



View Related Case Study

You have an Azure Databricks workspace.
You are creating a Lakeflow Spark Declarative Pipelines (SDP) pipeline that scales automatically.
You need to configure compute for the pipeline. The solution must minimize operational costs and administrative effort.
What should you use?

  1. serverless compute
  2. a single-node, all-purpose cluster
  3. an all-purpose cluster that uses autoscaling
  4. an existing SQL warehouse
  5. a job cluster that uses autoscaling

Answer(s): A

Explanation:

To best achieve an automatically scaling compute environment for Lakeflow Spark Declarative Pipelines (SDP) while keeping operational and administrative costs low, you should deploy the pipeline using Serverless Compute configured in Standard Performance Mode with an enforced Max Workers limit.
This combination eliminates the administrative overhead of infrastructure management, leverages enhanced vertical and horizontal auto-scaling, limits cost exposure from unexpected spikes, and optimizes financial efficiency.


Reference:

https://docs.databricks.com/aws/en/ldp/auto-scaling



Viewing page 4 of 23
Viewing questions 16 - 20 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!