PL-300 Question 72

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose B1

  * Answer: B. No * Explanation: Using a DAX FILTER expression does not limit how many rows are imported from SQL Server. DAX operates after the data is already loaded into the model (import mode) and only filters data at query/evaluation time in visuals/measures. It won’t reduce the volume of data brought into Power BI during development. * What would meet the goal instead: - Apply row reduction before loading in Power Query (Transform Data) so it folds back to SQL: Use Keep Top Rows, filters, or Table.FirstN while the folding icon is present. - Use a native SQL statement (e.g., SELECT TOP (100000) ... FROM dbo.Order WHERE ...) when connecting. - Use parameters (e.g., RangeStart/RangeEnd) and filter on a date column during development (commonly used with Incremental Refresh).

• Chose B2

  The FILTER function in DAX operates after data is already loaded into Power BI. Since the Order table has over 100 million records, using DAX filtering does not reduce the dataset size before import, meaning all data would still be loaded into memory, slowing down performance.

• Chose B1

  No, this solution does not meet the goal. The FILTER function in DAX is used for filtering data within the context of a DAX expression, usually for creating calculated columns, measures, or tables within a Power BI model. It does not help in importing a subset of data from the SQL Server table into Power BI. To import a sample of the data from a large SQL Server table during the development process, you should use Power Query to apply a filter at the query level. This way, only the filtered subset of data is imported into Power BI, making it more manageable and efficient.