PL-300 Prepare the data Practice Question
Your Power BI dataset uses a SQL view that joins multiple tables. You notice that some columns have null values where you expect data. You suspect the view definition has a bug. How can you verify the view's output in Power Query?
⚠ Common exam trap
Test-takers frequently confuse 'View Native Query' (which shows the folded query after transformations) with the ability to run the original view SQL directly, leading them to choose option C instead of B.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a new query that runs the view's SQL directly against the source
Creating a new query that runs the view's SQL directly against the source in Power Query allows you to isolate and execute the exact SQL statement, bypassing any transformations or folding issues. This lets you compare the raw output from the source with the view's expected results, directly verifying if the view definition itself contains a bug. It is the most straightforward method to confirm whether the null values originate from the view or from subsequent Power Query steps.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Check the 'Table Preview' in the data model
Why it's wrong here
The Table Preview in the data model displays the data as loaded into the model, after all Power Query transformations have been applied. It does not show the original SQL view output; any filtering, column changes, or data type conversions are already baked in. Therefore, it cannot be used to verify the raw result set of the view.
- ✓
Create a new query that runs the view's SQL directly against the source
Why this is correct
By creating a new Power Query query that executes the view's SQL statement directly against the source database, you bypass any existing transformations and fetch the exact rows and columns the view returns. This gives you an independent, unfiltered look at the view's output, allowing you to compare it against what the dataset actually uses. This is the only method listed that reliably exposes the raw view result set.
- ✗
Use 'View Native Query' in Power Query
Why it's wrong here
The View Native Query feature in Power Query displays the native query (e.g., SQL statement) that Power Query generates for the current transformation step, which may include filters, JOINs, or other pushdown operations. It reveals the exact query sent to the source, but it does not execute or return the resulting data, so you cannot see the view's raw output. It is useful for troubleshooting query folding, not for inspecting the view's result set.
- ✗
Use 'Data Profiling' in Power Query
Why it's wrong here
Data Profiling in Power Query provides column-level statistics such as value counts, null counts, minimum/maximum, and distribution, based on the current transformed data. It does not display the actual rows of the view or the raw output of the SQL view; it only summarizes the data after all steps have been applied. Thus, it cannot be used to directly view the view's original result set.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-300 question from scratch — 217 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PL-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-300 exam.