What causes item data to be invalidated in the SAP Commerce Cloud entity cache? Note: There are 2 correct answer to this question.

In SmartEdit, what can you do with variations defined for a customization? Note: There are 3 correct answer to this question.

You have these example item types defined in myext-items.xml: What additional steps are needed to support the identification attribute?
< ?xml version="l.O" encoding="IS0-8859-1"? >
<items>
< itemtype code=" Passport" autocreate="true" generate="true" >
< deployment typecode="8995" table="passport" />
< attributes > ... </attributes>
< /itemtype >
< itemtype code="Student" extends="Customer" autocreate="true" generate="true" >
< attributes >
< attribute type="localized:Passport" qualifier="identification" >
< persistence type="property" />
< /attribute >
</attributes>
< /itemtype >
</items>
What additional steps are needed to support the identification attribute?
Define a one-to-many relation between Student and Passport using a relation tag with parameter locaIized="true".
Add a maptype tag for localized:Passport with parameters argumenttype="Language" and returntype="Passport".
Run an ant updatesystem command. A passportlp table will be generated to store the localized property values.
Define a localized Passport attribute for the Student type in myext/resources/localization/myext- locales_XY. properties.