Adobe AD0-E605 Exam Questions

When an audience is imported into Adobe Experience Platform from an external source (like a CSV upload or a partner destination), it is treated as an External Audience. Unlike audiences natively generated within AEP, external audiences are 'non-durable' by default regarding their metadata. This means that while the platform knows which profiles belong to that audience, the specific attributes associated with that external list (such as 'Destination.City') are not automatically ingested into the Real-Time Customer Profile as permanent attributes.

The 'challenges' mentioned occur because the Segment Builder requires attributes to be part of an XDM schema to perform complex cross-attribute filtering. Because the 'Destination.City' attribute exists only within the context of the external audience membership and is not linked to the unified profile schema, it cannot be used in a join with behavioral Event attributes.

Option A is incorrect because external audiences are limited in combination with any other dynamic criteria in the visual builder unless they are first converted into profile attributes. Option D is a potential workaround but does not explain the reason for the immediate failure. Option C is incorrect as the UI does support basic external audience selection. The fundamental issue is that external attributes are transient and not part of the XDM Profile store, thus they lack the relational 'glue' required for complex segmentation logic involving time-series events.

When working with the Adobe Experience Platform (AEP) Web SDK, the standard practice for handling identities is to use the Identity Map field group. This field group allows for the collection of multiple identities (such as an ECID for anonymous tracking and a CRM ID for authenticated users) within a single event.

For schemas designed for the Web SDK, the Identity Map is the preferred method because it provides the flexibility to handle both ambiguous (anonymous) and authenticated data dynamically. When data is sent via the Web SDK, the primary identity is not hard-coded as a specific single field in the schema definition (like a specific 'email' field marked as primary). Instead, the identity information is contained within the identityMap object of the JSON payload.

Adobe Experience Platform's Identity Service automatically processes this identityMap. The primary identity is determined based on the contents of the map sent in the hit---for example, the Web SDK can designate the ECID as the primary identity for anonymous hits or a CRM ID as the primary identity once the user logs in. Therefore, the architect does not need to manually select a fixed field in the schema to be the primary identity; the platform relies on the dynamic identity map to resolve the profile at ingestion time. This approach is essential for supporting the transition from an anonymous visitor to a known customer without requiring separate schema configurations.

For website personalization that needs to happen 'in-page' or between page loads with sub-second latency, Edge Segmentation is the required method. While Batch and Streaming segmentation occur in the AEP 'Hub,' Edge segmentation is executed directly on the Adobe Experience Platform Edge Network. This is critical because it eliminates the 'round-trip' time required to send data to the central data center and back to the user's browser.

Edge Segmentation allows the platform to evaluate segment membership at the point of interaction. When a user lands on a page, the Edge Network uses the Edge Profile (a subset of the full Hub profile) to immediately determine if the user qualifies for a segment based on their current session behavior and historical data. This enables immediate personalization, such as showing a 'Welcome Back' banner the instant the user arrives.

Option A (Batch) is unsuitable for real-time needs as it runs every 24 hours. Option B (Streaming) is 'near real-time,' meaning it updates the Hub profile in seconds or minutes, but it is still too slow for an immediate web-response scenario where milliseconds matter. By using Edge Segmentation, the marketer ensures that the audience qualification is available at the 'Edge,' providing the fastest possible response time for Adobe Target or custom personalization engines.

When working with the Adobe Experience Platform (AEP) Web SDK, the standard practice for handling identities is to use the Identity Map field group. This field group allows for the collection of multiple identities (such as an ECID for anonymous tracking and a CRM ID for authenticated users) within a single event.

For schemas designed for the Web SDK, the Identity Map is the preferred method because it provides the flexibility to handle both ambiguous (anonymous) and authenticated data dynamically. When data is sent via the Web SDK, the primary identity is not hard-coded as a specific single field in the schema definition (like a specific 'email' field marked as primary). Instead, the identity information is contained within the identityMap object of the JSON payload.

Adobe Experience Platform's Identity Service automatically processes this identityMap. The primary identity is determined based on the contents of the map sent in the hit---for example, the Web SDK can designate the ECID as the primary identity for anonymous hits or a CRM ID as the primary identity once the user logs in. Therefore, the architect does not need to manually select a fixed field in the schema to be the primary identity; the platform relies on the dynamic identity map to resolve the profile at ingestion time. This approach is essential for supporting the transition from an anonymous visitor to a known customer without requiring separate schema configurations.

When utilizing the Adobe Experience Platform Server-Side API to communicate with the Edge Network, the most critical parameter is the Datastream ID (internally referred to in the API as configId). The Datastream acts as the central router on the Edge Network; it identifies which Experience Platform sandbox, dataset, and schema the incoming data should be mapped to, as well as which other Adobe solutions (like Target or Analytics) should receive the data.

The correct endpoint structure is POST https://server.adobedc.net/ee/v2/interact?configId={DATASTREAM_ID}. Options A and B are incorrect because the Edge Network does not accept raw data targeted directly at a Dataset or Schema ID; those mappings are handled server-side within the Datastream configuration to simplify the client-side (or console-side) implementation. Option D is incorrect because while a sandbox name might be part of a header or organizational context, it is not the primary routing parameter for the Edge Network interaction. By targeting the configId, the gaming company ensures that their event data is correctly processed by the Edge Network Service, allowing for real-time profile enrichment and future personalization.