AD0-E605 Exam Questions & Answers

The relationship between the Hub (Real-Time Customer Profile) and the Edge (Edge Profile) is a key architectural distinction in Adobe Experience Platform. The Hub represents the 'Source of Truth'---a massive, comprehensive repository of all attributes, behavioral events, and segment memberships for every customer.

In contrast, an Edge Profile is a lightweight, low-latency subset of that Hub profile. It contains only the specific attributes and segment qualifications required to deliver real-time personalization at the 'edge' of the network (e.g., website or mobile app). When a user interacts with a digital property, the Adobe Experience Platform Edge Network retrieves this subset to make instantaneous decisions, such as showing a specific offer or banner.

Option C is the correct answer because it accurately identifies the Edge profile as a functional subset focused on immediate activation and personalized campaigns. Option A is incorrect as it reverses the relationship (Edge is the subset, not the Hub). Option B is incorrect because the Hub provides the 'detailed view,' not the Edge. Option D is partially true in concept but misleading; profiles are not 'always' synced. Instead, only profiles that qualify for Edge-enabled segments are projected to the Edge to optimize performance and storage. This architecture ensures that high-volume, low-latency requests are handled efficiently without the overhead of processing the entire multi-terabyte Hub profile for every web hit.

In the Adobe Real-Time Customer Data Platform, the activation process is the final step where unified audiences are sent to Destinations (such as social media platforms, email service providers, or advertising networks) for execution. The primary technical consideration for an architect is ensuring that the destination is capable of receiving and interpreting the data payload sent by the platform.

Adobe Real-Time CDP supports various destination types, including Streaming Destinations (API-based) and File-based Destinations (SFTP/S3). The key requirement is that the target system must be configured to map the incoming XDM attributes and segment memberships to its own native fields. If a destination cannot consume the specific segment identifiers or the associated profile attributes (like hashed emails for matching), the activation will fail to produce the desired personalization.

Option A is incorrect because activation often requires historical attributes or persistent IDs, not just the 'latest transaction.' Option B is a business process rather than a technical platform requirement for activation. Option D is incorrect because Adobe Experience Platform performs validation during the mapping phase of destination setup; the goal is to send 'ready-to-use' data so the execution channel does not have to perform complex validation. By ensuring the channel has the technical capacity to consume the data (Option C), the marketing manager guarantees that the audience logic defined in the CDP is correctly translated into a personalized message on the end platform.

To facilitate an efficient profile merge across multiple data sources, the Identity Service must be configured to recognize when different records belong to the same person. This is achieved primarily through the strategic use of Identity Namespaces.

Option E is the foundational step: setting up appropriate namespaces (such as Email, CRM ID, or ECID) provides the necessary context for the platform to link identities. Option A is the critical tactical approach: for the platform to 'stitch' profiles efficiently, disparate data sources must share common namespaces. For example, if both a CRM system and a Web SDK implementation use the standard 'Email' namespace for the same email address, the Identity Graph can automatically bridge these two sources into a single, unified profile. Using the same namespace across sources prevents the creation of 'identity silos' and ensures that the Merge Policy can accurately aggregate all profile fragments into a 360-degree view.

Option B is incorrect because creating separate namespaces for every source would prevent stitching unless another common ID exists to bridge them, leading to fragmented profiles. Option C is incorrect as AEP performs merging automatically based on identity links and merge policies, not manual union tools. Option D is incorrect as the system has fixed Identity Guardrails (limits on the number of IDs per profile) to maintain performance and prevent 'graph collapses' where unrelated individuals are merged.

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.

Implementing Attribute-Based Access Control (ABAC) for granular restrictions like geography and department requires a structured metadata approach. The first essential step is to define the geographical locations and departments as attributes (Option D) within the XDM schema or as custom labels. In Adobe Experience Platform, ABAC relies on these specific data characteristics to categorize information, allowing the system to distinguish between data belonging to, for example, the 'Europe' region versus 'North America,' or the 'Marketing' department versus 'Finance'.

The second critical step is to incorporate these labels in access policies (Option A). Once the attributes are labeled (e.g., applying a 'Region: EU' label to a specific dataset or field), an administrator must create a policy that ties these labels to specific roles. For instance, a policy might state that 'Users in the EU Marketing Role' can only view attributes labeled with 'Region: EU' and 'Dept: Marketing'.

Option C is technically incorrect because you do not assign labels to roles; you assign permissions/policies that reference those labels to roles. Option B is incorrect because including every attribute in every policy defeats the purpose of granular access control and creates unnecessary system overhead. By defining attributes and linking them via policies to roles, the corporation ensures automated, scalable data segregation that meets regional and organizational security requirements.