PL-300 Sample Questions & Answers

This formula uses the CALCULATE function to modify the filter context. The FILTER function iterates over a table specified by the ALL(Products) function. ALL(Products) removes any existing filters from the 'Products' table, ensuring the calculation considers all products initially. FILTER then applies a new condition to include only rows where the category is 'Bikes'. This correctly isolates the 'Bikes' category sales, ignoring other report filters on the 'Products' table.

The ALL function is used to remove filters from a table or columns. To create a measure that is unaffected by the 'Campaign Name' slicer, you would wrap the 'Campaigns' table or the 'Campaign Name' column within an ALL function inside a CALCULATE statement. For example: Total Budget = CALCULATE(SUM(Campaigns[Budget]), ALL(Campaigns)). This removes the filter context applied by the slicer, ensuring the sum is always calculated over all campaigns.

Creating a report page tooltip is the correct solution. You would create a new, smaller report page, enable it as a tooltip in the page settings, and add a visual (like a bar chart) showing sales by salesperson. Then, on the main matrix visual, you would set its tooltip property to use this new report page. This allows for rich, data-driven tooltips that provide additional context on hover.

Dynamic Row-Level Security (RLS) is the most scalable solution. It involves creating a single security role with a DAX filter expression that dynamically filters data based on the user's identity, typically their User Principal Name (UPN) or email. This requires a lookup table that maps users to their respective departments. This approach allows for a single report to serve all departments while ensuring data is securely filtered, and it is much easier to manage than creating separate reports or static roles for each department.

A Live Connection is required when connecting to SSAS, as it creates a direct link to the model without importing data or the model structure into Power BI. Because the SSAS instance is on-premises, an on-premises data gateway (in standard mode) is mandatory to act as a bridge, securely relaying queries from the Power BI service to the on-premises SSAS server. This combination ensures real-time data access.

The DATEDIFF function is designed to calculate the difference between two dates in a specified interval. The correct syntax is DATEDIFF( , , ). This formula correctly subtracts the start time from the end time and returns the result in minutes.

The drill-through feature requires you to define the target page ('Product Details') and specify which field will be used to pass the filter context.

This action designates the page as a valid drill-through target, making it appear in the context menu of source visuals.

This is a classic pattern for semi-additive measures like inventory or account balances. The LASTDATE function finds the last date in the current filter context (e.g., the end of a month or quarter). This is used within a CALCULATE function to modify the filter context of a standard headcount measure (like a COUNT of active employees) to evaluate it only at that specific last date, effectively giving the period-end value.

This statement is true. The publishing process separates the .pbix file into two distinct artifacts in the Power BI service: the report and the semantic model (dataset). This separation is fundamental to Power BI's architecture, promoting the creation of a 'golden dataset' that can be certified and reused as a single source of truth for multiple reports, ensuring consistency and manageability.

Field Parameters are the ideal feature for this scenario. They allow developers to create a parameter that contains a list of measures (or dimensions). This parameter can then be used in a slicer or filter, and its selection can be used to dynamically control which measure is displayed in the value field of a visual. This provides a user-friendly way to switch between different calculations without complex DAX or bookmarking tricks.