Exam DP-600 topic 1 question 24 discussion

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.

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.

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.

BAdmin access to the deployment pipeline DViewer access to the Production workspace EContributor access to the Development and Test workspaces

To meet the requirements while following the principle of least privilege, you should assign the following levels of access to the developers: B. Admin access to the deployment pipeline - This is needed so developers can manage the deployment pipeline itself, including moving items between stages. E. Contributor access to the Development and Test workspaces - This allows developers to deploy and make changes to the items in the Development and Test workspaces. D. Viewer access to the Production workspace - This ensures developers can view the Production workspace but cannot make any changes or deploy items to it.

B - There's only one role for pipelines so it's either having an Admin role or no access to a pipeline. You have to have an Admin role on a pipeline in order to do any deployments. D - Pipeline permissions and workspace permissions are kind of linked but the way it works is if a user has viewer permissions on a workspace and Admin on the Pipeline - They won't be able to do a deployment to that workspace, but they can still see things inside of it (as is the case as a viewer in any workspace). E - If you have the Contributer/Member/Admin role on a workspace AND Admin permissions on a pipeline, then you can deploy to that workspace.

It does not say Developers need to manage deployments, just access items within the pipeline. So A, D, and E

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

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.

Respostas BDE

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

I agree with 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.

Admin access is needed in the development workspace for pipeline.

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?

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

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