Practice Exams:

View All

Microsoft Fabric Analytics Engineer DP-600 Analytics Development Lifecycle And Reusable Assets Practice Test

Skill 1.2 – 90 original questions

This Microsoft DP-600 practice test focuses on analytics development lifecycle and reusable assets through original scenario-based questions aligned to the active DP-600 skills measured as of July 21, 2026. Use the complete ExamSnap DP-600 collection for broader practice across Microsoft Fabric analytics lifecycle, data preparation, querying, and semantic modeling. For broader exam preparation, review the Microsoft DP-600 Exam Dumps page.

Instructions: Select the best answer for each question. Review the explanation after answering; each option includes a reason it is or is not the strongest choice for the scenario.

Question 1

The marketing semantic model at Litware is moving from proof of concept to production. Before rollout, the security analytics team must track Fabric workspace item definitions in a branch and review changes through pull requests, while ensuring that the team wants to keep governance centralized. Which action best meets both needs? Existing users should keep their current access.

Assign the developers the Contributor workspace role
Use the XMLA endpoint to manage the semantic model programmatically
Connect the workspace to a supported Git repository by using Fabric Git integration
Define and assign row-level security roles for the semantic model
Create a Power BI template (.pbit) file

Correct answer: C

Why: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

Option review:

A: Contributor permits creation and modification of workspace content without the broader membership-management permissions of Member or Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

B: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

D: RLS filters rows by user or role so consumers see only the permitted records. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

E: A PBIT captures reusable report and model definitions while omitting imported data. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Connect the workspace to a supported Git repository by using Fabric Git integration

Question 2

Woodgrove Bank has a change request for the supply-chain lakehouse: separate development work by branch while keeping supported Fabric items synchronized with source control. The Fabric center of excellence wants a solution where the approach should remain understandable to future maintainers. Which implementation is most suitable? Existing users should keep their current access.

Use the XMLA endpoint to manage the semantic model programmatically
Use Fabric Git integration and map the development workspace to the appropriate repository branch
Publish and reuse a shared semantic model
Use Fabric lineage and impact analysis before making the change
Create a OneLake security role scoped to the required folders or tables

Correct answer: B

Why: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

Option review:

A: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

B: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

C: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

D: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

E: OneLake security roles can scope data access to specific tables or folders for users who should not receive broad item write access. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Use Fabric Git integration and map the development workspace to the appropriate repository branch

Question 3

A solution architect reviewing Coho Winery’s IoT telemetry solution asks the customer insights team to track Fabric workspace item definitions in a branch and review changes through pull requests. Since the implementation should reduce operational overhead, which recommendation is strongest? No unrelated workspace or model permissions should be changed.

Assign the auditors the Viewer workspace role
Assign the developers the Contributor workspace role
Assign the release lead the Member workspace role
Create a Power BI template (.pbit) file
Connect the workspace to a supported Git repository by using Fabric Git integration

Correct answer: E

Why: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

Option review:

A: The Viewer role provides read access to workspace content without create, edit, or workspace-management rights. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

B: Contributor permits creation and modification of workspace content without the broader membership-management permissions of Member or Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: Member supports creating, modifying, and sharing content while reserving full workspace administration for Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

D: A PBIT captures reusable report and model definitions while omitting imported data. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

E: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

Learning point: Connect the workspace to a supported Git repository by using Fabric Git integration

Question 4

The next sprint for Adventure Works’s finance reporting platform includes a task to separate development work by branch while keeping supported Fabric items synchronized with source control. The acceptance criteria add that the solution must remain maintainable as usage grows. Which Fabric or Power BI action is appropriate? No unrelated workspace or model permissions should be changed.

Use Fabric Git integration and map the development workspace to the appropriate repository branch
Use the item Manage permissions or sharing experience for that item
Use Fabric lineage and impact analysis before making the change
Create a OneLake security role scoped to the required folders or tables
Connect to the workspace XMLA endpoint with read/write operations enabled

Correct answer: A

Why: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

Option review:

A: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

B: Item permissions are scoped to an individual item and are appropriate when workspace-wide access is unnecessary. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

D: OneLake security roles can scope data access to specific tables or folders for users who should not receive broad item write access. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

E: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Use Fabric Git integration and map the development workspace to the appropriate repository branch

Question 5

Tailspin Toys is troubleshooting a design decision in the retail performance dashboard. The desired end state is to track Fabric workspace item definitions in a branch and review changes through pull requests; the team wants the smallest administrative blast radius. Which change should the BI platform team make? The team will validate the change first in a nonproduction environment.

Save the solution as a Power BI Desktop project (.pbip)
Share only that report and grant the required item permission
Connect the workspace to a supported Git repository by using Fabric Git integration
Promote the item
Create a Power BI template (.pbit) file

Correct answer: C

Why: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

Option review:

A: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

B: Item-level sharing can grant access to a specific Fabric item without assigning a workspace role. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

D: Promotion is appropriate for recommended content that has not gone through the formal certification process. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Connect the workspace to a supported Git repository by using Fabric Git integration

Question 6

For the marketing semantic model, Fourth Coffee has documented a business requirement to separate development work by branch while keeping supported Fabric items synchronized with source control. The security analytics team must meet it in a way where the team wants to keep governance centralized. What is the best choice? The team will validate the change first in a nonproduction environment.

Use Fabric Git integration and map the development workspace to the appropriate repository branch
Apply column-level security to the sensitive columns
Use the item Manage permissions or sharing experience for that item
Assign the auditors the Viewer workspace role
Use the XMLA endpoint to manage the semantic model programmatically

Correct answer: A

Why: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

Option review:

A: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

B: Column-level security restricts access at the column boundary while preserving access to permitted data. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: Item permissions are scoped to an individual item and are appropriate when workspace-wide access is unnecessary. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

D: The Viewer role provides read access to workspace content without create, edit, or workspace-management rights. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

E: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Use Fabric Git integration and map the development workspace to the appropriate repository branch

Question 7

A governance review of Wide World Importers’s supply-chain lakehouse asks for evidence that the solution can track Fabric workspace item definitions in a branch and review changes through pull requests. Because the approach should remain understandable to future maintainers, which action should be approved? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Apply column-level security to the sensitive columns
Use the XMLA endpoint to manage the semantic model programmatically
Grant Build permission on the semantic model rather than a workspace role
Connect the workspace to a supported Git repository by using Fabric Git integration
Promote the item

Correct answer: D

Why: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

Option review:

A: Column-level security restricts access at the column boundary while preserving access to permitted data. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: Build permission enables creation of content from the semantic model while keeping unrelated workspace items out of scope. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

D: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

E: Promotion is appropriate for recommended content that has not gone through the formal certification process. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Connect the workspace to a supported Git repository by using Fabric Git integration

Question 8

Before expanding the IoT telemetry solution, the customer insights team at Northwind Traders must separate development work by branch while keeping supported Fabric items synchronized with source control. The rollout plan says that the implementation should reduce operational overhead. Which option most directly addresses the requirement? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Create a deployment pipeline with separate lifecycle stages
Promote the item
Use Fabric Git integration and map the development workspace to the appropriate repository branch
Create and distribute a Power BI data source (.pbids) file
Apply the required sensitivity label to the report

Correct answer: C

Why: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

Option review:

A: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

B: Promotion is appropriate for recommended content that has not gone through the formal certification process. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

D: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

E: Sensitivity labels are the native mechanism for classifying protected content according to the information-protection policy. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Use Fabric Git integration and map the development workspace to the appropriate repository branch

Question 9

Trey Research is redesigning its finance reporting platform. The retail insights team must track Fabric workspace item definitions in a branch and review changes through pull requests. In addition, the solution must remain maintainable as usage grows. Which action is the best fit? The design decision will be reviewed by both data engineering and BI owners.

Define and assign row-level security roles for the semantic model
Share only that report and grant the required item permission
Connect the workspace to a supported Git repository by using Fabric Git integration
Create and distribute a Power BI data source (.pbids) file
Use the item Manage permissions or sharing experience for that item

Correct answer: C

Why: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

Option review:

A: RLS filters rows by user or role so consumers see only the permitted records. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

E: Item permissions are scoped to an individual item and are appropriate when workspace-wide access is unnecessary. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Connect the workspace to a supported Git repository by using Fabric Git integration

Question 10

During a design review for Alpine Ski House’s retail performance dashboard, one requirement is non-negotiable: separate development work by branch while keeping supported Fabric items synchronized with source control. Because the team wants the smallest administrative blast radius, what should the BI platform team implement? The design decision will be reviewed by both data engineering and BI owners.

Save the solution as a Power BI Desktop project (.pbip)
Use Fabric Git integration and map the development workspace to the appropriate repository branch
Publish and reuse a shared semantic model
Create a OneLake security role scoped to the required folders or tables
Create and distribute a Power BI data source (.pbids) file

