Free Microsoft DP-600 Practice Exam with Questions & Answers

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

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.

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

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.

Add the pickupDate column: .withColumn( " pickupDate " , df[ " pickupDateTime " ].cast( " date " ))

Filter the DataFrame: .filter( " fareAmount > 0 AND fareAmount < 100 " )

In PySpark, you can add a new column to a DataFrame using the .withColumn method, where the first argument is the new column name and the second argument is the expression to generate the content of the new column. Here, we use the .cast( " date " ) function to extract only the date part from a timestamp. To filter the DataFrame, you use the .filter method with a condition that selects rows where fareAmount is greater than 0 and less than 100, thus ensuring only positive values less than 100 are included.

When using XMLA endpoint for deployment or processing , the semantic model storage format impacts deployment times.

Small storage format allows faster metadata operations and shorter deployment times.

Large semantic model storage format is only needed for extremely large models ( > 10 GB dataset limit), and it increases deployment overhead.

The other options (B: service editing, C: cache for shortcuts) are unrelated to XMLA endpoint deployment performance.

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.

Requirements:

Revert to previous versions of Model1.

Identify differences between saved versions.

Publish from Power BI Desktop.

Edit item definition files with Visual Studio Code.

Analysis:

To meet version control and difference tracking requirements, you must use Git integration in the Fabric workspace.

To enable editing with VS Code, you must use PBIP format (Power BI Project), which saves report/model as a folder with definition JSON files (not PBIX).

PBIX is a single binary file, not suitable for Git versioning or editing definition files.

" Enable users to edit in service " is irrelevant.

Correct Answers:

A. Enable Git integration for Workspace1.

C. Save Model1 in Power BI Desktop as a PBIP file.

Remove the files: Run the VACUUM command on a schedule.

Combine the files: Set the optimizeWrite table setting. or Run the OPTIMIZE command on a schedule.

To remove files that are no longer used, the VACUUM command is used in Delta Lake to clean up invalid files from a table. To combine smaller files into larger ones, you can either set the optimizeWrite setting to combine files during write operations or use the OPTIMIZE command, which is a Delta Lake operation used to compact small files into larger ones.