Free Adobe AD0-E605 Practice Exam with Questions & Answers

In Adobe Real-Time CDP,Attribute-Based Access Control (ABAC)is a powerful governance feature that allows for granular control over who can view specific data at the field level. The primary mechanism used to drive this functionality isAccess Labels(Option A).

Access labels are metadata tags applied directly toXDM schema fieldsor datasets. These labels categorize data based on its sensitivity or functional purpose (e.g., "PII," "Financial," or "Regional"). Once a field is tagged with an access label, the platform’sPermissionssystem usesPoliciesto evaluate whether a user's assigned role has the authority to view data associated with that specific label. If a user belongs to a functional team that lacks the corresponding permission for a "Sensitive" label, the data in those specific schema fields will be masked or completely hidden from them throughout the platform UI, including the Profile viewer and Query Service.

Options B, C, and D are not recognized technical terms or primary attributes within the Adobe Experience Platform ABAC framework. While "Access Profiles" might exist in general security terminology, AEP specifically utilizesRolesandPoliciestied toLabels. By leveraging Access Labels, a company can ensure that internal teams—such as a support team or a regional marketing group—only see the data necessary for their specific business function, maintaining strict data privacy and security compliance.

When new attributes are added to anXDM Schema, several technical failure points must be verified to ensure data flows correctly into theReal-Time Customer Profile. The first and most critical investigation step is to review the schema and the ingestion payload mapping.

In Adobe Experience Platform, simply adding a field to a schema does not automatically populate it; the ingestion source (the REST API payload in this case) must have the new field mapped exactly to the correct XDM path. If there is a mismatch in the field name (e.g., preferred_channel vs. preferredChannel) or if the field was added to the schema but not "enabled for profile," the data will land in theData Lakebut will be ignored by theProfile Service.

Option A and D are unlikely to be the cause if other parts of the profile are updating correctly. Option C is rarely the issue for specific field missingness, as capacity issues usually result in total ingestion failure or significant latency across all fields. By verifying thePayload-to-XDM mappingand ensuring the schema is marked forProfile, the engineer can confirm that the data is being correctly recognized and stored within the customer's unified view.

In Adobe Experience Platform, managing theAddressable Audiencecount is critical for license compliance, especially when ingesting high volumes of top-of-funnel data via Web and Mobile SDKs.Pseudonymous TTL (Time-to-Live)is the primary architectural strategy used to automatically manage the lifecycle of profiles that lack a durable identity.

When users browse a website or app anonymously, the system creates profiles keyed off apseudonymous identifier(like an ECID). Without a management strategy, these transient profiles persist indefinitely, quickly exhausting the 5 million profile license limit. By configuring aPseudonymous TTLat the sandbox or identity level, the architect can instruct theReal-Time Customer Profileservice to automatically delete profiles that have not seen any activity within a specific timeframe (e.g., 14 or 30 days) and do not possess a "durable" identity (such as an Email or CRM ID).

Option A (Experience Event TTL) removes individual events but does not delete the profile record itself. Option B (Privacy API) is intended for one-off GDPR/CCPA requests, not automated capacity management. Option D (Datalake Storage TTL) only affects the long-term storage and not theActive Profilecount used for licensing. By implementing Option C, the architect ensures that only active or known customers occupy the 5 million slots, while stale, anonymous fragments are purged to make room for new prospects.

For high-volume data loading, theBatch Ingestion APIis the architecturally sound choice for maintaining high throughput while managing system resources effectively. Unlike streaming ingestion, which processes messages individually, the Batch Ingestion API allows for the uploading of large data files (such as Parquet or JSON) that are processed as a single unit of work.

To optimize infrastructure load, the architect should utilizespecified batch sizes. Adobe Experience Platform provides a "Large File Upload" workflow within the Batch Ingestion API that allows developers to break a single large file into smaller chunks, which are then stitched together on the platform side. This prevent timeouts and memory issues on the client-side infrastructure while ensuring the platform's ingestion engine can process the data in a scalable manner.

Option A is incorrect because a single HTTP API request is typically used for streaming or small payloads, not bulk profile loading. Option B is not a technical method, as even the UI utilizes these underlying APIs. By leveraging the Batch Ingestion API, the retailer can ensure that millions of profile records are validated against XDM schemas and moved into theData LakeandReal-Time Customer Profilestore with high efficiency and robust error reporting.

To create a unified Real-Time Customer Profile, Adobe Experience Platform relies on theIdentity Serviceto stitch data together across disparate sources. The correct approach involves configuringIdentity Namespaceswithin the XDM schemas used by each data source. An Identity Namespace provides context for an identity value (e.g., distinguishing an "Email" from a "CRM ID").

When multiple datasets are "Profile-enabled," the system looks for common identity markers. For example, a CRM record might contain a CRM_ID and an Email, while a website interaction contains an ECID and an Email. By defining these fields as identities within their respective schemas and assigning them to the correct namespaces, theIdentity Graphcan link the CRM_ID to the ECID via the shared Email.

