support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  1. Home
  2. Exams
  3. Microsoft
  4. DP-750

Microsoft DP-750 Exam Prep
Implementing Data Engineering Solutions Using Azure Databricks (Page 2 )

Updated On: 13-Sep-2026
Page 2 of 12
PDF with 108 Questions
View Related Case Study

You need to configure compute for the ingestion of telemetry data. The solution must meet the data ingestion and processing requirements.
What should you do?

  1. Move the ingestion pipelines to shared compute.
  2. Enable Photon acceleration for a job compute cluster.
  3. Increase an all-purpose cluster to a larger fixed node type.
  4. Disable autoscaling for a job compute cluster.

Answer(s): B

Explanation:

Enabling Photon acceleration on a job compute cluster is the best option. It significantly speeds up data engineering pipelines, handles JSON file ingestion seamlessly, and optimizes cost-efficiency for bursty production workloads, which are key for processing rapidly arriving IoT sensor events.
Enable Photon acceleration for a job compute cluster: Databricks Auto Loader is designed for low-latency, high-volume file ingestion. Running Auto Loader on a job compute cluster provides the lowest operational cost because job clusters are billed at a much lower rate than all-purpose clusters.
Enabling Photon acceleration heavily optimizes the ingestion, parsing, and processing of raw JSON data strings, allowing the cluster to handle bursty workloads faster and auto-scale more efficiently.
Scenario,
Data Environment, Contoso ingests the following operational and business data:
Telemetry data: More than 40,000 IoT sensors across 28 sites emit JSON telemetry events every few seconds. Each site sends the events to the nearest event hub, which writes the data into the corresponding Data Lake Storage Gen2 account. These files frequently experience schema drift.
Contoso identifies the following data ingestion and processing requirements: -> Auto-scale ingestion pipelines to handle bursty workloads. Handle schema drift for the maintenance and telemetry data. -> Ingest file-based telemetry data by using minimal operational effort.



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 effort.
What should you use?

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

Answer(s): C

Explanation:

The best option for a Lakeflow Spark Declarative Pipelines (SDP) pipeline that scales automatically while keeping costs and administrative effort low is a job cluster that uses autoscaling.
Lowest Costs: Job clusters (also called automated compute) are billed at a significantly lower Data Processing Unit (DBU) rate compared to all-purpose clusters. By enabling autoscaling, Databricks dynamically allocates or removes worker nodes based on real-time pipeline demand, ensuring you never pay for unutilized resources.
Low Administrative Effort: While Databricks generally recommends Serverless compute as the absolute ideal for zero-admin pipelines, when selecting from classic compute options, a job cluster automatically handles its own lifecycle. It deploys when the pipeline starts executing and terminates automatically when processing is finished.
Incorrect: [Not A] Databricks SQL warehouses are designed to run standalone materialized views and streaming tables via standard SQL. They are not the native compute vehicle for running a fully automated, dedicated Lakeflow Spark Declarative Pipelines (SDP) deployment framework.
[Not B] All-purpose compute is meant for interactive development, debugging, and ad-hoc analysis. It is billed at a much higher DBU rate, which violates the requirement to keep costs low.
[Not D] Aside from the higher billing rate of all-purpose compute, a single-node configuration does not scale horizontally. This directly conflicts with your requirement to build a pipeline that scales automatically.



DRAG DROP (Drag and Drop is not supported)
You have an Azure Databricks workspace that contains an all-purpose compute cluster named Cluster1. Cluser1 is used for interactive development.
You need to configure Cluster1 to meet the following requirements:
-Automatically add and remove worker nodes based on workload demand.
-Automatically shut down when the cluster has been idle for a specific period.
What should you configure for each requirement? To answer, drag the appropriate options to the correct requirements. Each option may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
Note: Each correct selection is worth one point.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:


Box 1: Autoscaling To dynamically scale your worker nodes based on workload demand, you must enable and configure Autoscaling on the cluster.
Cluster Type: Select All-Purpose during creation.
*-> Autoscaling Toggle: Check the Enable autoscaling checkbox.
Minimum Workers: Define the lowest number of nodes to keep active.
Maximum Workers: Define the highest number of nodes allowed to launch.
Box 2: Auto Termination To configure an Azure Databricks all-purpose compute cluster to shut down automatically when idle, you must enable and configure the Auto Termination feature.
Default Value: Azure Databricks typically sets a default auto-termination period of 120 minutes.
Minimum Value: You can set the idle timeout to a minimum of 10 minutes.
Activity Triggers: The idle timer resets whenever commands are run, or when Spark jobs, notebook executions, or API calls interact with the cluster.
Cost Management: Setting a lower threshold (e.g., 20–30 minutes) prevents unnecessary costs from clusters left running overnight or during breaks.



