DP-600 Maintain a Data Analytics Solution Practice Question
You are maintaining a Fabric workspace and need to grant a colleague the ability to commit changes to the Git repository but prevent them from deleting the workspace itself. Which workspace role should you assign?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Contributor
Role-based access control (RBAC) is fundamental to maintaining a secure and functional Fabric environment. Each role provides a different level of authority. For developers who need to interact with Git integration, the role must allow for item modification and synchronization while adhering to the principle of least privilege to protect the workspace infrastructure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Viewer
Why it's wrong here
The Viewer role only allows users to consume content and does not permit any modifications or interactions with source control. Viewers cannot commit changes or sync the workspace with Git. This role is strictly for end-users who only need to see the final reports and dashboards.
- ✓
Contributor
Why this is correct
The Contributor role allows users to create, edit, and delete items within the workspace, as well as interact with Git integration to commit changes. Crucially, Contributors cannot delete the workspace or modify its settings, making it the ideal role for a developer who needs to manage the data solution's code.
- ✗
Admin
Why it's wrong here
The Admin role has full control over the workspace, including the ability to delete the entire workspace and manage user permissions. While an Admin can commit to Git, this role provides more power than necessary for a standard developer and introduces the risk of accidental workspace deletion or misconfiguration.
- ✗
Member
Why it's wrong here
The Member role can do everything a Contributor can, plus they can share items and manage some workspace permissions. While they can't delete the workspace, they have more authority than needed for just Git operations. Contributor is the more precise role for the specific requirement of code maintenance.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
About these practice questions
This DP-600 question is part of Courseiva's 12-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This DP-600 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-600 exam.