Option A is incorrect because using a single namespace for different ID types would lead to data collisions and failed resolution. Option C is incorrect because datamustbe mapped to XDM and enabled for Profile to be included in the unified view; raw, unmapped data remains in the data lake and cannot participate in real-time services. Option D is a strategic choice but not a technical requirement for unification; the platform is designed to handle both high-velocity behavioral data and high-volume batch data (offline) simultaneously to form a complete 360-degree view.

When utilizing theAdobe Experience Platform Server-Side APIto communicate with theEdge Network, the most critical parameter is theDatastream 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.

Implementing data governance for sensitive personal data in Adobe Real-Time CDP requires a multi-layered approach involving labeling, access control, and privacy management.

The first step is applyingData Usage Labels (Option D)to sensitive datasets. These labels (such as PII or Sensitive) allow the system to identify which data points are subject to specific privacy regulations and govern how they are activated to downstream destinations.

Secondly,stricter access control (Option E)must be implemented usingRole-Based Access Control (RBAC)andAttribute-Based Access Control (ABAC). RBAC manages what a user can do (permissions), while ABAC manages what data a user can see based on labels applied to schemas and fields. This ensures that only authorized personnel can view or manipulate sensitive financial or personal records.

Finally, for ongoing compliance with regulations like GDPR or CCPA, the analyst must be able to processPrivacy Job Requests (Option B). This involves using the Adobe Privacy Service to fulfill "Right to be Forgotten" or "Right to Access" requests by deleting or exporting specific profile data from the system. Option A is counterproductive as non-sensitive data is rarely the priority for governance, and Option C is an over-restriction that would prevent legitimate business operations; instead, the platform uses policies to selectively restrict exports based on labels.

In Adobe Experience Platform,Identity Namespacesare used to categorize the types of identities that distinguish an individual across various channels and devices. When modeling data for theReal-Time Customer Profile, selecting the correctIdentity Typeis fundamental for accurate profile stitching and the integrity of the identity graph.

customer_id (Cross-Device ID):A customer_id is typically an internal, durable identifier assigned by a brand (such as a CRM ID or Loyalty ID). Since this ID remains constant regardless of the hardware or browser the user utilizes, it is classified as aCross-Device ID. This classification allows the Identity Service to link multiple device-specific IDs (like ECIDs) to a single, stable person-level identifier, facilitating a unified cross-channel view.

email_address (Email):For an email address, the recommended type isEmail. This is an out-of-the-box identity type optimized for handling string-based email identifiers. It is often the primary key used for marketing orchestration and cross-device identification when a user authenticates.

UsingCookie IDorDevice IDfor a customer_id would be technically inaccurate, as those are transient or hardware-bound.Person IDis a conceptual term rather than a standard identity type used for internal CRM IDs in the platform's namespace configuration. By correctly assigningCross-Device IDto the internal ID andEmailto the email field, developers ensure that the Identity Service can effectively perform "identity stitching" to merge data fragments into a cohesive profile.

Adobe Experience PlatformEdge Segmentationis designed for ultra-low latency personalization and carries specific architectural guardrails that differ from Hub-based (Batch or Streaming) segmentation. One of the primary limitations of Edge Segmentation is thelookback windowand the complexity of time-based event relationships.

Edge segmentation is optimized for "in-session" or very recent cross-session behavior. A segment requiring a30-day lookbackor a specific duration of inactivity (over 30 days) between two discrete events exceeds the current technical capabilities of the Edge Network's real-time evaluation engine. Edge segments typically support shorter lookback windows (typically up to 24 hours for certain attributes) and are intended to react to the "current" state of the user.

Option B is incorrect because Web SDK automatically includes timestamps. Option C is incorrect because segments are evaluated against ingested data based on rules, not manual "population" flags during ingestion. Option D is unlikely as the prompt implies the data is being ingested but just not populating the segment. Therefore, the "30 days" logic is the root cause; while this segment would work perfectly as aBatch Segmentin the Hub, it is ineligible forEdge Segmentationdue to the memory and processing requirements of maintaining a 30-day state at the network edge.

When a business requirement specifies that data updates must be sent to a third-party tool at a fixed daily interval, the architecture must leverageBatch (C)andScheduled (D)activation patterns. In Adobe Real-Time CDP, destinations are categorized based on how they receive data.Batch-based destinations(such as Amazon S3, SFTP, or Azure Blob Storage) are specifically designed to export data in files rather than individual event streams.

TheScheduledpattern is the operational component that triggers these batch exports. Within the destination dataflow configuration, a marketer can define an export schedule, such as "Daily," to ensure that all profile attributes and segment memberships that have changed or qualified since the last run are bundled into a file and delivered to the external tool. This approach is highly efficient for third-party systems that do not support real-time APIs or for use cases where high-volume data synchronization is preferred over instantaneous updates.

Options A and B are incorrect for this specific use case.Real-Time(streaming) activation sends updates immediately as they occur, which contradicts the "daily interval" requirement.Asynchronousis a technical processing method but not a configurable activation pattern within the Adobe Experience Platform UI. By combining a Batch destination with a Daily Schedule, the marketer ensures predictable data delivery that aligns with the processing capabilities of the third-party tool while maintaining system performance by avoiding unnecessary constant streaming.