Microsoft DP-700 Practice Test 5
Question 40
A Fabric warehouse's schema changes need code review as individual SQL objects rather than a one-off GUI export. What representation should the team use?
- Manage warehouse schema through a source-controlled database project with object SQL files.
- Apply an incremental schema deployment from the updated warehouse database project.
- Update the stored procedure's SQL definition in the warehouse database project and submit it for review.
- Validate the database project schema diff and downstream object dependencies in a preproduction stage.
Explanation
Correct Answer
A:Warehouse Git integration represents schema definitions as database project files, allowing incremental comparison and review. Inspect the generated project SQL files after a schema change.
Incorrect Answers
B:DacFx-based warehouse synchronization applies relevant schema differences instead of treating every change as a full database replacement.
C:Keeping the procedure in the schema project preserves change history and enables deployment with the rest of the warehouse definitions.
D:Schema-as-code provides reviewability but does not make a breaking column rename automatically safe for dependent reports and queries.
Question 41
A developer changes one warehouse view and wants to avoid rebuilding all unrelated tables during promotion. What deployment model fits?
- Compare the warehouse state with its database project source and reconcile the drift through controlled deployment.
- Apply an incremental schema deployment from the updated warehouse database project.
- Treat the database project as schema definitions and design separate governed data-migration or loading procedures.
- Validate the database project schema diff and downstream object dependencies in a preproduction stage.
Explanation
Correct Answer
B:DacFx-based warehouse synchronization applies relevant schema differences instead of treating every change as a full database replacement. Review deployment differences before applying the change.
Incorrect Answers
A:Untracked portal edits create schema drift; the declared project must be reconciled before claiming source and live definitions agree.
C:Warehouse schema source control is not a backup or version history of all table rows, so data movement requires its own process.
D:Schema-as-code provides reviewability but does not make a breaking column rename automatically safe for dependent reports and queries.
Question 42
A warehouse project contains a renamed column that could break reporting dependencies. What should happen before production deployment?
- Validate the database project schema diff and downstream object dependencies in a preproduction stage.
- Compare repository commit IDs with production but deploy the renamed column without testing dependent reports or views.
- Apply an incremental schema deployment from the updated warehouse database project.
- Check out the warehouse's source-controlled database project from the approved repository.
Explanation
Correct Answer
A:Schema-as-code provides reviewability but does not make a breaking column rename automatically safe for dependent reports and queries. Run dependent queries against the updated preproduction schema.
Incorrect Answers
B:Repository-to-production version comparison alone does not establish whether dependent reports and views still use the old column name. The renamed object and downstream consumers must be validated using a schema diff in a preproduction stage before deployment.
C:DacFx-based warehouse synchronization applies relevant schema differences instead of treating every change as a full database replacement.
D:The project provides declarative object definitions; copying table data alone is not a substitute for managed schema source.
Question 43
A new developer needs a reproducible warehouse definition outside the Fabric portal. Which artifact should they retrieve?
- Update the stored procedure's SQL definition in the warehouse database project and submit it for review.
- Check out the warehouse's source-controlled database project from the approved repository.
- Compare the warehouse state with its database project source and reconcile the drift through controlled deployment.
- Apply an incremental schema deployment from the updated warehouse database project.
Explanation
Correct Answer
B:The project provides declarative object definitions; copying table data alone is not a substitute for managed schema source. Build or inspect the project in a compatible development environment.
Incorrect Answers
A:Keeping the procedure in the schema project preserves change history and enables deployment with the rest of the warehouse definitions.
C:Untracked portal edits create schema drift; the declared project must be reconciled before claiming source and live definitions agree.
D:DacFx-based warehouse synchronization applies relevant schema differences instead of treating every change as a full database replacement.
Question 44
A migration adds a SQL stored procedure and must be reviewed before deployment. Where should its definition be changed?
- Validate the database project schema diff and downstream object dependencies in a preproduction stage.
- Check out the warehouse's source-controlled database project from the approved repository.
- Update the stored procedure's SQL definition in the warehouse database project and submit it for review.
- Compare the warehouse state with its database project source and reconcile the drift through controlled deployment.
Explanation
Correct Answer
C:Keeping the procedure in the schema project preserves change history and enables deployment with the rest of the warehouse definitions. Confirm the revised procedure exists after test deployment.
Incorrect Answers
A:Schema-as-code provides reviewability but does not make a breaking column rename automatically safe for dependent reports and queries.
B:The project provides declarative object definitions; copying table data alone is not a substitute for managed schema source.
D:Untracked portal edits create schema drift; the declared project must be reconciled before claiming source and live definitions agree.
Question 45
A production warehouse's actual schema diverges from its repository definition. What should the owner inspect?
- Update the stored procedure's SQL definition in the warehouse database project and submit it for review.
- Deploy the current repository schema again without comparing the production warehouse or reporting dependencies.
- Validate the database project schema diff and downstream object dependencies in a preproduction stage.
- Compare the warehouse state with its database project source and reconcile the drift through controlled deployment.
Explanation
Correct Answer
D:Untracked portal edits create schema drift; the declared project must be reconciled before claiming source and live definitions agree. Review the project diff and validate the resulting schema.
Incorrect Answers
A:Keeping the procedure in the schema project preserves change history and enables deployment with the rest of the warehouse definitions.
B:Blind redeployment can overwrite intentional warehouse changes and does not first identify the exact source-to-production drift or affected dependencies. Review the project diff and validate the resulting schema.
C:Schema-as-code provides reviewability but does not make a breaking column rename automatically safe for dependent reports and queries.
Question 46
A team plans to manage data contents through warehouse Git schema integration. What limitation should the architect explain?
- Treat the database project as schema definitions and design separate governed data-migration or loading procedures.
- Apply an incremental schema deployment from the updated warehouse database project.
- Validate the database project schema diff and downstream object dependencies in a preproduction stage.
- Manage warehouse schema through a source-controlled database project with object SQL files.
Explanation
Correct Answer
A:Warehouse schema source control is not a backup or version history of all table rows, so data movement requires its own process. Verify the deployment and the data load as separate checks.
Incorrect Answers
B:DacFx-based warehouse synchronization applies relevant schema differences instead of treating every change as a full database replacement.
C:Schema-as-code provides reviewability but does not make a breaking column rename automatically safe for dependent reports and queries.
D:Warehouse Git integration represents schema definitions as database project files, allowing incremental comparison and review.
Question 47
Development artifacts are ready for user acceptance testing. What Fabric-native mechanism promotes approved items between linked workspaces?
- Use a Fabric deployment pipeline to promote from Development to Test.
- Use Git update-from-branch to replace the Test workspace before creating a supported deployment-pipeline stage mapping.
- Apply supported stage-specific parameterization or deployment rules during promotion.
- Define the needed deployment order and post-deployment dependency validation in the release process.
Explanation
Correct Answer
A:A deployment pipeline defines stages and supports controlled promotion of Fabric items between workspaces. Verify the intended Test items and their bindings after deployment.
Incorrect Answers
B:Updating Git synchronizes repository definitions with a connected workspace, but it does not configure the linked Deployment pipeline stages needed for a reviewable Development-to-Test promotion. Verify the intended Test items and their bindings after deployment.
C:Promotion must account for environment-specific references and credentials; copying the definition blindly can point Test code to production resources.
D:Successful item copying does not imply every downstream prerequisite or connection is ready for execution.
Question 48
The same notebook should reference a test connection in Test and a production connection in Production. What should be configured?
- Inspect dependency binding and supported autobinding behavior for the promoted items.
- Define the needed deployment order and post-deployment dependency validation in the release process.
- Apply supported stage-specific parameterization or deployment rules during promotion.
- Promote the tested item definitions through the deployment pipeline after approval.
Explanation
Correct Answer
C:Promotion must account for environment-specific references and credentials; copying the definition blindly can point Test code to production resources. Inspect resolved connections before running the promoted notebook.
Incorrect Answers
A:Fabric deployment can rebind supported dependencies, but not every cross-workspace reference resolves automatically.
B:Successful item copying does not imply every downstream prerequisite or connection is ready for execution.
D:Promoting a tested version reduces untracked direct production edits and retains stage visibility.
Question 49
A deployment succeeds but a downstream item still points to the old workspace. What should be reviewed?
- Apply supported stage-specific parameterization or deployment rules during promotion.
- Use a Fabric deployment pipeline to promote from Development to Test.
- Promote the tested item definitions through the deployment pipeline after approval.
- Inspect dependency binding and supported autobinding behavior for the promoted items.
Explanation
Correct Answer
D:Fabric deployment can rebind supported dependencies, but not every cross-workspace reference resolves automatically. Open the target item and verify its upstream reference.
Incorrect Answers
A:Promotion must account for environment-specific references and credentials; copying the definition blindly can point Test code to production resources.
B:A deployment pipeline defines stages and supports controlled promotion of Fabric items between workspaces.
C:Promoting a tested version reduces untracked direct production edits and retains stage visibility.
Question 50
A team wants reviewable promotion from Test to Production without editing production notebooks by hand. What workflow is appropriate?
- Promote the tested item definitions through the deployment pipeline after approval.
- Inspect dependency binding and supported autobinding behavior for the promoted items.
- Define the needed deployment order and post-deployment dependency validation in the release process.
- Promote the Development workspace directly to Production, skipping the approved Test workspace.
Explanation
Correct Answer
A:Promoting a tested version reduces untracked direct production edits and retains stage visibility. Compare deployed definitions with the approved Test stage.
Incorrect Answers
B:Fabric deployment can rebind supported dependencies, but not every cross-workspace reference resolves automatically.
C:Successful item copying does not imply every downstream prerequisite or connection is ready for execution.
D:Skipping the validated Test stage contradicts the required reviewed Test-to-Production promotion and can bypass approval and environment-specific rules. Compare deployed definitions with the approved Test stage.
