Free DP-700 Exam Braindumps
Implementing Data Engineering Solutions Using Microsoft Fabric Questions 61–65 (page: 14)

Updated On: 17-Sep-2026

DRAG DROP (Drag and Drop is not supported) (Drag and Drop is not supported)
You have the Fabric deployment pipeline shown in the exhibit. (Click the Exhibit tab.)

In the Development workspace, you build a new feature named Feature1.
You need to deploy Feature1 to the Test workspace. The solution must ensure that only a pipeline is deployed.
Which four 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:





Step 1: Select pipeline1 Step 2: Select the Test stage.
Incorrect: * Select the Development stage.
Step 3: From deploy from, select Development
Incorrect: * From deploy from, select Production
Step 4: Select Deploy


Reference:

https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/get-started-with-deployment-pipelines



HOTSPOT (Drag and Drop is not supported) (Drag and Drop is not supported)
You have a Fabric tenant that is linked to a Microsoft Entra tenant. The Microsoft Entra tenant contains a user named User1 and two groups named Group1 and Group2.
The Fabric tenant contains the workspaces shown in the following table.

You need to meet the following access requirements:
-User1 must have read access to the following:
-The operations department reports
-The HR department warehouse and reports
-The legal department warehouse and reports
-User1 must be able to create new items in Workspace2.
-Group1 must have access to the finance department warehouse and reports.
-Group1 must be able to add new users to the finance department workspace.
-Group2 must have access to only the HR warehouse and the legal warehouse.
The solution must follow the principle of least privilege.
What should you do? 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: Assign the Contributor role for Workspace1. To Group1
Group1 must have access to the finance department warehouse and reports. -> Viewer role is enough.
Group1 must be able to add new users to the finance department workspace. -> Contributor role is required.
Box 2: Configure only item security for Workspace2. To Group2
Group2 must have access to only the HR warehouse and the legal warehouse.
To assign a Microsoft Entra ID group roles only to specific items within a Fabric workspace, you must use item-level permissions, which are applied directly to individual items (reports, semantic models, etc.) rather than the entire workspace. This requires assigning the group a "Viewer" role at the workspace level, then configuring specific permissions (Read, Reshare, or Write) on the individual items.
Box 3: Assign the Contributor role for Workspace2 and the Viewer role for Workspace4. To User1
Here are the recommended roles for the user: Workspace2 Workspace: Assign the Contributor role. Reasoning: The Contributor role alloWorkspace the user to view and modify all content, including creating new items (warehouses, reports, etc.) in the workspace.
Workspace4 Workspace (Operations): Assign the Viewer role. The operations department reports is in Workspace 4. Reasoning: The Viewer role provides read-only access to all items (reports and warehouses) in the workspace.
Summary of Access: Workspace2 (HR & Legal): Contributor (AlloWorkspace create/read/write) Workspace4 (Operations): Viewer (AlloWorkspace read-only)


Reference:

https://learn.microsoft.com/en-us/fabric/security/permission-model



You have a Fabric workspace named Workspace1 that is connected to a GitHub repository named repo1. Workspace1 contains the items shown in the following table.

You modify Semanticmodel1, Semanticmodel2, and Report2.
You need to commit the changes to repo1.
What is the minimum number of commits you should perform?

  1. 1
  2. 2
  3. 3
  4. 4

Answer(s): A

Explanation:

To commit the updates for the two semantic models and the second report to the GitHub repository, the minimum number of commits required is one. In Microsoft Fabric's Git integration, you can select multiple changed items simultaneously and commit them in a single batch.
Key Factors for Committing Batch Operations: The Fabric Source Control pane allows you to check the boxes next to all modified items (the two semantic models and the second report) and click Commit once.
Item Support: All the items mentioned (Semantic Models, Power BI Reports, and Dataflow Gen2) are supported for Git integration in Fabric.
Commit Logic: Git integration in Fabric does not force a "one commit per item" rule. As long as the items are in the same workspace and connected to the same branch, they can be grouped into one revision.


Reference:

https://community.fabric.microsoft.com/t5/Issues/Semantic-Model-and-Report-Syncing-Issues-with-Git-Integration/idi-p/3980544



You have a Fabric workspace that contains a lakehouse named Lakehouse1. Lakehouse1 contains a table named Table1.
You need to ensure that a user named User1 can view only specific rows in Table1.
What should you do first?

  1. Create a security predicate.
  2. Create a function.
  3. Create a security policy.
  4. Grant User1 the SELECT permission for Table1.

Answer(s): D

Explanation:

To restrict a user to specific rows in a Microsoft Fabric Lakehouse table, you must use Row-Level Security (RLS).
Because Fabric Lakehouses do not currently support native RLS directly on the Delta files in the Lakehouse explorer, you must implement this logic via the SQL Analytics Endpoint.
Phase 1: Grant Initial Access The user needs permission to connect to the SQL endpoint before you can restrict their view. Workspace Role: Assign the user the Viewer role.
Note: Higher roles (Member/Admin) bypass RLS.
*-> SQL Permissions: Run this in a SQL Query tab:
GRANT SELECT ON dbo.YourTableName TO [user@example.com];
Phase 2: Create the Security Logic You will define a function that determines which rows a user can see based on their identity.
1. Create a Mapping Table (Optional but Recommended) Create a table that links users to specific attributes (e.g., Department or Region). Columns: UserEmail, AccessAttribute
2. Create the Security Function [Not B]
3. Apply the Security Policy [Not C] This binds the function to your actual data table.


Reference:

https://medium.com/tech-start/data-security-in-fabric-datawarehouse-c9552705944f



You have a Fabric workspace named Workspace1 that contains a lakehouse.
You have a Microsoft Entra tenant that contains a user named User1.
You need to ensure that User1 can create items in Workspace1. The solution must follow the principle of least privilege.
Which workspace role should you assign to User1?

  1. Member
  2. Contributor
  3. Admin
  4. Viewer

Answer(s): B

Explanation:

To enable a user to create items (such as notebooks, reports, or Lakehouses) in a Microsoft Fabric workspace with minimum permissions, assign the Contributor role. This role allows full creation and modification of items while restricting them from managing permissions or deleting the workspace itself.
Contributor Role: Ideal for developers. Can create, edit, and delete items, but cannot share items or manage workspace access.
Incorrect: [Not C] Alternative (Too High): The Member or Admin roles allow sharing and permission management.
[Not D] Alternative (Too Low): The Viewer role only allows reading, not creation.


Reference:

https://learn.microsoft.com/en-us/fabric/security/permission-model



Viewing page 14 of 33
Viewing questions 66 - 70 out of 160 questions


Post your Comments and Discuss Microsoft DP-700 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!