What determines which records become part of the profile during Adobe Real-Time CDP's profile assembly...

In Adobe Real-Time CDP, the profile assembly process is governed byMerge Policies. When data is ingested from multiple sources, it often results in "profile fragments"—disparate pieces of information about the same individual. The Merge Policy acts as the set of rules that theReal-Time Customer Profileservice uses to determine how these fragments are prioritized and combined into a single, unified view.

A Merge Policy specifies two critical components: theIdentity Stitchingmethod (Private Graph or Co-occurrence) and theAttribute Prioritization. The latter determines which dataset's values "win" in the event of a conflict (e.g., if Dataset A says a user lives in New York and Dataset B says Los Angeles). By associating a dataset with a specific merge policy, the architect ensures that only the data intended for the unified profile is included and that the most accurate, authoritative source is represented.

Options B and C are incorrect because profile assembly is an automated structural process, not a manual selection or a result of segmentation logic. Option D is incorrect because the identity graph defines thelinksbetween identities, but the Merge Policy is what defines therulesfor the data assembly itself. Therefore, the Merge Policy is the ultimate arbiter of how records are merged and which data points constitute the final "Active Profile."