An analytics engineer joins a "Microsoft Fabric" workspace and must be able to create and edit reports, semantic models, and a "Lakehouse", and to publish content into the workspace. The team lead wants this person to have the lowest workspace role that still allows authoring all those items, without the ability to add or remove other users or change workspace settings. Which workspace role should be assigned?
- AAssign the Contributor role, which lets the engineer create, edit, and publish workspace items while withholding the ability to manage workspace access and settings. Correct
- BAssign the Viewer role, which lets the engineer open and consume the workspace items and refresh any semantic models that back the published reports.
- CAssign the Member role, which lets the engineer author all items and additionally share the workspace and add other users with lower roles.
- DAssign the Admin role, which grants full authoring plus control over workspace settings, user roles, and deletion of the entire workspace.
Why A is correct: Contributor is the lowest role that grants full authoring of items yet excludes adding users and changing settings, matching the least-privilege authoring requirement exactly.
Why B is wrong: Viewer is read-only and cannot create or edit items, so it cannot satisfy a requirement to author reports, semantic models, and a Lakehouse.
Why C is wrong: Member does grant authoring, but it also lets the user add others and reshare, exceeding the stated limit of no access management, so it is not the lowest sufficient role.
Why D is wrong: Admin gives the broadest control including settings and user management, far more than authoring needs, so it breaks the least-privilege constraint the lead set.