Maintain the Analytics Development Lifecycle DP-600 Practice Questions (Page 2)

Questions 6–10

1. 6expert · hard

   You are deploying a semantic model to production using the XMLA endpoint. The model is currently in use by a live dashboard. You need to deploy a new version that includes a breaking change (removing a column). You want to avoid downtime and ensure that the dashboard continues to work until the change is ready. What should you do?

   • AUse the XMLA endpoint to replace the model in place, accepting a brief downtime.
   • BUse the REST API to update the model and then refresh the dashboard.
   • CDeploy the new version to a separate workspace, test it, and then switch the dashboard to the new workspace using a redirect.
   • DUse the deployment pipeline to deploy the change and then manually update the dashboard.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   You have a deployment pipeline with three stages: development, test, and production. You need to ensure that when you deploy from test to production, the semantic model's refresh schedule is not overwritten by the development stage's schedule. What should you configure?

   • ACreate a separate deployment pipeline for the refresh schedule.
   • BSet the refresh schedule as a stage-level parameter and exclude it from deployment rules.
   • CDisable the refresh schedule in the development stage.
   • DUse the XMLA endpoint to manually set the refresh schedule after each deployment.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   Your team uses Git for version control of Fabric items. You have a workspace that contains reports, semantic models, and dataflows. You want to ensure that only reports and semantic models are tracked in Git, while dataflows are excluded. What should you configure?

   • AIn the workspace Git settings, select the item types to include in version control.
   • BMove dataflows to a different workspace that is not connected to Git.
   • CUse the XMLA endpoint to export only reports and semantic models to Git.
   • DCreate a .gitignore file in the repository to exclude dataflows.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   You are planning to rename a column in a lakehouse table that is used by several downstream dataflows and semantic models. Before making the change, you need to identify all items that depend on this table so you can assess the impact. What should you use in Fabric?

   • AUse the deployment pipeline's deployment history to see which items were deployed.
   • BSearch the Git repository for references to the column name in code files.
   • CQuery the XMLA endpoint to list all semantic models that reference the table.
   • DRun the built-in impact analysis from the lakehouse item's context menu.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   Your team is developing a Power BI report using Power BI Desktop projects (.pbip). You want to integrate with Git for source control. However, you notice that the .pbip project contains a semantic model that is also used by other reports. You want to avoid duplicating the semantic model in each report's project. What is the best approach?

   • AKeep the semantic model in each .pbip project and use Git to manage changes.
   • BUse the XMLA endpoint to deploy the semantic model to each workspace and connect reports to it.
   • CUse a shared semantic model in a Fabric workspace and have each report connect to it, while keeping the report project in Git.
   • DCreate a .pbit template that includes the semantic model and use it for all reports.
   Reveal Solution Discussion Select an answer first