Northern Trail Outfitters (NTO) is troubleshooting why a triggered send isn't being delivered to the customer. When querying the _subscribers data view, NTO notices this subscriber key exists twice, and one of them has a status of'Held'.
What is the source of the duplicate subscriber key?
Suggested Answer: A
Get Premium Salesforce Certified Marketing Cloud Engagement Specialist (MC-202) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
13 comments · newest first
WE
Wendell
12 months ago
Nah, it’s probably from the Global Unsubscribe List.
JE
Jenelle
12 months ago
Wait, how can a subscriber key exist twice? That’s odd!
AR
Arlean
12 months ago
I think it’s the Auto Suppression List causing this.
RE
Reita
1 year ago
Definitely a triggered send issue.
KI
Kirk
1 year ago
Sounds like a classic case of duplicate keys!
BR
Britt
1 year ago
I'm a bit confused; I thought duplicates were usually due to the Global Unsubscribe List, but now I'm not so sure.
VI
Viola
1 year ago
I feel like we've seen a question like this before in practice, and it was related to Managed Lists.
HA
Hassie
1 year ago
I think it might be the Auto Suppression List, but I also recall something about the Global Unsubscribe List affecting delivery.
CO
Corinne
1 year ago
I remember studying about how triggered sends can interact with different lists, but I'm not entirely sure which one causes duplicates.
TA
Tayna
1 year ago
Alright, time to put my ZFS knowledge to the test. I'm confident I can solve this question and get the right answer.
TE
Telma
1 year ago
Okay, let's think this through. The requirement is to view the membership data, not to store or update it. So I'm thinking Salesforce Connect with External Objects might be the way to go, as it allows you to access the data without having to replicate it.
BI
Billye
1 year ago
Hmm, I'm a bit unsure about the relationship between vitamin D and osteoporosis. I'll need to think through each statement carefully.
HE
Hershel
1 year ago
Option C sounds right to me because accessing specific partitions should definitely help with efficiency.