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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Analytics-Con-301 Exam - Topic 6 Question 6 Discussion

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

A client has a pipeline dashboard that takes a long time to load. The dashboard is connected to only one large data source that is an extract.

It contains two calculated fields:

. TOTAL([Opportunities])

* SUM([Value])

It also contains two filters:

. A Relative Date filter on Created Date, a Date field containing values from 5 years ago until today

. A Multiple Values (Dropdown) filter on Account Name, a String field containing 1,000 distinct values

A consultant creates a Performance Recording to troubleshoot the issue, and finds out that the longest-running event is "Executing Query."

Which step should the consultant take to resolve this issue?

Show Suggested Answer Hide Answer
Suggested Answer: B

To improve the loading time of the pipeline dashboard, which primarily suffers from long query execution times due to a comprehensive Relative Date filter:

Relative Date Filter Issue: The existing Relative Date filter on 'Created Date' covers a broad range (5 years), leading to significant data processing overhead as it includes granular date calculations over a large dataset.

Optimized Approach: By replacing the Relative Date filter with a Multiple Values (Dropdown) filter based on YEAR([Created Date]), the filter granularity is reduced. Filtering by year simplifies the query by limiting the volume of data processed and reducing the complexity of the filter condition.

Implementation Benefit: This approach still provides the flexibility to view data across different years but does so by reducing the load on the database during query execution, which is critical for improving the performance of the dashboard.

References This recommendation aligns with Tableau performance optimization strategies, specifically regarding the management of date filters to minimize their impact on query load, as discussed in Tableau performance tuning sessions and guides.


by Dominque at Aug 12, 2025, 05:56 AM

Limited Time Offer

25%

Off

Get Premium Analytics-Con-301 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Vivan
2 months ago
I think replacing the TOTAL calculation is a good idea.
upvoted 0 times
...
Eugene
3 months ago
Totally agree, that filter setup can slow things down!
upvoted 0 times
...
Hillary
3 months ago
Not sure about that, I feel like the date filter is the real issue here.
upvoted 0 times
...
Moon
3 months ago
Wait, why would a custom list filter be faster?
upvoted 0 times
...
Daron
3 months ago
The dashboard is pulling from a single large data source.
upvoted 0 times
...
Milly
3 months ago
I recall that using a Grand Total instead of TOTAL could simplify the calculation, but I'm not entirely convinced it would solve the loading problem.
upvoted 0 times
...
Jani
4 months ago
I'm a bit confused about the calculations. I feel like using WINDOW_SUM might not really address the query execution time issue.
upvoted 0 times
...
Rasheeda
4 months ago
I think replacing the Relative Date filter could be a good idea. We practiced a similar question where changing the filter type improved loading times.
upvoted 0 times
...
Valentine
4 months ago
I remember we discussed how filters can impact performance, especially with large datasets. I'm not sure if changing the dropdown filter would help, though.
upvoted 0 times
...
Mary
4 months ago
I think the consultant should focus on optimizing the data source and the calculations. Replacing the TOTAL([Opportunities]) with a Grand Total and using WINDOW_SUM([Value]) could help improve performance.
upvoted 0 times
...
Eleni
4 months ago
I'm a bit confused by the options here. Replacing the filter with a custom list or changing the date filter doesn't seem directly related to the performance issue. I'll need to think this through more carefully.
upvoted 0 times
...
Coletta
5 months ago
Okay, the key seems to be that the longest-running event is "Executing Query." That suggests the issue is with the data source or the filters, so I'll focus on those areas.
upvoted 0 times
...
Felix
5 months ago
Hmm, this looks like a tricky one. I'll need to carefully analyze the details of the dashboard and the performance recording to figure out the best approach.
upvoted 0 times
...

Save Cancel