PL-300 Visualize and analyze the data Practice Question
A company wants to create a Power BI report that shows sales performance by region. The data contains a table 'Sales' with columns: Date, Amount, RegionID, and ProductID. They also have a 'Regions' table with RegionID and RegionName. They want to display a matrix visual with RegionName on rows and Year on columns, with the sum of Amount as values. However, the report displays only 'RegionID' instead of 'RegionName'. What is the most likely cause?
⚠ Common exam trap
Test-takers frequently assume the RegionName column is missing due to a hidden column or relationship cardinality, but the core issue is the absence of an active relationship, which Power BI requires to combine data from different tables in a visual.
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
✓
There is no active relationship between the Sales and Regions tables.
If there is no active relationship between the Sales and Regions tables, Power BI cannot use the RegionName from the Regions table to filter or group the Sales data. Instead, it defaults to displaying the RegionID from the Sales table, which is the only related field available in the visual. An active relationship must exist between the two tables on the RegionID columns for RegionName to appear in the matrix.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The relationship is configured as many-to-many.
Why it's wrong here
Many-to-many cardinality does not prevent Power BI from resolving a filter from Sales to Regions; if a relationship is active, even a many-to-many configuration will still allow the report to display RegionName by cross-filtering between the tables. The cardinality only defines how matching rows are handled (e.g., via a bridge table or direct many-to-many), but it does not disable the relationship itself. The symptom of showing RegionID instead of RegionName points to the relationship being inactive or absent, not to its cardinality, so the many-to-many setting is irrelevant to this issue.
- ✗
The relationship direction is set to Both.
Why it's wrong here
Setting cross-filter direction to Both controls whether filters propagate bidirectionally across the relationship, but it has no effect on whether the relationship is active. Even a single-direction filter from Regions to Sales would be sufficient to allow the report to look up and display RegionName when the relationship is active. Since the described problem is a missing or inactive relationship, changing the direction to Both cannot activate it; bi-directional filtering only applies to an existing active relationship and cannot compensate for one that is inactive.
- ✗
The RegionID column in the Sales table is hidden.
Why it's wrong here
Hiding a column in the Sales table only removes it from the field list and from visual-level drag-and-drop interactions; it does not affect the underlying data model or the relationship metadata. Relationships in Power BI are defined at the model level and continue to function normally even if a column is hidden, so hiding RegionID would not prevent Power BI from using it as a foreign key. The visible display of RegionID instead of RegionName is due to the lack of an active relationship that would enable a lookup to the Regions table, not because the column is hidden.
- ✓
There is no active relationship between the Sales and Regions tables.
Why this is correct
In Power BI, an active relationship is what enables automatic filter propagation between tables; without one, Power BI cannot traverse from the Sales table to the Regions table to retrieve RegionName. When a foreign key column like RegionID is placed in a visual and no active relationship links it to the Regions table, Power BI simply shows the raw ID value because it has no way to perform the lookup. The correct fix is to create or activate a relationship between Sales[RegionID] and Regions[RegionID] (typically with a single-direction filter), so that the relationship becomes active and the report can display the corresponding RegionName.
Go deeper
Related to this question
About these practice questions
One of 217 original PL-300 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.