Correct answer: B

Why: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

Option review:

B: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

E: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Use Fabric Git integration and map the development workspace to the appropriate repository branch

Question 11

The security analytics team at Contoso is preparing the next release of its marketing semantic model. They need to track Fabric workspace item definitions in a branch and review changes through pull requests; the team wants to keep governance centralized. Which choice most directly satisfies the requirement? Existing users should keep their current access.

Save the solution as a Power BI Desktop project (.pbip)
Use the item Manage permissions or sharing experience for that item
Connect the workspace to a supported Git repository by using Fabric Git integration
Use Fabric lineage and impact analysis before making the change
Share only that report and grant the required item permission

Correct answer: C

Why: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

Option review:

C: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

E: Item-level sharing can grant access to a specific Fabric item without assigning a workspace role. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Connect the workspace to a supported Git repository by using Fabric Git integration

Question 12

A production readiness review at Wingtip Toys found a gap in the supply-chain lakehouse. The remediation must separate development work by branch while keeping supported Fabric items synchronized with source control, and the approach should remain understandable to future maintainers. What is the most appropriate action? Existing users should keep their current access.

Use Fabric Git integration and map the development workspace to the appropriate repository branch
Configure deployment rules for the target stage
Create a OneLake security role scoped to the required folders or tables
Review downstream dependencies in the lineage or impact-analysis view
Connect to the workspace XMLA endpoint with read/write operations enabled

Correct answer: A

Why: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

Option review:

A: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

B: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: OneLake security roles can scope data access to specific tables or folders for users who should not receive broad item write access. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

D: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Use Fabric Git integration and map the development workspace to the appropriate repository branch

Question 13

For a new phase of the IoT telemetry solution, Proseware asks the customer insights team to track Fabric workspace item definitions in a branch and review changes through pull requests. The architecture decision record also states that the implementation should reduce operational overhead. Which approach should be selected? No unrelated workspace or model permissions should be changed.

Create a OneLake security role scoped to the required folders or tables
Certify the semantic model
Apply column-level security to the sensitive columns
Assign the release lead the Member workspace role
Connect the workspace to a supported Git repository by using Fabric Git integration

Correct answer: E

Why: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

Option review:

A: OneLake security roles can scope data access to specific tables or folders for users who should not receive broad item write access. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

B: Certification is the stronger endorsement used for content that has been reviewed and approved as authoritative. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: Column-level security restricts access at the column boundary while preserving access to permitted data. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

D: Member supports creating, modifying, and sharing content while reserving full workspace administration for Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

E: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

Learning point: Connect the workspace to a supported Git repository by using Fabric Git integration

Question 14

Blue Yonder Airlines is standardizing how the finance reporting platform is managed. The immediate goal is to separate development work by branch while keeping supported Fabric items synchronized with source control. Given that the solution must remain maintainable as usage grows, which option should the retail insights team choose? No unrelated workspace or model permissions should be changed.

Create a OneLake security role scoped to the required folders or tables
Assign the platform owner the Admin workspace role
Connect to the workspace XMLA endpoint with read/write operations enabled
Use Fabric Git integration and map the development workspace to the appropriate repository branch
Create and distribute a Power BI data source (.pbids) file

Correct answer: D

Why: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

Option review:

B: Admin is the workspace role intended for full workspace administration, including permissions and settings. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

D: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This directly matches the stated requirement.

Learning point: Use Fabric Git integration and map the development workspace to the appropriate repository branch

Question 15

An internal audit of Fabrikam’s retail performance dashboard identifies this requirement: track Fabric workspace item definitions in a branch and review changes through pull requests. The BI platform team also notes that the team wants the smallest administrative blast radius. What should they do? The team will validate the change first in a nonproduction environment.

Define and assign row-level security roles for the semantic model
Apply the required sensitivity label to the report
Connect the workspace to a supported Git repository by using Fabric Git integration
Use the item Manage permissions or sharing experience for that item
Configure object-level security for the protected table or column

Correct answer: C

Why: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

Option review:

B: Sensitivity labels are the native mechanism for classifying protected content according to the information-protection policy. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

C: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This directly matches the stated requirement.

D: Item permissions are scoped to an individual item and are appropriate when workspace-wide access is unnecessary. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

E: OLS prevents users from discovering or querying protected model objects. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Configure version control for a workspace’.

Learning point: Connect the workspace to a supported Git repository by using Fabric Git integration

Question 16

The customer 360 model at Litware is moving from proof of concept to production. Before rollout, the data governance group must store a Power BI report and semantic model as source-control-friendly project files instead of one binary PBIX file, while ensuring that the team wants to keep governance centralized. Which action best meets both needs? Existing users should keep their current access.

Connect the workspace to a supported Git repository by using Fabric Git integration
Use the XMLA endpoint to manage the semantic model programmatically
Save the solution as a Power BI Desktop project (.pbip)
Apply the required sensitivity label to the report
Assign the developers the Contributor workspace role

Correct answer: C

Why: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Option review:

A: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

C: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

D: Sensitivity labels are the native mechanism for classifying protected content according to the information-protection policy. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

E: Contributor permits creation and modification of workspace content without the broader membership-management permissions of Member or Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

Learning point: Save the solution as a Power BI Desktop project (.pbip)

Question 17

Woodgrove Bank has a change request for the sales analytics solution: enable text-based review of Power BI project metadata in Git. The enterprise reporting group wants a solution where the approach should remain understandable to future maintainers. Which implementation is most suitable? Existing users should keep their current access.

Define and assign row-level security roles for the semantic model
Promote the item
Use the PBIP project format and commit the project folder
Assign the developers the Contributor workspace role
Use the item Manage permissions or sharing experience for that item

Correct answer: C

Why: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

Option review:

C: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

D: Contributor permits creation and modification of workspace content without the broader membership-management permissions of Member or Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

Learning point: Use the PBIP project format and commit the project folder

Question 18

A solution architect reviewing Coho Winery’s risk analytics environment asks the finance analytics squad to store a Power BI report and semantic model as source-control-friendly project files instead of one binary PBIX file. Since the implementation should reduce operational overhead, which recommendation is strongest? No unrelated workspace or model permissions should be changed.

Configure object-level security for the protected table or column
Configure deployment rules for the target stage
Save the solution as a Power BI Desktop project (.pbip)
Apply the appropriate Microsoft Purview sensitivity label to the item
Create a deployment pipeline with separate lifecycle stages

Correct answer: C

Why: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Option review:

A: OLS prevents users from discovering or querying protected model objects. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

C: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

D: Sensitivity labels provide governance classification and can propagate through supported Power BI and Fabric workflows. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

E: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

Learning point: Save the solution as a Power BI Desktop project (.pbip)

Question 19

The next sprint for Adventure Works’s service-operations warehouse includes a task to enable text-based review of Power BI project metadata in Git. The acceptance criteria add that the solution must remain maintainable as usage grows. Which Fabric or Power BI action is appropriate? No unrelated workspace or model permissions should be changed.

Configure deployment rules for the target stage
Assign the auditors the Viewer workspace role
Apply the appropriate Microsoft Purview sensitivity label to the item
Grant Build permission on the semantic model rather than a workspace role
Use the PBIP project format and commit the project folder

Correct answer: E

Why: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

Option review:

A: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

B: The Viewer role provides read access to workspace content without create, edit, or workspace-management rights. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

C: Sensitivity labels provide governance classification and can propagate through supported Power BI and Fabric workflows. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

D: Build permission enables creation of content from the semantic model while keeping unrelated workspace items out of scope. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

E: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

Learning point: Use the PBIP project format and commit the project folder

Question 20

Tailspin Toys is troubleshooting a design decision in the executive reporting workspace. The desired end state is to store a Power BI report and semantic model as source-control-friendly project files instead of one binary PBIX file; the team wants the smallest administrative blast radius. Which change should the operations data team make? The team will validate the change first in a nonproduction environment.

Save the solution as a Power BI Desktop project (.pbip)
Review downstream dependencies in the lineage or impact-analysis view
Connect the workspace to a supported Git repository by using Fabric Git integration
Use the item Manage permissions or sharing experience for that item
Configure object-level security for the protected table or column

Correct answer: A

Why: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Option review:

A: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

B: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

C: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

Learning point: Save the solution as a Power BI Desktop project (.pbip)

Question 21

For the customer 360 model, Fourth Coffee has documented a business requirement to enable text-based review of Power BI project metadata in Git. The data governance group must meet it in a way where the team wants to keep governance centralized. What is the best choice? The team will validate the change first in a nonproduction environment.

