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

Salesforce Exam Marketing Cloud Intelligence Topic 1 Question 17 Discussion

Actual exam question for Salesforce's Marketing Cloud Intelligence exam
Question #: 17
Topic #: 1
[All Marketing Cloud Intelligence Questions]

What are two potential reasons for performance issues (when loading a dashboard) when using the CRM data stream type?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Kerry at Sep 12, 2024, 03:02 AM

Limited Time Offer

25%

Off

Get Premium Marketing Cloud Intelligence Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Lashon
2 months ago
Wait, so the CRM data stream is creating a row for every lead and opportunity, daily? That's like a million rows a day! No wonder the dashboard is sluggish - the poor server must be gasping for air!
upvoted 0 times
Robt
25 days ago
C) No mappable measurements - all measurements are calculated
upvoted 0 times
...
Pedro
27 days ago
B) Pacing - daily rows are being created for every lead and opportunity keys
upvoted 0 times
...
Ty
1 months ago
A) When a data stream type ''CRM - Leads' is created, another complementary 'CRM - Opportunity' is created automatically.
upvoted 0 times
...
...
Nicolette
2 months ago
D) The data is stored at the workspace level - oh, that's a good one. If the data is not partitioned or optimized for querying, that could definitely slow things down. Workspace-level storage is probably not the best choice for a CRM data stream.
upvoted 0 times
...
Melvin
2 months ago
I'm surprised option A) is even an option. Creating a complementary data stream type automatically? That sounds like a recipe for disaster, not a reason for performance issues!
upvoted 0 times
...
Francesco
2 months ago
C) No mappable measurements - all measurements are calculated - that's an interesting point. If there are no pre-calculated metrics and everything needs to be computed on the fly, that could definitely impact performance.
upvoted 0 times
Glendora
1 months ago
C) No mappable measurements - all measurements are calculated - that's an interesting point. If there are no pre-calculated metrics and everything needs to be computed on the fly, that could definitely impact performance.
upvoted 0 times
...
Carey
1 months ago
B) Pacing - daily rows are being created for every lead and opportunity keys
upvoted 0 times
...
Sheridan
1 months ago
A) When a data stream type 'CRM - Leads' is created, another complementary 'CRM - Opportunity' is created automatically.
upvoted 0 times
...
...
Nelida
3 months ago
B) Pacing - daily rows are being created for every lead and opportunity keys - that seems like a reasonable explanation for performance issues. The constantly growing data volume could definitely slow down the dashboard loading.
upvoted 0 times
Edna
2 months ago
B) Pacing - daily rows are being created for every lead and opportunity keys - that seems like a reasonable explanation for performance issues.
upvoted 0 times
...
Lonny
2 months ago
A) When a data stream type 'CRM - Leads' is created, another complementary 'CRM - Opportunity' is created automatically.
upvoted 0 times
...
...
Tamra
3 months ago
I believe the data being stored at the workspace level could also contribute to performance issues.
upvoted 0 times
...
Reid
3 months ago
I agree with Nan. Pacing and no mappable measurements can definitely cause performance issues.
upvoted 0 times
...
Nan
3 months ago
I think the potential reasons could be pacing and no mappable measurements.
upvoted 0 times
...

Save Cancel