Microsoft DP-700 Practice Test 4
Question 30
A DAG should accept a per-run reporting date without editing its Python source every day. Which approach supports that flexibility?
- Configure an Apache Airflow job and deploy the DAG in the intended Fabric workspace.
- Configure a suitable custom Apache Airflow runtime pool in workspace Data Factory settings.
- Inspect the failed Airflow task instance logs and retry history.
- Supply a run-time parameter or DAG configuration value and read it in the relevant task.
Explanation
Correct Answer
D:Parameterizing the DAG separates execution-specific values from committed task definitions and avoids repetitive code changes. Run two dates and confirm the task consumes each configured value.
Incorrect Answers
A:Airflow uses DAGs and tasks for dependency-driven workflow execution, preserving a Python orchestration pattern instead of forcing it into a query editor.
B:Custom Airflow pools permit controlled node sizing and an always-on runtime, while starter pools are oriented to intermittent development use.
C:Task logs show the exception at the failing operation and separate recoverable retries from graph-level status.
Question 31
A large DAG's independent tasks are unnecessarily executed sequentially. What should the designer adjust?
- Remove artificial dependencies between independent tasks so Airflow can schedule eligible work concurrently.
- Provide the DAG's required Python dependencies in the Airflow job's supported environment configuration.
- Configure a suitable custom Apache Airflow runtime pool in workspace Data Factory settings.
- Configure an Apache Airflow job and deploy the DAG in the intended Fabric workspace.
Explanation
Correct Answer
A:The dependency graph, not alphabetical task order, should represent true data requirements; false dependencies increase critical-path length. Compare the graph and run durations before and after the dependency change.
Incorrect Answers
B:A DAG's source alone cannot satisfy missing imports; the execution environment must include libraries referenced by tasks.
C:Custom Airflow pools permit controlled node sizing and an always-on runtime, while starter pools are oriented to intermittent development use.
D:Airflow uses DAGs and tasks for dependency-driven workflow execution, preserving a Python orchestration pattern instead of forcing it into a query editor.
Question 32
A DAG uses a missing external connection secret after promotion to a new workspace. What should be restored?
- Configure the destination Airflow connection or secret reference used by the DAG tasks.
- Configure a suitable custom Apache Airflow runtime pool in workspace Data Factory settings.
- Remove artificial dependencies between independent tasks so Airflow can schedule eligible work concurrently.
- Supply a run-time parameter or DAG configuration value and read it in the relevant task.
Explanation
Correct Answer
A:Code deployment does not by itself guarantee corresponding environment-specific credentials and connections exist in the destination. Validate the connection separately before replaying the DAG.
Incorrect Answers
B:Custom Airflow pools permit controlled node sizing and an always-on runtime, while starter pools are oriented to intermittent development use.
C:The dependency graph, not alphabetical task order, should represent true data requirements; false dependencies increase critical-path length.
D:Parameterizing the DAG separates execution-specific values from committed task definitions and avoids repetitive code changes.
Question 33
Two Fabric engineers overwrite one another's notebook changes. They need reviewable source history and branches. Which capability should they adopt?
- Update the workspace's Git connection to the approved repository and branch.
- Connect the development workspace to supported Git integration with an agreed branching workflow.
- Record the tested Git commit identifier and promote the matching definition across release stages.
- Review the incoming changes and use the supported update-from-Git workflow.
Explanation
Correct Answer
B:Git integration versions supported Fabric item definitions and enables review before syncing changes to shared workspaces. Commit a harmless notebook update and verify its history.
Incorrect Answers
A:Branch association determines the source-control state with which the workspace synchronizes; a deployment pipeline stage does not select that Git branch.
C:A commit SHA identifies an exact reviewed source snapshot; a moving branch label alone cannot prove which version was deployed.
D:Connecting a branch does not automatically make every remote commit effective in the workspace; an explicit sync/update reconciles changes.
Question 34
A workspace reports pending incoming Git changes. The team wants to update its items from the branch. What should be performed?
- Review the incoming changes and use the supported update-from-Git workflow.
- Record the tested Git commit identifier and promote the matching definition across release stages.
- Connect the development workspace to supported Git integration with an agreed branching workflow.
- Review the conflicting versions and explicitly choose or merge the desired item definition before synchronizing.
Explanation
Correct Answer
A:Connecting a branch does not automatically make every remote commit effective in the workspace; an explicit sync/update reconciles changes. Inspect the workspace Git status after the update.
Incorrect Answers
B:A commit SHA identifies an exact reviewed source snapshot; a moving branch label alone cannot prove which version was deployed.
C:Git integration versions supported Fabric item definitions and enables review before syncing changes to shared workspaces.
D:Blindly overwriting either side can discard work; Fabric Git conflict resolution requires deciding which definition becomes authoritative.
Question 35
A developer edited a notebook in Fabric but the remote repository still shows the prior version. Which direction of sync is required?
- Commit the supported local workspace changes to the connected Git branch.
- Check Fabric Git integration support for that particular item type and configuration.
- Update the workspace's Git connection to the approved repository and branch.
- Review the conflicting versions and explicitly choose or merge the desired item definition before synchronizing.
Explanation
Correct Answer
A:Workspace-to-Git commit publishes item definitions to version control; updating from Git performs the opposite direction. Check the resulting commit diff in the repository.
Incorrect Answers
B:Not every Fabric item and setting has identical Git serialization support; absence from status is not proof that the workspace item was deleted.
C:Branch association determines the source-control state with which the workspace synchronizes; a deployment pipeline stage does not select that Git branch.
D:Blindly overwriting either side can discard work; Fabric Git conflict resolution requires deciding which definition becomes authoritative.
Question 36
An item type does not appear among the pending Git changes even though it is in the workspace. What should be confirmed first?
- Commit the supported local workspace changes to the connected Git branch.
- Record the tested Git commit identifier and promote the matching definition across release stages.
- Review the conflicting versions and explicitly choose or merge the desired item definition before synchronizing.
- Check Fabric Git integration support for that particular item type and configuration.
Explanation
Correct Answer
D:Not every Fabric item and setting has identical Git serialization support; absence from status is not proof that the workspace item was deleted. Compare the item type against the current supported-items matrix.
Incorrect Answers
A:Workspace-to-Git commit publishes item definitions to version control; updating from Git performs the opposite direction.
B:A commit SHA identifies an exact reviewed source snapshot; a moving branch label alone cannot prove which version was deployed.
C:Blindly overwriting either side can discard work; Fabric Git conflict resolution requires deciding which definition becomes authoritative.
Question 37
Two engineers have conflicting notebook changes in Git and Fabric. How should the conflict be resolved safely?
- Commit the supported local workspace changes to the connected Git branch.
- Update the workspace's Git connection to the approved repository and branch.
- Record the tested Git commit identifier and promote the matching definition across release stages.
- Review the conflicting versions and explicitly choose or merge the desired item definition before synchronizing.
Explanation
Correct Answer
D:Blindly overwriting either side can discard work; Fabric Git conflict resolution requires deciding which definition becomes authoritative. Verify the resolved notebook content and commit history.
Incorrect Answers
A:Workspace-to-Git commit publishes item definitions to version control; updating from Git performs the opposite direction.
B:Branch association determines the source-control state with which the workspace synchronizes; a deployment pipeline stage does not select that Git branch.
C:A commit SHA identifies an exact reviewed source snapshot; a moving branch label alone cannot prove which version was deployed.
Question 38
A workspace is connected to an unintended repository branch. What configuration should be corrected?
- Check Fabric Git integration support for that particular item type and configuration.
- Update the workspace's Git connection to the approved repository and branch.
- Connect the development workspace to supported Git integration with an agreed branching workflow.
- Review the conflicting versions and explicitly choose or merge the desired item definition before synchronizing.
Explanation
Correct Answer
B:Branch association determines the source-control state with which the workspace synchronizes; a deployment pipeline stage does not select that Git branch. Check the connected branch in workspace Git settings.
Incorrect Answers
A:Not every Fabric item and setting has identical Git serialization support; absence from status is not proof that the workspace item was deleted.
C:Git integration versions supported Fabric item definitions and enables review before syncing changes to shared workspaces.
D:Blindly overwriting either side can discard work; Fabric Git conflict resolution requires deciding which definition becomes authoritative.
Question 39
A production team wants immutable traceability of exactly which source change was tested. What should be recorded?
- Record the tested Git commit identifier and promote the matching definition across release stages.
- Update the workspace's Git connection to the approved repository and branch.
- Review the incoming changes and use the supported update-from-Git workflow.
- Review the conflicting versions and explicitly choose or merge the desired item definition before synchronizing.
Explanation
Correct Answer
A:A commit SHA identifies an exact reviewed source snapshot; a moving branch label alone cannot prove which version was deployed. Compare release metadata with the tested commit hash.
Incorrect Answers
B:Branch association determines the source-control state with which the workspace synchronizes; a deployment pipeline stage does not select that Git branch.
C:Connecting a branch does not automatically make every remote commit effective in the workspace; an explicit sync/update reconciles changes.
D:Blindly overwriting either side can discard work; Fabric Git conflict resolution requires deciding which definition becomes authoritative.
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.
