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

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

You have an Azure Databricks workspace that is enabled for Unity Catalog.
You have a CSV file stored in an Azure Data Lake Storage Gen2 container.
You plan to ingest the data into an existing table by running the following SQL statement.
COPY INTO Customer
FROM ‘abfss://container1@storageaccount.dfs.core.windows.net/data/customer’
FILEFORMAT = CSV
You need to ensure that the statement can access the data in the container.
What should you configure?

  1. an external table named Customer in the CSV file format
  2. a Lakeflow ingestion gateway
  3. an external location that uses a storage credential
  4. a volume in a catalog

Answer(s): C

Explanation:

To ensure that the COPY INTO statement can successfully access and ingest the data from the Azure Data Lake Storage Gen2 (ADLS Gen2) container using Unity Catalog, you must configure the following minimum Unity Catalog privilege:READ FILES on the External Location object.
Additionally, the executing user must have USE CATALOG and USE SCHEMA privileges on the target table's parent path, along with the MODIFY privilege (or be the owner) on the target Customer table.


Reference:

https://docs.databricks.com/gcp/en/ingestion/cloud-object-storage/copy-into/unity-catalog



View Related Case Study

Your company has sales, finance, and HR departments.
You have an Azure Databricks workspace that is enabled for Unity Catalog.
You need to implement Unity Catalog to meet the following requirements:
-Access to Unity Catalog for each department must be managed independently from that of the other departments.
-The data assets of each department must be isolated logically from those of the other departments.
-The solution must support centralized governance.
What should you do for each department?

  1. Create a separate Azure Data Lake Storage Gen2 account.
  2. Create dynamic views.
  3. Create a new workspace.
  4. Create a new catalog.

Answer(s): D

Explanation:

To satisfy all requirements, the required action is to create a separate Unity Catalog Catalog for each department within the single centralized workspace.
The required action is to create a separate top-level Catalog for each department within the Unity Catalog metastore. This ensures strict logical data isolation and decentralized access management, while maintaining a single metastore for centralized governance.


Reference:

https://community.databricks.com/t5/technical-blog/unity-catalog-as-a-foundation-for-governance-that-democra tizes/ba-p/126983



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure Databricks workspace that is enabled for Unity Catalog and contains a catalog named catalog1.
You have a group named group1. Group1 already has the USE CATALOG privilege on catalog1.
You create a schema named schema1 in catalog1.
You need to ensure that group1 can create tables in schema1. Group1 must not be able to grant permissions on the schema or its objects. The solution must follow the principle of least privilege.
How should you complete the SQL statement? 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: CREATE TABLE, USE SCHEMA
To ensure that the group can create tables in the schema while maintaining the principle of least privilege—and without allowing them to grant permissions to others—you must grant exactly two schema-level privileges: USE SCHEMA and CREATE TABLE.
You must avoid granting ALL PRIVILEGES or changing the object ownership to the group, as either action would inadvertently grant them permission-management (MANAGE / GRANT) capabilities.
USE SCHEMA: This is a mandatory prerequisite that allows the group to interact with and traverse into the schema. Without it, they cannot see or access any objects inside it.
CREATE TABLE: This isolates their permissions specifically to creating new tables within that targeted schema.
Box 2: to group1
The Command to Use
Execute the following SQL command in your Azure Databricks workspace:
lGRANT USE SCHEMA, CREATE TABLE ON SCHEMA catalog_name.schema_name TO `group_name`;


Reference:

https://learn.microsoft.com/en-us/azure/databricks/data-governance/unity-catalog/manage-privileges/



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
Which SCD type should you use to support the planned data modeling changes? To answer, drag the appropriate types to the correct issues. Each type 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: Type 1
Data-entry mistakes by the equipment manufactures:
Scenario: Technical Requirements
Contoso identifies the following data modeling and optimization requirements:
Build curated tables that standardize business logic.
-> Overwrite equipment metadata attributes, such as name, manufacturer, model, and commissioning date, when the attributes change. Historical values are NOT required.
SCD Type 1 is the best choice for this scenario.
Overwrites Data: New data replaces old data directly in the existing record.
No History: It does not maintain any historical tracking of past values.
Easy Maintenance: It requires the least storage and simplest query logic.
Box 2: Type 2
Changes to IoT sensor ownership
Scenario:
Problem statement
Governance: Ownership of the IoT sensors changes over time, and analysts must track the full history of the ownership
SCD Type 2 is the best choice for tracking the full history of data changes over time.
Full History: It creates a new row for every change.
Retains Old Data: Past records are never overwritten or deleted.
Time-Slice Analysis: It uses start/end dates to show exactly how data looked at any point in history.
Incorrect:
Type 0: Fixed. It never allows changes or overwrites after the initial load.