You have an Azure Databricks workspace that is attached to a Unity Catalog metastore named metastore1, metastore1 contains a catalog named catalog1.
You need to create a new schema named schema2 that meets the following requirements:
-Is contained in catalog1
-Uses abfss://container@storageaccount.dfs.core.windows.net/data as the managed location
Which SQL statement should you execute?

  1. CREATE SCHEMA catalog1.schema2
    LOCATION ‘abfss://container@storageaccount.dfs.core.windows.net/data’;
  2. CREATE SCHEMA catalog1.schema2
    MANAGED LOCATION ‘abfss://container@storageaccount.dfs.core.windows.net/data’;
  3. CREATE CATALOG schema2
    MANAGED LOCATION ‘abfss://container@storageaccount.dfs.core.windows.net/data’;
  4. CREATE SCHEMA catalog1.schema2
    WITH DBPROPERTIES (LOCATION-’abfss:// container@storageaccount.dfs.core.windows.net/data’);

Answer(s): B

Explanation:

To create a new schema with a specific managed location in Azure Databricks Unity Catalog, use the CREATE SCHEMA command.
CREATE SCHEMA catalog_name.schema_name MANAGED LOCATION 'abfss://container@storageaccount.dfs.core.windows.net/data';
Catalog Name: Replace catalog_name with your existing catalog.
Schema Name: Replace schema_name with your desired new schema name.Quotes: The storage path must be enclosed in single quotes.
Privileges: You must have CREATE SCHEMA privileges on the parent catalog and ownership (or adequate permissions) on the external location.



You have an Azure Databricks workspace named Workspace1.
You create a compute cluster named Cluster1 that will be used to ingest data.
You need to install the required libraries on Cluster1. The solution must use Unity Catalog for access control.
What should you do?

  1. Install the libraries by using pip3.
  2. Create a custom dependency management script and run the script from a Databricks notebook.
  3. Upload the libraries to Workspace1 and install the libraries on Cluster1.
  4. Install the libraries on Cluster1 and manually restart the cluster.

Answer(s): C

Explanation:

The best action is uploading the libraries to the workspace and installing the libraries on the cluster (or ideally uploading them to Unity Catalog volumes).
Unity Catalog Compatibility: When using Unity Catalog for access control, compute clusters are typically configured with Standard (Shared) access mode. In this mode, traditional cluster init scripts [Not B.] face strict execution restrictions or are completely blocked to maintain secure user isolation.
Governance: Uploading your packages as Workspace Files or to Unity Catalog volumes allows administrators to manage access permissions directly and add them to an allowlist if needed.
Cluster-Wide Availability: Installing the libraries via the cluster's Libraries tab ensures that the required ingestion packages are automatically pre-installed and available across all nodes and notebooks running on that cluster.
Incorrect: [Not A] Running pip3 install manually on a cluster terminal or inside a notebook only applies to the specific notebook session (notebook-scoped). It does not natively persist across cluster restarts or handle cross-node execution effectively for data ingestion pipelines.
[Not B] Running a custom script or a legacy init script to modify system-level paths introduces security risks and is generally incompatible with Unity Catalog's strict execution isolation policies for shared compute.



DRAG DROP (Drag and Drop is not supported)
You have an Azure Databricks workspace that is enabled for Unity Catalog and contains a catalog named finance, finance contains two schemas named default and procurement.
You need to create a table named assets in the procurement schema, assets must contain the following columns:
-asset_id asset_type asset_name
How should you complete the SQL statement? To answer, drag the appropriate values to the correct targets. Each value may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
Note: Each correct selection is worth one point.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Completed SQL Statements USE CATALOG finance; USE SCHEMA procurement; CREATE TABLE assets ( asset_id INT, asset_name STRING, asset_type STRING );
Box 1: CATALOG finance CATALOG finance - the root container holding your data.
Box 2: SCHEMA procurement SCHEMA procurement - the specific database/schema where the table must live.
Box 3: TABLE assets TABLE assets - The name of the table you are creating.



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.



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"))



  PDF
Viewing page 2 of 12
Viewing questions 9 - 16 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!