Microsoft Certified: Fabric Analytics Engineer AssociateGovern and administer Fabric (10-15%)Hard
A data analytics department has multiple teams, each working on distinct projects within Microsoft Fabric. They want to implement a solution where each team has its own isolated environment for development and testing, ensuring that changes made by one team do not accidentally affect another. Furthermore, they need a clear separation of billing for the compute resources consumed by each team. How should the Fabric administrator structure their environment to meet these requirements efficiently?
- AUse deployment pipelines to isolate development efforts.
- BCreate a single workspace for all teams and use item-level permissions.
- CCreate separate workspaces for each team, each assigned to its own dedicated Fabric Capacity SKU.
- DCreate separate workspaces for each team within a shared capacity.
Show answer & explanationAnswer & explanation
Correct answer: C. Create separate workspaces for each team, each assigned to its own dedicated Fabric Capacity SKU.
Creating separate workspaces for each team provides logical isolation. Assigning each workspace to its own dedicated Fabric Capacity SKU ensures complete resource isolation, preventing one team's activity from impacting another's performance, and enables accurate chargeback for compute resources, fulfilling all requirements.
Why the other options are wrong
- A. Deployment pipelines manage content lifecycle, not resource isolation or separate billing for development/testing environments.
- B. A single workspace with item-level permissions does not provide resource isolation or separate billing for compute.
- D. Separate workspaces provide logical isolation, but a shared capacity still means shared compute resources and no clear separate billing for compute.
Fabric Capacity per Team
Assigning dedicated Fabric Capacity SKUs to individual teams or projects allows for resource isolation, performance guarantees, and granular cost allocation (chargeback) within an organization.
- Ensures performance isolation between teams.
- Enables accurate cost tracking for each team's compute.
- Provides dedicated compute resources for specific workloads.
- Requires purchasing separate Fabric Capacity SKUs.
Memory trick: Give each team their own 'house' (workspace) and their own 'power meter' (capacity SKU).