PL-300 Visualize and analyze the data Practice Question
You are a Power BI developer for a retail company. You have a semantic model that includes a 'Sales' fact table with columns: 'Date', 'ProductID', 'StoreID', 'Quantity', 'UnitPrice'. The 'Product' dimension table includes 'ProductID', 'ProductName', 'Category', 'SubCategory'. The 'Store' dimension table includes 'StoreID', 'StoreName', 'Region', 'District'. You need to create a report page that allows users to analyze sales performance by product category and store region. The report must include a matrix visual with: - Rows: Product Category - Columns: Store Region - Values: Total Sales Amount (Quantity * UnitPrice) Additionally, users must be able to drill down from category to subcategory in the rows, and from region to district in the columns. You also need to ensure that when a user selects a specific store region, the matrix only shows data for that region and its districts. You have created the measures and the matrix visual. However, when you test the drill down, the hierarchy does not work as expected: clicking the expand icon on a category does not show subcategories. What is the most likely cause?
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
✓
The matrix rows do not have a hierarchy defined; Category and SubCategory are separate fields.
The correct answer is C: the matrix rows do not have a hierarchy defined, with Category and SubCategory as separate fields. In Power BI, drill-down in a matrix requires a single field well containing a hierarchy (or nested fields in the Rows bucket) so the expand/collapse icon can navigate from Category to SubCategory; placing Category and SubCategory as independent fields prevents the expected drill behavior. Option A is wrong because a blank Total Sales measure would show empty values, not block the hierarchy expansion. Option B is wrong because a Store Region slicer filters data but does not disable matrix drill-down. Option D is wrong because single-direction relationships affect filter propagation and drillthrough pages, not in-matrix hierarchy expansion.
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 Total Sales measure is incorrectly defined, causing blank values for subcategories.
Why it's wrong here
If the Total Sales measure were truly defective, it would likely return blanks across all levels, not just subcategories, and could be diagnosed separately. However, a correctly written measure such as SUM(Sales[Amount]) respects filter context and would return values for both Category and SubCategory. The symptom of subcategories appearing blank when expanding rows points to the row structure, not the measure definition, so this is not the root cause.
- ✗
A slicer for Store Region is interfering with the matrix drill down behavior.
Why it's wrong here
Slicers apply a filter to the data shown in the matrix, reducing the records that contribute to each category and subcategory, but they do not alter the matrix's drill-down functionality. Drill-down and expand/collapse are interactive visual features governed by the row hierarchy, not by slicers or cross-filtering from other visuals. Even with a region slicer active, you can still drill from Category to SubCategory if a hierarchy exists. Therefore, this option misattributes the behavior.
- ✓
The matrix rows do not have a hierarchy defined; Category and SubCategory are separate fields.
Why this is correct
For drill down to work in a Power BI matrix, the fields placed on Rows must be part of a single hierarchy that defines the parent-child relationship between levels. When Category and SubCategory are added as separate fields, the matrix treats them as independent, always-expanded columns and does not show expand/collapse icons. To enable drill down, create a hierarchy in the Product table (e.g., Product Hierarchy: Category > SubCategory) and place that hierarchy on Rows. This is the necessary condition being tested.
- ✗
The relationship between Sales and Product is set to single direction, preventing drill through.
Why it's wrong here
Relationship direction in a data model controls how filters propagate from one table to another, but it has no bearing on drill-down behavior within a single visual. Drill down is a visual hierarchy operation that works solely with the fields and hierarchy defined on the matrix rows, not with the underlying data model relationships. A single-direction relationship between Sales and Product would not prevent you from expanding rows that are already visible in the matrix. Thus, this is not the cause.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-300 question from scratch — 524 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.