DA0-002 Visualization and Reporting Practice Question
In Tableau, which of the following is used to create a calculated field that aggregates data at a different level of detail than the view?
⚠ Common exam trap
A common mix-up: candidates confuse LOD expressions with other Tableau features that also allow some level of control over aggregation, such as table calculations or parameters, but only LOD expressions are specifically designed to aggregate at a different level of detail than the view.
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
✓
LOD expressions
LOD (Level of Detail) expressions in Tableau allow you to compute aggregations at a specified granularity that can be finer or coarser than the view's level of detail. They are written using curly braces with keywords FIXED, INCLUDE, or EXCLUDE, and they enable calculations like average sales per customer regardless of the dimensions in the view. This directly addresses the need to aggregate data at a different level of detail than the view.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
LOD expressions
Why this is correct
LOD expressions compute aggregations at a declared dimension level, independent of the view's granularity. This satisfies the stem's constraint of aggregating at a different level of detail than the view, using FIXED, INCLUDE or EXCLUDE scopes.
- ✗
Marks
Why it's wrong here
Marks controls how dimensions and measures are rendered visually, such as colour and shape, and performs no aggregation. It is tempting because it sits alongside calculated fields on the shelf, but it would be correct for encoding a dimension graphically, not for computing values at a different level of detail.
- ✗
Parameters
Why it's wrong here
Parameters hold user-supplied constant values for calculations and filters; they do not alter aggregation granularity. They are tempting because they feed dynamic values into calculated fields, which suits what-if analysis, but the stem needs a level-of-detail expression to aggregate independently of the view's dimensions.
- ✗
Dashboard actions
Why it's wrong here
Dashboard actions filter or highlight data across views; they cannot define aggregation granularity. They are tempting because they control how views interact, which suits interactive dashboards, but the stem requires a calculated field using level-of-detail expressions to aggregate beyond the view's dimensions.
About these practice questions
Courseiva writes every DA0-002 question from scratch — 1,004 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This DA0-002 practice question is part of Courseiva's free CompTIA 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 DA0-002 exam.