Reference:

https://weld.app/blog/what-is-slowly-changing-dimensions



View Related Case Study

DRAG DROP (Drag and Drop is not supported)
Which ingestion option should you recommend for each data source? To answer, drag the appropriate options to the correct data sources. 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: Auto Loader
Telemetry data
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.
Auto Loader is the optimal choice. It is purpose-built to continuously ingest massive volumes of streaming/cloud storage JSON files while automatically handling unpredictable schema drift.
Schema Inference and Evolution: Auto Loader automatically detects new columns, handles changing data types, and rescues corrupted data using a rescued
DataColumn without crashing your pipeline. This directly solves your frequent schema drift problem.
High-Frequency Streaming: It efficiently processes millions of files file-by-file from Azure Data Lake Storage Gen2 (ADLS Gen2) as they arrive, making it perfect for events emitted every few seconds.
Cost-Efficient Scalability: Instead of scanning entire directories of tens of thousands of IoT sensors, Auto Loader uses optimized directory listing or file notification modes to ingest only newly arrived files.
Box 2: Lakeflow Connect managed connector
Operational maintenance data
Scenario: Operational maintenance data: Structured operational maintenance data is stored on the Azure Database for PostgreSQL server.
The Lakeflow Connect managed connector is the best option for ingesting structured operational maintenance data from an Azure Database for PostgreSQL server into Databricks.
Native Database Support: Databricks Lakeflow Connect explicitly features a fully-managed database connector for Azure Database for PostgreSQL.
Built-in Change Data Capture (CDC): It automatically handles structured operational data by using PostgreSQL's logical replication to incrementally ingest changes (inserts, updates, deletes) without putting a heavy load on your production database.
Automated Engineering: It comes with out-of-the-box support for schema evolution, automatic error retries, and direct integration with Unity Catalog governance.
Box 3: Auto Loader
Maintenance logs
Scenario: Maintenance logs: Maintenance systems generate historical repair logs, daily incremental updates, technician notes, and unstructured attachments that are stored in the Data Lake Storage Gen2 accounts.
For ingesting varied data formats from cloud storage, Auto Loader is the best option. Because your maintenance logs, incremental updates, and attachments are already stored in ADLS Gen2, Auto Loader cloudFiles efficiently processes millions of files incrementally, supports automatic schema inference, and handles unstructured data.
Handles Diverse Formats: It natively ingests structured historical logs, semi-structured daily updates, and unstructured data like technician notes and file attachments.
Incremental Ingestion: Auto Loader automatically detects new files using directory listing or notification modes without complex tracking logic, keeping ingestion highly optimized.
Schema Evolution: As maintenance systems change log structures over time, Auto Loader detects changes and handles schema drift seamlessly without breaking the pipeline.
Box 4: Azure Data Factory
External weather data
Scenario: External weather data: Hourly weather forecasts are retrieved from a REST API and written to the Data Lake Storage Gen2 accounts.
The best option for pulling data from a custom REST API and writing it to Azure Data Lake Storage Gen2 (ADLS Gen2) is Azure Data Factory.
Native REST Support: Azure Data Factory (ADF) features a built-in, low-code Copy Activity designed specifically to handle authentication, pagination, and token refreshes required by custom REST APIs.
Optimized for ADLS Gen2: ADF natively interfaces with ADLS Gen2 as a sink. It efficiently writes data to cloud object storage without needing an active Spark compute cluster running, which dramatically lowers costs.


Reference:

https://learn.microsoft.com/en-us/azure/databricks/ingestion/lakeflow-connect/postgresql-pipeline https://learn.microsoft.com/en-us/azure/databricks/ingestion/lakeflow-connect/faq https://abylon.io/blog/lakeflow-connect-vs-azure-data-factory-salesforce/



Viewing page 10 of 23
Viewing questions 46 - 50 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!