MENU
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 MKT-101 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
QU
Quentin
12 months ago
Yeah, I agree, it must be the Auto Suppression List!
KA
Kati
12 months ago
Wait, how can a subscriber key exist twice? That seems odd.
LE
Leslie
12 months ago
I've seen this happen with Triggered Send Managed Lists too.
AN
Anjelica
1 year ago
Definitely not the Global Unsubscribe List.
HA
Hannah
1 year ago
I think it's the Auto Suppression List.
LE
Lelia
1 year ago
I’m a bit confused; I thought duplicates were mainly from Managed Lists, but I need to double-check that.
LE
Lezlie
1 year ago
I practiced a similar question about triggered sends and suppression lists, and I feel like the Auto Suppression List could be the answer.
LA
Lavonna
1 year ago
I think the Global Unsubscribe List might be involved here, but I can't recall if it directly causes duplicates.
PO
Portia
1 year ago
I remember studying about how subscriber statuses can affect delivery, but I'm not sure which list causes duplicates.
JO
Josphine
1 year ago
I'm a bit confused about the Dockerfile part. What exactly are the security best practice issues I need to address? I'll have to read through it carefully to identify them.
BE
Belen
1 year ago
Okay, let's think this through step-by-step. The key details seem to be the serial number and the name changes between the two discoveries.
DE
Deja
1 year ago
Detective Technical Control, for sure. Checking backgrounds is a technical security measure.