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

Updated On: 3-Nov-2026
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 managed Delta table named Table1.
Table1 is written by batch jobs every hour and is queried frequently by filtering two columns named CustomerId and EventDate.
You expect Table1 to grow significantly over time.
The rows in Table1 are frequently updated and deleted to support compliance requests.
You need to keep query performance consistent as Table1 grows. The solution must minimize update and deletion effort.
What should you include in the solution? 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: Liquid Clustering
To optimize query performance, implement:
To optimize query performance for a rapidly growing, frequently updated managed Delta table filtered by customer and date in Unity Catalog, you must implement Liquid Clustering on both the customer and date columns, while running regular OPTIMIZE and VACUUM maintenance.
Liquid Clustering replaces traditional partitioning and Z-Ordering, drastically improving performance for tables with high-frequency write, update, and delete workloads.
Box 2: Enable deletion vectors.
To optimize updates and deletions:
Write and Execution Strategies
Use Deletion Vectors: Ensure Deletion Vectors are enabled (default in Databricks Runtime 12.1+). They record deletes and updates in a separate lightweight file instead of rewriting the entire data file immediately.
Leverage MERGE INTO: Execute updates and deletions in a single atomic batch using the MERGE command. Ensure your ON search condition explicitly includes filters for both the customer and date columns to trigger file pruning.


Reference:

https://blog.devgenius.io/liquid-clustering-in-databricks-4002fddbf0be



View Related Case Study

You need to curate Unity Catalog objects that reference the ERP data. The solution must meet the governance requirements.
What should you do?

  1. In the managed analytics catalog, create views that reference foreign catalog tables that use three-level naming.
  2. Create Delta tables directly inside the foreign catalog by running the CREATE TABLE AS SELECT (CTAS) command.
  3. Run the ALTER TABLE command on the foreign catalog tables to add new columns that are required for analytics.
  4. Create a volume in the foreign catalog and store curated Delta tables in the volume.

Answer(s): A

Explanation:

You should create views that reference foreign catalog tables using three-level naming in your managed analytics catalog.
Read-only enforcement: Views act as virtual overlays. They pull data dynamically from the Azure SQL source without creating duplicate physical files, keeping the mechanism truly read-only.
CTAS limitation: Running a CREATE TABLE AS SELECT (CTAS) command directly inside a foreign catalog is fundamentally unsupported. Lakehouse Federation foreign catalogs represent the external database schemas natively; you cannot write or store native Delta tables inside an external Azure SQL database.
Namespace structure: Unity Catalog uses a strict three-level namespace (catalog.schema.table). Using this format in your views allows you to curate clean, business-friendly datasets in your managed catalog while seamlessly pointing back to the underlying foreign catalog.
Scenario:
Governance Requirements: Provide a read-only mechanism to reference the ERP data through a foreign catalog.
Azure Environment
Contoso has a single Azure Databricks workspace named Workspace1 in the West US Azure region. Workspace1 is enabled for Unity Catalog.
A single Azure SQL database in the West US region that hosts enterprise resource planning (ERP) data


Reference:

https://www.databricks.com/blog/enterprise-scale-governance-migrating-hive-metastore-unity-catalog



View Related Case Study

You need to organize Unity Catalog. The solution must meet the governance requirements.
What should you do?

  1. Use a single shared schema for all the development teams and rely on table-level permissions for isolation.
  2. Enable the development teams to create objects directly in the default catalog and schema.
  3. Create a separate catalog for each development team and enable each team to choose its own schema names.
  4. Create a shared development catalog, enforce a standardized naming convention, and assign each development team its own schema.

Answer(s): D

Explanation:

Scenario:Governance Requirements
Contoso identifies the following governance requirements:
*-> Centralize the metadata catalog.
*-> Provide isolated development areas that follow standard naming conventions.
Problem Statements,The company’s existing analytics environment has several issues:
Governance:
Naming conventions are inconsistent across development teams, regions, and products.
--
The best approach is: Create a shared development catalog, enforce a standardized naming convention, and assign each development team its own schema.
This option perfectly balances governance, isolation, and scalability according to Azure Databricks Well-Architected frameworks.
Enforces Consistency: It directly solves your problem of inconsistent naming by forcing a uniform structure at the schema level.
Simplifies Governance: Managing permissions at the schema level is much cleaner and less error-prone than managing individual table privileges.
Aligns with Unity Catalog Best Practices: Databricks recommends a catalog.schema.table model where the catalog represents the environment (e.g., dev, staging, prod), and schemas represent functional or team boundaries.
Incorrect:
[Not A]
Single shared schema: This creates a high administrative burden. Managing table-level permissions for multiple teams in a single schema is difficult to audit and highly prone to security leaks.
[Not C]
Separate catalogs per team: This leads to catalog sprawl and completely defeats the goal of a centralized metadata catalog. It also allows teams to continue using inconsistent naming conventions.


