DP-600 Microsoft Implementing Analytics Solutions Using Microsoft Fabric Free Practice Exam Questions (2026 Updated)

Comprehensive Detailed Explanation

Requirement

Tenant: Fabric tenant Tenant1

Data target: Lakehouse1

Data source: CSV file in an Azure Storage account (outside of Fabric)

Requirement: Minimize development effort

Step 1: Understand options

A. Dataflow Gen2

Used for ETL (transformations, cleansing, ingestion).

More effort because you need to build Power Query transformations.

Not minimal effort for simply exposing a file.

B. Shortcut

Fabric supports creating shortcuts to external data sources (OneLake, ADLS Gen2, Azure Blob, Dataverse, etc.).

Shortcut directly exposes external files/tables inside the lakehouse without copying or moving data .

This is the lowest-effort solution to access external CSV.

C. Copy job

Pipelines have a copy activity to physically copy data into Fabric.

Requires setup and execution. More development effort than a shortcut.

D. Pipeline

Used for orchestrating complex ETL workflows.

Overhead for this scenario.

Step 2: Correct Answer

Since the goal is simply to access a CSV in external storage with minimal development effort , the right solution is:

B. a shortcut

References

Shortcuts in Microsoft Fabric OneLake

Dataflow Gen2 overview

There is no USEROBJECT() function in DAX. The correct functions available are USERNAME() and USERPRINCIPALNAME() .

USERPRINCIPALNAME() is the one that returns the UPN directly.

Since the solution refers to a non-existent function ( USEROBJECT() ), it cannot solve the problem.

Correct approach: Update the measure to use USERPRINCIPALNAME() , not USEROBJECT() .

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

You need to recommend which type of Fabric capacity SKU meets the data analytics requirements for the Research division.

Requirement: “The Research division workspaces must use a dedicated, on-demand capacity that has per-minute billing.”

Fabric capacity SKUs:

F (Fabric) = dedicated Fabric capacity, available on pay-as-you-go with per-minute billing.

P (Premium) and EM are Power BI capacities (not Fabric-native).

A refers to Azure Analysis Services capacity.

The only correct option is F SKU .

In Microsoft Fabric, the OneLake endpoint allows users with appropriate permissions to read data from a lakehouse, leveraging the unified data storage system. Since DBUser has been granted access to Lakehouse1, they can utilize the OneLake endpoint for reading data. For querying, the OneLake file explorer provides a user interface to interact with and query data within the lakehouse, aligning with DBUser ' s access rights without requiring broader tenant permissions.

Comprehensive Detailed Explan ation

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

Requirement: “The number of rows added to the Orders table during refreshes must be minimized.”

The Orders table has a sequential OrderID .

To minimize refresh size, you must only import new rows , not the entire table.

This requires retrieving the maximum OrderID currently loaded, then only loading rows with a greater OrderID.

So, the correct solution is to use a pipeline (ADF) with a dataflow to retrieve the maximum OrderID .

Answer: C. an Azure Data Factory pipeline that executes a dataflow to retrieve the maximum value of the OrderID column in the destination lakehouse

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 Se lections:

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

A lakehouse (A) is the type of data store you should use. It supports dat aflows 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.

Scenario:

Semantic model contains a measure: TotalSalesAmount .

This measure returns sales revenue translated into a selected currency .

Requirement: Format the result using the correct currency symbol dynamically.

Analysis:

Dynamic format string in DAX is specifically designed for applying formats (like currency symbols) dynamically based on slicers or calculation context.

WINDOW function → used for windowing calculations, not formatting.

Linguistic schema → used for Q & A natural language, not for formatting.

Field parameter → used to swap fields/measures dynamically, not for formatting.

Correct Answer:

A. A dynamic format string

When deploying via the XMLA endpoint , deployment time is impacted by the storage format of the semantic model.

Large semantic model storage format (also known as Premium/Large models) supports more efficient processing and partitioned deployments, reducing overall deployment time for large models.

Small semantic model storage format is for smaller models and limits partitioning capabilities.

" Users can edit data models in the service " is unrelated to deployment optimization.

" Enable Cache for Shortcuts " improves query performance for shortcut data, not model deployment.

Correct answer: C

GRANT ALTER ON SCHEMA::schemaA TO User1;

The ALTER permission allows a user to modify the schema of an object, and granting ALTER on a schema will allow the user to perform operations like TRUNCATE TABLE on any object within that schema. It is the correct permission to grant to User1 for truncating tables in schemaA .

References =

GRANT Schema Permissions

Permissions That Can Be Granted on a Schema

You need to configure OneLake security for two users with the following requirements:

User1 : Read all the Spark data

User2 : Read all the SQL endpoint data

The available permissions are: Read , ReadAll , and ReadData .

Understanding the permissions:

Read → Grants access to metadata but not the data itself.

ReadData → Grants access to query data through SQL endpoints (SQL-based access).

ReadAll → Grants access to read data across all engines (including Spark and SQL endpoints).

Applying least privilege principle:

User1 (Spark access): Needs to read all the Spark data → Assign ReadAll because Spark requires this permission to access data in OneLake.

User2 (SQL endpoint access): Needs to read SQL endpoint data only → Assign ReadData , as this grants access to SQL endpoints without over-provisioning Spark access.

Final Answer:

User1: ReadAll

User2: ReadData