Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem.After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen.You have an Azure Databricks workspace named Workspace1 that contains a lakehouse and is enabled for Unity Catalog.You have a connection to a Microsoft SQL Server database named DB1.You need to expose the schemas and tables of DB1 to meet the following requirements:-The schemas and tables can be queried in Databricks.-The schemas and tables appear alongside other Unity Catalog objects.-The data is NOT copied into Databricks-managed storage.Solution: You create a Lakeflow Connect pipeline and connect it to DB1.Does this meet the goal?
Answer(s): B
Correct: * You create a foreign catalog in Catalog Explorer. You should create a Foreign Catalog using Lakehouse Federation. Data Copying: Lakehouse Federation queries data directly in the source SQL Server without moving or copying it.Seamless Integration: The database schemas and tables appear right inside Unity Catalog alongside your other data objects.Real-time Access: It provides immediate access to live SQL Server data.Incorrect: * You create a Databricks access connector.* You create a Lakeflow Connect pipeline and connect it to DB1. Data Copying: Lakeflow Connect is an ingestion tool that physically replicates and copies data into Databricks-managed storage (Delta tables).Storage Costs: It violates your requirement to keep data out of Databricks storage.* You create a new native catalog in Unity Catalog.Note: To expose the external SQL Server database in Unity Catalog without copying the data, you must use Lakehouse Federation.Here are the step-by-step actions you need to take: 1. Create a Connection Create a securable object in Unity Catalog that specifies the path and credentials to access the SQL Server database. Go to Catalog Explorer or use SQL. Select External Data > Connections. Create a connection using the SQL Server connection details (URL, host, port, and database credentials).*-> 2. Create a Foreign CatalogCreate a specific type of catalog in Unity Catalog that mirrors the external database. Use the CREATE FOREIGN CATALOG SQL command or the Catalog Explorer UI. Link this foreign catalog directly to the connection you created in step 1.3. Query the DataOnce the foreign catalog is created, Unity Catalog automatically syncs the schemas and tables from SQL Server.
Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem.After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen.You have an Azure Databricks workspace named Workspace1 that contains a lakehouse and is enabled for Unity Catalog.You have a connection to a Microsoft SQL Server database named DB1.You need to expose the schemas and tables of DB1 to meet the following requirements:-The schemas and tables can be queried in Databricks.-The schemas and tables appear alongside other Unity Catalog objects.-The data is NOT copied into Databricks-managed storage.Solution: You create a Databricks access connector.Does this meet the goal?
Correct: * You create a foreign catalog in Catalog Explorer. You should create a Foreign Catalog using Lakehouse Federation. Data Copying: Lakehouse Federation queries data directly in the source SQL Server without moving or copying it.Seamless Integration: The database schemas and tables appear right inside Unity Catalog alongside your other data objects.Real-time Access: It provides immediate access to live SQL Server data.Incorrect: * You create a Databricks access connector.* You create a Lakeflow Connect pipeline and connect it to DB1. Data Copying: Lakeflow Connect is an ingestion tool that physically replicates and copies data into Databricks-managed storage (Delta tables).Storage Costs: It violates your requirement to keep data out of Databricks storage.* You create a new native catalog in Unity Catalog.Note: To expose the external SQL Server database in Unity Catalog without copying the data, you must use Lakehouse Federation.Here are the step-by-step actions you need to take: 1. Create a Connection Create a securable object in Unity Catalog that specifies the path and credentials to access the SQL Server database. Go to Catalog Explorer or use SQL. Select External Data > Connections. Create a connection using the SQL Server connection details (URL, host, port, and database credentials).*-> 2. Create a Foreign Catalog Create a specific type of catalog in Unity Catalog that mirrors the external database. Use the CREATE FOREIGN CATALOG SQL command or the Catalog Explorer UI. Link this foreign catalog directly to the connection you created in step 1.3. Query the DataOnce the foreign catalog is created, Unity Catalog automatically syncs the schemas and tables from SQL Server.
Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem.After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen.You have an Azure Databricks workspace named Workspace1 that contains a lakehouse and is enabled for Unity Catalog.You have a connection to a Microsoft SQL Server database named DB1.You need to expose the schemas and tables of DB1 to meet the following requirements:-The schemas and tables can be queried in Databricks.-The schemas and tables appear alongside other Unity Catalog objects.-The data is NOT copied into Databricks-managed storage.Solution: You create a foreign catalog in Catalog Explorer.Does this meet the goal?
Answer(s): A
Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem.After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen.You have an Azure Databricks workspace named Workspace1 that contains a lakehouse and is enabled for Unity Catalog.You have a connection to a Microsoft SQL Server database named DB1.You need to expose the schemas and tables of DB1 to meet the following requirements:-The schemas and tables can be queried in Databricks.-The schemas and tables appear alongside other Unity Catalog objects.-The data is NOT copied into Databricks-managed storage.Solution: You create a new native catalog in Unity Catalog.Does this meet the goal?
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?
Answer(s): D
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.
https://community.databricks.com/t5/technical-blog/unity-catalog-as-a-foundation-for-governance-that-democratizes/ba-p/126983
DRAG DROP (Drag and Drop is not supported)You have an Azure Databricks workspace named Workspace1.You have a user named User1 that is a non-admin user for Workspace1.You need to ensure that User1 can perform the following tasks:-Provision clusters of any size.-Run Databricks jobs.The solution must follow the principle of least privilege.What should you do?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:
Box 1: Assign the Allow unrestricted cluster creation entitlement. To allow a non-admin user to provision clusters of any size while maintaining the principle of least privilege, you should grant the user the "Allow unrestricted cluster creation" entitlement while leaving their workspace role as a standard User.By default, non-admin users cannot create standard clusters unless explicitly granted specific entitlements or assigned to strict cluster policies. Assigning this specific entitlement satisfies the exact requirement without escalating the user's role to a Workspace Admin.Box 2: Grant the CAN RUN permission for the jobs. To allow a non-admin user to run Databricks jobs while adhering to the principle of least privilege, a workspace administrator must configure Object-Level Access Control List (ACL) permissions rather than granting administrative group memberships.Required Configuration The workspace administrator must grant the non-admin user specific Job Access Permissions on the targeted job(s): *-> Can Manage Run: Grant this permission if the user only needs to trigger manual runs, skip tasks, or cancel active runs.Can View: Grant this permission if the user only needs to see the job configurations and monitor previous run history or logs.
https://learn.microsoft.com/en-us/azure/databricks/security/auth/entitlements https://learn.microsoft.com/en-us/azure/databricks/jobs/privileges
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 = CSVYou need to ensure that the statement can access the data in the container.What should you configure?
Answer(s): C
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.
https://docs.databricks.com/gcp/en/ingestion/cloud-object-storage/copy-into/unity-catalog
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:
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`;
https://learn.microsoft.com/en-us/azure/databricks/data-governance/unity-catalog/manage-privileges/
Post your Comments and Discuss Microsoft DP-750 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the DP-750 content, but please register or login to continue.