You are creating a product with a new feature using a classification system. What should you pay attention to? Note: There are 2 correct answer to this question.

• A.Create a classifying category with an attribute assignment model and assign it to the product.
• B.Create an empty classification unit even if the new feature doesn't have a unit.
• C.Use feature descriptor values if the values of the new feature are limited to a selection.
• D.Use a feature descriptor to represent the name of the new feature and assign it to the product.

Comment: *

Name: *

Email: *

Verification: *

You are implementing a new custom promotion action that changes the delivery mode of an order. What steps are required to make sure that the effects of this action are reverted as soon as the condition that triggered it is NO longer fulfilled? Note: There are 2 correct answer to this question.

• A.Implement your custom action item so that it can store the original delivery mode
• B.Define a new session attribute to store the original delivery mode
• C.Implement the undo method in your custom rule action strategy
• D.Create a promotion that uses the inverse action if the condition is NOT fulfilled

Comment: *

Name: *

Email: *

Verification: *

Which configuration options are available on a cache region? Note: There are 3 correct answer to this question.

• A.Clustering enabled
• B.Persistence mode
• C.Eviction policy
• D.Size
• E.Statistics enabled

Comment: *

Name: *

Email: *

Verification: *

What can a *-backoffice-widgets.xml contain in the Backoffice framework? Note: There are 2 correct answer to this question.

• A.Widget connection
• B.Context configuration object definition
• C.Spring beans of backoffice web context
• D.Virtual socket definition

Comment: *

Name: *

Email: *

Verification: *

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.

• A.Define a one-to-many relation between Student and Passport using a relation tag with parameter localized="true".
• B.Add a maptype tag for localized:Passport with parameters argumenttype="Language" and returntype="Passport".
• C.Run an ant updatesystem command. A passportlp table will be generated to store thelocalized property values.
• D.Define a localized Passport attribute for the Student type in myext/resources/localization/myext- locales_XY.properties.

Comment: *

Name: *

Email: *

Verification: *