Practice Free DP-600 Implementing Analytics Solutions Using Microsoft Fabric Exam Questions Answers With Explanation

In Azure DevOps workspace (project) security settings, role assignments determine access levels for groups:

Viewer (equivalent to the Readers security group): Grants read-only access to work items, code, pipelines, and other artifacts. Ideal for review-only scenarios where users need to view but not edit content.

Contributor (equivalent to the Contributors security group): Allows full edit and contribute privileges, such as updating work items, code reviews, and pipeline runs. Suitable for active participation in reviews that may involve feedback or changes.

Based on the group names implying review-focused access, Viewer fits Group1 for passive observation, while Contributor fits Group2 for interactive review tasks. These align with default Azure DevOps permissions for secure, least-privilege access.

The goal is to denormalize the data into a customer dimension with one row per distinct CustomerID, minimizing query processing time and resources. Since each customer is associated with a single SalesRegion and a single CustomerAddress, and all foreign key values are non-null, a left outer join is appropriate to ensure all customers from the Customer table are included, even if there are any unexpected missing addresses (though the problem states each customer has a single address). However, given the non-null foreign key constraint, an inner join could also work, but left outer join is safer and aligns with denormalization to ensure completeness.

The join condition should link the Customer table (C) with the CustomerAddress table (CA) using CustomerID, as this ensures each customer ' s address data is included.

The join with SalesRegion (SR) on SalesRegionID is already included in the query, and since each customer has a single SalesRegion, it fits the denormalization requirement.

The where CA.AddressType = ' Main Office ' filter ensures only the main office address is included, which is a valid constraint for a customer dimension.

Thus, the completed T-SQL statement would effectively denormalize the data while minimizing resource use by leveraging the existing relationships and constraints.

Comprehensive Detailed Explanation

Requirement

We have two columns in Power Query Editor:

Order_Date

Shipping_Date

We need to calculate the number of days between the two dates.

Step 1: How date differences work in Power Query (M language)

Subtracting two date or datetime values in Power Query returns a duration value.

Example:

[Shipping_Date] - [Order_Date]

This produces a duration such as 3.00:00:00 (3 days).

Step 2: Converting duration into days

To get the number of days as an integer, we use Duration.Days().

Example:

Duration.Days([Shipping_Date] - [Order_Date] )

This returns 3 if the shipping date is 3 days after the order date.

Step 3: Evaluate other options

A. Duration.From ? Converts a value to a duration type but does not extract the number of days.

B. Date.AddDays ? Adds days to a given date, not used for calculating the difference.

C. Duration.Days ? Correct, extracts total days from a duration.

D. DateTime.LocalNow ? Returns the current system datetime, unrelated to this requirement.

References

Duration.Days function (Power Query M)

Working with dates in Power Query

Comprehensive Detailed Explanation

The requirement is to logically group the Research division workspaces and support filtering in the OneLake data hub.

Why Domain?

Microsoft Fabric allows you to assign workspace domains (e.g., Finance, HR, Research).

This provides a logical grouping of workspaces within the organization.

Domains are the only supported way to enable filtering in OneLake data hub by department.

Capacity or tenant grouping would not allow filtering by department in OneLake.

Why OneLake data hub?

The OneLake data hub is the centralized interface to browse and discover data assets across the organization.

With workspace domains configured, users can filter directly in the OneLake data hub by domain (e.g., “Research”).

The Fabric Admin portal and Entra admin center are used for administration, not for workspace filtering in data discovery.

Correct Selection for the Hotspot

Grouping method: Domain

Tool: OneLake data hub

References

Workspace domains in Microsoft Fabric

Discover and filter data in OneLake data hub

Final Answer:

Grouping method = Domain

Tool = OneLake data hub

A lakehouse (A) is the type of data store you should use. It supports dataflows to load and append data and ensures that Delta tables are Z-Order optimized and compacted automatically. References = The capabilities of a lakehouse and its support for Delta tables are described in the lakehouse and Delta table documentation.

Comprehensive Detailed Explanation

From the case study:

Research division data for Productline2 is currently in CSV format in storage2.

Requirement: “All the Research division data in the lakehouses must be presented as managed tables in Lakehouse explorer.”

