Free AD0-E605 Practice Test

Total Data Volume is a license metric for Adobe Real-Time CDP that measures the total size of data stored in the data lake. Experience Events, which capture behavioral data over time, are a primary contributor to this volume. Each event record adds to the total storage consumed. Therefore, the number of Experience Events linked to profiles directly impacts the Total Data Volume calculation. This metric is distinct from Profile Richness, which is related to the number of attributes and identifiers per profile.

A. The number of unique identifiers contributes to the "Profile Richness" license metric, not the Total Data Volume, which measures storage size.
B. The number of namespaces is also a factor in Profile Richness, reflecting the diversity of identity sources, not the total storage volume.

1. Adobe Experience Platform Documentation. (2023). License entitlement usage dashboard overview. Adobe Experience League. See the section "License entitlement usage dashboard metrics," which defines "Total Data Volume" as "the total data size in the data lake" and "Profile Richness" as related to "the average number of attributes per profile."

Rule-based segments in Segment Builder allow chaining multiple logical conditions, while batch-evaluation segments support complex expressions and extended look-back windows—ideal for intricate filters needed for a sale event audience.

B. Audience Export merely transfers existing audiences; it does not create or evaluate complex real-time logic.
C. Computed attributes aggregate metrics but don’t themselves filter multiple complex conditions; they can be inputs, not full segment strategies.

1. Segment Builder UI – “Rule-based segments enable combining several logical operators for sophisticated audience definitions.” (Docs › Segmentation › Segment Builder, Rules section)

2. Segmentation Best Practices – “For complex expressions or long look-back periods, create batch-evaluation segments.” (Experience League, Best-Practices, bullet ‘Batch’)

3. Computed Attributes Guide – “Computed attributes summarize event data; use them inside segments but they do not replace segmentation logic.” (Docs › Profile › Computed Attributes, Overview)

The most efficient and scalable method to set up attribute-based access control (ABAC) in Adobe Real-Time CDP is by applying custom labels to data attributes (such as schema fields or segments) and then creating policies that link these labels to user roles. This approach allows administrators to define access rules based on the data's characteristics rather than managing permissions for each user or group individually. When a user's role has a policy attached, their access to data is dynamically determined by the labels on that data, making it highly efficient to manage complex access requirements.

A. Creating individual policies for each user group is a feature of role-based access control (RBAC) and is less efficient and scalable than ABAC.
B. Distributing data into different databases is a data architecture strategy, not the method for implementing ABAC within the AEP environment.
C. Regularly updating user roles is a manual maintenance task associated with RBAC, which ABAC is designed to simplify and automate.

1. Adobe Experience Platform Documentation. (2023). Attribute-based access control overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/access-control/abac/overview.html. (The "Introduction" states, "Attribute-based access control is a capability... that enables administrators to control access to specific objects and/or capabilities based on attributes. Attributes are metadata that describe objects, such as a label that has been added to a schema field or segment.")

2. Adobe Experience Platform Documentation. (2023). End-to-end guide for attribute-based access control. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/access-control/abac/end-to-end-guide.html. (This guide outlines the workflow: "Label your data", "Create roles", and "Create policies" that connect roles and labels.)

Attribute-Based Access Control (ABAC) in Adobe Experience Platform operates on a two-step principle. First, you must define and apply labels to specific schema fields (attributes) that you want to control, such as "geographical locations" and "departments." Second, you create an access control policy that incorporates these labels and assigns permissions to user roles. This policy dictates that users in a specific role can only access data where the labeled attributes match the policy's criteria.

B. Including all attributes in every policy is unnecessary and inefficient. Policies should only contain the specific labeled attributes required for control.
C. Labels are applied to schema fields (data), not directly to user roles. Roles are granted permissions through policies that reference these labels.

1. Adobe Experience Platform Documentation. (2023). Attribute-based access control overview. Adobe Experience League. See the "End-to-end workflow" diagram and description, which outlines the process: "Label your schema fields," "Create a role," and "Create an access policy."

2. Adobe Experience Platform Documentation. (2023). Attribute-based access control end-to-end guide. Adobe Experience League. See "Step 2: Label your schema fields" and "Step 4: Create an access policy."

A comprehensive data governance strategy for sensitive data in Real-Time CDP involves three key actions. First, applying data usage labels to sensitive datasets (D) is the foundational step to classify data. Second, enabling stricter access control using RBAC and ABAC (E) ensures that only authorized users can view or manipulate this sensitive data. Third, leveraging Privacy Service to manage privacy job requests (B), such as data access or deletion requests from consumers, is essential for complying with regulations like GDPR and CCPA.

A. While labeling all data is good practice, the immediate priority for handling sensitive data and ensuring compliance is to label the sensitive datasets first.
C. Completely disabling the ability to export personal data is an overly broad and impractical measure; governance focuses on controlling exports based on policies.

1. Adobe Experience Platform Documentation. (2023). Data Governance overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/data-governance/home.html. (See the "Data usage labels" and "Data usage policies" sections.)

2. Adobe Experience Platform Documentation. (2023). Privacy Service overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/privacy/home.html. (See the "Introduction" which describes creating and managing privacy jobs.)

3. Adobe Experience Platform Documentation. (2023). Attribute-based access control overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/access-control/abac/overview.html. (This document explains how to use labels to restrict access to specific data.)

“Frequent visitors” and “purchases over $10,000 in the past six months” are conditions tied to events occurring within a defined time window. Event-based segmentation lets you specify behavioral criteria with temporal constraints, making it the best fit.

