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

Staging

Production

Pre-Production

Test

Development

Spring beans of backoffice web context

Context configuration object definition

Virtual socket definition

Widget connection

Assign the customer a custom search profile if a variation is in effect.

Apply a variation to customers who belong to a combination of segments.

Show different content in a slot if a variation is in effect.

More than one variation in a customization can be triggered at the same time.

Give the customer a coupon if a variation is in effect.

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.

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

A flexible search query for an incremental update

A solrconfig XML file

An ImpEx script for a full load

A flexible search query for a full load

The available non-virtual sockets

The available virtual sockets

The view file

The default values for widget settings

The business logic of the widget via a bean shell script

Disable the autostart for the default instance. Enable the autostart for the cloud instance. Set the

cloud instance mode to true.

Disable the autostart for the cloud instance. Enable the autostart for the default instance. Set the

default instance mode to cloud.

Disable the autostart for the default instance. Enable the autostart for the cloud instance. Set the

cloud instance mode to cloud.

Disable the autostart for the cloud instance. Enable the autostart for the default instance. Set the

cloud instance mode to true.

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.

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

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.

SSL Certificate

IP Filter Sets

Trusted Certificates

Redirect Sets

Host Alias Sets

A ConfigurationCategory, an AbstractConfiguratorSetting for color, a ConfiguratorType, and an

OrderEntryProductInfo for each color a given replica is available in.

A VariantCategory for color, a VariantValueCategory for each color, and a GenericVariantProduct

for each color a given replica is available in.

A ClassficationCategory, a ClassificationAttribute for color, a ClassificationAttributeUnit, a

ClassificationAttributeValue for each color a given replica is available in, and a

ClassAttributeAssignmentModel instance to tie them together.

A ComposedType, that extends the VariantProduct type to add a color attribute, and an instance

of this type for each color a given replica is available in.

properties

addons

webapps

extensions

It is automatically generated and assigned.

It is generated from a counter and the type code of the item.

It is generated from the item’s unique business key(s).

It is provided by the user in the Create wizard or as a column value in ImpEx.

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

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.

Customer Interests

Wish List

B2B Scheduled Replenishment

Newsletter Subscription

Configurable Promotions

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

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( ).

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