Use the PBIP project format and commit the project folder
Assign the release lead the Member workspace role
Grant Build permission on the semantic model rather than a workspace role
Share only that report and grant the required item permission
Create a OneLake security role scoped to the required folders or tables

Correct answer: A

Why: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

Option review:

A: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

B: Member supports creating, modifying, and sharing content while reserving full workspace administration for Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

D: Item-level sharing can grant access to a specific Fabric item without assigning a workspace role. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

Learning point: Use the PBIP project format and commit the project folder

Question 22

A governance review of Wide World Importers’s sales analytics solution asks for evidence that the solution can store a Power BI report and semantic model as source-control-friendly project files instead of one binary PBIX file. Because the approach should remain understandable to future maintainers, which action should be approved? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Configure deployment rules for the target stage
Save the solution as a Power BI Desktop project (.pbip)
Use the XMLA endpoint to manage the semantic model programmatically
Share only that report and grant the required item permission
Create and distribute a Power BI data source (.pbids) file

Correct answer: B

Why: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Option review:

B: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

C: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

Learning point: Save the solution as a Power BI Desktop project (.pbip)

Question 23

Before expanding the risk analytics environment, the finance analytics squad at Northwind Traders must enable text-based review of Power BI project metadata in Git. The rollout plan says that the implementation should reduce operational overhead. Which option most directly addresses the requirement? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Connect to the workspace XMLA endpoint with read/write operations enabled
Certify the semantic model
Apply the appropriate Microsoft Purview sensitivity label to the item
Use the PBIP project format and commit the project folder
Use Fabric Git integration and map the development workspace to the appropriate repository branch

Correct answer: D

Why: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

Option review:

A: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

D: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

E: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

Learning point: Use the PBIP project format and commit the project folder

Question 24

Trey Research is redesigning its service-operations warehouse. The analytics engineering team must store a Power BI report and semantic model as source-control-friendly project files instead of one binary PBIX file. In addition, the solution must remain maintainable as usage grows. Which action is the best fit? The design decision will be reviewed by both data engineering and BI owners.

Save the solution as a Power BI Desktop project (.pbip)
Grant Build permission on the semantic model rather than a workspace role
Create and distribute a Power BI data source (.pbids) file
Connect the workspace to a supported Git repository by using Fabric Git integration
Assign the release lead the Member workspace role

Correct answer: A

Why: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Option review:

A: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

B: Build permission enables creation of content from the semantic model while keeping unrelated workspace items out of scope. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

C: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

D: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

E: Member supports creating, modifying, and sharing content while reserving full workspace administration for Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

Learning point: Save the solution as a Power BI Desktop project (.pbip)

Question 25

During a design review for Alpine Ski House’s executive reporting workspace, one requirement is non-negotiable: enable text-based review of Power BI project metadata in Git. Because the team wants the smallest administrative blast radius, what should the operations data team implement? The design decision will be reviewed by both data engineering and BI owners.

Publish and reuse a shared semantic model
Assign the developers the Contributor workspace role
Use the PBIP project format and commit the project folder
Apply the required sensitivity label to the report
Create and distribute a Power BI data source (.pbids) file

Correct answer: C

Why: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

Option review:

A: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

C: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

Learning point: Use the PBIP project format and commit the project folder

Question 26

The data governance group at Contoso is preparing the next release of its customer 360 model. They need to store a Power BI report and semantic model as source-control-friendly project files instead of one binary PBIX file; the team wants to keep governance centralized. Which choice most directly satisfies the requirement? Existing users should keep their current access.

Assign the auditors the Viewer workspace role
Grant Build permission on the semantic model rather than a workspace role
Apply the appropriate Microsoft Purview sensitivity label to the item
Use the XMLA endpoint to manage the semantic model programmatically
Save the solution as a Power BI Desktop project (.pbip)

Correct answer: E

Why: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Option review:

D: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

E: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Learning point: Save the solution as a Power BI Desktop project (.pbip)

Question 27

A production readiness review at Wingtip Toys found a gap in the sales analytics solution. The remediation must enable text-based review of Power BI project metadata in Git, and the approach should remain understandable to future maintainers. What is the most appropriate action? Existing users should keep their current access.

Assign the auditors the Viewer workspace role
Use the PBIP project format and commit the project folder
Connect to the workspace XMLA endpoint with read/write operations enabled
Connect the workspace to a supported Git repository by using Fabric Git integration
Share only that report and grant the required item permission

Correct answer: B

Why: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

Option review:

B: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

Learning point: Use the PBIP project format and commit the project folder

Question 28

For a new phase of the risk analytics environment, Proseware asks the finance analytics squad to store a Power BI report and semantic model as source-control-friendly project files instead of one binary PBIX file. The architecture decision record also states that the implementation should reduce operational overhead. Which approach should be selected? No unrelated workspace or model permissions should be changed.

Assign the platform owner the Admin workspace role
Create a deployment pipeline with separate lifecycle stages
Save the solution as a Power BI Desktop project (.pbip)
Create and distribute a Power BI data source (.pbids) file
Promote the item

Correct answer: C

Why: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Option review:

A: Admin is the workspace role intended for full workspace administration, including permissions and settings. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

B: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

C: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Learning point: Save the solution as a Power BI Desktop project (.pbip)

Question 29

Blue Yonder Airlines is standardizing how the service-operations warehouse is managed. The immediate goal is to enable text-based review of Power BI project metadata in Git. Given that the solution must remain maintainable as usage grows, which option should the analytics engineering team choose? No unrelated workspace or model permissions should be changed.

Define and assign row-level security roles for the semantic model
Use the PBIP project format and commit the project folder
Create a deployment pipeline with separate lifecycle stages
Create and distribute a Power BI data source (.pbids) file
Configure deployment rules for the target stage

Correct answer: B

Why: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

Option review:

B: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This directly matches the stated requirement.

C: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

E: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

Learning point: Use the PBIP project format and commit the project folder

Question 30

An internal audit of Fabrikam’s executive reporting workspace identifies this requirement: store a Power BI report and semantic model as source-control-friendly project files instead of one binary PBIX file. The operations data team also notes that the team wants the smallest administrative blast radius. What should they do? The team will validate the change first in a nonproduction environment.

Create a deployment pipeline with separate lifecycle stages
Apply the appropriate Microsoft Purview sensitivity label to the item
Save the solution as a Power BI Desktop project (.pbip)
Use Fabric lineage and impact analysis before making the change
Use the XMLA endpoint to manage the semantic model programmatically

Correct answer: C

Why: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Option review:

B: Sensitivity labels provide governance classification and can propagate through supported Power BI and Fabric workflows. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and manage a Power BI Desktop project (.pbip)’.

C: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This directly matches the stated requirement.

Learning point: Save the solution as a Power BI Desktop project (.pbip)

Question 31

The marketing semantic model at Litware is moving from proof of concept to production. Before rollout, the security analytics team must promote Fabric and Power BI content through development, test, and production stages with controlled comparisons, while ensuring that the team wants to keep governance centralized. Which action best meets both needs? Existing users should keep their current access.

Review downstream dependencies in the lineage or impact-analysis view
Use the PBIP project format and commit the project folder
Apply the appropriate Microsoft Purview sensitivity label to the item
Use Fabric lineage and impact analysis before making the change
Create a deployment pipeline with separate lifecycle stages

Correct answer: E

Why: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Option review:

A: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

B: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

E: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Learning point: Create a deployment pipeline with separate lifecycle stages

Question 32

Woodgrove Bank has a change request for the supply-chain lakehouse: change environment-specific connection values while deploying the same content between pipeline stages. The Fabric center of excellence wants a solution where the approach should remain understandable to future maintainers. Which implementation is most suitable? Existing users should keep their current access.

Configure deployment rules for the target stage
Grant Build permission on the semantic model rather than a workspace role
Connect to the workspace XMLA endpoint with read/write operations enabled
Use Fabric lineage and impact analysis before making the change
Assign the platform owner the Admin workspace role

Correct answer: A

Why: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Option review:

A: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

E: Admin is the workspace role intended for full workspace administration, including permissions and settings. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

Learning point: Configure deployment rules for the target stage

Question 33

A solution architect reviewing Coho Winery’s IoT telemetry solution asks the customer insights team to promote Fabric and Power BI content through development, test, and production stages with controlled comparisons. Since the implementation should reduce operational overhead, which recommendation is strongest? No unrelated workspace or model permissions should be changed.

Apply the appropriate Microsoft Purview sensitivity label to the item
Apply column-level security to the sensitive columns
Certify the semantic model
Grant Build permission on the semantic model rather than a workspace role
Create a deployment pipeline with separate lifecycle stages

Correct answer: E

Why: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Option review:

A: Sensitivity labels provide governance classification and can propagate through supported Power BI and Fabric workflows. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

C: Certification is the stronger endorsement used for content that has been reviewed and approved as authoritative. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

