The "Timestamp ordered" merge method is the correct choice because it prioritizes data based on the event timestamp associated with each attribute. When a conflict occurs between attributes from different datasets, this method ensures the value from the most recent timestamp is used to form the unified profile. This directly addresses the requirement to have attributes from the "latest datasets" take precedence and is applied dynamically across all datasets contributing to the profile without manual intervention.

A. Dataset timestamp: This is not a valid, selectable merge method when creating a custom merge policy in the Adobe Experience Platform user interface. The available methods are "Timestamp ordered" and "Dataset precedence".

C. Dataset precedence: This method requires creating a pre-defined, static list of datasets. It prioritizes data based on a dataset's position in that list, not on the recency of the data, which contradicts the use case requirement.

1. Adobe Experience Platform

Real-Time Customer Profile Guide

"Merge policies overview."

Section: Merge methods - This section explicitly lists and defines the two available merge methods: "Timestamp ordered" and "Dataset precedence." It states

"When creating a merge policy

you can specify a merge method... There are two possible merge methods: Timestamp ordered and Dataset precedence." This confirms that "Dataset timestamp" (Option A) is not a valid choice.

Section: Timestamp ordered - The documentation describes this method: "When merging profile fragments

if a conflict occurs

the fragment with the more recent timestamp is prioritized." This directly supports the selection of Option B as it fulfills the requirement to use the latest data.

Section: Dataset precedence - This section explains: "When merging profile fragments

if a conflict occurs

the fragment from the dataset that is higher on the precedence list is prioritized." This confirms why Option C is incorrect for a use case based on data recency.