Interview Insights · Power BI
What a Blank Stare During a Power BI Question Really Means
Quick summary — Power BI blank stare
A blank stare on a Power BI question usually means a missing idea about context, not a lack of hands-on time. Many learners build Power BI reports by dragging fields onto visuals, which works until a number looks wrong. Interview questions about why a measure does not split by category, when to use a calculated column, or what CALCULATE actually does all depend on filter context and row context. If those ideas were never made clear, the candidate has nothing to reason with and goes blank. Naming which filters reach the measure is the fastest way back.
In this guide you will learn:
- The Power BI questions that cause the most blank stares
- Filter context and row context explained in interview-ready words
- Why a measure shows the same value in every row of a table visual
- DAX examples for columns, measures, CALCULATE and iterators
- A first sentence that turns a freeze into reasoning
SECTION 01The Power BI questions that freeze candidates most
In Power BI rounds, freezes cluster around a small number of questions. They are not trick questions. They are the questions that arise naturally the first time a report shows a wrong number, which is why I use them: they tell me whether you have ever debugged a report or only built one.
The most common is a measure that shows the same grand total on every row of a table visual. Candidates who have met this know immediately that the slicer or row field is not filtering the measure. Candidates who have not met it stare at the screen.
| Question | Concept behind it | What a freeze suggests | First thing to say |
|---|---|---|---|
| Why does the measure show the same total on every row? | Relationships and filter propagation | Never checked the model view | The row field may not be related to the fact table |
| Should margin be a calculated column or a measure? | Row context vs filter context | Uses whichever worked once | A column is computed per row at refresh; a measure at query time |
| What does CALCULATE do? | Modifying filter context | Uses it by copying examples | It evaluates an expression under changed filters |
| Why does SUM not work on this expression? | Aggregators vs iterators | Has not used SUMX | SUM takes one column; SUMX evaluates row by row |
Situation: a table visual with Product[Category]
and the measure [Total Sales]. Every row shows
the same grand total.
Total Sales = SUM ( Sales[Amount] )
Thinking aloud:
'The measure is fine. The problem is that the
category filter is not reaching the Sales table.
I would open Model view and check:
1. Is there a relationship from Product to Sales?
2. Is it on the right key, ProductID to ProductID?
3. Is it active (solid line, not dotted)?
4. Does the filter direction go from Product
to Sales?'
Fixing the relationship fixes the visual.-- Calculated column: computed once per row at refresh
-- Row context: it can see the current row's values
Line Margin = Sales[Amount] - Sales[Cost]
-- Measure: computed at query time for each cell
-- of a visual, under that cell's filter context
Total Margin = SUM ( Sales[Amount] ) - SUM ( Sales[Cost] )
Margin % =
DIVIDE ( [Total Margin], SUM ( Sales[Amount] ) )
What to say:
'A ratio like Margin % must be a measure, because
it has to be recalculated for whatever filters
the user selects. Averaging a row-level percentage
would give the wrong answer.'In both tabs, the strong answer begins by naming where the problem lives: in the model, or in when the calculation happens. That single framing step is what most frozen candidates are missing.
SECTION 02Filter context and row context in interview-ready words
If you can explain these two ideas clearly, most DAX questions stop being frightening. Row context means 'I am looking at one row at a time'. It exists in calculated columns and inside iterator functions such as SUMX and FILTER. Filter context means 'these are the filters currently applied', coming from slicers, visual rows and columns, page filters and CALCULATE.
A measure placed in a visual has no row context of its own. It only knows the filter context of the cell it is calculating. That is why measures respond to slicers and calculated columns do not.
| Idea | Where it comes from | Example | Common confusion |
|---|---|---|---|
| Row context | Calculated columns, iterators like SUMX | Sales[Qty] * Sales[Price] per row | Thinking measures have it automatically |
| Filter context | Slicers, visual axes, filters, CALCULATE | Category = Bikes, Year = 2025 | Thinking it affects calculated columns |
| Context transition | CALCULATE inside a row context | Using a measure inside a calculated column | Surprise at results that change per row |
| Filter propagation | Relationships from dimension to fact | Product filter reaching Sales rows | Missing or inactive relationships |
-- Sales has Qty and UnitPrice, but no Amount column.
-- Fails: SUM accepts only a single column
-- Revenue = SUM ( Sales[Qty] * Sales[UnitPrice] )
-- Works: SUMX creates row context, multiplies per
-- row, then adds the results under the current
-- filter context
Revenue =
SUMX ( Sales, Sales[Qty] * Sales[UnitPrice] )
-- Average order value with an iterator over orders
Avg Order Value =
AVERAGEX (
VALUES ( Sales[OrderID] ),
CALCULATE ( SUMX ( Sales, Sales[Qty] * Sales[UnitPrice] ) )
)-- Base measure
Total Sales = SUM ( Sales[Amount] )
-- Replace any filter on Category with Bikes
Bike Sales =
CALCULATE ( [Total Sales], Product[Category] = "Bikes" )
-- Keep the existing filters AND add Bikes
Bike Sales (Kept) =
CALCULATE ( [Total Sales], KEEPFILTERS ( Product[Category] = "Bikes" ) )
How to explain it:
'CALCULATE takes an expression and evaluates it
under a modified filter context. Here it overrides
whatever Category the visual is showing and uses
Bikes instead. KEEPFILTERS makes it intersect
with the existing filter rather than replace it.'You do not need to explain context transition in detail as a fresher. But knowing that it exists, and that wrapping an expression in CALCULATE inside an iterator makes each row act as a filter, puts you ahead of most candidates.
SECTION 03Talking your way out of a Power BI freeze
When a Power BI question freezes you, stop searching for a DAX function and start describing the report. Say which visual you would look at, which table the numbers come from, and which filters are applied. This turns an abstract question into a debugging walkthrough, and debugging is exactly what the interviewer wants to see.
If you genuinely do not know a function, describe the logic you need. 'I need total sales but ignoring the category filter' is a correct description of ALL or REMOVEFILTERS inside CALCULATE, and many interviewers will help you with the name.
| Stuck on | Describe instead | Function it points to | Follow-up to expect |
|---|---|---|---|
| Total that ignores a slicer | Same total whatever is selected | CALCULATE with REMOVEFILTERS or ALL | What about ALLSELECTED? |
| Last year's sales | Same period shifted back one year | SAMEPERIODLASTYEAR with a date table | Why must the date table be marked? |
| Count of unique customers | Each customer once, not each order | DISTINCTCOUNT | Why is COUNTROWS different? |
| Ranking products | Position of each product by sales | RANKX over ALL products | How are ties handled? |
Q: Your manager says the Delhi sales number on
the dashboard looks too low. What do you do?
Strong answer (thinking aloud):
1. 'I would click the Delhi value and check which
filters apply: page filters, visual filters and
any slicer selections.'
2. 'I would compare with the source: total Delhi
rows in Power Query or the source table.'
3. 'If the source is higher, I would check Power
Query steps for removed rows or type errors.'
4. 'Then the model: is City in a separate table,
and is the relationship active and one-to-many?'
5. 'Finally the measure: does it filter something
out, like a CALCULATE condition on Status?'Q: Show each category's sales as a % of all sales.
Candidate (stuck on the function name):
'I need two numbers: sales for the current category,
which the visual gives me, and sales for all
categories, ignoring the category filter. Then
I divide one by the other.'
Interviewer: Which function removes a filter?
Candidate: 'REMOVEFILTERS inside CALCULATE.'
Category % =
DIVIDE (
[Total Sales],
CALCULATE ( [Total Sales], REMOVEFILTERS ( Product[Category] ) )
)The debug walkthrough in the first tab is worth memorising as a structure: filters, source, Power Query, model, measure. It works for almost any 'this number looks wrong' question, and it shows a calm, methodical approach.
SECTION 04Drill: explain the context before the DAX
Use this drill with any practice report, such as a sample sales model. For each card, explain the filter context out loud first, then write the DAX, then check it in a table visual with a slicer.
SAY THE CONTEXT, THEN WRITE THE DAX
1. Total sales that changes with the year slicer
2. Total sales that ignores the year slicer
3. Sales for Bikes only, in any visual
4. Revenue from Qty x Price with no Amount column
5. Number of unique customers
6. Category share of total sales
7. Line margin as a calculated column
8. Margin % that works with any filter
For each, answer first:
- Row context or filter context?
- Which filters must reach the measure?
- Column or measure?WHEN A NUMBER LOOKS WRONG, CHECK IN ORDER
[ ] Filters pane: page and visual filters
[ ] Slicers: what is selected right now
[ ] Model view: relationship exists
[ ] Correct key columns on both sides
[ ] Cardinality: one-to-many as expected
[ ] Relationship active (solid line)
[ ] Filter direction: dimension -> fact
[ ] Measure: any CALCULATE filters inside
[ ] Power Query: rows removed or errors
Say each step out loud in mock interviews.PRACTISE SAYING THESE IN UNDER 15 SECONDS
Row context: 'the current row, used in calculated
columns and iterators like SUMX.'
Filter context: 'the filters active for a cell,
from slicers, visuals, filters and CALCULATE.'
CALCULATE: 'evaluates an expression under a
modified filter context.'
Measure vs column: 'measures calculate at query
time under filters; columns calculate per row at
refresh and are stored.'SECTION 05Habits that keep Power BI questions from freezing you
These habits give you a starting point for any Power BI question, even one you have not seen before.
- Start from the model — When a number looks wrong, mention relationships first. Many Power BI issues are model problems rather than DAX problems.
- Name the filters — Say which slicers, visual fields and filters apply to the cell. It shows you think about context before code.
- Build measures, not columns — Default to measures for anything that aggregates or divides, and explain why when you choose a calculated column.
- Describe logic when stuck — If a function name escapes you, describe what it must do. Interviewers often supply the name if your logic is right.
- Test with a table visual — Mention that you check new measures in a simple table with a slicer before using them in charts.
SECTION 06Interview Q&A — Power BI blank stare
Q1What is the difference between a calculated column and a measure?
A calculated column is computed for each row when the data refreshes and is stored in the model, using row context. A measure is computed at query time for each cell of a visual, using that cell's filter context. I use columns for row-level attributes I want to slice by, and measures for totals, ratios and anything that should respond to filters.
Q2What does CALCULATE do in DAX?
CALCULATE evaluates an expression under a modified filter context. Its filter arguments can add, replace or remove filters, for example showing sales for one category regardless of the visual, or removing a filter to get a grand total. Inside a row context it also performs context transition, turning the current row into a filter.
Q3Why does a measure show the same value in every row of a table?
Usually because the field on the rows does not filter the table the measure reads from. The relationship may be missing, inactive, on the wrong columns or pointing the wrong way. It can also happen if the measure uses ALL or REMOVEFILTERS on that field. I check the model view first, then the measure.
Q4When do you use SUMX instead of SUM?
When the value to add is an expression across columns, such as quantity times price, rather than a single existing column. SUMX iterates the table row by row, evaluates the expression in row context and sums the results. SUM can only take one column.
Q5What is filter context in Power BI?
It is the set of filters that apply when a measure is evaluated. It comes from slicers, the rows and columns of the visual, page and report filters, and any filters added by CALCULATE. Relationships carry these filters from dimension tables to fact tables.
SECTION 07Test yourself — Power BI blank stare quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
What Power BI questions are asked in interviews for freshers?
Common questions cover measures versus calculated columns, filter and row context, CALCULATE, relationships and star schema, Power Query cleaning steps, time intelligence like year-over-year, and how you would debug a wrong number on a dashboard.
How do I explain filter context in a Power BI interview?
Say that filter context is the set of filters active when a measure is calculated, coming from slicers, visual fields, filters and CALCULATE, and that relationships pass those filters from dimension tables to fact tables. Then give one example, such as a year slicer changing total sales.
Why do I struggle with DAX questions even though I make dashboards?
Building visuals by dragging fields does not require understanding context. DAX questions do. Practise writing measures by hand, testing them in a table visual with slicers, and explaining why the result changes.
Is DAX important for a Power BI developer interview?
Yes. Most Power BI interviews include DAX questions, from basic measures to CALCULATE, iterators and time intelligence. Data modelling and Power Query are also important, but DAX is where many candidates are tested most directly.
What should I say if I don't know a DAX function in an interview?
Describe what the calculation needs to do, such as 'total sales ignoring the category filter', and suggest the type of function you think fits. This shows understanding, and interviewers often help with the exact function name.
Is there a course that covers Power BI interview questions?
Yes. Uncodemy's Power BI Training Course in Noida (classroom and online) includes live projects, one-to-one mock interviews and resume reviews, so you practise Power BI interview questions with trainer feedback before the real interview. You can book a free demo class from this page to see how the sessions work.
SECTION 09Related reads
Classroom & online · Noida
Understand Power BI context, not just visuals
Our Power BI Training Course teaches DAX, data modelling and Power Query through hands-on reports, so you can explain every number on your dashboard with confidence.
Talk to a counsellor for current fees- Hands-on DAX practice
- Data modelling projects
- Mock Power BI interviews
- Weekday & weekend batches