Free Practice Questions for Salesforce Comm-Dev-101 Exam

Every Page Designer component type has aJSON meta definition. That metadata describes the configurable structure exposed to Page Designer, including attributes and, for container/layout components, theregions into which merchants can place other components.

Salesforce documentation states that each page type and component type requires a JSON meta definition file. For component types, the file describes merchant-configurable attributes and can define regions. Salesforce ' s example of a three-column layout component represents each column as a region in that component ' s metadata.

The JSON file does not itself define the CSS responsive behavior of the rendered component; responsive visual structure belongs to the component ' s rendering/template implementation and associated styling. Nor does the JSON meta definition contain the complete business and rendering logic. Traditional Page Designer component types have a corresponding script implementation that performs rendering, obtains application data when appropriate, and sends content to the template.

The metadata file is therefore declarative: it describes what Page Designer understands about the component and what configuration merchants can manipulate.

Study Guide reference:Application Development — Page Designer component types, JSON meta definitions,region_definitions, component attributes, and Page Designer architecture.

===============

A storefront filter is represented in B2C Commerce product search as asearch refinement. Therefore, after creating or selecting an appropriate product attribute, the administrator must create a Search Refinement Definition that associates the refinement with that attribute and the appropriate category/search context.

Merely marking an attribute searchable is not equivalent to defining it as a refinement. " Searchable " primarily determines participation in keyword-search behavior, while a refinement definition instructs the search system to expose attribute values as shopper-selectable filters. The attribute must also contain values on relevant products and be represented in the search index for the refinement to produce useful values.

Changingproductsearchrefinebar.ismlis not normally required. SFRA retrieves available refinements dynamically from the Product Search Model, so configured refinements can appear through the standard refinement components without hard-coding each attribute into the template.

Salesforce confirms that custom Product attributes can be created forsite search, search refinements, or sorting rules, demonstrating that refinement configuration is a distinct use of the attribute.

Study Guide reference:Data Management Using Business Manager Usage — Search Refinement Definitions, custom Product attributes, search indexing, and storefront product filtering.

===============

B2C Commerce imposes a daily size quota on custom logs to prevent unlimited logging from consuming storage or degrading instance performance. Once the applicable custom-log size limit is reached, additional custom logging issuspended until the next logging dayrather than rolling immediately to another unlimited file.

Current Salesforce documentation states that each application server can write up to the defined daily amount into the custom debug, info, fatal, error, and warn logs, and that logging is suspended until the next day once the limit is reached. The logging day is based on GMT.

Option A describes normal archival/retention handling rather than quota behavior. Existing log files can later be compressed and moved according to retention policy, but reaching the daily file-size quota doesn ' t simply bypass the quota by opening another unrestricted file. Option B is also incorrect because B2C Commerce doesn ' t delete the current log merely to continue writing.

Developers should therefore avoid excessive diagnostic logging, particularly in frequently executed storefront code, and choose appropriate log levels and categories.

Study Guide reference:Application Development — custom logging quotas, log-file management, Business Manager log settings, WebDAV logs, and production diagnostics.

===============

ThePayment Methodsconfiguration is the appropriate Business Manager location because payment-method applicability can be restricted according to criteria that include the shopper ' s billing country. The merchant can therefore configure the relevant payment method so that it is not available where the country condition excludes Denmark.

Salesforce ' s Business Manager documentation for payment methods describes configuration controls for availability based on customer groups, billing countries, and order-amount conditions. The underlying payment-management logic evaluates these configured applicability rules when determining which methods are available for the current basket and shopper context.

A payment processor represents the back-end processing integration or transaction handler associated with one or more payment methods; it is not the primary mechanism for defining a country ' s storefront eligibility. “Locale Payments” is not the appropriate Business Manager module for this requirement.

This separation is important: thepayment methoddescribes whether a shopper can select a payment option under particular storefront conditions, while thepayment processordetermines how an accepted payment is technically processed.

Study Guide reference:Data Management Using Business Manager Usage — payment methods, payment applicability, billing-country restrictions, payment processors, and checkout configuration.

===============

The call syntax shown is valid:CustomObjectMgr.createCustomObject(type, keyValue)accepts the object type followed by the unique key value. The issue is persistence. A custom object is a persistent business object, so creation or modification must occur within a B2C Commerce database transaction.

Salesforce ' sTransactiondocumentation states thatbefore a persistent business object can be created, changed, or deleted, a transaction must be started. Changes become durable only after that transaction is successfully committed. The usual SFRA implementation pattern isTransaction.wrap(function () { ... });, although explicitbegin()andcommit()operations are also supported.

Atry/catchblock provides exception handling but does not establish transactional persistence, so option B does not solve the fundamental issue. Option C is incorrect because the API does not accept a third argument representing the key attribute name. The object ' s metadata already establishes which attribute is its key.

Transactions should cover only the minimum necessary mutation logic to reduce locking and maintain efficient storefront processing.

Study Guide reference:Application Development — persistent objects,CustomObjectMgr,dw.system.Transaction, transaction boundaries, and custom-object persistence.

===============

Theurlform of < isinclude > performs aremote include. In this example,URLUtils.url( ' Account-Header ' , ' mobile ' , true)constructs a URL for theAccount-Headerendpoint and supplies that URL to < isinclude > . B2C Commerce therefore makes a separate request to the generated endpoint and inserts the resulting response into the surrounding page.

Salesforce distinguishes this behavior from a local template include. A local include uses thetemplateattribute and incorporates another ISML template within the current rendering context. By contrast, an < isinclude > that specifiesurlis explicitly classified as a remote include and can execute another controller or pipeline endpoint.

Option B is therefore incorrect because the code does not use the local-template syntax. Option C is also incorrect:URLUtils.url()does construct a URL, but placing that URL in theurlattribute of < isinclude > does not render an anchor or navigational link. It causes the endpoint ' s output to be included in the current response.

Study Guide reference:Application Development — ISML includes, remote includes,URLUtils, controller endpoints, and composable storefront rendering.

===============