AD0-E605 · Question #96
After creating the Entity Relationship Diagram (ERD) of the data sources that will be connected into an Adobe Experience Platform (AEP) implementation for a utility company, the service details (inclu
The correct answer is A. Create a Data Type B. Create a Field Group (cross-class). Data Types (A) and cross-class Field Groups (B) are the two correct mechanisms because they each solve a distinct reuse problem. A Data Type is an XDM reusable object definition - it lets you define the service details structure (name, cost, type, category) once and embed it mult
Question
After creating the Entity Relationship Diagram (ERD) of the data sources that will be connected into an Adobe Experience Platform (AEP) implementation for a utility company, the service details (including information such as name, cost, type, and category) appear multiple times across different entities (for example, in the transactional events and in the customer profile details). When designing the XDM data model for that ERD, the data architect and the business stakeholders validate that the service details information must be included at both levels, record, and time series. The service details will be used multiple times within the same structure. In what two ways should the service details be defined in the AEP data model to make it consistent and re-usable? (Choose two.)
Options
- ACreate a Data Type
- BCreate a Field Group (cross-class)
- CCreate a Class
- DCreate a Schema
How the community answered
(53 responses)- A81% (43)
- C13% (7)
- D6% (3)
Explanation
Data Types (A) and cross-class Field Groups (B) are the two correct mechanisms because they each solve a distinct reuse problem. A Data Type is an XDM reusable object definition - it lets you define the service details structure (name, cost, type, category) once and embed it multiple times within the same Field Group or schema without redefining it. A cross-class Field Group is a bundle of fields that can be attached to schemas of different XDM classes - enabling the same service details fields to be used in both an XDM Individual Profile schema (record-level) and an XDM ExperienceEvent schema (time-series level), satisfying the requirement to appear at both levels consistently.
Why C is wrong: A Class defines the foundational behavior of a schema (record vs. time series) and represents a new type of entity - not a set of reusable fields. Service details are attributes, not a new entity type.
Why D is wrong: A Schema is the complete blueprint for an entire dataset. You can't embed one schema inside another; schemas consume Field Groups and Data Types, they don't become them.
Memory tip: Think "Data Type = object blueprint for within-schema reuse; cross-class Field Group = field bundle for across-schema (cross-class) reuse." The word "within" maps to Data Type, and "cross" maps directly to cross-class Field Group.
Topics
Community Discussion
No community discussion yet for this question.