DP-600 Deployment Pipelines and CI/CD 1 — Questions and Answers
Question 1: What are the three default stages in a Microsoft Fabric deployment pipeline?
- Development, Testing, and Production (Correct answer)
- Build, Deploy, and Release
- Alpha, Beta, and Production
- Source, Staging, and Archive
Correct answer: Development, Testing, and Production
Fabric deployment pipelines have three built-in stages — Development, Testing, and Production — mirroring the standard software development lifecycle.
Question 2: When deploying a lakehouse between Fabric deployment pipeline stages, what content is transferred?
- Only the lakehouse item definition and schema; underlying data is not copied (Correct answer)
- All data including Delta tables and files is copied to the target stage
- Data is moved from the source stage and deleted after deployment
- A read-only snapshot of all data is created in the target lakehouse
Correct answer: Only the lakehouse item definition and schema; underlying data is not copied
Fabric deployment pipelines deploy item definitions and configurations, not the underlying data stored in lakehouses or warehouses.
Question 3: What is the minimum workspace role required to deploy content to a stage in a Fabric deployment pipeline?
- Admin or Member (Correct answer)
- Contributor
- Viewer
- Any user with a Fabric license
Correct answer: Admin or Member
Deploying content to a pipeline stage requires Admin or Member role in the target workspace to ensure write-level access.
Question 4: What is the purpose of deployment rules in Microsoft Fabric deployment pipelines?
- To override item properties such as data source connections when deploying between stages (Correct answer)
- To restrict which users can trigger deployments between stages
- To schedule automatic deployments on a recurring basis
- To validate data quality before promoting content to production
Correct answer: To override item properties such as data source connections when deploying between stages
Deployment rules let you override specific item configurations like connection strings so each pipeline stage automatically uses the appropriate environment settings.
Question 5: How many workspaces can be assigned to a single stage in a Fabric deployment pipeline?
- One workspace per stage (Correct answer)
- Up to three workspaces per stage
- Up to five workspaces per stage
- Unlimited workspaces per stage
Correct answer: One workspace per stage
Each deployment pipeline stage supports exactly one workspace assignment, enforcing a one-to-one mapping between stages and environments.
Question 6: Which of the following Fabric items is supported for deployment using Fabric deployment pipelines?
- Semantic models (Correct answer)
- Lakehouse data rows
- OneLake shortcut target configurations
- SQL endpoint query result sets
Correct answer: Semantic models
Semantic models (formerly datasets) are supported deployment pipeline items; underlying data content such as table rows is not deployed by pipelines.
Question 7: Which feature in Fabric deployment pipelines lets you review differences between two pipeline stages before triggering a deployment?
- Compare stages (Correct answer)
- Delta view
- Stage diff report
- Audit trail
Correct answer: Compare stages
The 'Compare stages' feature displays a side-by-side diff of items between two pipeline stages so you understand exactly what will change before deploying.
DP-600 Deployment Pipelines and CI/CD 1
What are the three default stages in a Microsoft Fabric deployment pipeline?