Self-Referencing Relationships in Power BI for Reporting Structures
You have a Power BI data model with a table named Employees that includes columns: EmployeeID, ManagerID, and EmployeeName. You need to create a hierarchy that shows the reporting structure. Which type of relationship is required?
Quick Answer
The correct choice is a self-referencing relationship, because the Employees table contains both EmployeeID and ManagerID, where ManagerID points back to EmployeeID within the same table. This creates a parent-child hierarchy that models the reporting structure, allowing Power BI to traverse levels of management from the CEO down to individual contributors. On the PL-300 exam, this concept tests your understanding of how to handle recursive data models without needing a separate table—a common trap is confusing this with a bridge table or a many-to-many relationship. A strong memory tip is to think of the ManagerID as a “foreign key pointing to its own table’s primary key,” which is the hallmark of a self-referencing relationship. When you see a single table with both an ID and a parent ID field, immediately recognize that Power BI requires a self-referencing relationship to build an accurate org chart hierarchy.
⚠ Common exam trap
It's easy for candidates to confuse a self-referencing relationship with a one-to-many relationship to a separate table, thinking a manager table is required, when Power BI can handle parent-child hierarchies directly within a single table.
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
✓
A self-referencing relationship
A self-referencing relationship (Option C) is required because the Employees table contains both EmployeeID and ManagerID, where ManagerID references EmployeeID within the same table. This allows Power BI to create a parent-child hierarchy that accurately represents the reporting structure, such as an org chart. In Power BI, this is implemented by creating a relationship from ManagerID to EmployeeID within the same table.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Many-to-many relationship
Why it's wrong here
An employee has one manager, so many-to-many is incorrect.
- ✗
Bidirectional cross-filtering
Why it's wrong here
Bidirectional filtering is not required for parent-child hierarchies; a self-referencing relationship suffices.
- ✓
A self-referencing relationship
Why this is correct
A self-referencing relationship connects EmployeeID to ManagerID within the same table, enabling a hierarchy.
- ✗
One-to-many relationship to a separate table
Why it's wrong here
A separate table would duplicate data and complicate the hierarchy.
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 →
Same concept, more angles
1 more way this is tested on PL-300
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You have a Power BI data model with a table named Employees that contains: EmployeeID, ManagerID, Department, and Salary. You need to create a parent-child hierarchy for the reporting structure. Which THREE actions should you perform?
hard- ✓ A.Enable the 'Group on' feature in the visual to expand/collapse
- ✓ B.Create calculated columns for the hierarchy path (e.g., PATH, PATHITEM)
- ✓ C.Create a relationship between Employees[EmployeeID] and Employees[ManagerID]
- D.Create a separate table for managers
- E.Set cross filter direction to Both on the relationship
Why A: Enabling the 'Group on' feature in a visual (such as a matrix or table) allows users to expand and collapse parent-child hierarchies, making the reporting structure interactive. This feature works with the hierarchy path created by calculated columns (Option B) and the self-referencing relationship (Option C) to display the drill-down behavior.
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.