E: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Learning point: Create a deployment pipeline with separate lifecycle stages

Question 34

The next sprint for Adventure Works’s finance reporting platform includes a task to change environment-specific connection values while deploying the same content between pipeline stages. The acceptance criteria add that the solution must remain maintainable as usage grows. Which Fabric or Power BI action is appropriate? No unrelated workspace or model permissions should be changed.

Share only that report and grant the required item permission
Define and assign row-level security roles for the semantic model
Review downstream dependencies in the lineage or impact-analysis view
Grant Build permission on the semantic model rather than a workspace role
Configure deployment rules for the target stage

Correct answer: E

Why: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Option review:

A: Item-level sharing can grant access to a specific Fabric item without assigning a workspace role. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

B: RLS filters rows by user or role so consumers see only the permitted records. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

C: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

E: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Learning point: Configure deployment rules for the target stage

Question 35

Tailspin Toys is troubleshooting a design decision in the retail performance dashboard. The desired end state is to promote Fabric and Power BI content through development, test, and production stages with controlled comparisons; the team wants the smallest administrative blast radius. Which change should the BI platform team make? The team will validate the change first in a nonproduction environment.

Define and assign row-level security roles for the semantic model
Create a deployment pipeline with separate lifecycle stages
Use the item Manage permissions or sharing experience for that item
Create a Power BI template (.pbit) file
Assign the developers the Contributor workspace role

Correct answer: B

Why: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Option review:

B: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Learning point: Create a deployment pipeline with separate lifecycle stages

Question 36

For the marketing semantic model, Fourth Coffee has documented a business requirement to change environment-specific connection values while deploying the same content between pipeline stages. The security analytics team must meet it in a way where the team wants to keep governance centralized. What is the best choice? The team will validate the change first in a nonproduction environment.

Use the PBIP project format and commit the project folder
Configure deployment rules for the target stage
Create a Power BI template (.pbit) file
Use the XMLA endpoint to manage the semantic model programmatically
Save the solution as a Power BI Desktop project (.pbip)

Correct answer: B

Why: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Option review:

A: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

B: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

C: A PBIT captures reusable report and model definitions while omitting imported data. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

E: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

Learning point: Configure deployment rules for the target stage

Question 37

A governance review of Wide World Importers’s supply-chain lakehouse asks for evidence that the solution can promote Fabric and Power BI content through development, test, and production stages with controlled comparisons. Because the approach should remain understandable to future maintainers, which action should be approved? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Apply column-level security to the sensitive columns
Create a deployment pipeline with separate lifecycle stages
Use the item Manage permissions or sharing experience for that item
Grant Build permission on the semantic model rather than a workspace role
Save the solution as a Power BI Desktop project (.pbip)

Correct answer: B

Why: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Option review:

B: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Learning point: Create a deployment pipeline with separate lifecycle stages

Question 38

Before expanding the IoT telemetry solution, the customer insights team at Northwind Traders must change environment-specific connection values while deploying the same content between pipeline stages. The rollout plan says that the implementation should reduce operational overhead. Which option most directly addresses the requirement? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Assign the release lead the Member workspace role
Create a Power BI template (.pbit) file
Use Fabric lineage and impact analysis before making the change
Configure deployment rules for the target stage
Use the XMLA endpoint to manage the semantic model programmatically

Correct answer: D

Why: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Option review:

A: Member supports creating, modifying, and sharing content while reserving full workspace administration for Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

B: A PBIT captures reusable report and model definitions while omitting imported data. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

D: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Learning point: Configure deployment rules for the target stage

Question 39

Trey Research is redesigning its finance reporting platform. The retail insights team must promote Fabric and Power BI content through development, test, and production stages with controlled comparisons. In addition, the solution must remain maintainable as usage grows. Which action is the best fit? The design decision will be reviewed by both data engineering and BI owners.

Create a deployment pipeline with separate lifecycle stages
Grant Build permission on the semantic model rather than a workspace role
Configure object-level security for the protected table or column
Assign the platform owner the Admin workspace role
Use Fabric Git integration and map the development workspace to the appropriate repository branch

Correct answer: A

Why: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Option review:

A: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

C: OLS prevents users from discovering or querying protected model objects. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

D: Admin is the workspace role intended for full workspace administration, including permissions and settings. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

Learning point: Create a deployment pipeline with separate lifecycle stages

Question 40

During a design review for Alpine Ski House’s retail performance dashboard, one requirement is non-negotiable: change environment-specific connection values while deploying the same content between pipeline stages. Because the team wants the smallest administrative blast radius, what should the BI platform team implement? The design decision will be reviewed by both data engineering and BI owners.

Review downstream dependencies in the lineage or impact-analysis view
Share only that report and grant the required item permission
Define and assign row-level security roles for the semantic model
Assign the auditors the Viewer workspace role
Configure deployment rules for the target stage

Correct answer: E

Why: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Option review:

C: RLS filters rows by user or role so consumers see only the permitted records. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

E: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Learning point: Configure deployment rules for the target stage

Question 41

The security analytics team at Contoso is preparing the next release of its marketing semantic model. They need to promote Fabric and Power BI content through development, test, and production stages with controlled comparisons; the team wants to keep governance centralized. Which choice most directly satisfies the requirement? Existing users should keep their current access.

Connect to the workspace XMLA endpoint with read/write operations enabled
Use the PBIP project format and commit the project folder
Assign the developers the Contributor workspace role
Review downstream dependencies in the lineage or impact-analysis view
Create a deployment pipeline with separate lifecycle stages

Correct answer: E

Why: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Option review:

C: Contributor permits creation and modification of workspace content without the broader membership-management permissions of Member or Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

E: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Learning point: Create a deployment pipeline with separate lifecycle stages

Question 42

A production readiness review at Wingtip Toys found a gap in the supply-chain lakehouse. The remediation must change environment-specific connection values while deploying the same content between pipeline stages, and the approach should remain understandable to future maintainers. What is the most appropriate action? Existing users should keep their current access.

Review downstream dependencies in the lineage or impact-analysis view
Assign the developers the Contributor workspace role
Configure deployment rules for the target stage
Save the solution as a Power BI Desktop project (.pbip)
Apply column-level security to the sensitive columns

Correct answer: C

Why: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Option review:

C: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

D: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

E: Column-level security restricts access at the column boundary while preserving access to permitted data. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

Learning point: Configure deployment rules for the target stage

Question 43

For a new phase of the IoT telemetry solution, Proseware asks the customer insights team to promote Fabric and Power BI content through development, test, and production stages with controlled comparisons. The architecture decision record also states that the implementation should reduce operational overhead. Which approach should be selected? No unrelated workspace or model permissions should be changed.

Apply the appropriate Microsoft Purview sensitivity label to the item
Create a deployment pipeline with separate lifecycle stages
Use the item Manage permissions or sharing experience for that item
Use the XMLA endpoint to manage the semantic model programmatically
Assign the developers the Contributor workspace role

Correct answer: B

Why: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Option review:

B: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Learning point: Create a deployment pipeline with separate lifecycle stages

Question 44

Blue Yonder Airlines is standardizing how the finance reporting platform is managed. The immediate goal is to change environment-specific connection values while deploying the same content between pipeline stages. Given that the solution must remain maintainable as usage grows, which option should the retail insights team choose? No unrelated workspace or model permissions should be changed.

Grant Build permission on the semantic model rather than a workspace role
Configure deployment rules for the target stage
Review downstream dependencies in the lineage or impact-analysis view
Connect the workspace to a supported Git repository by using Fabric Git integration
Apply column-level security to the sensitive columns

Correct answer: B

Why: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Option review:

A: Build permission enables creation of content from the semantic model while keeping unrelated workspace items out of scope. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

B: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This directly matches the stated requirement.

Learning point: Configure deployment rules for the target stage

Question 45

An internal audit of Fabrikam’s retail performance dashboard identifies this requirement: promote Fabric and Power BI content through development, test, and production stages with controlled comparisons. The BI platform team also notes that the team wants the smallest administrative blast radius. What should they do? The team will validate the change first in a nonproduction environment.

Connect to the workspace XMLA endpoint with read/write operations enabled
Apply the required sensitivity label to the report
Promote the item
Apply column-level security to the sensitive columns
Create a deployment pipeline with separate lifecycle stages

Correct answer: E

Why: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Option review:

C: Promotion is appropriate for recommended content that has not gone through the formal certification process. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

D: Column-level security restricts access at the column boundary while preserving access to permitted data. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Create and configure deployment pipelines’.

E: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This directly matches the stated requirement.

Learning point: Create a deployment pipeline with separate lifecycle stages

Question 46

