New Year Sale 2026! 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 9 Discussion

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

A client wants to see the average number of orders per customer per month, broken down by region. The client has created the following calculated field:

Orders per Customer: {FIXED [Customer ID]: COUNTD([Order ID])}

The client then creates a line chart that plots AVG(Orders per Customer) over MONTH(Order Date) by Region. The numbers shown by this chart are far higher

than the customer expects.

The client asks a consultant to rewrite the calculation so the result meets their expectation.

Which calculation should the consultant use?

Show Suggested Answer Hide Answer
Suggested Answer: B

The calculation {FIXED [Customer ID], [Region]: COUNTD([Order ID])} is the correct one to use for this scenario. This Level of Detail (LOD) expression will calculate the distinct count of orders for each customer within each region, which is then averaged per month. This approach ensures that the average number of orders per customer is accurately calculated for each region and then broken down by month, aligning with the client's expectations.

References: The LOD expressions in Tableau allow for precise control over the level of detail at which calculations are performed, which is essential for accurate data analysis. The use of {FIXED} expressions to specify the granularity of the calculation is a common practice and is well-documented in Tableau's official resources12.

The initial calculation provided by the client likely overestimates the average number of orders per customer per month by region due to improper granularity control. The revised calculation must take into account both the customer and the region to correctly aggregate the data:

FIXED Level of Detail Expression: This calculation uses a FIXED expression to count distinct order IDs for each customer within each region. This ensures that the count of orders is correctly grouped by both customer ID and region, addressing potential duplication or misaggregation issues.

Accurate Aggregation: By specifying both [Customer ID] and [Region] in the FIXED expression, the calculation prevents the overcounting of orders that may appear if only customer ID was considered, especially when a customer could be ordering from multiple regions.

References:

Level of Detail Expressions in Tableau: These expressions allow you to specify the level of granularity you need for your calculations, independent of the visualization's level of detail, thus offering precise control over data aggregation.


Contribute your Thoughts:

0/2000 characters
Arlene
3 days ago
Not sure if changing the calculation will really help.
upvoted 0 times
...
Dottie
8 days ago
Surprised the client didn't expect higher averages!
upvoted 0 times
...
Herman
13 days ago
I bet the client is regretting creating that calculated field in the first place! Option B is the way to go.
upvoted 0 times
...
Hester
18 days ago
Option A seems too simple, the client wants a more complex calculation. I'd go with B or D.
upvoted 0 times
...
Glendora
24 days ago
Haha, the client must be really confused if the numbers are way off! Option C would be a funny way to mess with them.
upvoted 0 times
...
Leah
29 days ago
I'm not sure why the numbers are so high, but option D seems like it would give the most detailed breakdown.
upvoted 0 times
...
Goldie
1 month ago
I recall that using FIXED with multiple dimensions can give a more accurate breakdown. Option D seems like it might be the right choice here.
upvoted 0 times
...
Eden
1 month ago
I'm not entirely sure, but I feel like excluding certain dimensions might help. Option C sounds like it could work, but I need to double-check.
upvoted 0 times
...
Elvis
1 month ago
I think I practiced a similar question where including more dimensions helped clarify the results. Could it be option B?
upvoted 0 times
...
Jordan
2 months ago
I'm not totally sure, but I think option D might be the way to go. By including the order date, it's breaking things down by customer, region, and month, which is exactly what the client wants. And the distinct count of orders should give us the average per customer per month.
upvoted 0 times
...
Bette
2 months ago
Hmm, I'm leaning towards option B. That seems to be the one that groups the data by both customer and region, which is what the client wants. And it's calculating the distinct count of orders, which should give us the average per customer.
upvoted 0 times
...
Goldie
2 months ago
I'm a bit confused by the different options here. I think the key is to understand what each of those calculated field options is doing. Maybe we can walk through them one by one and see which one seems to match what the client is looking for.
upvoted 0 times
...
Ernest
2 months ago
Option B looks good, it should give the average orders per customer per region.
upvoted 0 times
...
Norah
2 months ago
I remember that FIXED calculations can sometimes lead to inflated numbers if not used correctly. Maybe we need to consider the region in the calculation?
upvoted 0 times
...
Adrianna
3 months ago
I think option B makes the most sense here.
upvoted 0 times
...
Marget
3 months ago
The original calculation uses FIXED, which might inflate the numbers.
upvoted 0 times
...
Cecil
3 months ago
Okay, let's think this through. The client wants the average number of orders per customer per month, broken down by region. So we need to somehow group the data by customer, region, and month, and then calculate the average orders for each of those groups.
upvoted 0 times
...
Virgilio
3 months ago
Hmm, this looks tricky. I'm not sure why the numbers are so high, but I think the key is to figure out how the client's original calculation is working and then adjust it to get the right result.
upvoted 0 times
Norah
3 months ago
Option B seems like it could work.
upvoted 0 times
...
...

Save Cancel