Exam AD0-E605 Topic 3 Question 4 Discussion

Migrating from a highly normalized RDBMS to Adobe Real-Time CDP requires transitioning from a "table- join" mindset to aProfile-plus-Behaviormodel. In Adobe Experience Platform, the core of the NoSQL architecture is theReal-Time Customer Profile, which is assembled from two distinct types of data:
attributes and events.
The optimal approach (Option C) involves creating anXDM Individual Profileschema to act as the "source of truth" for slow-changing patient demographics (e.g., name, DOB, insurance ID). Simultaneously, time- series data such as patient visits, diagnoses, and treatments should be modeled using theXDM ExperienceEventclass. Unlike an RDBMS where you might link five tables via foreign keys, XDM uses Primary Identitiesand theIdentity Serviceto "stitch" these events to the profile in real-time.
Option A is technically incorrect because "demographics" and "patient events" are not the names of the base classes (the classes areXDM Individual ProfileandXDM ExperienceEvent). Option B (monolithic) would create a massive, non-performant record that fails to capture the chronological nature of healthcare visits.
Option D is incorrect because Adobe Experience Platform does not support traditional SQL composite keys for linking schemas; instead, it relies on a flattened, denormalized event structure orLookup Relationships.
By using a Profile-Event architecture, the healthcare provider can perform real-time segmentation (e.g.,
"Patients with Diagnosis X who visited in the last 24 hours") with extreme efficiency.