PL-300 domain - 24% of the exam

Prepare the Data

Prepare the Data is 24% of the PL-300 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

53
Practice questions
3
Objectives
10
Easy
32
Medium
11
Hard

Where people go wrong

  • Swapping the DirectQuery limits

    The wrong options for DirectQuery limits offer the wrong number, and some are real figures from elsewhere. The 32,764 long-text character limit is offered as a row cap, beside 100,000 and ten million. Any query or intermediate operation returning more than 1,000,000 rows fails. The per-query timeout is 4 minutes, while 30 seconds is where usability begins to degrade and 15 minutes is the minimum tile refresh interval. The default per-file connection cap is 10.

    See it in a sample question
  • Giving Direct Lake on OneLake the behaviour of Direct Lake on SQL

    The wrong options credit Direct Lake on OneLake with fallback to DirectQuery, or place the restrictions on the other variant. Direct Lake on SQL is the variant that falls back to DirectQuery when a guardrail is reached, provided fallback stays enabled. On OneLake, a reached guardrail makes the model unqueryable until the Delta tables are optimised. The documented OneLake restrictions are no personal workspaces, no gateways and no cross-region models, not calculated columns or auto date/time.

    See it in a sample question
  • Misplacing which Power Query features are Online-only

    The wrong options misplace which Power Query features depend on the edition. Fuzzy grouping in the Group by dialog is only available in Power Query Online, so an analyst on Power BI Desktop cannot find the checkbox, and switching between Basic and Advanced mode or changing the column type does not change that. Don't aggregate, under the Advanced option of the pivot dialog, is the opposite case: it is available in both Online and Desktop, so an option calling it Online-only is wrong.

    See it in a sample question
  • Trusting a data type that looks adequate

    The wrong options lean on a type that looks adequate. Decimal number is a 64-bit floating-point type that cannot represent every number in its range exactly, and Percentage inherits the same concern, so currency belongs in Fixed decimal number, which is always precise. Detect data type interprets values using the document locale, so a United Kingdom day/month/year column in an English (United States) file still errors. Change type, Using locale, with English (United Kingdom) resolves it.

    See it in a sample question
  • Misreading how Merge and Append match and update queries

    The wrong options assume the wrong matching rule or the wrong target. A multi-column Merge pairs columns in selection order, so the first column selected on the left meets the first on the right. Identical column names are not required, and pre-sorting does not decide the match. Append matches columns by header name rather than position, and the query it is run from gains the appended step while the other table is unchanged.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free samplePrepare the Datamedium

A DirectQuery visual against Azure SQL Database fails with an error after a filter is removed. Which documented intermediate-result limit is the most likely cause?

  • AAny query or intermediate operation that returns more than 100,000 rows fails outside Premium-raised limits.
  • BAny query or intermediate operation that returns more than 32,764 rows fails outside Premium-raised limits.
  • CAny query or intermediate operation that returns more than 10,000,000 rows fails outside Premium-raised limits.
  • DAny query or intermediate operation that returns more than 1,000,000 rows fails outside Premium-raised limits. Correct
The DirectQuery intermediate-row cap is one million rows outside Premium-raised limits. DirectQuery documentation states any query or intermediate operation returning more than 1,000,000 rows fails and that Premium capacities can raise this limit.

Why A is wrong: The documented DirectQuery row cap is one million rows, not one hundred thousand; 100,000 is not the cited threshold.

Why B is wrong: 32,764 is the long-text column character limit, not the DirectQuery row limit; the documented DirectQuery row cap is one million.

Why C is wrong: The documented DirectQuery intermediate-row cap is one million rows; ten million is not cited as the failure threshold.

Why D is correct: Correct. DirectQuery documentation states any query or intermediate operation returning more than 1,000,000 rows fails and that Premium capacities can raise this limit.

Free samplePrepare the Datahard

A semantic-model designer needs DirectQuery fallback when a Delta guardrail is reached, because the report cannot fail under any condition. Which Direct Lake variant should be configured?

  • ADirect Lake on OneLake with fallback enabled so queries fall back to DirectQuery when a guardrail is reached.
  • BDirect Lake on OneLake with composite Import tables so queries fall back to Import when a guardrail is reached.
  • CDirect Lake on SQL with fallback disabled so queries fall back to DirectQuery when a guardrail is reached.
  • DDirect Lake on SQL with fallback enabled so queries fall back to DirectQuery when a guardrail is reached. Correct
Only Direct Lake on SQL supports DirectQuery fallback when guardrails or unsupported objects are hit. Direct Lake on SQL falls back to DirectQuery mode when it cannot load directly from a Delta table or when a guardrail is exceeded, with the Direct Lake behavior model property controlling this. Direct Lake on OneLake does not fall back to DirectQuery via the SQL endpoint and fails refresh instead.

