The answer is to create a self-join relationship from Employees[EmployeeID] to Employees[ManagerID]. This is the correct first step because Power BI cannot interpret a parent-child hierarchy without a relational path that links each employee to their manager within the same table. By establishing this self-referential relationship, you enable the model to use DAX functions like PATH and PATHITEM to traverse the reporting structure and generate a natural hierarchy. On the Microsoft Power BI Data Analyst PL-300 exam, this concept tests your understanding of modeling complex organizational structures, often appearing in scenario-based questions where a flat table must be transformed into a drillable hierarchy. A common trap is attempting to create a calculated column or a separate table first, but the relationship must come before any DAX logic. Memory tip: think of it as a mirror—EmployeeID looks at ManagerID in the same table, reflecting the chain of command.
PL-300 Model the data Practice Question
This PL-300 practice question tests your understanding of model the data. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 have a Power BI model with a table 'Employees' that includes columns: 'EmployeeID', 'ManagerID', 'Name'. You need to create a hierarchy that shows the reporting structure. What should you do first?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "first"
Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a self-join relationship from Employees[EmployeeID] to Employees[ManagerID].
To create a hierarchy that shows the reporting structure in Power BI, you first need to establish a self-join relationship between the Employees table and itself, linking EmployeeID to ManagerID. This allows Power BI to traverse the parent-child relationship and build a natural hierarchy (e.g., using Parent-Child functions like PATH). Without this relationship, the model cannot understand how employees relate to their managers.
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.
✓
Create a self-join relationship from Employees[EmployeeID] to Employees[ManagerID].
Why this is correct
Self-join enables parent-child hierarchy.
Clue confirmation
The clue word "first" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Merge the Employees table with itself using Merge Queries.
Why it's wrong here
Merging would create a flat table, not a dynamic hierarchy.
✗
Add a calculated column that concatenates EmployeeID and ManagerID.
Why it's wrong here
Concatenating doesn't create a hierarchy.
✗
Create a many-to-many relationship between Employees and itself.
Why it's wrong here
Many-to-many is not needed; one-to-many is correct.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse a self-join relationship (which is a logical model relationship) with a Merge Queries operation (which physically combines tables), leading them to choose Option B instead of A.
Detailed technical explanation
How to think about this question
Under the hood, Power BI uses the self-join relationship to enable DAX functions like PATH, PATHITEM, and PATHCONTAINS, which rely on a one-to-many cardinality from ManagerID (many side) to EmployeeID (one side). A real-world scenario is an organizational chart where you need to calculate the level of each employee (e.g., CEO at level 1, direct reports at level 2) using PATHLENGTH. Without the self-join, these functions return errors or incorrect results.
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.
Model the data — This question tests Model the data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a self-join relationship from Employees[EmployeeID] to Employees[ManagerID]. — To create a hierarchy that shows the reporting structure in Power BI, you first need to establish a self-join relationship between the Employees table and itself, linking EmployeeID to ManagerID. This allows Power BI to traverse the parent-child relationship and build a natural hierarchy (e.g., using Parent-Child functions like PATH). Without this relationship, the model cannot understand how employees relate to their managers.
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.
Are there clue words in this question I should notice?
Yes — watch for: "first". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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.