Question #1
Case study -This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.To start the case study -To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.Overview -Contoso, Ltd. is a US-based health supplements company. Contoso has two divisions named Sales and Research. The Sales division contains two departments named Online Sales and Retail Sales. The Research division assigns internally developed product lines to individual teams of researchers and analysts.Existing Environment -Identity Environment -Contoso has a Microsoft Entra tenant named contoso.com. The tenant contains two groups named ResearchReviewersGroup1 and ResearchReviewersGroup2.Data Environment -Contoso has the following data environment:The Sales division uses a Microsoft Power BI Premium capacity.The semantic model of the Online Sales department includes a fact table named Orders that uses Import made. In the system of origin, the OrderID value represents the sequence in which orders are created.The Research department uses an on-premises, third-party data warehousing product.Fabric is enabled for contoso.com.An Azure Data Lake Storage Gen2 storage account named storage1 contains Research division data for a product line named Productline1. The data is in the delta format.A Data Lake Storage Gen2 storage account named storage2 contains Research division data for a product line named Productline2. The data is in the CSV format.Requirements -Planned Changes -Contoso plans to make the following changes:Enable support for Fabric in the Power BI Premium capacity used by the Sales division.Make all the data for the Sales division and the Research division available in Fabric.For the Research division, create two Fabric workspaces named Productline1ws and Productine2ws.In Productline1ws, create a lakehouse named Lakehouse1.In Lakehouse1, create a shortcut to storage1 named ResearchProduct.Data Analytics Requirements -Contoso identifies the following data analytics requirements:All the workspaces for the Sales division and the Research division must support all Fabric experiences.The Research division workspaces must use a dedicated, on-demand capacity that has per-minute billing.The Research division workspaces must be grouped together logically to support OneLake data hub filtering based on the department name.For the Research division workspaces, the members of ResearchReviewersGroup1 must be able to read lakehouse and warehouse data and shortcuts by using SQL endpoints.For the Research division workspaces, the members of ResearchReviewersGroup2 must be able to read lakehouse data by using Lakehouse explorer.All the semantic models and reports for the Research division must use version control that supports branching.Data Preparation Requirements -Contoso identifies the following data preparation requirements:The Research division data for Productline1 must be retrieved from Lakehouse1 by using Fabric notebooks.All the Research division data in the lakehouses must be presented as managed tables in Lakehouse explorer.Semantic Model Requirements -Contoso identifies the following requirements for implementing and managing semantic models:The number of rows added to the Orders table during refreshes must be minimized.The semantic models in the Research division workspaces must use Direct Lake mode.General Requirements -Contoso identifies the following high-level requirements that must be considered for all solutions:Follow the principle of least privilege when applicable.Minimize implementation and maintenance effort when possible.You need to ensure that Contoso can use version control to meet the data analytics requirements and the general requirements.What should you do?
Answer: C
The question requires implementing version control for Research division semantic models and reports that supports branching, while adhering to the least privilege principle and minimizing implementation and maintenance effort. This scenario aligns with DP-600 objectives covering Fabric collaboration, workspace configuration, and application lifecycle management for Fabric artifacts. The correct solution leverages native Fabric Git integration for workspaces, as custom versioning implementations add unnecessary overhead. Azure Repos is the optimal choice because Contoso already uses a Microsoft Entra tenant, and Azure Repos integrates natively with Entra identities, eliminating the need for separate identity management, reducing implementation effort, and simplifying permission assignment to meet least privilege requirements. Option Analysis:
A. Incorrect. Storing artifacts in Azure Data Lake Gen2 only provides raw storage, not built-in version control with branching support for Fabric semantic models and reports. Implementing custom versioning on top of ADLS Gen2 would significantly increase maintenance effort, violating the minimal effort requirement, and does not integrate natively with Fabric workspace artifact management.
B. Incorrect. While Fabric supports GitHub integration for Git, Contoso uses a Microsoft Entra tenant for identity management. Using GitHub would require configuring separate identity access or federation, adding implementation and maintenance overhead compared to native Azure Repos integration, which uses existing Entra identities directly, so it does not meet the minimal effort and least privilege requirements optimally.
C. Correct. Modifying Research workspaces to integrate with an Azure Repos repository enables native Fabric Git integration, which fully supports branching for version control of semantic models and reports as explicitly required. Azure Repos integrates seamlessly with Contoso's existing Microsoft Entra tenant, simplifying permission management to align with least privilege, and requires minimal custom implementation, meeting all stated requirements.
D. Incorrect. OneDrive provides only basic file version history, no support for branching which is explicitly required for the Research division's version control needs. It also does not integrate natively with Fabric workspace version control for semantic models and reports, so it cannot meet the requirements. Key Concepts:
1. Fabric Git Integration: This core Fabric feature enables connecting workspaces to Git repositories to track changes to artifacts including semantic models and reports, support branching for parallel development, and enable version rollback. It is a key DP-600 topic covering Fabric collaboration and application lifecycle management.
2. Least Privilege Access: This security principle requires granting users only the permissions required to perform their assigned tasks. Integrating Fabric with Azure Repos leverages existing Microsoft Entra identities, eliminating the need for separate credential management and simplifying implementation of least privilege access controls, a core DP-600 security objective.
3. Fabric Workspace Configuration: Workspace settings including Git integration, capacity assignment, and access control are core DP-600 topics, as workspaces are the primary container for Fabric artifacts, and aligning workspace configuration with business requirements is a critical exam objective. References:
Git integration in Microsoft Fabric overview, Configure Git integration for a Fabric workspace