Exam DP-600 All QuestionsBrowse all questions from this exam
Go to Exam
Question 24

You plan to deploy Microsoft Power BI items by using Fabric deployment pipelines. You have a deployment pipeline that contains three stages named Development, Test, and Production. A workspace is assigned to each stage.

You need to provide Power BI developers with access to the pipeline. The solution must meet the following requirements:

Ensure that the developers can deploy items to the workspaces for Development and Test.

Prevent the developers from deploying items to the workspace for Production.

Follow the principle of least privilege.

Which three levels of access should you assign to the developers? Each correct answer presents part of the solution.

NOTE: Each correct answer is worth one point.

    Correct Answer: B, D, E

    To meet the requirements, you should assign Admin access to the deployment pipeline to allow developers to manage the process and promote content through the stages. Contributor access should be provided to the Development and Test workspaces to enable developers to deploy items within these environments. Viewer access to the Production workspace ensures that developers cannot deploy items to the production environment, adhering to the principle of least privilege while still allowing them to view the production content.

Discussion
sraakesh95Options: BDE

As pointed out by XiltroX, B - Admin access is provided to the developers for the developers to manage the deployent process across the various stages (in this case Dev and Test). This is a basic necessary. D - To restrict the access on the Production workspace, provide an overriding Viewer access which lets the developers only view the Production environment and not make any changes. E - This is to provide the developers with the permissions to develop, edit and update the Dev and Test pipelines.

XiltroXOptions: BDE

I think the answer should be BDE. If you have contributer access to the workspace, then you don't need to assign an additional viewer access (C) to the developers. One of the requirements is to grant access to the pipeline and the only option that fulfills that is (B). D and E fulfill the rest of the requirements in the question.

estrelle2008Options: CDE

I think build permission to the production semantic model, conflicts with requirement that any changes to the Production workspace should be prevented. If question really requires 3 answers, I think both Viewer access (C) and Contributor access (E) can coexist effectively for the Development and Test workspaces.

thussOptions: BDE

I get a feeling the "trick" is making you think that B would allow publishing on Prod, but I think if you don't give them access to the workspace, they can indeed have admin rights on the build pipeline but not deploy on Prod? So BDE would be my guess. Also B is the only option granting access to the pipeline at all, and D and E are a must.

282b85dOptions: BDE

E. Contributor access to the Development and Test workspaces: This allows developers to deploy and manage content in the Development and Test workspaces, meeting the requirement to allow deployments in these stages. D. Viewer access to the Production workspace: This provides developers with read-only access to the Production workspace, ensuring they can view content but cannot deploy or make changes, which aligns with the requirement to prevent deployments to Production. B. Admin access to the deployment pipeline: This allows developers to manage the deployment pipeline itself, including deploying items to the Development and Test stages but not to the Production stage. This ensures they can oversee the deployment process without overstepping into the Production environment.

David_WebbOptions: BDE

Admin access is needed in the development workspace for pipeline.

stilferxOptions: BDE

IMHO, B->D->E B. Admin access to the deployment pipeline - to be able to run D. Viewer access to the Production workspace - to not be able to run Prod E. Contributor access to the Development and Test workspaces - to be able to run Dev/Test

Mhmod48

I like your answers

72bd3bc

I see that contributors aren't able to deploy. Only members Workspace contributor (and pipeline admin) Consume content​ Compare stages View semantic models Unassign a workspace from a stage Workspace member (and pipeline admin) View workspace content​ Compare stages Deploy items (must be a member or admin of both source and target workspaces) Update semantic models Unassign a workspace from a stage Configure semantic model rules (you must be the semantic model owner) https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process#permissions-table

PazaBIandDataOptions: BD

Member or Admin rights on the workspace level are required to deploy datasets so E doesn't match the requirements. https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process#permissions-table

NefirsOptions: BDE

my reasoning: A: nope since they should not be able to build things there B: not sure C: nope since this would prevent them from deploying stuff there D: yes because of least privilege E: yes so they can build/deploy stuff there F: nope. Too much permissions. --> so this leaves option B as the third answer.

STH

yes, admin permission on the pipeline is required to manage the deployments between workspaces so BDE confirmed

MomoanwarOptions: ADE

I think its correct if developper can read data on production. Dont need b and c with E F is too high

AhmadpbiOptions: ADE

A D E because: In Power BI, having Viewer access to a workspace does not automatically grant Build permission for a semantic model within that workspace. The Viewer role allows a user to view and interact with items in the workspace, but it does not include the ability to create new content or edit existing content. To have Build permission, a user must be explicitly granted that permission, which allows them to build new content from the semantic model, access reports that use composite models on Power BI Pro workspaces, and pull data into Analyze in Excel, among other capabilities. This permission can be given by the workspace Admin or Member who has the authority to manage semantic model permissions

bmc15Options: BDE

B: It's admin or nothing for pipeline access. D: Viewer, so they cannot create it in production. E: You need Contributor on the workspaces you want to deploy and create.

SilvanoRamalhoOptions: BDE

Respostas BDE

Jons123sonOptions: BDE

Was in exam. Scored 95% Chose BDE Answers swtichted Contributor for Member role

GeraldOptions: BDE

I agree with BDE

72bd3bcOptions: CDE

To deploy from one stage to another in the pipeline, you must be a pipeline admin, and either a member or an admin of the workspaces assigned to the stages involved. For example, a pipeline admin that isn't assigned a workspace role, can view the pipeline and share it with others. However, this user can't view the content of the workspace in the pipeline, or in the service, and can't perform deployments. https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process#permissions/?azure-portal=true From task: Prevent the developers from deploying to the production. So B is not correct, we can't give pipeline admin access?

72bd3bc

we can and wee need viewer access to the Production, so that developers can't deploy at this stage. Without admin access they can't deploy from dev to test stages.

a_51Options: BDE

I think it is B,D,E, but the admin title throws you off as it can deploy items and is a key to what it asks. Build permission allows to create new content in the workspace, so not sure that is right, answer A. https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process?WT.mc_id=access_pane#permissions