A data engineer creates a custom identity namespace within Adobe Experience Platform.

In Adobe Experience Platform, once anIdentity Namespaceis created and saved, its core configuration—specifically theIdentity 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 theIdentity Graph.

If an Identity Namespace is created with the wrong type, the only corrective action is to create anew custom Identity Namespacewith 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 correspondingXDM schemasto point to the new namespace and re-ingest or backfill the data to ensure that theIdentity Serviceaccurately 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.