A. “Population-based” is not a supported segmentation type in Real-Time CDP.
C. Profile-based segmentation works on static attributes, not time-bounded behavioral events.
D. “Time-based segmentation” is not a native classification; time windows are configured inside event-based rules.

1. Segment Builder UI – “Choose Event criteria to build rules like ‘purchases over $100 in last 30 days.’” (Docs › Segmentation › Segment Builder, Event criteria section)

2. Segmentation Best Practices – “Use event-based rules for behaviors within a time frame such as visit frequency or purchase value.” (Experience League, Best-Practices, table “When to use event criteria”)

Attribute-based access control (ABAC) in Adobe Experience Platform uses labels to categorize schema fields and other resources based on their sensitivity or organizational relevance. These labels are the primary attribute applied directly to objects. Administrators then create roles with specific permissions and define policies that link these roles and labels. This system allows for granular control, ensuring that users can only access the specific schema fields for which they have been granted permission via the labels applied to them.

B. "Access Profile" is not a standard ABAC component in AEP. Access is managed through roles assigned to product profiles in the Adobe Admin Console.
C. "Access Schema" is not a feature. Schemas are the objects to which access control labels are applied, not the control mechanism itself.
D. "Access Security" is a general term for the entire domain of security and is not a specific feature or attribute within AEP's ABAC framework.

1. Adobe Experience Platform Documentation. (2023). Attribute-based access control overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/access-control/abac/overview.html. (See the "Attribute-based access control components" section, which lists "Labels" as a key component applied to objects like schema fields.)

2. Adobe Experience Platform Documentation. (2023). End-to-end attribute-based access control guide. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/access-control/abac/end-to-end-guide.html. (Step 2, "Add labels to your schema fields," explicitly demonstrates that labels are the attribute applied to schemas.)

In Adobe Experience Platform, identities are categorized using standard namespaces. An emailaddress is a personally identifiable piece of information and should use the standard "Email" identity type. A customerid is typically a system-specific, deterministic identifier (like a CRM ID) used to recognize a customer across different devices and sessions after they authenticate. The "Cross-Device ID" namespace is the appropriate standard type for such an identifier, as its purpose is to link cross-device activity to a single profile.

B. customerid uses a type of Cookie ID; emailaddress uses a type of Device ID: This is incorrect. A customerid is not a cookie, and an email address is not a device-specific identifier.
C. customerid uses a type of Person ID; emailaddress uses a type of Email: "Person ID" is not a standard, out-of-the-box identity namespace in Adobe Experience Platform. "Cross-Device ID" is the correct standard choice.

1. Adobe Experience Platform Documentation, Identity Service. (2023). Identity namespaces overview. "The following table outlines the standard identity namespaces provided by Adobe." The table lists "Email" and "Cross-Device ID" as standard namespaces.

2. Adobe Experience Platform Documentation, Identity Service. (2023). Standard identity namespaces. "Cross-Device ID: Used for identifiers that are deterministic in nature and can be used to identify the same person across devices, such as a CRM ID."

Adobe Experience Platform (AEP) Sandboxes are the recommended feature for this scenario. Sandboxes are virtual partitions within a single AEP instance that isolate data, profiles, and other resources. This allows different platform engineering teams to develop and test applications, data models, and configurations independently without impacting the production environment or each other's work. Assigning different teams to different sandboxes provides the necessary segregation for development, testing, and production lifecycles, ensuring effective management and isolation of data and profiles across various services and teams.

A. The Data Lifecycle feature is used to manage data retention and schedule the deletion of datasets or records, not to segregate development environments.
C. The Data Governance Framework is used to manage how data can be used (e.g., for marketing), not to partition the platform for different teams.
D. Adobe Privacy Service is a tool for managing consumer data privacy requests (GDPR/CCPA), not for managing development sandboxes or team segregation.

1. Adobe Experience Platform Documentation, "Sandboxes: Sandboxes overview". The document states: "Sandboxes are virtual partitions within a single instance of Adobe Experience Platform, which allow for seamless integration with the development process of your digital experience applications... Sandboxes are used to isolate development environments and to help you manage the development lifecycle."

2. Adobe Experience Platform Documentation, "Sandboxes: Access control for sandboxes". This section explains how permissions and roles can be used to assign specific users (teams) to specific sandboxes, reinforcing their use for team segregation.

When ingesting data using the Batch Data Ingestion API, the payload must conform to a specific Experience Data Model (XDM) schema. This schema acts as a constraint, defining the structure, data types, and fields that are permissible within the batch. If the data in the payload does not validate against the referenced XDM schema, the batch will fail. This ensures data consistency and quality within the Adobe Experience Platform data lake and Real-Time Customer Profile.

A. Encryption Type: Encryption is a transport-level or storage-level concern, not a constraint defined within the API payload for a specific batch.
B. Batch Size: Batch size is a constraint on the overall batch file or set of files, but it is not a parameter defined within the JSON payload itself.
D. Batch Frequency: Batch frequency relates to how often data is sent. It is a scheduling aspect of the data pipeline, not a constraint within the data payload.

1. Adobe Experience Platform Documentation. (2023). Batch Data Ingestion API overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/data-ingestion/batch-ingestion/overview.html. (The "How it works" section explains that data must conform to an XDM schema).

2. Adobe Experience Platform Documentation. (2023). Create a batch. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/data-ingestion/batch-ingestion/api-reference.html#create-a-batch. (The API reference shows the datasetId is required, which is associated with a specific XDM schema, thus enforcing the schema constraint).