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 Marketing Cloud Intelligence Accredited Professional (AP-215) Exam - Topic 1 Question 17 Discussion

Actual exam question for Salesforce's Marketing Cloud Intelligence Accredited Professional (AP-215) exam
Question #: 17
Topic #: 1
[All Marketing Cloud Intelligence Accredited Professional (AP-215) 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 Accredited Professional (AP-215) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Geraldo
4 months ago
Totally agree with B, too many daily rows can be a nightmare!
upvoted 0 times
...
Salley
4 months ago
Wait, is it really D? I thought data was stored differently.
upvoted 0 times
...
Lashonda
4 months ago
C makes sense, calculated measurements can be a hassle.
upvoted 0 times
...
Arlette
4 months ago
A seems off, I don't think they create automatically.
upvoted 0 times
...
Antonio
5 months ago
Definitely B, pacing can slow things down a lot.
upvoted 0 times
...
Cristal
5 months ago
I’m a bit confused about option A. I don’t recall if the automatic creation of 'CRM - Opportunity' impacts loading times, but it seems possible.
upvoted 0 times
...
Oren
5 months ago
I practiced a similar question, and I think the workspace level storage mentioned in option D might also contribute to performance issues.
upvoted 0 times
...
Linsey
5 months ago
I'm not entirely sure, but I feel like option C could be a factor too. If all measurements are calculated, that might slow things down.
upvoted 0 times
...
Letha
5 months ago
I think one reason could be related to pacing, like option B. I remember something about daily rows affecting performance.
upvoted 0 times
...
Shaquana
5 months ago
Hmm, I'm not sure about the workspace-level data storage. Does that mean the data is less accessible or optimized for dashboard loading? I'll have to think about that one.
upvoted 0 times
...
Rose
5 months ago
And the fact that all the measurements are calculated rather than mapped could also be a factor. That extra processing might be causing performance problems when loading the dashboard.
upvoted 0 times
...
Tracey
5 months ago
Ah, I think I know one of the reasons - the pacing of the data creation. If it's generating daily rows for every lead and opportunity, that could really slow things down, especially for large datasets.
upvoted 0 times
...
Regenia
5 months ago
Okay, let's see. I'm guessing it has something to do with the way the data is structured or processed. Maybe the automatic creation of the 'CRM - Opportunity' data stream is causing issues?
upvoted 0 times
...
Francene
5 months ago
Hmm, this looks like it could be a tricky one. I'll need to think carefully about the potential reasons for performance issues with the CRM data stream type.
upvoted 0 times
...
Aleta
6 months ago
Hmm, I'm a bit unsure about this one. The options seem to be focused on different aspects of communication, but I'm not sure which one specifically indicates the behavioral tier. I'll have to think this through carefully.
upvoted 0 times
...
Lashon
10 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
9 months ago
C) No mappable measurements - all measurements are calculated
upvoted 0 times
...
Pedro
9 months ago
B) Pacing - daily rows are being created for every lead and opportunity keys
upvoted 0 times
...
Ty
10 months ago
A) When a data stream type ''CRM - Leads' is created, another complementary 'CRM - Opportunity' is created automatically.
upvoted 0 times
...
...
Nicolette
10 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
10 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
10 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
10 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
10 months ago
B) Pacing - daily rows are being created for every lead and opportunity keys
upvoted 0 times
...
Sheridan
10 months ago
A) When a data stream type 'CRM - Leads' is created, another complementary 'CRM - Opportunity' is created automatically.
upvoted 0 times
...
...
Nelida
11 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
10 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
10 months ago
A) When a data stream type 'CRM - Leads' is created, another complementary 'CRM - Opportunity' is created automatically.
upvoted 0 times
...
...
Tamra
11 months ago
I believe the data being stored at the workspace level could also contribute to performance issues.
upvoted 0 times
...
Reid
11 months ago
I agree with Nan. Pacing and no mappable measurements can definitely cause performance issues.
upvoted 0 times
...
Nan
12 months ago
I think the potential reasons could be pacing and no mappable measurements.
upvoted 0 times
...

Save Cancel