The correct answer is to trim the text columns in both tables before merging. This step removes any leading or trailing spaces that would otherwise cause mismatches during the merge operation, because Power Query treats "Product" and "Product " as entirely different values. On the PL-300 exam, this scenario tests your understanding of data cleaning prerequisites for relational operations—a common trap is assuming that a merge will automatically ignore whitespace, when in fact it performs an exact character-by-character match. A reliable memory tip is "Trim before you join," ensuring both sides of the merge are normalized. Additionally, while trimming addresses spaces, you may also need to use the Transform tab to change case to uppercase for both columns if case sensitivity is an issue, further ensuring the merge works correctly with leading or trailing spaces.
PL-300 Prepare the data Practice Question
This PL-300 practice question tests your understanding of prepare the data. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are working with a Power Query that uses a merge operation between two tables. The merge is based on a column with text values, but some values have leading or trailing spaces. Which THREE steps can you take to ensure the merge works correctly?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the 'Transform' tab to change the case to uppercase for both columns.
Option A is correct because using the 'Transform' tab to change the case to uppercase for both columns ensures that the merge operation is case-insensitive, which is necessary when text values have leading or trailing spaces but also differ in case. This step normalizes the text values, making the merge more reliable by eliminating case mismatches that could cause the merge to fail or produce incorrect results.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Use the 'Transform' tab to change the case to uppercase for both columns.
Why this is correct
This normalizes case, which helps if there are case differences.
Related concept
Read the scenario before looking for a memorised answer.
✗
Remove duplicate rows from both tables.
Why it's wrong here
Duplicates are not the issue; spaces are.
✓
Create a custom column that contains the trimmed and normalized value, then merge on that column.
Why this is correct
This ensures consistency without altering original data.
Related concept
Read the scenario before looking for a memorised answer.
✗
Split the column by delimiter and merge on the first part.
Why it's wrong here
Splitting may not be relevant.
✓
Trim the text columns in both tables before merging.
Why this is correct
Trimming removes leading/trailing spaces.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think removing duplicates or splitting columns solves the whitespace issue, but only trimming and case normalization directly address the root cause of mismatched text values due to spaces and case differences.
Detailed technical explanation
How to think about this question
In Power Query, the merge operation uses exact string matching by default, so any leading or trailing spaces cause mismatches even if the visible text is identical. Trimming (using Text.Trim) removes these spaces, while changing case to uppercase (using Text.Upper) ensures case-insensitive matching; both steps can be applied via the Transform tab or in the M language. In real-world scenarios, data imported from legacy systems or user input often contains inconsistent whitespace and case, making these transformations critical for accurate joins.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Prepare the data — This question tests Prepare the data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use the 'Transform' tab to change the case to uppercase for both columns. — Option A is correct because using the 'Transform' tab to change the case to uppercase for both columns ensures that the merge operation is case-insensitive, which is necessary when text values have leading or trailing spaces but also differ in case. This step normalizes the text values, making the merge more reliable by eliminating case mismatches that could cause the merge to fail or produce incorrect results.
What should I do if I get this PL-300 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.