Reference:

https://dzone.com/articles/automate-databricks-unity-catalog-permissions-at-schema-level



View Related Case Study

DRAG DROP (Drag and Drop is not supported)
You have an Azure Databricks workspace named Workspace1 that is attached to a Unity Catalog metastore named metastore1.
You need to register an Azure Storage account named account1 that has a hierarchical namespace enabled as an external location. The external location must use a managed identity to authenticate to account1 and the solution must follow the principle of least privilege.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




To register an Azure Storage account (ADLS Gen2) as an external location using a managed identity and an Access Connector under the principle of least privilege, you must complete the following configuration workflow:
Step 1: Create a Databricks access Connector
Action 1: Create an Access Connector for Azure Databricks
Navigate to the Azure Portal.
Create a new resource and search for Access Connector for Azure Databricks.
Configure it in the same Azure region as your ADLS Gen2 storage account.
Ensure the System-assigned managed identity status is turned On (or attach a specific user-assigned managed identity).Once deployed, navigate to its properties and copy the Resource ID.
Step 2: Assign Workspace1 the Storage Blob Data Contributor role for account1.
Action 2: Configure Least-Privilege IAM Roles on the Storage Account
Navigate to your hierarchical namespace-enabled Azure Storage Account.
Open Access Control (IAM) and click Add role assignment.
*-> Assign the Storage Blob Data Contributor role.
Note on Least Privilege: To enforce true least privilege, avoid assigning this role at the entire storage account level. Instead, scope this role assignment specifically to the target container inside the storage account. Select Managed identity as the assignee type and select your Access Connector.
Step 3: Register the access connector as a storage credential in metastore1
Action 3: The Databricks access connector must be registered in the metastore (via a Unity Catalog Storage Credential), not in the individual workspace.
Centralized Security: Unity Catalog manages security at the account/metastore level.
Cross-Workspace Access: Registering it in the metastore allows the credential to be safely shared across multiple workspaces attached to that same metastore.
Object Hierarchy: In Unity Catalog, an External Location relies on a Storage Credential. Both are metastore-level securable objects.


Reference:

https://community.databricks.com/t5/data-governance/unity-catalog-error-creating-table-errorclass-invalid-state /td-p/10009



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure Databricks workspace that is enabled for Unity Catalog.
You need to ensure that data lineage is captured and can be reviewed for tables accessed by Databricks notebooks and jobs. The solution must minimize administrative effort.
Which compute configuration should you use to capture the data lineage and what should you use to review the data lineage? 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: A Serverless cluster
To capture automated data lineage via Unity Catalog for both Databricks notebooks and jobs with low administrative overhead, you should use Serverless compute (or Shared access mode clusters if serverless is unavailable).
Recommended Compute Options
Serverless Compute (Highly Recommended):
This option completely minimizes administrative overhead. It requires no infrastructure management, scales automatically, starts instantly, and captures lineage inherently for both Databricks Notebooks and Jobs.
Box 2: Catalog Explorer
To review data lineage in an Azure Databricks workspace enabled for Unity Catalog, you should use Catalog Explorer.
Because you are using Unity Catalog and Serverless compute, table-level and column-level data lineage is automatically captured for notebooks and jobs without any manual configuration or administrative overhead.
View Lineage in Catalog Explorer
You can visually explore how data flows between tables by navigating through the Azure Databricks user interface:
Open the Catalog icon in the sidebar.
Select the desired catalog, schema, and table.
Click the Lineage tab.
Click See lineage graph to view an interactive map of upstream and downstream dependencies.


Reference:

https://learn.microsoft.com/en-us/azure/databricks/data-governance/unity-catalog/best-practices https://kanerika.com/blogs/databricks-data-lineage/



Viewing page 5 of 23
Viewing questions 21 - 25 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!