P_C4H340_24 SAP Certified Development Professional - SAP Commerce Cloud Developer Questions and Answers

Cached classification attributes provide better performance than fixed properties.

Classification attributes are applied dynamically in response to customer actions.

Business users can create or modify classification attribute definitions using the Backoffice.

D. Rebuilding and redeployment are NOT required.

Create or reuse an add-on, and install it into the storefront.

Create a new multiplexer widget for the borderlayout widget.

Create or reuse a Backoffice extension with the proper meta information.

Add a new layout widget in config.xml.

Use feature descriptor values if the values of the new feature are limited to a selection.

Create an empty classification unit even if the new feature doesn't have a unit.

Use a feature descriptor to represent the name of the new feature and assign it to the product.

Create a classifying category with an attribute assignment model and assign it to the product.

Define the process in BPMN format.

Define the actions as Spring beans.

Create actions in Java code.

Define actions as new item types.

Define the process in XML format.

Both staged and online media items now refer to the same image file in the file system.

The staged and online media items now refer to two different image files in the file system.

The values of the attributes are copied from the source item in the staged catalog to the target item in the online catalog.

The media format in the staged version is also synchronized to the media format in the online version.

1

3

4

2

Create a search restriction to secure an integration object for only a certain integration user group.

Set up access rights for integration objects.

Force-delete an integration object even if it is associated with an InboundChannelConfiguration (ICC).

Export the configuration types so that they can be imported into a target system.

Trigger the experience calculation for certain URL patterns.

Trigger the experience calculation after a defined number of requests.

Trigger the experience calculation when the customer logs in.

Trigger the experience calculation when the customer adds a product to the cart.

Trigger the experience calculation when the customer is promoted to a reward-level status.

All instances of the enclosing type are stored in the specified database table.

Only non-inherited properties of the enclosing type are stored in the deployment table.

The deployment typecode is used as part of the primary key (PK) of that type's items.

The name of the deployment table is generated automatically.