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

Implement the ClusterAwareEvent interface.

Extend the AbstractEvent class.

Implement the TransactionAwareEvent interface.

Change the platformClusterEventSender Spring bean configuration.

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.

When modifying, Rebuilding and redeployment are NOT required.

To store the configuration of the rule engine

To provide the data as facts in rule conditions and actions

To persist the results of the rule evaluation

To eliminate unnecessary data provided by complex objects

Overload the existing method of CommerceCartService by adding the new parameter.

Add a new property to CommerceCartParameter in a beans.xml file.

Extend the default strategy called by the method to handle the new parameter.

Extend the default implementation of the method to handle the new parameter.

FULL

UPDATE

DELETE

PARTIAL_UPDATE

When an administrator approves the order

After the order is placed, but before it is sourced successfully

When the user adds items to the cart

After the order is placed and after it has been sourced successfully

A webhook requires an integration object as notification payload and consumed destination as the webhook…

A webhook uses the optional filter attribute to control which consumed destination will received notifications

A webhook can be configured to send notifications when an item is created, updated or deleted.

A webhook guarantees the At Least Once(ALO) principal and concurrent events are not completely discarded.

A populator

An interceptor

A voter

A controller

2000 products and 1000 price rows

1000 products and 2000 price rows

2000 products and 2000 price rows

1000 products and 1000 price rows

A type access right on the Product type for the user group

A search restriction on the UserGroup type

A search restriction on the Product type for the user group

A type access right on the UserGroup type

The Page item has a position map that links each component to the component in the page that

the item should be displayed in.

The ContentSlot item’s code property is used to determine which slot in the page that the item

should be displayed in.

The component’s CurrentPosition attribute is used to determine which component within the

page the item should be displayed in.

The position attribute in the ContentSlotForTemplate item is used to identify the slot in the page

that the item should be displayed in.

Create a new EventTemplate in an ImpEx file.

Create a new ItemType in an items.xml file.

Extend a pre-defined event DTO in a custom beans.xml.

Create a new DTO in a beans.xml file.

A list of Content Catalogs providing the pages, slots, and other CMSItems shown to Customers

A list of Product Catalogs providing the product info shown to Customers

A list of customers associated with the BaseStore.

A list of warehouses that support the delivery

A list of points of service that represent local branches

Implement the undo method in your custom rule action strategy

Define a new session attribute to store the original delivery mode

Implement your custom action item so that it can store the original delivery mode

Create a promotion that uses the inverse action if the condition is NOT fulfilled

Manually create SolrValueRange items to define the range boundaries.

Create a SolrValueRangeSet, add SolrValueRange items, and add to the SolrIndexProperty.

Define the number of ranges in the SolrIndexProperty.

Provide sample data that is used to

generate the SolrValueRange items.

Define the cadence of the ranges in the SolrIndexProperty.

Provide the sample data that is used

to generate the SolrValueRangeSet.

Create SolrValueRange items to define the range boundaries.

Add them to the SolrIndexProperty

They have the same feature parity, but Spartacus is more upgradable.

Accelerators are JSP-based while Spartacus is JavaScript-based.

They are both using OCC API to connect to the commerce platform.

They are both extensible according to project requirement.

Create a JSP named [componentTypeCode].jsp that pulls data from a [ComponentTypeCode]Data

object.

Configure a custom controller bean and redefine the DefaultCMSComponentController alias to

point to it.

Configure a renderer in the cmsComponentRendererRegistry that doesn’t need to use a data

object or a view.

Create a controller for this component and register it in the cmsComponentControllerRegistry

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.

Create models using Java’s ‘new’ keyword

Use modelService.get() to obtain an item referenced by another using its PK.

Save the model using the modelService after the model is modified.

Create models using modelService.create( ).

The output socket’s type does not have to be the same as the input socket’s type.

The input socket’s type should be the same as the output socket’s type.

The output socket's type must be the same as the input socket type.

The input socket's type must be a sub type of a composed item type.

Synchronize the category page in the Backoffice Administration Cockpit

Run a Solr indexer operation in the Backoffice Administration Cockpit

Synchronize the involved product in the Backoffice Product Cockpit directly

Re-import the price using ImpEx