Tableau-Desktop-Found Understanding Tableau Concepts Practice Question
Exhibit
Error: Aggregate and non-aggregate arguments cannot be mixed in IF expression.
Refer to the exhibit. You receive this error when creating a calculation. What is the fundamental Tableau concept that prevents this formula from executing?
⚠ Common exam trap
Candidates often try to fix the error by adding an aggregation to only one field, forgetting that the entire calculation must be consistent in its level of detail.
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
✓
One field is aggregated and the other is not, causing a level-of-detail mismatch.
Tableau requires consistent dimensionality in calculations. You cannot mix aggregated values, like SUM(Sales), with non-aggregated values, like Profit, in the same expression because they operate at different levels of granularity. Understanding this concept is critical because it forces users to align their data grain. To fix this, one must either aggregate the non-aggregated field using functions like ATTR() or MIN(), or disaggregate the aggregated field if appropriate for the analysis.
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 calculation is using an invalid syntax for the IF statement.
Why it's wrong here
The IF syntax itself is likely correct; the error specifically identifies an aggregation mismatch. Tableau syntax requires that if any part of the logic involves an aggregate function, the other components must be either aggregated or treated as constants, otherwise the calculation engine cannot determine the correct level of granularity.
- ✓
One field is aggregated and the other is not, causing a level-of-detail mismatch.
Why this is correct
Tableau calculations must operate at a consistent level of detail. When you mix an aggregated field with a row-level field, the engine doesn't know whether to calculate the result per row or per the entire set. This mismatch forces an error to prevent incorrect mathematical logic in the visualization output.
- ✗
The data source has not been refreshed with the latest metadata.
Why it's wrong here
Aggregation errors are logical calculation issues, not connectivity or metadata synchronization problems. Refreshing the data source will not resolve a mismatch in the mathematical dimensionality of a formula. The issue lies within the calculation logic authored by the user, independent of the external data source's current status or metadata.
- ✗
The calculation uses a field that is not in the current view.
Why it's wrong here
Calculations can reference fields not present in the view. The error stems from how fields are combined mathematically within the expression, not their presence in the visualization shelves. The core issue is the logical incompatibility between row-level data and aggregated data when evaluated against each other in a single statement.
About these practice questions
This Tableau-Desktop-Found question is part of Courseiva's 126-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Tableau (Salesforce) exam blueprint
This Tableau-Desktop-Found practice question is part of Courseiva's free Tableau (Salesforce) 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 Tableau-Desktop-Found exam.