S07 Lifecycle Management CICD

What is the role of Git in the CI/CD process in Fabric?

• Git is used to deploy code changes to different environments.

• Git is used for automated testing of code changes.

• Git lets your team collaborate using branches, and provides version control. It helps manage incremental code changes, and see code history.

• None of the above

What is the purpose of connecting a Fabric workspace to a Git repository?

• To automatically deploy changes made in the workspace to a live environment.

• To sync content between the workspace and Git, ensuring they have the same content.

• To allow multiple developers to work on the same code simultaneously without conflicts.

• None of the above

What is the primary function of deployment pipelines in Fabric?

• Deployment pipelines are used to create new content in Fabric.

• Deployment pipelines are used to delete old content from Fabric.

• Deployment pipelines automate the movement of content through the development, test, and production stages.

• None of the above

When promoting validated artifacts from a shared Test workspace to several hundred production workspaces—each mapped to a different customer—which Fabric feature streamlines this process the most?

• OneLake shortcuts

• Workspace separation rule

• Deployment pipelines using the “Deploy to Workspace” action

• XMLA-endpoints for bulk copy

“Option 4 – CI/CD for ISVs in Fabric (managing multiple customers/solutions)” documentation you provided.
In Option 4, when does the solution branch out from a single shared workspace into the hundreds or thousands of customer-specific workspaces?

• During the Dev stage

• During the Test stage

• During the Prod stage

• During the initial Git commit