In personalization (based on SmartEdit), you want to configure when the experience calculation is triggered for registered customers without requiring any customization. What are the available options? Note: There are 3 correct answer to this question.

• A.Trigger the experience calculation when the customer is promoted to a reward-level status.
• B.Trigger the experience calculation when the customer logs in.
• C.Trigger the experience calculation for certain URL patterns.
• D.Trigger the experience calculation after a defined number of requests.
• E.Trigger the experience calculation when the customer adds a product to the cart.

Comment: *

Name: *

Email: *

Verification: *

In an extension named myext, you defined Pump, a subtype of the Product item type with a property named efficiency. You have also extended the productDTO bean to have an efficiency property. To copy the efficiency property to the productDTO, what do you need to do? Note: There are 2 correct answer to this question.

• A.Write a PumpProductConverter class that extends AbstractPopulatingConverter, and copies the efficiency property from the Pump item to the productDTO bean if the item is an instance of Pump. Configure an instance of this converter in myext-spring.xml.
• B.Write a PumpAttributePopulator class that copies the efficiency property from the item to the OTO only if its method is passed an instance of PumpModel. Define a bean for this new class in myext-spring.xml, and use a modifyPopulatorList bean to add it to the productConverter's list of populators.
• C.Create a PumpPopulator class that extends ProductPopulator and, if necessary, copies the efficiency property from the Pump item to the productDTO bean. In myext-spring.xml, redefine the productPopulator alias to point to an instance of PumpPopulator.
• D.Make sure the definition of the Pump item type defines the efficiency attribute with persistence type property. When you run ant all, the productConverter class generated in bootstrap/gensrc will copy the efficiency property to the productDTO.

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

Comment: *

Name: *

Email: *

Verification: *

What is the effect of the redeclare attribute within an itemtype definition? Note: There are 2 correct answer to this question.

• A.It can be used to change the class of an itemtype.
• B.It can be used to change the name of an attribute.
• C.It can be used to change the modifier of an attribute.
• D.It can be used to change the type of an attribute.

Comment: *

Name: *

Email: *

Verification: *

Which of the following can you configure in a widget definition (definition.xml) file? Note: There are 3 correct answer to this question.

• A.The business logic of the widget via a bean shell script
• B.The available non-virtual sockets
• C.The default values for widget settings
• D.The view file
• E.The available virtual sockets

Comment: *

Name: *

Email: *

Verification: *