Adobe AD0-E605 Practice Test Questions Answers

In Adobe Real-Time Customer Data Platform, licensing is often tied to two primary metrics: theAddressable Audiencecount (the number of unified profiles) and theTotal Data VolumeorProfile Enrichmentcapacity.

TheNumber of Experience Events linked to a profile (Option C)is a significant factor in the calculation of data volume and profile richness. WhileIndividual Profileattributes (like name or email) are relatively static and small,ExperienceEvents(like clicks, purchases, or page views) are time-series data that can grow exponentially. Every interaction captured via the Web SDK or Batch ingestion adds to the total storage and processing requirements of theReal-Time Customer Profilestore.

Options A and B relate to theIdentity Serviceand the complexity of theIdentity Graph, but they generally do not drive the "Data Volume" metric in the same way as behavioral event history. While having many identifiers or namespaces increases the metadata size of a profile, the bulk of the data weight—and the metric most closely monitored for license overages regarding storage—is the volume of ingested ExperienceEvents. Developers must implement data retention strategies, such asExperience Event TTL, to purge old events and keep the total data volume within the client's contractual limits.

To satisfy the requirements for multi-channel marketing and behavioral segmentation while ensuring data consistency, the architect must select identities that bridge both internal systems and external communication channels. In the provided schema,customer_idserves as the primary key of the source system, making it the most reliable "anchor" for internal data consistency and linking behavioral records (like purchasing behavior) to the profile.

However, for multi-channel marketing activities, theemailfield is critical. By defining bothcustomer_idandemailas identities within the XDM Individual Profile schema, the Adobe Experience PlatformIdentity Servicecan perform identity stitching across different data streams. For instance, if a customer browses the website (identified by email) and later makes an in-store purchase (identified by customer_id), the platform can merge these fragments into a single, unified Real-Time Customer Profile.

Option A is incorrect because "first_name" is a descriptive attribute, not a unique identifier, and would lead to "collisions" (merging unrelated people with the same name). Option D is incorrect because "gender" is a demographic trait with very low cardinality; it cannot uniquely identify an individual. Option B, while containing valid identifiers, lacks the customer_id which is the primary key and the most stable link to the legacy RDBMS. SelectingOption Censures that the system can uniquely identify the individual internally while providing the necessary "stitching" point (email) to associate web, mobile, and email marketing interactions with that specific person.

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

Option Eis 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 Ais 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, theIdentity Graphcan 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 theMerge Policycan 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 fixedIdentity Guardrails(limits on the number of IDs per profile) to maintain performance and prevent "graph collapses" where unrelated individuals are merged.

ImplementingAttribute-Based Access Control (ABAC)for granular restrictions like geography and department requires a structured metadata approach. The first essential step is todefine 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 toincorporate 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 assignlabelsto roles; you assignpermissions/policiesthat 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.

In Adobe Real-Time CDP, anIdentity Graphis a structural representation of the relationships between different identity namespaces that belong to an individual. It is the engine that enablesIdentity Stitching. When multiple datasets are ingested into the platform, they often contain different "fragments" of a customer’s identity—for instance, one dataset might identify a user by their Email, while another uses a loyalty_id. The Identity Graph manages these connections, ensuring that all data associated with these various IDs is aggregated into a single, unified profile.

Option B describes a transaction log, not an identity structure. Option C is incorrect because the graph linksidentities(people), not the datasets themselves. Option D describes a "Customer Journey," which is a visualization of interactions over time; while the Identity Graphenablesthe tracking of that journey by linking the sessions, the graph itself is strictly the map of identity overlaps. By maintaining this graph, Real-Time CDP can resolve identities in real-time, allowing for consistent messaging even as a customer moves between anonymous browsing and authenticated states across different devices and platforms.