The customer 360 model at Litware is moving from proof of concept to production. Before rollout, the data governance group must identify downstream reports and models that could break before changing a warehouse table, while ensuring that the team wants to keep governance centralized. Which action best meets both needs? Existing users should keep their current access.

Assign the release lead the Member workspace role
Configure object-level security for the protected table or column
Save the solution as a Power BI Desktop project (.pbip)
Publish and reuse a shared semantic model
Use Fabric lineage and impact analysis before making the change

Correct answer: E

Why: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Option review:

B: OLS prevents users from discovering or querying protected model objects. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

C: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

D: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

E: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Learning point: Use Fabric lineage and impact analysis before making the change

Question 47

Woodgrove Bank has a change request for the sales analytics solution: determine which dependent items are affected by replacing a dataflow output schema. The enterprise reporting group wants a solution where the approach should remain understandable to future maintainers. Which implementation is most suitable? Existing users should keep their current access.

Assign the auditors the Viewer workspace role
Apply the appropriate Microsoft Purview sensitivity label to the item
Review downstream dependencies in the lineage or impact-analysis view
Publish and reuse a shared semantic model
Share only that report and grant the required item permission

Correct answer: C

Why: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

Option review:

B: Sensitivity labels provide governance classification and can propagate through supported Power BI and Fabric workflows. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

C: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

Learning point: Review downstream dependencies in the lineage or impact-analysis view

Question 48

A solution architect reviewing Coho Winery’s risk analytics environment asks the finance analytics squad to identify downstream reports and models that could break before changing a warehouse table. Since the implementation should reduce operational overhead, which recommendation is strongest? No unrelated workspace or model permissions should be changed.

Use Fabric lineage and impact analysis before making the change
Connect the workspace to a supported Git repository by using Fabric Git integration
Create a deployment pipeline with separate lifecycle stages
Configure deployment rules for the target stage
Assign the release lead the Member workspace role

Correct answer: A

Why: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Option review:

A: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

B: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

C: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

D: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

E: Member supports creating, modifying, and sharing content while reserving full workspace administration for Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

Learning point: Use Fabric lineage and impact analysis before making the change

Question 49

The next sprint for Adventure Works’s service-operations warehouse includes a task to determine which dependent items are affected by replacing a dataflow output schema. The acceptance criteria add that the solution must remain maintainable as usage grows. Which Fabric or Power BI action is appropriate? No unrelated workspace or model permissions should be changed.

Create a OneLake security role scoped to the required folders or tables
Assign the auditors the Viewer workspace role
Review downstream dependencies in the lineage or impact-analysis view
Promote the item
Use Fabric Git integration and map the development workspace to the appropriate repository branch

Correct answer: C

Why: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

Option review:

B: The Viewer role provides read access to workspace content without create, edit, or workspace-management rights. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

C: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

E: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

Learning point: Review downstream dependencies in the lineage or impact-analysis view

Question 50

Tailspin Toys is troubleshooting a design decision in the executive reporting workspace. The desired end state is to identify downstream reports and models that could break before changing a warehouse table; the team wants the smallest administrative blast radius. Which change should the operations data team make? The team will validate the change first in a nonproduction environment.

Configure deployment rules for the target stage
Use Fabric lineage and impact analysis before making the change
Configure object-level security for the protected table or column
Assign the developers the Contributor workspace role
Apply the required sensitivity label to the report

Correct answer: B

Why: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Option review:

A: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

B: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

D: Contributor permits creation and modification of workspace content without the broader membership-management permissions of Member or Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

Learning point: Use Fabric lineage and impact analysis before making the change

Question 51

For the customer 360 model, Fourth Coffee has documented a business requirement to determine which dependent items are affected by replacing a dataflow output schema. The data governance group must meet it in a way where the team wants to keep governance centralized. What is the best choice? The team will validate the change first in a nonproduction environment.

Assign the auditors the Viewer workspace role
Grant Build permission on the semantic model rather than a workspace role
Review downstream dependencies in the lineage or impact-analysis view
Apply the required sensitivity label to the report
Use Fabric Git integration and map the development workspace to the appropriate repository branch

Correct answer: C

Why: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

Option review:

B: Build permission enables creation of content from the semantic model while keeping unrelated workspace items out of scope. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

C: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

D: Sensitivity labels are the native mechanism for classifying protected content according to the information-protection policy. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

E: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

Learning point: Review downstream dependencies in the lineage or impact-analysis view

Question 52

A governance review of Wide World Importers’s sales analytics solution asks for evidence that the solution can identify downstream reports and models that could break before changing a warehouse table. Because the approach should remain understandable to future maintainers, which action should be approved? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Create a Power BI template (.pbit) file
Connect to the workspace XMLA endpoint with read/write operations enabled
Assign the auditors the Viewer workspace role
Use the item Manage permissions or sharing experience for that item
Use Fabric lineage and impact analysis before making the change

Correct answer: E

Why: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Option review:

A: A PBIT captures reusable report and model definitions while omitting imported data. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

B: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

C: The Viewer role provides read access to workspace content without create, edit, or workspace-management rights. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

E: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Learning point: Use Fabric lineage and impact analysis before making the change

Question 53

Before expanding the risk analytics environment, the finance analytics squad at Northwind Traders must determine which dependent items are affected by replacing a dataflow output schema. The rollout plan says that the implementation should reduce operational overhead. Which option most directly addresses the requirement? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Configure object-level security for the protected table or column
Use Fabric Git integration and map the development workspace to the appropriate repository branch
Share only that report and grant the required item permission
Use the PBIP project format and commit the project folder
Review downstream dependencies in the lineage or impact-analysis view

Correct answer: E

Why: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

Option review:

A: OLS prevents users from discovering or querying protected model objects. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

B: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

C: Item-level sharing can grant access to a specific Fabric item without assigning a workspace role. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

D: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

E: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

Learning point: Review downstream dependencies in the lineage or impact-analysis view

Question 54

Trey Research is redesigning its service-operations warehouse. The analytics engineering team must identify downstream reports and models that could break before changing a warehouse table. In addition, the solution must remain maintainable as usage grows. Which action is the best fit? The design decision will be reviewed by both data engineering and BI owners.

Certify the semantic model
Grant Build permission on the semantic model rather than a workspace role
Use Fabric lineage and impact analysis before making the change
Assign the auditors the Viewer workspace role
Apply the required sensitivity label to the report

Correct answer: C

Why: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Option review:

A: Certification is the stronger endorsement used for content that has been reviewed and approved as authoritative. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

B: Build permission enables creation of content from the semantic model while keeping unrelated workspace items out of scope. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

C: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Learning point: Use Fabric lineage and impact analysis before making the change

Question 55

During a design review for Alpine Ski House’s executive reporting workspace, one requirement is non-negotiable: determine which dependent items are affected by replacing a dataflow output schema. Because the team wants the smallest administrative blast radius, what should the operations data team implement? The design decision will be reviewed by both data engineering and BI owners.

Review downstream dependencies in the lineage or impact-analysis view
Assign the auditors the Viewer workspace role
Certify the semantic model
Use the item Manage permissions or sharing experience for that item
Create a Power BI template (.pbit) file

Correct answer: A

Why: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

Option review:

A: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

B: The Viewer role provides read access to workspace content without create, edit, or workspace-management rights. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

Learning point: Review downstream dependencies in the lineage or impact-analysis view

Question 56

The data governance group at Contoso is preparing the next release of its customer 360 model. They need to identify downstream reports and models that could break before changing a warehouse table; the team wants to keep governance centralized. Which choice most directly satisfies the requirement? Existing users should keep their current access.

Save the solution as a Power BI Desktop project (.pbip)
Use the PBIP project format and commit the project folder
Connect to the workspace XMLA endpoint with read/write operations enabled
Configure object-level security for the protected table or column
Use Fabric lineage and impact analysis before making the change

Correct answer: E

Why: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Option review:

D: OLS prevents users from discovering or querying protected model objects. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

E: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Learning point: Use Fabric lineage and impact analysis before making the change

Question 57

A production readiness review at Wingtip Toys found a gap in the sales analytics solution. The remediation must determine which dependent items are affected by replacing a dataflow output schema, and the approach should remain understandable to future maintainers. What is the most appropriate action? Existing users should keep their current access.

Create a OneLake security role scoped to the required folders or tables
Assign the auditors the Viewer workspace role
Certify the semantic model
Connect to the workspace XMLA endpoint with read/write operations enabled
Review downstream dependencies in the lineage or impact-analysis view

Correct answer: E

Why: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

Option review:

B: The Viewer role provides read access to workspace content without create, edit, or workspace-management rights. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

D: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

E: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

Learning point: Review downstream dependencies in the lineage or impact-analysis view

Question 58

