Power BI basics interviewers expect
Good answers connect visuals to the model behind them. Interviewers often test data modeling, DAX reasoning, filters, relationships, and whether your dashboard helps a stakeholder decide.
Practice Power BI interview questions on modeling, DAX, measures, calculated columns, relationships, star schema, filters, dashboard design, performance, and business cases.
Published by PrepNPlaced. Last updated 2026-05-31. Preparation guidance, not a hiring guarantee.
Guide
Good answers connect visuals to the model behind them. Interviewers often test data modeling, DAX reasoning, filters, relationships, and whether your dashboard helps a stakeholder decide.
Most Power BI interviews become easier when you can explain grain, star schema, measures, filter context, and why a metric changes under slicers.
DAX hint
A measure is evaluated at query time based on filter context; a calculated column is stored row by row.
Modeling hint
A star schema keeps facts and dimensions clear, making filters and measures easier to reason about.
BI interviews often test whether you can ask the right business question, avoid misleading charts, and explain tradeoffs to non-technical users.
Answered DAX and modeling questions that decide most analyst and BI rounds. Tie every answer back to filter context.
Measure vs calculated column
A measure is evaluated at query time under the current filter context and stored as a formula; a calculated column is computed row by row and stored in the model, growing file size. Prefer measures for aggregations.
What does CALCULATE do
CALCULATE evaluates an expression after modifying filter context, for example CALCULATE(SUM(Sales[Amt]), Sales[Region] = "West"). It is the core function behind percent-of-total and time intelligence.
Row context vs filter context
Filter context is the set of filters applied by slicers, rows, and visuals when a measure evaluates; row context is the current row inside a calculated column or an iterator like SUMX. CALCULATE can turn row context into filter context.
Star schema and why it matters
One fact table joined to dimension tables through single-direction relationships keeps measures simple, filters predictable, and performance high, versus a tangled snowflake or one flat table.
Import vs DirectQuery
Import loads data into the model for fast in-memory queries but needs scheduled refresh; DirectQuery queries the source live for freshness at the cost of speed and some DAX limits. Choose by data size and freshness needs.
Year-over-year growth in DAX
Use time intelligence with a marked date table: subtract CALCULATE([Sales], SAMEPERIODLASTYEAR('Date'[Date])) from [Sales] and wrap the ratio in DIVIDE to avoid divide-by-zero errors.
Single vs bidirectional relationship filtering
Single-direction filtering (dimension filters fact) is the safe default. Bidirectional filtering can cause ambiguous or circular paths and slower models, so use it sparingly or replace it with CROSSFILTER inside a measure.
Why is my measure wrong under a slicer
It is almost always filter context: the slicer adds filters the measure must respect or override. Use CALCULATE with ALL or REMOVEFILTERS to control which filters apply, for example when computing percent of total.
Question bank
Real questions from beginner to advanced, each with a concise model answer — practice them, then rehearse live in a mock interview.
Power BI is Microsoft's business intelligence tool for connecting to data, modeling it, and building interactive reports. Its main parts are Power BI Desktop (authoring), the Power BI Service (sharing online), and Power BI Mobile for viewing.
DAX (Data Analysis Expressions) is the formula language in Power BI used to create measures, calculated columns, and calculated tables. It includes functions for aggregation, filtering, and time intelligence that operate over the data model.
A calculated column is computed row by row and stored in the model, using memory. A measure is computed on the fly at query time based on the current filter context, so it's more efficient for aggregations like totals and ratios. Prefer measures for aggregates.
Power Query is Power BI's data transformation layer, used to connect, clean, and shape data before it loads into the model. Its steps are recorded in the M language. Transformations here happen before DAX and the data model.
Import mode loads a copy of the data into Power BI's in-memory engine for fast performance but needs refreshes. DirectQuery leaves data in the source and queries it live, giving real-time data at the cost of slower interactions and some feature limits.
A star schema has a central fact table (transactions/metrics) linked to surrounding dimension tables (date, product, customer). It's recommended because it makes relationships simple, DAX easier to write, and the model faster than a flat or snowflake design.
Row context is the current row being evaluated, used in calculated columns and iterators. Filter context is the set of filters applied by visuals, slicers, and CALCULATE. Understanding how they interact is the key to correct DAX.
CALCULATE evaluates an expression under a modified filter context. It's the most important DAX function because it lets you add, remove, or change filters — for example, computing sales for a specific region or ignoring a slicer.
SUM aggregates a single column directly. SUMX is an iterator that evaluates an expression row by row and then sums the results, so use it when the value depends on multiple columns, like quantity times price.
Relationships connect tables on a key, usually one-to-many from a dimension to a fact table, with a filter direction (single or both). Correct one-to-many relationships let filters flow from dimensions to facts so measures aggregate correctly.
Time intelligence functions (TOTALYTD, SAMEPERIODLASTYEAR, DATEADD) compute period-based calculations like year-to-date and year-over-year. They require a marked, continuous date table in the model to work reliably.
RELATED pulls a single value from the one-side of a relationship into the many-side (like a lookup). RELATEDTABLE returns the related rows from the many-side and is typically used inside an iterator to aggregate them.
A dedicated, continuous date dimension marked as a date table enables time-intelligence functions, ensures no missing dates break calculations, and lets you add useful attributes like fiscal year, quarter, and weekday for consistent reporting.
VAR stores the result of an expression within a measure so it's computed once and reused. Variables make DAX more readable, avoid recalculating the same logic, and prevent context-transition surprises, improving both clarity and performance.
RLS restricts the data a user can see by applying DAX filter rules to roles — for example, a regional manager sees only their region. Roles are defined in Desktop and members are assigned in the Service.
Context transition happens when CALCULATE (or a measure reference) turns the current row context into an equivalent filter context. It's why a measure called inside an iterator like SUMX evaluates for the current row.
Use a star schema, prefer measures over calculated columns, reduce cardinality, remove unused columns and tables, push heavy transformations into Power Query or the source, limit visuals per page, and use variables in DAX to avoid recomputation.
ALL removes all filters from a table or columns; ALLEXCEPT removes filters except the columns you list; REMOVEFILTERS (the modern equivalent of ALL as a filter modifier) clears filters within CALCULATE. They're used to compute totals or percentages of a whole.
USERELATIONSHIP activates an inactive relationship for a specific calculation inside CALCULATE — useful when a fact table has multiple date columns (order date, ship date) and you want a measure to use a different one.
Related Guides
Move between roadmap, interview-question, and product pages without losing the preparation thread.
Connect BI dashboards to trusted data modeling.
Read guideStrengthen the SQL foundation behind Power BI models.
Read guideUnderstand upstream pipeline and warehouse context.
Read guideReturn to the parent resource hub for the full preparation path.
Open hubFAQ
Expect questions on data modeling, DAX measures, calculated columns, relationships, slicers, dashboard design, and performance basics.
A measure is evaluated based on filter context during analysis; a calculated column is computed row by row and stored in the model.
No. A strong dashboard answers a decision clearly. Too many visuals can hide the important metric.
SQL helps you understand joins, grain, filters, and source data quality before building measures and dashboards.
Show the business question, model design, measures, dashboard decisions, and what actions the dashboard supports.
Use courses and Open Learning for BI foundations, then practice stakeholder-style explanations in AI Mock Interview.
Next Step
Use PrepNPlaced tools to turn this learning path into resume proof, targeted practice, and interview-ready explanations.