Microsoft Certified: Fabric Analytics Engineer AssociateGovern and administer Fabric (10-15%)Medium
A data analytics team has built several critical reports and dashboards in a Microsoft Fabric workspace. They want to ensure that these items remain available even if the underlying data sources or connected services experience temporary outages. They need a mechanism to quickly revert to a previous, stable state of these reports and dashboards if issues arise after a new deployment. Which Fabric feature should they primarily rely on for this recovery capability?
- AItem-level sharing permissions
- BGit integration for version control
- CDeployment pipeline rollback
- DWorkspace backup and restore
Show answer & explanationAnswer & explanation
Correct answer: B. Git integration for version control
Git integration provides robust version control for Fabric artifacts (like notebooks, report definitions, etc.), allowing teams to track changes, revert to previous versions, and manage development branches. This is crucial for quickly reverting reports and dashboards to a stable state after deployment issues.
Why the other options are wrong
- A. Item-level sharing permissions control access, not versioning or recovery.
- C. While deployment pipelines manage deployments, the underlying version control for the artifacts themselves (which enables rollback) is often facilitated by Git integration.
- D. Workspace backup and restore is for disaster recovery of the entire workspace, not granular item-level rollback for reports and dashboards.
Fabric Git Integration
Microsoft Fabric's Git integration allows developers to connect workspaces to Azure DevOps Git repositories, enabling version control, collaborative development, and change tracking for Fabric items.
- Supports collaborative development.
- Enables versioning and change tracking.
- Facilitates rollback to previous stable states.
- Crucial for CI/CD pipelines.
Memory trick: Git is your time machine for Fabric items, letting you go back to stable versions.