The Implementing Analytics Solutions Using Microsoft Fabric (DP-600)

Requirement Analysis

Sales table → Users should only see sales data for their own region .

This requires filtering rows based on a condition (e.g., Region = User’s Region).

The correct feature: Row-level security (RLS) .

Employees table → Restrict access to Personally Identifiable Informat ion (PII) while allowing access to non-sensitive columns.

This requires restricting access to specific columns (such as SSN, phone, address, etc.), but leaving others visible.

The correct feature: Column-level security .

Maintain access to unrestricted data for all users → Both RLS and column-level security allow users to continue accessing non-restricted data.

Why Other Options Are Not Correct

Item permissions : Control access at the object level (e.g., table or report), not at the row or column level. Too coarse for this requirement.

Workspace permissions : Apply at the workspace level, not suitable for table-level data filtering.

Completed Answer

Employees → Column-level security

Sales → Row-level security (RLS)

References

Row-level security in Microsoft Fabric

Column-level security in Microsoft Fabric

PBIR-Legacy format → No

Located in Power BI service → No

Opens in full edit mode → Yes

Comprehensive Detailed Explanation

We are analyzing a Power BI Report (PBIR) definition file in JSON format:

{

" version " : " 1.0 " ,

" byPa th " : {

" path " : " ../Sales.Dataset "

}

}

}

Step 1: Is this PBIR-Legacy?

PBIR-Legacy format is used when referencing a dataset hosted in the Power BI service (cloud).

In this case, the JSON uses byPath , which references a local dataset file ( Sales.Dataset ) in the pro ject folder , not a service dataset.

Therefore: No , it is not PBIR-Legacy.

Step 2: Where is the semantic model located?

The datasetReference points to ../Sales.Dataset .

That means the semantic model is stored locally in the project structure , not in the Power BI service.

Therefore: No , it is not located in the Power BI service.

Step 3: What happens when opening in Power BI Desktop?

Since the dataset reference is local ( byPath ), Power BI Desktop opens the semantic model in full edit mode (allowing schema, relationships, measures, etc. to be modified).

If it were PBIR-Legacy with a service model, only Live Connection mode would be available.

Therefore: Yes , Power BI Desktop opens it in full edit mode.

References

PBIR file structure in Power BI projects

Semantic model references: byPath vs byConnection

Final Answer:

PBIR-Legacy format → No

Located in Power BI service → No

Opens in full edit mode → Yes

The code embeds an existing Power BI report. - No

The code creates a Power BI report. - Yes

The code displays a summary of the DataFrame. - Yes

The code provided seems to be a snippet from a SQL query or script which is neither creating nor embedding a Power BI report directly. It appears to be setting up a DataFrame for use within a larger context, potentially for visualization in Power BI, but the code itself does not perform the creation or embedding of a rep ort. Instead, it ' s likely part of a data processing step that summarizes data.

References =

Introduction to DataFrames - Spark SQL

Power BI and Azure Databricks

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)

The KEEPFILTERS function modifies the way filters are applied in calculations done through the CALCULATE function. It can be particularly beneficial to replace the FILTER function with KEEPFILTERS when the filter context is being overridden by nested CALCULATE functions, which may remove filters that are being applied on a column. This can potentially reduce execution time because KEEPFILTERS maintains the existing filter c ontext and allows the nested CALCULATE functions to be evaluated more efficiently.

The correct DMV to identify what is preventing the report query from completing is sys.dm_pdw_exec_requests (D). This DMV is specific to Microsoft Analytics Platform System (previously known as SQL Data Warehouse), which is the environment assumed to be used here. It provides information about all queries and load commands currently running or that have recently run. References = You can find more about DMVs in the Microsoft documentation for Analytics Platform System.

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 Visua l 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.

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() .