Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Analytics-Con-301 Exam - Topic 2 Question 12 Discussion

A consultant wants to improve the performance of reports by moving calculations to the data layer and materializing them in the extract.Which type of calculation is the consultant able to move?
A) A row-level calculation
B) A calculation that contains table calculation functions
C) A calculation that contains parameters
D) A calculation that contains an aggregation

Salesforce Analytics-Con-301 Exam - Topic 2 Question 12 Discussion

Actual exam question for Salesforce's Analytics-Con-301 exam
Question #: 12
Topic #: 2
[All Analytics-Con-301 Questions]

A consultant wants to improve the performance of reports by moving calculations to the data layer and materializing them in the extract.

Which type of calculation is the consultant able to move?

Show Suggested Answer Hide Answer
Suggested Answer: A

Comprehensive and Detailed Explanation From Exact Extract:

Tableau allows certain calculations to be materialized in extracts, meaning they are precomputed and stored inside the .hyper file to improve performance.

According to Tableau's extract documentation:

Materializable calculations must be compatible with the extract engine and must not depend on dynamic, view-based, or post-query logic.

Only row-level calculations and aggregation-level calculations without dependencies on runtime context can be materialized.

Tableau cannot materialize any calculation containing:

Table calculation functions

Functions requiring post-aggregation logic

View-dependent elements

Parameters that need runtime evaluation

Evaluation of the choices:

A . A row-level calculation --- Correct

Row-level calculations operate on each record individually before aggregation.

Tableau documentation specifies that these calculations can be pushed down into the extract and materialized because they do not depend on the visualization or user interaction.

Examples include concatenation, arithmetic, string manipulation, and row-based logic such as:

[Sales] * [Quantity] or IF [Region] = 'West' THEN 1 END

These can be precomputed inside the extract, improving performance.

B . A calculation that contains table calculation functions --- Not allowed

Table calculations (WINDOW_SUM, INDEX, RUNNING_SUM, RANK, etc.) depend on the table structure after aggregation and query execution.

Therefore, Tableau documentation states they cannot be materialized in extracts.

C . A calculation that contains parameters --- Not allowed

Parameters are evaluated at runtime, meaning the user can change their value.

Because of this, Tableau cannot permanently compute and store such a calculation inside an extract.

D . A calculation that contains an aggregation --- Generally not materialized

Aggregated calculations often depend on query context and cannot always be materialized.

Only simple, context-free aggregations might be materialized, but Tableau explicitly warns that aggregations are not guaranteed candidates for extract materialization.

Thus, this is not the best answer compared to row-level logic.

Conclusion

Only row-level calculations meet Tableau's exact requirements for materialization in extracts.

Reference From Tableau Consultant Documentation

Tableau Extract documentation describing materializable calculation types.

Tableau guidance stating table calculations and parameter-dependent calculations cannot be materialized.

Extract optimization guidelines describing row-level logic as eligible for materialization.


Contribute your Thoughts:

0/2000 characters
Barb
26 days ago
I think it’s more about aggregations, right?
upvoted 0 times
...
Dulce
1 month ago
A row-level calculation can definitely be moved.
upvoted 0 times
...
Johnetta
2 months ago
If I recall correctly, parameters are typically user-driven, so I don’t think they can be moved to the data layer.
upvoted 0 times
...
Jettie
2 months ago
I’m a bit confused about table calculations; I feel like those are more dependent on the visualization layer, but I could be wrong.
upvoted 0 times
...
Rosenda
2 months ago
I remember practicing a question about moving calculations, and I think aggregations are usually done in the data layer too.
upvoted 0 times
...
Fabiola
2 months ago
I think the consultant can move a row-level calculation since it’s often done at the data layer, but I’m not entirely sure.
upvoted 0 times
...

Save Cancel