A data engineering team uses a Microsoft Fabric workspace that contains a Lakehouse, several pipelines and a semantic model. A platform support analyst must view refresh history, monitor pipeline runs and inspect item configuration across the whole workspace, but must not be able to edit, run or delete any item. Which single workspace role grants exactly the access the analyst needs while following least privilege?
- AAssign the Viewer role, because it grants read access to workspace items and their run and refresh history without create, edit, run or delete rights. Correct
- BAssign the Contributor role, because it lets the analyst open every item in the workspace and observe how each pipeline and refresh is configured.
- CAssign the Member role, because membership lets the analyst monitor items and reshare the workspace with other read-only support staff later.
- DAssign the Admin role, because an administrator can see all run history and item settings across every artifact in the workspace.
Why A is correct: Viewer is the read-only workspace role: the analyst can view items and history but cannot modify, execute or remove anything, matching least privilege exactly.
Why B is wrong: Contributor can create, edit and run items including pipelines, which exceeds the read-only monitoring requirement and breaks least privilege.
Why C is wrong: Member can edit items and manage permissions, which is far broader than monitoring and grants write and sharing rights the analyst should not hold.
Why D is wrong: Admin can view everything but also delete the workspace and reassign roles, so it grossly overprovisions a read-only monitoring task.