BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Marketing Cloud Intelligence Topic 3 Question 18 Discussion

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

An implementation engineer has been asked to perform QA for a standard file ingestion, done by the client.

The source file that was ingested can be seen below:

The number of rows added to this data stream is 3. What could have led to this discrepancy?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Eladia
21 days ago
You know, this reminds me of that time I had to debug a file ingestion issue and the problem was a typo in the file name. Gotta love those simple yet elusive bugs!
upvoted 0 times
...
Tori
24 days ago
Aha, the Campaign Key is the missing piece of the puzzle. Well, at least it's not the Media Buy Key - that would be just embarrassing, am I right?
upvoted 0 times
...
Carma
27 days ago
Haha, leave it to the client to forget about the Media Buy Name. Classic move, really keeps you on your toes, doesn't it?
upvoted 0 times
Truman
2 days ago
B) All fields are mapped except for the Creative Name
upvoted 0 times
...
German
13 days ago
A) All fields are mapped except for the Media Buy Key.
upvoted 0 times
...
...
Christene
1 months ago
Hmm, interesting. I'd say the Creative Name is the culprit here. That's a pretty crucial field, how did they miss that one?
upvoted 0 times
Francoise
5 days ago
German: Definitely, missing a key field like that can cause discrepancies in the data.
upvoted 0 times
...
German
7 days ago
User 2: Yeah, that could be a possibility. It's important to double-check all fields before ingestion.
upvoted 0 times
...
Tran
8 days ago
Maybe they overlooked it during the mapping process.
upvoted 0 times
...
Shaun
12 days ago
I agree, missing a crucial field like Creative Name can definitely cause discrepancies in the data stream.
upvoted 0 times
...
Tess
22 days ago
Yeah, that could be a possibility. It's important to double-check all fields before ingestion.
upvoted 0 times
...
Miesha
28 days ago
Maybe they overlooked it during the mapping process.
upvoted 0 times
...
...
Claribel
2 months ago
I believe it could also be because of missing mapping for the Campaign Key.
upvoted 0 times
...
Dorothy
2 months ago
I agree with Leslie, missing mapping for the Media Buy Key could be the reason for the discrepancy.
upvoted 0 times
...
Janna
2 months ago
Ah, I see the issue - looks like the Media Buy Key is missing from the mapping. Classic mistake, easy to overlook those lesser-known fields.
upvoted 0 times
Dorethea
21 days ago
Beata: Agreed, we should make sure to include all necessary fields next time.
upvoted 0 times
...
My
23 days ago
It's a common mistake to overlook such fields during mapping.
upvoted 0 times
...
Beata
1 months ago
Yes, that could be the reason for the discrepancy in the number of rows added.
upvoted 0 times
...
Jame
1 months ago
Did you notice the missing Media Buy Key in the mapping?
upvoted 0 times
...
...
Leslie
2 months ago
I think the discrepancy could be due to missing mapping for the Media Buy Key.
upvoted 0 times
...

Save Cancel