10 Most Frequently Asked Tableau Interview Questions for Freshers in 2025
- Aditya Kumbhavdekar

- Apr 7
- 9 min read
Tableau has become a go-to tool for data visualization and business intelligence. Whether you're a fresher, a career switcher, or an experienced analyst, preparing for Tableau interview questions can boost your confidence and help you ace your next opportunity.
In this blog, we’ve curated a list of frequently asked Tableau interview questions — from beginner to advanced level — along with clear explanations and examples.
What are different types of Filters and what is the order of their operations?
There are 6 types of filters in Tableau and their order of operation are as below:
Extract Filter
Data Source Filters
Context Filter
Dimension Filter
Measure Filter
Table Calculation Filter
What are Dimensions and Measures in Tableau?
In Tableau, data is divided into two main types:
Dimensions → Qualitative data (categories, text, or IDs)
Measures → Quantitative data (numbers used for calculations)
Understanding with an Example
Imagine you have a Sales Dataset with the following columns:
Order ID | Customer Name | Region | Sales | Quantity |
101 | John Doe | East | 500 | 5 |
102 | Alice Smith | West | 800 | 8 |
103 | Bob Martin | North | 600 | 6 |
Dimensions (Categories / Labels):
Order ID → A unique identifier (not a number used for math).
Customer Name → Name of the customer.
Region → Which part of the country they belong to.
Measures (Numbers used for calculations):
Sales → A numerical value representing revenue.
Quantity → A count of items sold.
Key Differences in Simple Terms
Feature | Dimensions (Categories) | Measures (Numbers) |
Data Type | Text, IDs, Date | Numbers |
Used For | Grouping & filtering | Calculations (Sum, Avg, etc.) |
Example | City, Product Name | Sales, Profit |
In Tableau, Dimensions are usually blue and Measures are generally green.
What is discrete and continuous variable in Tableau?
Discrete Variables (Categorical Data)
Definition:
Discrete variables take distinct, separate values.
They create headers, labels, or categories in visualizations.
Discrete fields appear blue in Tableau.
Example: Imagine a dataset with Sales Data:
Order ID | Customer Name | Region | Sales |
101 | John Doe | East | 500 |
102 | Alice Smith | West | 800 |
103 | Bob Martin | North | 600 |
Discrete Fields:
Order ID → Unique values for each order.
Customer Name → Different customer names.
Region → Different geographic categories (East, West, North).
Continuous Variables (Numerical Data)
Definition:
Continuous variables can take any numeric value within a range.
They are used for aggregations, trends, and measurements.
Continuous fields appear green in Tableau.
Example: Using the same dataset, continuous fields include:
Sales → Any numeric value (500, 800, 600, etc.).
Key Differences: Discrete vs. Continuous in Tableau
Feature | Discrete (Blue) | Continuous (Green) |
Data Type | Categories, Labels, IDs | Numbers, Measures |
Example | Region, Customer Name | Sales, Profit |
Used For | Grouping, Headers | Aggregations, Trends |
Visualization | Creates separate labels | Creates continuous axis |
What is LOD expression? Give example for each of them?
LOD expressions allow you to control the level of granularity at which calculations are performed, regardless of what’s displayed in the visualization.
There are three types of LOD expressions:
FIXED → Defines a specific aggregation level.
INCLUDE → Includes extra dimensions in aggregation.
EXCLUDE → Removes dimensions from aggregation.
FIXED LOD
Definition:
Aggregates data at a fixed level, independent of filters in the view.
It ignores dimensions in the visualization unless explicitly mentioned in filters.
Syntax:
{ FIXED [Dimension]: Aggregation[Measure] }Example:
Find total sales per region, even if the user filters by product
{ FIXED [Region]: SUM([Sales]) }If you filter by Product, the total Sales per Region remains unchanged.
Use Case: When you need a constant value unaffected by filters (e.g., Total Customer Count per Region).
INCLUDE LOD
Definition:
Aggregates data at the granularity of dimensions in the view + extra ones you specify.
It is more flexible and works with visual-level filters. (Dimension and Measure Filters)
Syntax:
{ INCLUDE [Dimension]: Aggregation[Measure]}Example:
Find average sales per customer, even if the visualization is at a higher level (e.g., Region-level view)
{ INCLUDE [Customer Name]: AVG([Sales]) }Even if your view is at the Region level, Tableau will still calculate average sales per customer within each region.
Use Case: When you want to dynamically include extra detail but keep the existing granularity in visualization.
EXCLUDE LOD
Definition:
Aggregates data by removing specific dimensions from the visualization.
Useful when you need an aggregation at a higher level than what’s displayed.
Syntax:
{ EXCLUDE [Dimension]: Aggregation[Measure] }Example:
Find total sales per region, removing individual cities from the calculation
{ EXCLUDE [City]: SUM([Sales]) If you are viewing Sales by City, this will instead show Sales by Region (since City is excluded).
Use Case: When you want to calculate values at a higher level than the current view (e.g., % of Total Sales per Region while showing City-wise sales).
Quick Comparison of LOD Expressions
LOD Type | Effect on Granularity | Example Use Case |
FIXED | Ignores visualization level, keeps a fixed level | Total Sales per Region, even when filtering by Product |
INCLUDE | Adds extra details while keeping visualization granularity | Avg Sales per Customer, even at Region level |
EXCLUDE | Removes a dimension to calculate at a higher level | Total Sales per Region while displaying City-wise Sales |
When to Use Each?
✔ FIXED → When you need a constant, pre-defined aggregation.
✔ INCLUDE → When you want extra granularity but respect visualization structure.
✔ EXCLUDE → When you want to remove a dimension to get a higher-level aggregation.
Difference between Join and Relationship in Tableau? Which one is better?
Aspect | Join | Relationship |
What is it? | Combines data physically at the data source level. | Connects data logically at the workbook level. Tableau builds queries only as needed. |
When does it happen? | Happens immediately when you bring tables together in the data source tab. | Happens at the time of visualization — Tableau queries data when you build your view. |
Data Handling | Can cause data duplication or inflation (row multiplication). | Avoids data duplication because tables stay separate until visualization time. |
Performance | Can be slower if large tables are joined unnecessarily. | Usually better performance, especially for large datasets, because of query optimization. |
Flexibility | Less flexible — need to define join type (Inner, Left, Right, Full Outer). | More flexible — Tableau understands relationships and context between tables. |
Use Case | - Small datasets - You need row-level data immediately. | - Large datasets - When you want Tableau to decide best query paths dynamically. |
Example to Understand
Join Example (Immediate Merge)
You have:
Customers Table: Customer ID, Name
Orders Table: Customer ID, Order ID, Sales
If you do a Join on Customer ID, Tableau will immediately merge these tables:
Customer ID | Name | Order ID | Sales
--------------------------------------
101 | John | O-001 | 500
101 | John | O-002 | 700
102 | Alice | O-003 | 800
Risk: If one customer has multiple orders, customer data is repeated (duplication).
Relationship Example (Smart Connection)
You connect the same tables with a relationship:
Tableau keeps them separate.
When you create a visual, like "Total Sales by Customer", Tableau builds the correct query.
No duplication of data.
Cleaner, smarter, and Tableau manages the complexity for you!
What is Data Blending in Tableau?
Data blending is a method in Tableau to combine data from two different data sources that are not connected directly.
Unlike Joins and Relationships (which happen inside a single data source),
Blending is for situations when your data is coming from two separate sources — like Excel + SQL, or Google Sheets + Cloud database.
Simple Example:
Data Source 1 (Primary):
Table A
Country | Sales
USA | 5000
India | 7000
UK | 4000
Data Source 2 (Secondary):
Table B
Country | Sales
USA | 6000
India | 8000
Germany | 5000You want to compare Sales vs. Target.
But:
Sales data is in Excel.
Target data is in a Google Sheet.
They’re in different sources, so you can’t do a normal Join.
Solution: Use Data Blending!
How Does Blending Work?
You bring both data sources into Tableau.
Define a common field — here it is Country.
Tableau uses the common field to blend the data visually in the worksheet.
In Tableau, you'll see:
Primary Data Source (with a blue tick).
Secondary Data Source (with an orange link icon 🔗).
Data Blending is like making a VLOOKUP in Excel between two files.
You're not physically joining the data — Tableau combines the summary results in the view.
When Should You Use Data Blending?
Situation | Explanation |
Data from different databases | Example: Excel file + SQL database |
Different levels of detail in data | Example: Daily Sales (primary) + Monthly Target (secondary) |
You cannot join tables directly | Maybe no common joinable field or different data sources |
Data is already aggregated | Example: Budget summary vs. Actuals data |
When you need quick analysis from multiple sources without heavy data prep | Blend keeps data sources separate. |
Important Points to Know:
Blending happens after aggregation — Tableau first aggregates both sources, then blends.
Primary data source drives the view.
Blending does not create a single combined table — it blends at visualization level.
Filters from primary source affect the view, but secondary source filters may need care.
What is a context filter?
A context filter is like a first-level filter in Tableau. When you have multiple filters, and you want Tableau to apply one filter first, and then apply others based on that filtered data, you use a context filter.
In short:
Context Filter = Main filter that controls other filters.
Why do we need it?
Normally, Tableau applies all filters independently. But sometimes, you want Tableau to filter the data first, then apply other filters on top of that filtered data.
Using context filters:
Improves performance (especially with large data).
Helps you create dependent filters.
Example:
Imagine you have a Sales dataset:
Region | Category | Sales |
Asia | Furniture | 5000 |
Asia | Technology | 7000 |
Europe | Furniture | 4000 |
Europe | Technology | 6000 |
Now you apply 2 filters:
Region = Asia
Category = Furniture
Without Context Filter:
Tableau checks all data for both filters independently.
With Context Filter:
You set Region = Asia as a context filter.
Tableau first filters data to only Asia.
Then it applies the Category filter on the Asia data only.
Result: Faster and more accurate filtering!
What is the difference between Sets and Groups in Tableau?
Feature | Groups | Sets |
Purpose | Combine dimension members into higher-level categories | Create custom subsets of data based on conditions or selections |
Type | Static (Manual grouping) | Dynamic or Static (can be based on conditions, Top N, or manual selection) |
Use Case | Simplify your data by grouping similar items together (e.g., categories, regions) | Focus analysis on a subset (e.g., Top 10 customers, customers with sales > 10,000) |
Output | Creates a new dimension (like a new field) | Creates a True/False field (indicates whether a record belongs to the set) |
Flexibility | Mostly manual | Very flexible (manual, condition, formula, Top N) |
Visualisation | Groups appear as a new category in your views | Sets can be used for set actions, comparisons, or custom calculations |
Example:
Scenario: You have Categories like:
Chairs
Tables
Sofas
Beds
Desks
If you use a Group:
You can combine categories to make it simpler:
Group 1: Furniture (Chairs, Sofas, Beds)
Group 2: Office Furniture (Desks, Tables)
Now, Tableau treats them as new "grouped" categories.
If you use a Set:
You can create a set of Top 2 categories by sales.
Set contains: "Tables", "Sofas"
Tableau marks records inside the set as True, others as False.
When to use?
Situation | Use Group | Use Set |
You want to simplify your view by combining categories | ✅ | ❌ |
You want to compare "Top Customers" vs. the rest | ❌ | ✅ |
You want to use in set actions (interactive dashboard filters) | ❌ | ✅ |
Static data simplification | ✅ | ✅ (manual set) |
Dynamic filtering (e.g., Top N based on Sales) | ❌ | ✅ |
What is Hierarchy in Tableau?
A Hierarchy in Tableau is a way to organize your data fields from higher level to lower level — so you can drill down or drill up in your visualizations.
In simple words: Hierarchy = Parent → Child levels of data, like from broader to detailed view.
It allows you to click and explore the data step by step!
Let’s say you have Sales data with:
Country
State
City
If you create a Hierarchy like this:
Country > State > CityIn your chart, you can first see Sales by Country.
Then, click on a country to drill down to see Sales by State.
And then, drill down further to see Sales by City.
It’s like zooming in to see details!
Why use Hierarchy in Tableau?
Benefit | Explanation |
Drill-down analysis | Explore data step by step, from summary to details. |
Clean visualizations | Avoid clutter — show high level first, then details as needed. |
User interactivity | Make dashboards interactive with expanding views. |
Quick navigation | No need to create separate charts for each level. |
Summary:
Feature | Hierarchy |
Purpose | Organize data fields into levels |
Benefit | Drill-down analysis and better navigation |
Use Case | Geography, Time, Organization structures |
Result | Interactive, expandable data views |
What is Replace References?
In Tableau, "Replace References" is a feature that helps you swap out one field for another across your entire workbook without breaking anything.
In simple words: If you’ve removed or want to change a field, Tableau lets you replace it everywhere in one click!
Example:
Let’s say you built a dashboard using the field:
Sales 2023
Later, your data updates, and now you have:
Sales 2024
If you delete Sales 2023, Tableau will show errors everywhere it was used (charts, filters, calculations).
Instead of fixing each error manually, you can:
Right-click on the old field (Sales 2023).
Select "Replace References".
Choose Sales 2024.
Tableau will automatically update all uses of the old field to the new field across:
Worksheets
Filters
Calculations
Dashboards
✅ No errors! ✅ Saves time! ✅ No need to rebuild your charts.
When do you use it?
Situation | Use Replace References? |
You renamed a field in your data source | ✅ |
You are switching from old field to new (like year change) | ✅ |
You cleaned your data and removed duplicates | ✅ |
You want to replace calculated field with a raw field (or vice versa) | ✅ |





Comments