Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft DP-600 Exam - Topic 1 Question 42 Discussion

Actual exam question for Microsoft's DP-600 exam
Question #: 42
Topic #: 1
[All DP-600 Questions]

You need to provide Power Bl 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.

Show Suggested Answer Hide Answer
Suggested Answer: B, D, E

To meet the requirements, developers should have Admin access to the deployment pipeline (B), Contributor access to the Development and Test workspaces (E), and Viewer access to the Production workspace (D). This setup ensures they can perform necessary actions in development and test environments without having the ability to affect production. Reference = The Power BI documentation on workspace access levels and deployment pipelines provides guidelines on assigning appropriate permissions.


Contribute your Thoughts:

0/2000 characters
Xochitl
22 days ago
Exactly! Just stick to Contributor for Dev/Test and Viewer for Prod.
upvoted 0 times
...
Tiera
27 days ago
What about Build permission? We don’t need that for Production.
upvoted 0 times
...
Bethanie
1 month ago
Yes, Viewer access for Production is a must!
upvoted 0 times
...
Alba
1 month ago
But not for Production, right? Viewer access there is safer.
upvoted 0 times
...
Xochitl
1 month ago
Agreed! They should be able to deploy there.
upvoted 0 times
...
Gwen
2 months ago
Build permission for production models? No way, that’s too much access!
upvoted 0 times
...
Micaela
2 months ago
Viewer access to Production makes sense, but I’m surprised it’s even an option.
upvoted 0 times
...
Melita
2 months ago
Wait, why would they need Admin access to the pipeline? Seems risky.
upvoted 0 times
...
Herminia
3 months ago
Totally agree, they shouldn't touch Production at all.
upvoted 0 times
...
Jody
3 months ago
C, E. Haha, the devs are like kids in a candy store. Gotta keep 'em out of the production workspace!
upvoted 0 times
...
Annette
3 months ago
C, E. Ah, the classic "keep the devs away from production" scenario. Good call.
upvoted 0 times
...
Azzie
3 months ago
C, E. Yup, that's the way to go. Can't let the devs mess up the production environment.
upvoted 0 times
...
Lorenza
3 months ago
C, E. Seems straightforward. Gotta keep those devs out of production!
upvoted 0 times
...
Jeannetta
3 months ago
C, E. Definitely the right answer. Developers need to be able to deploy to the non-production environments, but should not have access to the production workspace.
upvoted 0 times
...
Matt
4 months ago
I’m a bit confused about the permissions for the Development and Test workspaces. Should we go with Contributor for both?
upvoted 0 times
...
Junita
4 months ago
I practiced a similar question where we had to limit access. I feel like Viewer access to Production is a safe choice.
upvoted 0 times
...
Nan
4 months ago
I think we need to give Contributor access to the Development and Test workspaces, but I'm not sure about the Production workspace.
upvoted 0 times
...
Nina
4 months ago
I think I've got it - E and C will give the developers the access they need while following the principle of least privilege. Time to lock in my answer.
upvoted 0 times
...
Ciara
4 months ago
The key here is to prevent the developers from deploying to Production, so I'm leaning towards E and D as the best solution.
upvoted 0 times
...
Wilda
4 months ago
I'm a bit confused on the difference between Viewer and Contributor access. I'll need to double-check the permissions for each to make sure I get this right.
upvoted 0 times
...
Malcolm
5 months ago
I think Contributor access to Dev and Test is a must!
upvoted 0 times
...
Sherita
5 months ago
C, E. Developers should have viewer access to the Development and Test workspaces, and contributor access to the Development and Test workspaces. This follows the principle of least privilege.
upvoted 0 times
...
Tiera
5 months ago
I think we need Contributor access for Development and Test.
upvoted 0 times
...
Mozelle
5 months ago
I remember something about least privilege, so we definitely shouldn't give Admin access to the pipeline. That seems risky.
upvoted 0 times
...
Aja
6 months ago
Okay, I see we need to give the developers access to deploy to Development and Test, but not Production. I'm thinking E and C might be the way to go.
upvoted 0 times
...
Barbra
6 months ago
Hmm, this looks like a tricky one. I'll need to think carefully about the principle of least privilege and how to balance access for the developers.
upvoted 0 times
Johnathon
20 hours ago
And no Build permission for production models either!
upvoted 0 times
...
Colton
6 days ago
Right! Viewer access to Production is a must.
upvoted 0 times
...
Loreta
11 days ago
Agreed! That way they can deploy without issues.
upvoted 0 times
...
Shakira
16 days ago
I think we should give Contributor access to Development and Test workspaces.
upvoted 0 times
...
Lanie
5 months ago
But we must avoid giving them access to Production.
upvoted 0 times
...
...

Save Cancel