In Fabric lakehouses, managed tables are stored in Delta format inside the Tables folder.

Step 1: Reading the source

df = spark.read.format( " csv " ) \

options(header= " true " , inferSchema= " true " ) \

load( " abfss://storage1.dfs.core.windows.net/files/productline2 " )

This correctly ingests the CSV source from ADLS Gen2.

Step 2: Writing to Lakehouse as a managed table

You must write the data in Delta format to ensure it is queryable and managed within the lakehouse.

The correct path is under Tables/, because this is where Fabric automatically manages Lakehouse managed tables.

The target table should be named productline2, so the correct path is:

df.write.mode( " overwrite " ).format( " delta " ).save( " Tables/productline2 " )

Why not other options?

CSV or Parquet formats would not create a managed Lakehouse table; they would just create files.

Writing to productline2 directly (without Tables/) would store unmanaged files in the Lakehouse Files area, not managed tables.

Writing to Tables/research/productline2 adds an unnecessary subdirectory and is not the standard structure for managed tables.

Correct Final Code

df.write.mode( " overwrite " ).format( " delta " ).save( " Tables/productline2 " )

References

Managed tables in Microsoft Fabric Lakehouse

Delta Lake support in Fabric

Spark write to Lakehouse

The df.explain() method does not meet the goal of evaluating data to calculate statistical functions. It is used to display the physical plan that Spark will execute. References = The correct usage of the explain() function can be found in the PySpark documentation.

Based on the duration breakdown provided, the major contributor to the rendering duration is categorized as " Other, " which is significantly higher than DAX Query and Visual display times. This suggests that the issue is less likely with the DAX calculation or visual rendering times and more likely related to model performance or the complexity of the visual. However, of the options provided, optimizing the DAX query can be a crucial step, even if " Other " factors are dominant. Using DAX Studio, you can analyze and optimize the DAX queries that power your visuals for performance improvements. Here’s how you might proceed:

Open DAX Studio and connect it to your Power BI report.

Capture the DAX query generated by the Orders By Date visual.

Use the Performance Analyzer feature within DAX Studio to analyze the query.

Look for inefficiencies or long-running operations.

Optimize the DAX query by simplifying measures, removing unnecessary calculations, or improving iterator functions.

Test the optimized query to ensure it reduces the overall duration.

Step 1: Requirement

We need to calculate total sales amount by OrderDate.

Total Sales Amount = Quantity × UnitPrice per row.

Then SUM over all rows per OrderDate.

Only include rows where the OrderDate matches a public holiday in Australia.

Step 2: Calculation Logic

If we select s.Quantity * s.UnitPrice, it only computes row-level values.

To calculate the total sales amount per OrderDate, we need:

SUM(s.Quantity * s.UnitPrice) AS TotalSalesAmt

Thus, the correct calculation: SUM(s.Quantity * s.UnitPrice)

Step 3: Join Type

We want to return only those sales that occurred on public holidays in Australia.

If we used a LEFT JOIN, we’d include all sales regardless of holiday.

A FULL OUTER JOIN would include non-matching rows, not required.

A CROSS JOIN would duplicate results unnecessarily.

A RIGHT OUTER JOIN would include holidays with no sales, which is not needed.

The correct choice is an INNER JOIN on matching dates.

Step 4: Final Query

SELECT

s.OrderDate,

SUM(s.Quantity * s.UnitPrice) AS TotalSalesAmt

FROM dbo.sales AS s

INNER JOIN dbo.publicholidays AS ph

ON s.OrderDate = ph.Date

WHERE ph.countryOrRegion = ' Australia '

GROUP BY s.OrderDate;

Why This is Correct

SUM(s.Quantity * s.UnitPrice) ? ensures sales are aggregated correctly.

INNER JOIN ? ensures only rows where OrderDate matches a holiday are included.

WHERE ph.countryOrRegion = ' Australia ' ? filters holidays to Australia only.

References

SUM (Transact-SQL)

JOIN operations in T-SQL

User1 must be able to:

Create a new domain.

Create two subdomains.

Assign Workspace1 to subdomain1.