For a new phase of the risk analytics environment, Proseware asks the finance analytics squad to identify downstream reports and models that could break before changing a warehouse table. The architecture decision record also states that the implementation should reduce operational overhead. Which approach should be selected? No unrelated workspace or model permissions should be changed.

Use Fabric lineage and impact analysis before making the change
Apply the appropriate Microsoft Purview sensitivity label to the item
Use Fabric Git integration and map the development workspace to the appropriate repository branch
Create a Power BI template (.pbit) file
Create and distribute a Power BI data source (.pbids) file

Correct answer: A

Why: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Option review:

A: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

B: Sensitivity labels provide governance classification and can propagate through supported Power BI and Fabric workflows. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

C: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

Learning point: Use Fabric lineage and impact analysis before making the change

Question 59

Blue Yonder Airlines is standardizing how the service-operations warehouse is managed. The immediate goal is to determine which dependent items are affected by replacing a dataflow output schema. Given that the solution must remain maintainable as usage grows, which option should the analytics engineering team choose? No unrelated workspace or model permissions should be changed.

Review downstream dependencies in the lineage or impact-analysis view
Assign the auditors the Viewer workspace role
Apply the required sensitivity label to the report
Connect to the workspace XMLA endpoint with read/write operations enabled
Define and assign row-level security roles for the semantic model

Correct answer: A

Why: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

Option review:

A: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This directly matches the stated requirement.

B: The Viewer role provides read access to workspace content without create, edit, or workspace-management rights. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

C: Sensitivity labels are the native mechanism for classifying protected content according to the information-protection policy. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

E: RLS filters rows by user or role so consumers see only the permitted records. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’.

Learning point: Review downstream dependencies in the lineage or impact-analysis view

Question 60

An internal audit of Fabrikam’s executive reporting workspace identifies this requirement: identify downstream reports and models that could break before changing a warehouse table. The operations data team also notes that the team wants the smallest administrative blast radius. What should they do? The team will validate the change first in a nonproduction environment.

Use the PBIP project format and commit the project folder
Define and assign row-level security roles for the semantic model
Assign the auditors the Viewer workspace role
Connect to the workspace XMLA endpoint with read/write operations enabled
Use Fabric lineage and impact analysis before making the change

Correct answer: E

Why: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Option review:

E: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This directly matches the stated requirement.

Learning point: Use Fabric lineage and impact analysis before making the change

Question 61

The marketing semantic model at Litware is moving from proof of concept to production. Before rollout, the security analytics team must automate semantic-model metadata deployment by using an external tabular-model tool, while ensuring that the team wants to keep governance centralized. Which action best meets both needs? Existing users should keep their current access.

Configure deployment rules for the target stage
Connect to the workspace XMLA endpoint with read/write operations enabled
Review downstream dependencies in the lineage or impact-analysis view
Save the solution as a Power BI Desktop project (.pbip)
Assign the release lead the Member workspace role

Correct answer: B

Why: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

Option review:

A: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

B: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

E: Member supports creating, modifying, and sharing content while reserving full workspace administration for Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Connect to the workspace XMLA endpoint with read/write operations enabled

Question 62

Woodgrove Bank has a change request for the supply-chain lakehouse: perform scripted model changes that are not practical through the report authoring interface. The Fabric center of excellence wants a solution where the approach should remain understandable to future maintainers. Which implementation is most suitable? Existing users should keep their current access.

Assign the platform owner the Admin workspace role
Publish and reuse a shared semantic model
Use the XMLA endpoint to manage the semantic model programmatically
Assign the developers the Contributor workspace role
Create and distribute a Power BI data source (.pbids) file

Correct answer: C

Why: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

Option review:

A: Admin is the workspace role intended for full workspace administration, including permissions and settings. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

B: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

C: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

D: Contributor permits creation and modification of workspace content without the broader membership-management permissions of Member or Admin. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Use the XMLA endpoint to manage the semantic model programmatically

Question 63

A solution architect reviewing Coho Winery’s IoT telemetry solution asks the customer insights team to automate semantic-model metadata deployment by using an external tabular-model tool. Since the implementation should reduce operational overhead, which recommendation is strongest? No unrelated workspace or model permissions should be changed.

Review downstream dependencies in the lineage or impact-analysis view
Connect to the workspace XMLA endpoint with read/write operations enabled
Create a OneLake security role scoped to the required folders or tables
Assign the release lead the Member workspace role
Create a deployment pipeline with separate lifecycle stages

Correct answer: B

Why: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

Option review:

B: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

E: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Connect to the workspace XMLA endpoint with read/write operations enabled

Question 64

The next sprint for Adventure Works’s finance reporting platform includes a task to perform scripted model changes that are not practical through the report authoring interface. The acceptance criteria add that the solution must remain maintainable as usage grows. Which Fabric or Power BI action is appropriate? No unrelated workspace or model permissions should be changed.

Apply the required sensitivity label to the report
Use the XMLA endpoint to manage the semantic model programmatically
Save the solution as a Power BI Desktop project (.pbip)
Define and assign row-level security roles for the semantic model
Connect the workspace to a supported Git repository by using Fabric Git integration

Correct answer: B

Why: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

Option review:

A: Sensitivity labels are the native mechanism for classifying protected content according to the information-protection policy. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

B: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

C: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

E: Fabric Git integration synchronizes supported workspace item definitions with source control for branching, review, and history. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Use the XMLA endpoint to manage the semantic model programmatically

Question 65

Tailspin Toys is troubleshooting a design decision in the retail performance dashboard. The desired end state is to automate semantic-model metadata deployment by using an external tabular-model tool; the team wants the smallest administrative blast radius. Which change should the BI platform team make? The team will validate the change first in a nonproduction environment.

Apply the appropriate Microsoft Purview sensitivity label to the item
Use the item Manage permissions or sharing experience for that item
Connect to the workspace XMLA endpoint with read/write operations enabled
Create a Power BI template (.pbit) file
Create and distribute a Power BI data source (.pbids) file

Correct answer: C

Why: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

Option review:

C: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

Learning point: Connect to the workspace XMLA endpoint with read/write operations enabled

Question 66

For the marketing semantic model, Fourth Coffee has documented a business requirement to perform scripted model changes that are not practical through the report authoring interface. The security analytics team must meet it in a way where the team wants to keep governance centralized. What is the best choice? The team will validate the change first in a nonproduction environment.

Use the XMLA endpoint to manage the semantic model programmatically
Apply column-level security to the sensitive columns
Create and distribute a Power BI data source (.pbids) file
Review downstream dependencies in the lineage or impact-analysis view
Connect the workspace to a supported Git repository by using Fabric Git integration

Correct answer: A

Why: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

Option review:

A: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

C: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Use the XMLA endpoint to manage the semantic model programmatically

Question 67

A governance review of Wide World Importers’s supply-chain lakehouse asks for evidence that the solution can automate semantic-model metadata deployment by using an external tabular-model tool. Because the approach should remain understandable to future maintainers, which action should be approved? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Publish and reuse a shared semantic model
Use Fabric lineage and impact analysis before making the change
Configure deployment rules for the target stage
Connect to the workspace XMLA endpoint with read/write operations enabled
Apply the appropriate Microsoft Purview sensitivity label to the item

Correct answer: D

Why: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

Option review:

A: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

B: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

C: Deployment rules let selected settings, such as data-source or parameter values, vary by stage without changing the source artifact. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

D: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

E: Sensitivity labels provide governance classification and can propagate through supported Power BI and Fabric workflows. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Connect to the workspace XMLA endpoint with read/write operations enabled

Question 68

Before expanding the IoT telemetry solution, the customer insights team at Northwind Traders must perform scripted model changes that are not practical through the report authoring interface. The rollout plan says that the implementation should reduce operational overhead. Which option most directly addresses the requirement? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Share only that report and grant the required item permission
Use Fabric Git integration and map the development workspace to the appropriate repository branch
Create a Power BI template (.pbit) file
Use the XMLA endpoint to manage the semantic model programmatically
Review downstream dependencies in the lineage or impact-analysis view

Correct answer: D

Why: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

Option review:

B: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

D: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

E: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Use the XMLA endpoint to manage the semantic model programmatically

Question 69

Trey Research is redesigning its finance reporting platform. The retail insights team must automate semantic-model metadata deployment by using an external tabular-model tool. In addition, the solution must remain maintainable as usage grows. Which action is the best fit? The design decision will be reviewed by both data engineering and BI owners.

Promote the item
Connect to the workspace XMLA endpoint with read/write operations enabled
Create a OneLake security role scoped to the required folders or tables
Assign the auditors the Viewer workspace role
Use Fabric Git integration and map the development workspace to the appropriate repository branch

Correct answer: B

Why: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

Option review:

A: Promotion is appropriate for recommended content that has not gone through the formal certification process. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

B: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

