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

Adobe AD0-E605 Exam - Topic 1 Question 3 Discussion

Actual exam question for Adobe's AD0-E605 exam
Question #: 3
Topic #: 1
[All AD0-E605 Questions]

A data engineer creates a custom identity namespace within Adobe Experience Platform. However, this custom Identity namespace is the wrong Identity type. What would the data engineer do to correct the situation?

Show Suggested Answer Hide Answer
Suggested Answer: C

In Adobe Experience Platform, once an Identity Namespace is created and saved, its core configuration---specifically the Identity Type (e.g., Cross-device, Phone, or Email)---becomes immutable. The platform's architecture does not allow for the editing of an existing namespace's type via the User Interface (UI) or the Identity Namespace APIs due to the potential for severe data corruption within the Identity Graph.

If an Identity Namespace is created with the wrong type, the only corrective action is to create a new custom Identity Namespace with the correct parameters. It is important to note that Identity Namespaces cannot be 'deleted' in the traditional sense if they have already been used to ingest data or are linked in a graph. While you can hide them or stop using them, the original erroneous namespace will persist in the system's metadata.

Choosing Option C is the standard operational procedure. After creating the correct namespace, the data engineer must update the corresponding XDM schemas to point to the new namespace and re-ingest or backfill the data to ensure that the Identity Service accurately reconciles the identities. Options A and B are technically impossible within the current AEP framework. Option D is incorrect because the platform generally restricts the deletion of namespaces once they are registered to prevent breaking existing identity links and historical profile fragments.


Contribute your Thoughts:

0/2000 characters
Nobuko
5 days ago
Deleting it sounds like a bad idea. Better to fix it!
upvoted 0 times
...
Gabriele
10 days ago
Wait, can you really just edit the Identity type? Seems risky.
upvoted 0 times
...
Lea
15 days ago
Definitely agree with option C!
upvoted 0 times
...
Janna
20 days ago
I think creating a new custom Identity Namespace is the way to go.
upvoted 0 times
...
Melynda
26 days ago
I vaguely recall that using APIs could be a solution, but I’m not confident about that. Could B actually work?
upvoted 0 times
...
Thad
1 month ago
This reminds me of a practice question where we had to delete and recreate something. I wonder if D is a valid option here too?
upvoted 0 times
...
Sena
1 month ago
I’m not entirely sure, but I feel like editing the Identity type directly might not be allowed. Could it be option A?
upvoted 0 times
...
Genevive
1 month ago
I think I remember something about needing to create a new namespace if the type is wrong. So maybe option C is the way to go?
upvoted 0 times
...

Save Cancel