Assign Workspace2 to subdomain2.

Key Role Definitions in Fabric:

Domain admin: Can manage domain settings, add/remove workspaces, manage contributors.

Domain contributor: Can contribute to an existing domain but cannot create a domain.

Workspace admin: Only controls permissions/settings inside a workspace, not domains.

Fabric admin: Tenant-wide admin, broader than required.

Requirement: Follow least privilege.

To create a new domain ? Requires Domain admin.

To assign workspaces to subdomains ? Domain admin rights are sufficient.

Fabric admin is excessive and breaks least privilege.

Correct Answer:

A. Domain admin

A possible cause for the failure is that query folding is NOT occurring (D). Query folding helps optimize refresh by pushing down the query logic to the source system, reducing the amount of data processed and transferred, hence conserving resources. References = The Power BI documentation on incremental refresh and query folding provides detailed information on this topic.

Scenario Recap

Fabric tenant ? Workspace1

Contains:

Lakehouse LH1 (with table signindata in schema dho)

Warehouse DW1

Task: Create a stored procedure in DW1 that deduplicates rows in signindata.

Step 1: Stored procedure structure

In T-SQL, stored procedures begin with:

AS

BEGIN

-- logic

END

So the correct option for the first blank is BEGIN.

BEGIN DISTRIBUTED TRANSACTION is not needed because we are not spanning multiple servers or needing distributed transactions.

SET is not the right way to start the logic block.

Step 2: Deduplication logic

To remove duplicates from signindata, the query should return unique rows.

The simplest way is:

SELECT DISTINCT PersonID, FirstName, LastName

FROM dho.signindata;

Thus the correct choice for the second blank is DISTINCT.

GROUP BY could also deduplicate but is less efficient here since no aggregation is requested.

TOP 100 PERCENT WITH TIES is irrelevant.

Step 3: Final T-SQL stored procedure

CREATE PROCEDURE dbo.usp_GetPerson

AS

BEGIN

SELECT DISTINCT PersonID, FirstName, LastName

FROM dho.signindata;

END;

Why this is correct

BEGIN ? correct stored procedure structure.

DISTINCT ? ensures deduplication of rows from signindata.

References

CREATE PROCEDURE (Transact-SQL)

DISTINCT (Transact-SQL)

We are designing a star schema for sales transactions. In a star schema:

Dimension tables contain descriptive attributes (e.g., Customer, Product, Date).

Fact tables contain measurable, quantitative data (e.g., SalesTransactionID, Quantity, UnitPrice).

Factless fact tables capture events without numeric measures.

Junk dimensions store miscellaneous low-cardinality attributes.

The requirement says dimension tables will use Type 2 Slowly Changing Dimensions (SCD) ? so Customer and Date attributes belong to Dimension tables.

Field-by-field classification

CustomerCode

A business key (natural key) for the customer dimension.

Belongs in the Customer Dimension table.

Answer: Dimension.

CustomerName

A descriptive attribute of the customer.

Belongs in the Customer Dimension table.

Answer: Dimension.

SaleDate

A time attribute used for analysis.

Belongs in the Date Dimension table.

Answer: Dimension.

Final Answer:

CustomerCode ? Dimension

CustomerName ? Dimension

SaleDate ? Dimension

For a Type 1 SCD, you should include actions that update rows when non-key attributes have changed (A), and insert new records when the natural key is a new value in the table (D). A Type 1 SCD does not track historical data, so you always overwrite the old data with the new data for a given key. References = Details on Type 1 slowly changing dimension patterns can be found in data warehousing literature and Microsoft ' s official documentation.

You should use CREATE VIEW to make the pricing group logic available for T-SQL queries.

The CASE statement should be used to determine the pricing group based on the list price.

The T-SQL statement should create a view that classifies products into pricing groups based on the list price. The CASE statement is the correct conditional logic to assign each product to the appropriate pricing group. This view will standardize the pricing group logic across different databases and semantic models.

A lakehouse (C) should be recommended for the AnalyticsPOC workspace. It combines the capabilities of a data warehouse with the flexibility of a data lake. A lakehouse supports semi-structured and unstructured data and allows for T-SQL and Python read access, fulfilling the technical requirements outlined for Litware. References = For further understanding, Microsoft ' s documentation on the lakehouse architecture provides insights into how it supports various data types and analytical operations.

