What are two considerations when choosing an object approach over free-form fields?

An Adobe Journey Optimizer team member needs to create a new schema.

What are two considerations when choosing an object approach over free-form fields? (Choose two.)
A . Objects indirectly help in creating a shorter structure, making it easier to reference the fields while using Adobe Experience Platform Query Service.
B. Objects indirectly help in creating a good menu structure in the Segment Builder Ul. The grouped fields within the schema are directly reflected Q in the folder structure provided in the Segment Builder Ul.
C. Objects indirectly help increase the visibility of the fields, since they are created directly under the root object of the schema (jenantld).
D. Objects are best used when creating a logical grouping of certain fields.

View Answer

Answer: B D

Explanation:

When choosing an object approach over free-form fields to create a schema, the developer should consider two advantages of using objects:

* Objects indirectly help in creating a good menu structure in the Segment Builder UI. The grouped fields within the schema are directly reflected in the folder structure provided in the Segment Builder UI. This makes it easier for the user to find and select the desired fields when creating a segment based on the schema.

* Objects are best used when creating a logical grouping of certain fields. For example, if the developer wants to group fields related to person details, such as name, gender, and age, they can create an object named "Person Details" and add those fields as properties of that object. This makes the schema moreorganized and structured. The other options are not valid or relevant considerations when choosing an object approach over free-form fields. Objects do not indirectly help in creating a shorter structure, making it easier to reference the fields while using Adobe Experience Platform Query Service. In fact, objects may make the structure longer and more complex, as they require dot notation to access their properties. For example, personDetails.name is longer and more complex than name. Objects also do not indirectly help increase the visibility of the fields, since they are created directly under the root object of the schema (tenantId). In fact, objects may make the fields less visible, as they require more navigation to access their properties. For example, personDetails.name is less visible than name.

References:

* https://experienceleague.adobe.com/docs/experience-platform/xdm/tutorials/create-schema-ui/step4-field-p

https://experienceleague.adobe.com/docs/journey-optimizer/using/segmentation/create-segment.html?lang