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

2000 products and 1000 price rows

1000 products and 2000 price rows

2000 products and 2000 price rows

1000 products and 1000 price rows

FULL

UPDATE

DELETE

PARTIAL_UPDATE

Assign it to a maximum of one page using a ContentSlotForPage item.

Add a list of CMSComponents to it.

Assign it to one or more pages using ContentSlotForPage items.

Define valid CMS Components for it by modifying the ElementsForSlot relation.

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.

You can monitor the inbound integration requests using the Meta API.

In Outbound monitoring, if the source of the OutboundRequest is not from outbound sync or

webhooks, it is set as UNKNOWN.

If you want to disable the monitoring, you need to change the dedicated properties in

local.properties and restart the commerce cloud server.

If the number of batches in a bulk request exceeds the limit allowed, then the system records one

Inbound Request with the payload.

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

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 a class that extends AbstractPatchesSystemSetup and configure any data patches, which

can run an import of your ImpEx files during an update.

Extract a SQL script of all the changes in a single environment, which a DBA can then run directly

against the database for all remaining environments.

Create a class that extends AbstractSystemSetup and use the @SystemSetup annotation with

TYPE.PROJECT, which can run an import of your ImpEx files during an update.

With each deployment, manually import the ImpEx files via the hybris Admin Console or via the

ant importimpex target.

Split by warehouse

Split by stock availability

Split by named delivery date

Split by order date

Split by payment method

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.

Make sure the definition of the Pump item type defines the efficiency attribute with persistence

type property. When you run at all, the productConverter class generated in bootstrap/gensrc will

copy the efficiency property to the productDTO.

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.

Write a PumpAttributePopulator class that copies the efficiency property from the item to the

DTO 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.

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.

The flexible search query returns a null value.

The flexible search query returns “PinkCandle”.

The flexible search query returns an SQL exception.

The flexible search query returns an empty list.

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

OrderCancelService

ReturnService

CustomerReviewService

CustomerAccountService

RefundService

Extend the Accelerator storefront.

Extend the Backoffice.

Provide additional RESTful web services for OCC.

Provide a new web application.

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.

Embedded with the SAP Commerce Cloud server

As one leading server and multiple subordinate servers

As one standalone server

As a Solr Cloud

In the customPromotion-backoffice-config.xml file

In the customPromotion-spring.xml file

In the customPromotion-beans.xml file

In the customPromotion-items.xml file

Services orchestrate Strategies

Services orchestrate Converters

Facades orchestrate Converters

Facades orchestrate Strategies

Facades orchestrate Services

Delete a build that is no longer needed

View the history of the past deployments of a selected build

Deploy a successful build to a certain environment

Rebuild a successful build to do a performance test

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.