For ingesting customer data into the data store in the AnalyticsPOC workspace, a dataflow (D) should be recommended. Dataflows are designed within the Power BI service to ingest, cleanse, transform, and load data into the Power BI environment. They allow for the low-code ingestion and transformation of data as needed by Litware ' s technical requirements. References = You can learn more about dataflows and their use in Power BI environments in Microsoft ' s Power BI documentation.

The PoC is planned to be completed using a Fabric trial capacity, which implies that users involved in the PoC should be able to try paid features. However, this should be limited to specific security groups involved in the PoC to prevent the entire organization from accessing these features before the trial is proven successful (A). The ability for users to create Fabric items should also be enabled for specific security groups to ensure that only the relevant team members participating in the PoC can create items in the Fabric environment (E).

The measure should use the AVERAGE function to calculate the average value.

It should reference the Response Value column from the ' Survey ' table.

The ' Number of months ' should be used to define the period for the average calculation.

To calculate the average overall satisfaction score using DAX, you would need to use the AVERAGE function on the response values related to satisfaction questions. The DATESINPERIOD function will help in calculating the rolling average over the last 12 months.

Comprehensive Detailed Explanation

When assigning permissions to roles in a Fabric workspace for analytics workloads, you must align permissions with the responsibilities and tools typically used by each persona:

1. Data Engineers

Their primary tasks include building and transforming data pipelines, as well as making datasets usable by others.

The appropriate permission is Build Reports on the default dataset, because this allows them to create and manage reports using the curated semantic model while preparing data for analysts and scientists.

2. Data Analysts

Analysts work heavily with Apache Spark for exploratory analysis, cleansing, and shaping data.

The correct permission is Read All Apache Spark, as this grants them the ability to query and analyze Spark-based data directly without elevated permissions that are unnecessary for their role.

3. Data Scientists

Data scientists often use SQL analytics endpoints to run queries, train models, and integrate data into machine learning workflows.

The correct permission is Read All SQL analytics endpoint data, since it enables direct programmatic access to the SQL endpoint, which is needed for advanced modeling and experimentation.

Summary of Selections:

DataEngineers ? Build Reports on the default dataset

DataAnalysts ? Read All Apache Spark

DataScientists ? Read All SQL analytics endpoint data

References (Microsoft Fabric – DP-600 exam scope):

Workspace roles and permissions in Microsoft Fabric

SQL analytics endpoint in Fabric

Apache Spark in Microsoft Fabric

Both a dataflow (A) and a Stored procedure activity in a pipeline (B) are capable of creating and populating a date dimension table. A dataflow can perform the transformation needed to create the date dimension, and it aligns with the preference for using low-code tools for data ingestion when possible. A Stored procedure could be written to generate the necessary date dimension data and executed within a pipeline, which also adheres to the technical requirements for the PoC.

For the semantic model design required for the customer satisfaction report, the choices for data source authentication method and mode should be made based on security and performance considerations as per the case study provided.

Authentication method: The data should be accessed securely, and given that row-level security (RLS) is required for users executing T-SQL queries, you should use an authentication method that supports RLS. Service principal authentication is suitable for automated and secure access to the data, especially when the access needs to be controlled programmatically and is not tied to a specific user ' s credentials.

Mode: The report needs to show data as soon as it is updated in the data store, and it should only contain data from the current and previous year. DirectQuery mode allows for real-time reporting without importing data into the model, thus meeting the need for up-to-date data. It also allows for RLS to be implemented and enforced at the data source level, providing the necessary security measures.

Based on these considerations, the selections should be:

Authentication method: Service principal authentication

Mode: DirectQuery

To meet the technical requirement that data loading activities must ensure the raw and cleansed data is updated completely before populating the dimensional model, you would need a mechanism that allows for ordered execution. A pipeline in Microsoft Fabric with dependencies set between activities can ensure that activities are executed in a specific sequence. Once set up, the pipeline can be scheduled to run at the required intervals (hourly or daily depending on the data source).