Why A is wrong: Direct Lake on OneLake does not fall back to DirectQuery; if a guardrail is reached the refresh fails and the model becomes unqueryable until the Delta tables are optimized.

Why B is wrong: Adding Import tables to a Direct Lake on OneLake composite model does not give DirectQuery fallback for the Direct Lake tables themselves.

Why C is wrong: Disabling fallback removes the safety net; fallback to DirectQuery requires fallback to remain enabled on the Direct Lake on SQL model.

Why D is correct: Correct. Direct Lake on SQL falls back to DirectQuery mode when it cannot load directly from a Delta table or when a guardrail is exceeded, with the Direct Lake behavior model property controlling this.

Free samplePrepare the Datahard

An analyst on Power BI Desktop wants to enable Use fuzzy grouping inside the Group by dialog. The checkbox is not visible. Which statement explains the most likely cause?

  • AFuzzy grouping requires the Group by dialog to be in Basic mode rather than Advanced mode.
  • BFuzzy grouping requires the data type of the grouping column to be Whole number for the checkbox to appear.
  • CFuzzy grouping is only available in Power Query Online, not in Power Query Desktop. Correct
  • DFuzzy grouping requires the View tab Column profile feature to be enabled before the checkbox appears.
Fuzzy grouping is Power Query Online-only; Desktop does not expose the checkbox. The Group by article explicitly notes that fuzzy grouping is only available in Power Query Online. Desktop users see the Group by dialog without the Use fuzzy grouping checkbox.

Why A is wrong: Fuzzy grouping is exposed inside the Group by dialog regardless of Basic or Advanced mode in Online; mode does not gate visibility.

Why B is wrong: Fuzzy grouping is text-oriented and uses similarity thresholds; it is not enabled by switching grouping columns to Whole number.

Why C is correct: Correct. The Group by article explicitly notes that fuzzy grouping is only available in Power Query Online.

Why D is wrong: Column profile and Group by are independent features; profiling toggles do not gate the fuzzy grouping checkbox.

Free samplePrepare the Datamedium

A finance analyst needs to store currency amounts with precise rounding behaviour to avoid floating-point artefacts in reports. Which data type does the Power Query documentation recommend for this scenario?

  • AUse the Decimal number type, which offers the highest precision available for currency values.
  • BUse the Percentage type, which is internally a Decimal number with a formatting mask applied.
  • CUse the Fixed decimal number type, which fixes the decimal separator and is always precise. Correct
  • DUse the Whole number type, which avoids decimal-separator rounding by truncating fractional values.
Fixed decimal number is the precise currency-style type; Decimal number is floating-point and can drift. The Data Types article describes Fixed decimal number, also known as the Currency type, as having a fixed location for the decimal separator with four digits to its right, 19 digits of significance, and notes it is always precise, unlike Decimal Number where floating-point representation may introduce minor precision differences.

Why A is wrong: Decimal number is a 64-bit floating-point type; the documentation warns it cannot represent all numbers within its range with 100% accuracy and may introduce minor precision differences.

Why B is wrong: Percentage is fundamentally the same as Decimal number with a display mask; it inherits the same floating-point precision concerns and is not designed for currency.

Why C is correct: Correct. The Data Types article describes Fixed decimal number, also known as the Currency type, as having a fixed location for the decimal separator with four digits to its right, 19 digits of significance, and notes it is always precise, unlike Decimal Number where floating-point representation may introduce minor precision differences.

Why D is wrong: Whole number stores integers only, so any currency cents value would be truncated; this is not a precise representation of monetary amounts.

Free samplePrepare the Datahard

An analyst configures a multi-column merge between two tables by Ctrl-clicking to pick the join columns. Which behaviour does the Merge queries article describe for the column selection order?

  • AThe columns must have identical names in both tables for the merge to find matches correctly.
  • BThe columns can be selected in any order on each side; Power Query auto-aligns them by data type compatibility.
  • CThe order in which columns are selected in each table must match between the left and right tables. Correct
  • DThe columns must be sorted ascending on both tables before opening the Merge dialog or join keys mismatch.
Multi-column merges align by selection order, not by column name; clicks must be in the same order on each side. The Merge queries article warns that when multiple columns are selected for a join, the order of selection in each table must match, because the first selected column on the left is matched with the first on the right, and so on. Otherwise the merge can yield incorrect results.

Why A is wrong: Identical column names are not required; the article explicitly notes that matching column names is not a requirement for the merge operation.

Why B is wrong: Power Query does not auto-align multi-column joins. The first selection on the left matches the first selection on the right, and so on; selection order is the alignment rule.

Why C is correct: Correct. The Merge queries article warns that when multiple columns are selected for a join, the order of selection in each table must match, because the first selected column on the left is matched with the first on the right, and so on.

Why D is wrong: Pre-sorting is not a requirement of the Merge dialog. Match alignment uses selection order, not sort order.

Other domains in this exam

See also the PL-300 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.