The most direct and intended method within the Adobe Experience Platform UI to monitor and be notified of ingestion issues is by creating alert rules. A data engineer can configure specific rules to trigger notifications for events like "Streaming end-to-end ingestion failure" or "Flow run failures." These alerts can be sent via email or to a webhook, providing immediate notification when an error occurs. This allows the engineer to promptly investigate the detailed error messages available in the dataflow monitoring dashboard to understand the root cause.

B. Partial ingestion is a data handling strategy to process valid records in a batch, not a monitoring capability to understand the cause of failures.

C. While Adobe I/O Events can be used for notifications, setting up alert rules in the UI is the more straightforward, built-in AEP capability for this specific purpose.

D. "System Events" is a generic term. "Alert Rules" is the specific, configurable feature in AEP designed to monitor and notify users about these events.

1. Adobe Experience Platform Documentation. (2023). Alerts overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/alerts/home.html. (This document introduces alerts as the primary mechanism for monitoring Platform operations.)

2. Adobe Experience Platform Documentation. (2023). Subscribe to alerts events. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/alerts/ui/subscribe.html. (See the table of "Available events," which lists "Streaming end-to-end ingestion failure" and "Flow run failed" as specific, monitorable events.)

3. Adobe Experience Platform Documentation. (2023). Monitor dataflows in the UI. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/sources/ui/monitor.html. (This page describes how to view detailed error diagnostics after being notified of a failure, which complements the function of alerts.)

To create a unified customer profile across multiple platforms, a common identity must be used to link the disparate data. Defining common identity namespaces (e.g., a hashed email address, a loyalty ID) that are used across these platforms allows the Adobe Experience Platform Identity Service to recognize that the activities belong to the same individual. This process stitches the identities together into a single identity graph, forming the basis of the real-time customer profile.

A. Merge policies resolve attribute conflicts within a single profile; they do not define how different identities are linked together in the first place.

B. Using unique identity namespaces for each platform would keep the profiles separate and prevent the system from understanding they belong to the same person.

1. Adobe Experience Platform Documentation. (2023). Identity Service overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/identity/home.html?lang=en. The overview states, "Identity Service helps you gain a better view of your customers and their behavior by bridging identities across devices and systems".

2. Adobe Experience Platform Documentation. (2023). Identity namespaces overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/identity/namespaces.html?lang=en. This document explains that namespaces are a component of an identity and are used to provide context. Using a common namespace across sources is fundamental to stitching.

Merge policies in Real-Time Customer Profile define how data from different datasets is combined to create the unified profile view. If a dataset is not included in the merge policy being used to view the profile, its data will be excluded from the final unified profile, even if it has been successfully ingested. In this scenario, the most likely reason the mobile and location data are missing is that the datasets containing these fragments were not added to the specific merge policy being used for inspection.

B. Real-Time Customer Profile is designed to unify fragments that arrive at different times; simultaneous loading is not a requirement for successful merging.

C. The order of fragment ingestion does not typically cause data to be entirely missing. Merge policies use rules like timestamps to resolve conflicts, not to exclude data based on load order.

D. This is factually incorrect. Real-Time Customer Profile fully supports standard data types, including mobile phone numbers and location information.

1. Adobe Experience Platform Documentation. (2023). Merge policies overview. Adobe Experience League. The documentation states, "Merge policies are rules that Platform uses to determine how data from multiple sources will be prioritized and combined to create a unified profile."

2. Adobe Experience Platform Documentation. (2023). Real-Time Customer Profile Guide. Adobe Experience League. In the section "Working with merge policies," it explains that you can create multiple merge policies and that each policy can include a different combination of datasets.

“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”)

Adobe Real-Time CDP's Segment Builder is the designated tool for creating audiences based on specific behavioral criteria. To target repeat customers, a marketer can define rules that filter for profiles based on the number of visit events (frequency) within a specific timeframe (recency). This approach directly leverages the time-series event data stored in the Experience Data Model (XDM) to create a precise, rule-based audience that meets the campaign's requirements without needing to compose multiple pre-existing audiences or import lists.

A. Audience Composition is for combining existing audiences, not for creating a new one from scratch based on specific event rules like frequency and recency.

C. While CRM data can be used, the core requirement is to build rules based on visit frequency and recency, which is a function of the rule builder, not composition.

D. Importing an audience from Adobe Target is a valid workflow, but it does not involve building the audience within Real-Time CDP using its native rule-building capabilities.

1. Adobe Experience Platform. (n.d.). Segmentation Service overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/segmentation/home.html. (This document outlines the purpose of the Segmentation Service in creating audiences from customer data.)

2. Adobe Experience Platform. (n.d.). Segment Builder user guide. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/segmentation/ui/segment-builder.html. (See the section "Building segment definitions," which details how to add rules based on events and attributes, including temporal constraints for recency.)