E: Workspace-to-branch integration provides source-controlled collaboration for supported Fabric items. This can be valid for ‘Configure version control for a workspace’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Connect to the workspace XMLA endpoint with read/write operations enabled

Question 70

During a design review for Alpine Ski House’s retail performance dashboard, one requirement is non-negotiable: perform scripted model changes that are not practical through the report authoring interface. Because the team wants the smallest administrative blast radius, what should the BI platform team implement? The design decision will be reviewed by both data engineering and BI owners.

Create a Power BI template (.pbit) file
Use Fabric lineage and impact analysis before making the change
Apply the required sensitivity label to the report
Use the XMLA endpoint to manage the semantic model programmatically
Create and distribute a Power BI data source (.pbids) file

Correct answer: D

Why: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

Option review:

A: A PBIT captures reusable report and model definitions while omitting imported data. This can be valid for ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

C: Sensitivity labels are the native mechanism for classifying protected content according to the information-protection policy. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

D: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

Learning point: Use the XMLA endpoint to manage the semantic model programmatically

Question 71

The security analytics team at Contoso is preparing the next release of its marketing semantic model. They need to automate semantic-model metadata deployment by using an external tabular-model tool; the team wants to keep governance centralized. Which choice most directly satisfies the requirement? Existing users should keep their current access.

Use the item Manage permissions or sharing experience for that item
Assign the developers the Contributor workspace role
Configure deployment rules for the target stage
Connect to the workspace XMLA endpoint with read/write operations enabled
Use Fabric lineage and impact analysis before making the change

Correct answer: D

Why: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

Option review:

A: Item permissions are scoped to an individual item and are appropriate when workspace-wide access is unnecessary. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

D: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

E: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Connect to the workspace XMLA endpoint with read/write operations enabled

Question 72

A production readiness review at Wingtip Toys found a gap in the supply-chain lakehouse. The remediation must perform scripted model changes that are not practical through the report authoring interface, and the approach should remain understandable to future maintainers. What is the most appropriate action? Existing users should keep their current access.

Assign the auditors the Viewer workspace role
Use the XMLA endpoint to manage the semantic model programmatically
Assign the platform owner the Admin workspace role
Promote the item
Save the solution as a Power BI Desktop project (.pbip)

Correct answer: B

Why: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

Option review:

B: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

C: Admin is the workspace role intended for full workspace administration, including permissions and settings. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Use the XMLA endpoint to manage the semantic model programmatically

Question 73

For a new phase of the IoT telemetry solution, Proseware asks the customer insights team to automate semantic-model metadata deployment by using an external tabular-model tool. The architecture decision record also states that the implementation should reduce operational overhead. Which approach should be selected? No unrelated workspace or model permissions should be changed.

Create a deployment pipeline with separate lifecycle stages
Use the item Manage permissions or sharing experience for that item
Assign the auditors the Viewer workspace role
Save the solution as a Power BI Desktop project (.pbip)
Connect to the workspace XMLA endpoint with read/write operations enabled

Correct answer: E

Why: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

Option review:

C: The Viewer role provides read access to workspace content without create, edit, or workspace-management rights. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

E: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

Learning point: Connect to the workspace XMLA endpoint with read/write operations enabled

Question 74

Blue Yonder Airlines is standardizing how the finance reporting platform is managed. The immediate goal is to perform scripted model changes that are not practical through the report authoring interface. Given that the solution must remain maintainable as usage grows, which option should the retail insights team choose? No unrelated workspace or model permissions should be changed.

Use Fabric lineage and impact analysis before making the change
Certify the semantic model
Use the XMLA endpoint to manage the semantic model programmatically
Share only that report and grant the required item permission
Create and distribute a Power BI data source (.pbids) file

Correct answer: C

Why: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

Option review:

A: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

C: XMLA provides programmatic access to tabular semantic-model metadata for advanced lifecycle operations. This directly matches the stated requirement.

D: Item-level sharing can grant access to a specific Fabric item without assigning a workspace role. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Use the XMLA endpoint to manage the semantic model programmatically

Question 75

An internal audit of Fabrikam’s retail performance dashboard identifies this requirement: automate semantic-model metadata deployment by using an external tabular-model tool. The BI platform team also notes that the team wants the smallest administrative blast radius. What should they do? The team will validate the change first in a nonproduction environment.

Assign the platform owner the Admin workspace role
Connect to the workspace XMLA endpoint with read/write operations enabled
Create a Power BI template (.pbit) file
Define and assign row-level security roles for the semantic model
Use the PBIP project format and commit the project folder

Correct answer: B

Why: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

Option review:

A: Admin is the workspace role intended for full workspace administration, including permissions and settings. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

B: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This directly matches the stated requirement.

E: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Deploy and manage semantic models by using the XMLA endpoint’.

Learning point: Connect to the workspace XMLA endpoint with read/write operations enabled

Question 76

The customer 360 model at Litware is moving from proof of concept to production. Before rollout, the data governance group must distribute a reusable report layout and model structure without packaging the source data, while ensuring that the team wants to keep governance centralized. Which action best meets both needs? Existing users should keep their current access.

Certify the semantic model
Connect to the workspace XMLA endpoint with read/write operations enabled
Use the item Manage permissions or sharing experience for that item
Create a Power BI template (.pbit) file
Review downstream dependencies in the lineage or impact-analysis view

Correct answer: D

Why: A PBIT captures reusable report and model definitions while omitting imported data. This directly matches the stated requirement.

Option review:

A: Certification is the stronger endorsement used for content that has been reviewed and approved as authoritative. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

B: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

D: A PBIT captures reusable report and model definitions while omitting imported data. This directly matches the stated requirement.

E: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

Learning point: Create a Power BI template (.pbit) file

Question 77

Woodgrove Bank has a change request for the sales analytics solution: give report authors a reusable file that points them to an approved Power BI data source connection. The enterprise reporting group wants a solution where the approach should remain understandable to future maintainers. Which implementation is most suitable? Existing users should keep their current access.

Create a deployment pipeline with separate lifecycle stages
Create and distribute a Power BI data source (.pbids) file
Assign the platform owner the Admin workspace role
Use Fabric lineage and impact analysis before making the change
Assign the release lead the Member workspace role

Correct answer: B

Why: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This directly matches the stated requirement.

Option review:

B: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This directly matches the stated requirement.

C: Admin is the workspace role intended for full workspace administration, including permissions and settings. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

Learning point: Create and distribute a Power BI data source (.pbids) file

Question 78

A solution architect reviewing Coho Winery’s risk analytics environment asks the finance analytics squad to ensure many reports reuse one centrally governed model instead of duplicating measures in separate files. Since the implementation should reduce operational overhead, which recommendation is strongest? Existing users should keep their current access.

Review downstream dependencies in the lineage or impact-analysis view
Connect to the workspace XMLA endpoint with read/write operations enabled
Apply column-level security to the sensitive columns
Certify the semantic model
Publish and reuse a shared semantic model

Correct answer: E

Why: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This directly matches the stated requirement.

Option review:

B: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

D: Certification is the stronger endorsement used for content that has been reviewed and approved as authoritative. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

E: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This directly matches the stated requirement.

Learning point: Publish and reuse a shared semantic model

Question 79

The next sprint for Adventure Works’s service-operations warehouse includes a task to distribute a reusable report layout and model structure without packaging the source data. The acceptance criteria add that the solution must remain maintainable as usage grows. Which Fabric or Power BI action is appropriate? No unrelated workspace or model permissions should be changed.

Create a OneLake security role scoped to the required folders or tables
Apply column-level security to the sensitive columns
Create a deployment pipeline with separate lifecycle stages
Create a Power BI template (.pbit) file
Review downstream dependencies in the lineage or impact-analysis view

Correct answer: D

Why: A PBIT captures reusable report and model definitions while omitting imported data. This directly matches the stated requirement.

Option review:

D: A PBIT captures reusable report and model definitions while omitting imported data. This directly matches the stated requirement.

E: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

Learning point: Create a Power BI template (.pbit) file

Question 80

Tailspin Toys is troubleshooting a design decision in the executive reporting workspace. The desired end state is to give report authors a reusable file that points them to an approved Power BI data source connection; the team wants the smallest administrative blast radius. Which change should the operations data team make? No unrelated workspace or model permissions should be changed.

Create and distribute a Power BI data source (.pbids) file
Share only that report and grant the required item permission
Save the solution as a Power BI Desktop project (.pbip)
Apply the appropriate Microsoft Purview sensitivity label to the item
Assign the platform owner the Admin workspace role

Correct answer: A

Why: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This directly matches the stated requirement.

Option review:

A: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This directly matches the stated requirement.

C: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

Learning point: Create and distribute a Power BI data source (.pbids) file

Question 81

