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 ANC-201 Exam - Topic 2 Question 41 Discussion

Actual exam question for Salesforce's ANC-201 exam
Question #: 41
Topic #: 2
[All ANC-201 Questions]

A CRM Analytics consultant has been asked to refactor a dashboard so that it loads quicker. After some analysis, the consultant found that most of the dashboard queries run in less than 5 seconds; however, the Opportunities Table takes more time to load when scrolled down from its initial view.

How should the consultant improve the performance of this dashboard?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Bulah
3 months ago
Wait, is it really that slow? I thought dashboards were supposed to be fast!
upvoted 0 times
...
Josephine
3 months ago
A second dashboard seems like overkill for just one table.
upvoted 0 times
...
Clement
3 months ago
Not sure if a Visualforce page is necessary for this.
upvoted 0 times
...
Tien
4 months ago
I think moving it to a second page is a solid idea!
upvoted 0 times
...
Gaynell
4 months ago
The Opportunities Table is the bottleneck here.
upvoted 0 times
...
Jean
4 months ago
I’m a bit confused about the best approach here. I think separating the table could help, but I’m not sure if a new page or a new dashboard is better.
upvoted 0 times
...
Luisa
4 months ago
I practiced a similar question where we had to optimize dashboard performance. I feel like using Visualforce could be overkill for just a table, so I'm leaning away from option C.
upvoted 0 times
...
Miriam
4 months ago
I'm not entirely sure, but I think creating a second dashboard could complicate things. Option B seems like it might just add more clicks for the user.
upvoted 0 times
...
Marylin
5 months ago
I remember we discussed how moving heavy components to a separate page can help with load times, so option A might be a good choice.
upvoted 0 times
...
Sophia
5 months ago
I think the key here is to focus on the Opportunities Table. The question is asking how to improve the dashboard performance, so I'd start by looking at ways to optimize that specific table, like caching or pagination, before considering a complete redesign.
upvoted 0 times
...
Alesia
5 months ago
Okay, let's think this through. The question says the other queries are fast, so the issue is likely with the Opportunities Table specifically. I'd try to optimize that table first before considering more drastic changes like creating a new page or dashboard.
upvoted 0 times
...
Matilda
5 months ago
Hmm, I'm a bit unsure about this one. Creating a new page or dashboard seems like a lot of work just to address one slow-loading table. I wonder if there are any other ways to improve the performance without major changes to the dashboard structure.
upvoted 0 times
...
Gilma
5 months ago
This seems like a straightforward performance optimization question. I'd start by looking at the Opportunities Table and seeing if I can optimize the query or the data retrieval process.
upvoted 0 times
...
Emerson
5 months ago
Okay, I've got this. The question is asking how to pass the postalcode attribute from a parent to a child FlexCard, so the answer must be {Parent PostalCode}.
upvoted 0 times
...
Candida
10 months ago
The slow-loading Opportunities Table is clearly the issue here. Why not try caching the data or optimizing the query? That way, we can keep the dashboard clean and fast-loading. *taps forehead* Just a thought.
upvoted 0 times
Dacia
8 months ago
C: Optimizing the query sounds like a smart idea to speed up the dashboard.
upvoted 0 times
...
Mozell
9 months ago
B: Yeah, moving the table to a separate page might help with the loading speed.
upvoted 0 times
...
Elli
9 months ago
A: I think creating a Visualforce page could be a good solution.
upvoted 0 times
...
...
Hobert
10 months ago
I dunno, guys. Seems like we're just moving the problem around instead of addressing the root cause. Why not try caching or indexing the data? That's probably the best way to speed things up.
upvoted 0 times
Jeannine
9 months ago
C) Create a Visualforce page and display a list view of the Opportunities on this new page.
upvoted 0 times
...
Salome
9 months ago
B) Create a second dashboard and move the table to this new dashboard.
upvoted 0 times
...
Tran
9 months ago
A) Create a second page on the dashboard and move the table to this new page.
upvoted 0 times
...
...
Elroy
10 months ago
Visualforce page, huh? Now we're talking! That's the way to go. Put that table on its own page and let it shine!
upvoted 0 times
Jules
10 months ago
Annabelle: Let's go with creating a Visualforce page then!
upvoted 0 times
...
Charisse
10 months ago
User 3: I agree, it will make the dashboard more efficient overall.
upvoted 0 times
...
Annabelle
10 months ago
User 2: Yeah, separating the table onto its own page should definitely help with loading time.
upvoted 0 times
...
Aracelis
10 months ago
User 1: Visualforce page sounds like a good idea.
upvoted 0 times
...
...
Anthony
10 months ago
Ah, the old 'out of sight, out of mind' approach. But hey, at least the dashboard will look cleaner, right? *wink wink*
upvoted 0 times
Leslie
9 months ago
B: Create a Visualforce page and display a list view of the Opportunities on this new page.
upvoted 0 times
...
Ruthann
10 months ago
A: Create a second page on the dashboard and move the table to this new page.
upvoted 0 times
...
...
Mignon
11 months ago
Wow, moving the table to a new page or dashboard? That's like trying to hide the problem instead of fixing it. If I was the consultant, I'd focus on optimizing the table's query and data retrieval.
upvoted 0 times
...
Ligia
11 months ago
I agree with Valene. Creating a Visualforce page seems like the most efficient solution for improving dashboard performance.
upvoted 0 times
...
Valene
11 months ago
I disagree, I believe option C is the best choice. Creating a Visualforce page could optimize the performance.
upvoted 0 times
...
Geraldine
11 months ago
I think option A could work. Moving the table to a second page might help with loading speed.
upvoted 0 times
...

Save Cancel