Free DP-750 Exam Braindumps
Implementing Data Engineering Solutions Using Azure Databricks Questions 1–5 (page: 2)

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

HOTSPOT (Drag and Drop is not supported)
You need to recommend a compute type for the production ingestion workloads and BI workloads. The solution must meet the environment and compute requirements.
What should you recommend for each type of workload? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Job compute
Job compute is the best choice for these production ingestion workloads.
Auto-Scaling during Spikes: Job clusters can be configured to auto-scale dynamically. This allows them to add worker nodes during telemetry spikes and scale down when data volume drops.
Non-Interactive & Scheduled: Job compute is specifically designed to run automated, non-interactive workflows (like Azure Databricks Jobs or Delta Live Tables) on a fixed or cron-based schedule.
Production Isolation: Job clusters are dedicated to a specific workload. They spin up when the job starts and terminate when it finishes. This completely prevents development activity or other shared workloads from affecting your production pipelines.
Scenario:
Ensure that production ingestion workloads run on compute clusters that can scale automatically during telemetry spikes.
Production ingestion workloads must run as scheduled, non-interactive pipelines rather than on shared interactive development clusters.
Prevent development activity from affecting production pipelines.
Box 2: Serverless SQL warehouse
Scenario: Provide fast and consistent performance for business intelligence (BI) workloads.
Serverless SQL warehouses are the best compute type for business intelligence (BI) workloads in Azure Databricks.
Instant Startup: Eliminates cluster start-up times with near-instant availability.BI Optimization: Specifically tuned for running SQL queries and serving BI tools.
Auto-Scaling: Scales up rapidly during peak usage to maintain consistent performance.
Concurrency: Handles multiple simultaneous queries from BI dashboards without slowdowns.
Cost Efficiency: Shuts down immediately when idle to prevent overpaying for compute.


Reference:

https://www.credencys.com/blog/databricks-cost-optimization-best-practices/



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.


Reference:

https://medium.com/@krthiak/10-days-of-data-engineering-interview-qna-day-5-db1c0b58bf86



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 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.


Reference:

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



View Related Case Study

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.


Reference:

https://maqsoftware.com/insights/azure-databricks-best-practices.html



View Related Case Study

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.


Reference:

https://dev.to/encorepartners/creating-your-first-catalog-schema-and-tables-in-databricks-20p3



Viewing page 2 of 23
Viewing questions 6 - 10 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!