For the customer 360 model, Fourth Coffee has documented a business requirement to ensure many reports reuse one centrally governed model instead of duplicating measures in separate files. The data governance group must meet it in a way where the team wants to keep governance centralized. What is the best choice? No unrelated workspace or model permissions should be changed.

Promote the item
Publish and reuse a shared semantic model
Assign the developers the Contributor workspace role
Apply the required sensitivity label to the report
Use the item Manage permissions or sharing experience for that item

Correct answer: B

Why: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This directly matches the stated requirement.

Option review:

A: Promotion is appropriate for recommended content that has not gone through the formal certification process. This can be valid for ‘Endorse items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

B: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This directly matches the stated requirement.

Learning point: Publish and reuse a shared semantic model

Question 82

A governance review of Wide World Importers’s sales analytics solution asks for evidence that the solution can distribute a reusable report layout and model structure without packaging the source data. Because the approach should remain understandable to future maintainers, which action should be approved? The team will validate the change first in a nonproduction environment.

Apply the required sensitivity label to the report
Review downstream dependencies in the lineage or impact-analysis view
Share only that report and grant the required item permission
Create a Power BI template (.pbit) file
Define and assign row-level security roles for the semantic model

Correct answer: D

Why: A PBIT captures reusable report and model definitions while omitting imported data. This directly matches the stated requirement.

Option review:

A: Sensitivity labels are the native mechanism for classifying protected content according to the information-protection policy. This can be valid for ‘Apply sensitivity labels to items’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

C: Item-level sharing can grant access to a specific Fabric item without assigning a workspace role. This can be valid for ‘Implement item-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

D: A PBIT captures reusable report and model definitions while omitting imported data. This directly matches the stated requirement.

E: RLS filters rows by user or role so consumers see only the permitted records. This can be valid for ‘Implement row-level, column-level, object-level, and file-level access control’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

Learning point: Create a Power BI template (.pbit) file

Question 83

Before expanding the risk analytics environment, the finance analytics squad at Northwind Traders must give report authors a reusable file that points them to an approved Power BI data source connection. The rollout plan says that the implementation should reduce operational overhead. Which option most directly addresses the requirement? The team will validate the change first in a nonproduction environment.

Assign the developers the Contributor workspace role
Save the solution as a Power BI Desktop project (.pbip)
Create and distribute a Power BI data source (.pbids) file
Assign the release lead the Member workspace role
Review downstream dependencies in the lineage or impact-analysis view

Correct answer: C

Why: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This directly matches the stated requirement.

Option review:

B: PBIP stores report and semantic-model definitions as project files that work better with source control and developer workflows. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

C: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This directly matches the stated requirement.

E: Dependency analysis exposes which artifacts consume the changed object and therefore require validation. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

Learning point: Create and distribute a Power BI data source (.pbids) file

Question 84

Trey Research is redesigning its service-operations warehouse. The analytics engineering team must ensure many reports reuse one centrally governed model instead of duplicating measures in separate files. In addition, the solution must remain maintainable as usage grows. Which action is the best fit? The team will validate the change first in a nonproduction environment.

Save the solution as a Power BI Desktop project (.pbip)
Define and assign row-level security roles for the semantic model
Connect the workspace to a supported Git repository by using Fabric Git integration
Create a deployment pipeline with separate lifecycle stages
Publish and reuse a shared semantic model

Correct answer: E

Why: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This directly matches the stated requirement.

Option review:

D: Deployment pipelines support staged promotion, comparison, and controlled deployment of supported content. This can be valid for ‘Create and configure deployment pipelines’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

E: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This directly matches the stated requirement.

Learning point: Publish and reuse a shared semantic model

Question 85

During a design review for Alpine Ski House’s executive reporting workspace, one requirement is non-negotiable: distribute a reusable report layout and model structure without packaging the source data. Because the team wants the smallest administrative blast radius, what should the operations data team implement? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Create a Power BI template (.pbit) file
Promote the item
Use the item Manage permissions or sharing experience for that item
Certify the semantic model
Apply the required sensitivity label to the report

Correct answer: A

Why: A PBIT captures reusable report and model definitions while omitting imported data. This directly matches the stated requirement.

Option review:

A: A PBIT captures reusable report and model definitions while omitting imported data. This directly matches the stated requirement.

Learning point: Create a Power BI template (.pbit) file

Question 86

The data governance group at Contoso is preparing the next release of its customer 360 model. They need to give report authors a reusable file that points them to an approved Power BI data source connection; the team wants to keep governance centralized. Which choice most directly satisfies the requirement? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Create a OneLake security role scoped to the required folders or tables
Create a deployment pipeline with separate lifecycle stages
Create and distribute a Power BI data source (.pbids) file
Use Fabric lineage and impact analysis before making the change
Assign the auditors the Viewer workspace role

Correct answer: C

Why: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This directly matches the stated requirement.

Option review:

C: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This directly matches the stated requirement.

E: The Viewer role provides read access to workspace content without create, edit, or workspace-management rights. This can be valid for ‘Implement workspace-level access controls’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

Learning point: Create and distribute a Power BI data source (.pbids) file

Question 87

A production readiness review at Wingtip Toys found a gap in the sales analytics solution. The remediation must ensure many reports reuse one centrally governed model instead of duplicating measures in separate files, and the approach should remain understandable to future maintainers. What is the most appropriate action? The solution must work with the current Fabric architecture rather than a parallel custom platform.

Define and assign row-level security roles for the semantic model
Create a deployment pipeline with separate lifecycle stages
Promote the item
Connect to the workspace XMLA endpoint with read/write operations enabled
Publish and reuse a shared semantic model

Correct answer: E

Why: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This directly matches the stated requirement.

Option review:

D: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

E: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This directly matches the stated requirement.

Learning point: Publish and reuse a shared semantic model

Question 88

For a new phase of the risk analytics environment, Proseware asks the finance analytics squad to distribute a reusable report layout and model structure without packaging the source data. The architecture decision record also states that the implementation should reduce operational overhead. Which approach should be selected? The design decision will be reviewed by both data engineering and BI owners.

Assign the platform owner the Admin workspace role
Connect to the workspace XMLA endpoint with read/write operations enabled
Create a Power BI template (.pbit) file
Assign the release lead the Member workspace role
Use the PBIP project format and commit the project folder

Correct answer: C

Why: A PBIT captures reusable report and model definitions while omitting imported data. This directly matches the stated requirement.

Option review:

B: The XMLA endpoint exposes semantic-model metadata to supported external tools and automation for management and deployment. This can be valid for ‘Deploy and manage semantic models by using the XMLA endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

C: A PBIT captures reusable report and model definitions while omitting imported data. This directly matches the stated requirement.

E: PBIP externalizes project definitions so changes can be reviewed and versioned using standard source-control practices. This can be valid for ‘Create and manage a Power BI Desktop project (.pbip)’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

Learning point: Create a Power BI template (.pbit) file

Question 89

Blue Yonder Airlines is standardizing how the service-operations warehouse is managed. The immediate goal is to give report authors a reusable file that points them to an approved Power BI data source connection. Given that the solution must remain maintainable as usage grows, which option should the analytics engineering team choose? The design decision will be reviewed by both data engineering and BI owners.

Share only that report and grant the required item permission
Apply the required sensitivity label to the report
Use Fabric lineage and impact analysis before making the change
Save the solution as a Power BI Desktop project (.pbip)
Create and distribute a Power BI data source (.pbids) file

Correct answer: E

Why: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This directly matches the stated requirement.

Option review:

E: A PBIDS file provides reusable connection information that helps authors connect to an approved data source. This directly matches the stated requirement.

Learning point: Create and distribute a Power BI data source (.pbids) file

Question 90

An internal audit of Fabrikam’s executive reporting workspace identifies this requirement: ensure many reports reuse one centrally governed model instead of duplicating measures in separate files. The operations data team also notes that the team wants the smallest administrative blast radius. What should they do? The design decision will be reviewed by both data engineering and BI owners.

Configure deployment rules for the target stage
Use the XMLA endpoint to manage the semantic model programmatically
Publish and reuse a shared semantic model
Assign the platform owner the Admin workspace role
Use Fabric lineage and impact analysis before making the change

Correct answer: C

Why: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This directly matches the stated requirement.

Option review:

C: A shared semantic model centralizes governed measures, relationships, and business logic for reuse across reports. This directly matches the stated requirement.

E: Lineage and impact analysis reveal downstream dependencies so changes can be evaluated before deployment. This can be valid for ‘Perform impact analysis of downstream dependencies from lakehouses, warehouses, dataflows, and semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Create and update reusable assets, including Power BI template (.pbit) files, Power BI data source (.pbids) files, and shared semantic models’.

Learning point: Publish and reuse a shared semantic model