Microsoft DP-700 Practice Test 6
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.
Question 51
Only one updated data pipeline should be deployed; unrelated drafts must stay in Development. What should the operator select?
- Apply supported stage-specific parameterization or deployment rules during promotion.
- Use selective deployment for the intended supported pipeline item.
- Inspect dependency binding and supported autobinding behavior for the promoted items.
- Use a Fabric deployment pipeline to promote from Development to Test.
Explanation
Correct Answer
B:Selective promotion reduces accidental release of unfinished artifacts when the deployment tooling and item type support it. Review the selected-item preview before deploying.
Incorrect Answers
A:Promotion must account for environment-specific references and credentials; copying the definition blindly can point Test code to production resources.
C:Fabric deployment can rebind supported dependencies, but not every cross-workspace reference resolves automatically.
D:A deployment pipeline defines stages and supports controlled promotion of Fabric items between workspaces.
Question 52
A workspace is associated with the wrong deployment stage. Which configuration must be fixed?
- Define the needed deployment order and post-deployment dependency validation in the release process.
- Assign the correct workspace to the intended deployment pipeline stage.
- Use a Fabric deployment pipeline to promote from Development to Test.
- Apply supported stage-specific parameterization or deployment rules during promotion.
Explanation
Correct Answer
B:A deployment stage is a workspace mapping; renaming an item does not change where pipeline promotion writes it. Verify Development, Test, and Production workspace associations.
Incorrect Answers
A:Successful item copying does not imply every downstream prerequisite or connection is ready for execution.
C:A deployment pipeline defines stages and supports controlled promotion of Fabric items between workspaces.
D:Promotion must account for environment-specific references and credentials; copying the definition blindly can point Test code to production resources.
Question 53
A release requires a linked item to exist before a dependent operation runs. What should the team design?
- Apply supported stage-specific parameterization or deployment rules during promotion.
- Use selective deployment for the intended supported pipeline item.
- Use a Fabric deployment pipeline to promote from Development to Test.
- Define the needed deployment order and post-deployment dependency validation in the release process.
Explanation
Correct Answer
D:Successful item copying does not imply every downstream prerequisite or connection is ready for execution. Execute dependency smoke checks in the target stage.
Incorrect Answers
A:Promotion must account for environment-specific references and credentials; copying the definition blindly can point Test code to production resources.
B:Selective promotion reduces accidental release of unfinished artifacts when the deployment tooling and item type support it.
C:A deployment pipeline defines stages and supports controlled promotion of Fabric items between workspaces.
Question 54
A Spark environment has staged Git changes to libraries but notebooks still run old versions. What completes the change?
- Publish the synchronized Fabric environment before new notebook sessions use it.
- Pin the tested environment definition and retain a previous reviewed source revision for redeployment.
- Replace the copied custom pool reference with a valid destination-workspace pool or starter pool.
- Verify that the notebook is attached to the intended published environment in the target workspace.
Explanation
Correct Answer
A:Git-synced environment definitions can remain staged until published; a repository commit is not the same as activating a runtime configuration. Inspect the published environment version and session libraries.
Incorrect Answers
B:Versioning the runtime and dependencies enables deliberate rollback to a known configuration rather than relying on memory of portal settings.
C:Custom Spark pools are workspace-scoped, so unchanged source pool identifiers may not exist in the promoted workspace.
D:A valid environment definition does not ensure every notebook references or inherits it correctly after promotion.
Question 55
A Fabric environment moves to another workspace and its custom pool ID no longer resolves. What should the team correct?
- Replace the copied custom pool reference with a valid destination-workspace pool or starter pool.
- Track supported environment settings with Git and promote the published environment through deployment pipelines.
- Pin the tested environment definition and retain a previous reviewed source revision for redeployment.
- Publish and validate the environment on a test notebook before changing the default assignment.
Explanation
Correct Answer
A:Custom Spark pools are workspace-scoped, so unchanged source pool identifiers may not exist in the promoted workspace. Launch a test Spark session against the resolved pool.
Incorrect Answers
B:Environment Git integration and deployment workflows control supported definitions across stages without repeated manual library entry.
C:Versioning the runtime and dependencies enables deliberate rollback to a known configuration rather than relying on memory of portal settings.
D:A controlled test prevents unreviewed package versions from becoming the baseline for every new job.
Question 56
A team wants a reviewed Spark library list reproduced in Development, Test, and Production. Which combination supports it?
- Verify that the notebook is attached to the intended published environment in the target workspace.
- Publish and validate the environment on a test notebook before changing the default assignment.
- Track supported environment settings with Git and promote the published environment through deployment pipelines.
- Replace the copied custom pool reference with a valid destination-workspace pool or starter pool.
Explanation
Correct Answer
C:Environment Git integration and deployment workflows control supported definitions across stages without repeated manual library entry. Compare library names and versions in each published stage.
Incorrect Answers
A:A valid environment definition does not ensure every notebook references or inherits it correctly after promotion.
B:A controlled test prevents unreviewed package versions from becoming the baseline for every new job.
D:Custom Spark pools are workspace-scoped, so unchanged source pool identifiers may not exist in the promoted workspace.
Question 57
A developer changed an environment only in the portal and wants the change included in the next Git release. What should they do?
- Track supported environment settings with Git and promote the published environment through deployment pipelines.
- Pin the tested environment definition and retain a previous reviewed source revision for redeployment.
- Publish and validate the environment on a test notebook before changing the default assignment.
- Commit supported environment-definition changes from the Fabric workspace to Git.
Explanation
Correct Answer
D:Uncommitted portal changes are not necessarily in the repository snapshot used for promotion. Inspect the commit's environment configuration diff.
Incorrect Answers
A:Environment Git integration and deployment workflows control supported definitions across stages without repeated manual library entry.
B:Versioning the runtime and dependencies enables deliberate rollback to a known configuration rather than relying on memory of portal settings.
C:A controlled test prevents unreviewed package versions from becoming the baseline for every new job.
Question 58
A new environment contains untested dependencies that must not replace the workspace default. What is the safe rollout?
- Pin the tested environment definition and retain a previous reviewed source revision for redeployment.
- Replace the copied custom pool reference with a valid destination-workspace pool or starter pool.
- Publish and validate the environment on a test notebook before changing the default assignment.
- Commit supported environment-definition changes from the Fabric workspace to Git.
Explanation
Correct Answer
C:A controlled test prevents unreviewed package versions from becoming the baseline for every new job. Compare test results before updating the workspace default.
Incorrect Answers
A:Versioning the runtime and dependencies enables deliberate rollback to a known configuration rather than relying on memory of portal settings.
B:Custom Spark pools are workspace-scoped, so unchanged source pool identifiers may not exist in the promoted workspace.
D:Uncommitted portal changes are not necessarily in the repository snapshot used for promotion.
Question 59
An environment's library list is correct in Git but a dependent notebook fails after deployment. Which dependency relationship should be checked?
- Verify that the notebook is attached to the intended published environment in the target workspace.
- Publish and validate the environment on a test notebook before changing the default assignment.
- Track supported environment settings with Git and promote the published environment through deployment pipelines.
- Pin the tested environment definition and retain a previous reviewed source revision for redeployment.
Explanation
Correct Answer
A:A valid environment definition does not ensure every notebook references or inherits it correctly after promotion. Inspect notebook environment selection and runtime imports.
Incorrect Answers
B:A controlled test prevents unreviewed package versions from becoming the baseline for every new job.
C:Environment Git integration and deployment workflows control supported definitions across stages without repeated manual library entry.
D:Versioning the runtime and dependencies enables deliberate rollback to a known configuration rather than relying on memory of portal settings.
Question 60
A release introduces a new Spark runtime and must allow rollback. Which practice best preserves recovery?
- Replace the copied custom pool reference with a valid destination-workspace pool or starter pool.
- Publish and validate the environment on a test notebook before changing the default assignment.
- Pin the tested environment definition and retain a previous reviewed source revision for redeployment.
- Verify that the notebook is attached to the intended published environment in the target workspace.
Explanation
Correct Answer
C:Versioning the runtime and dependencies enables deliberate rollback to a known configuration rather than relying on memory of portal settings. Rebuild a test session from the prior approved revision.
Incorrect Answers
A:Custom Spark pools are workspace-scoped, so unchanged source pool identifiers may not exist in the promoted workspace.
B:A controlled test prevents unreviewed package versions from becoming the baseline for every new job.
D:A valid environment definition does not ensure every notebook references or inherits it correctly after promotion.
