Salesforce Salesforce Certified B2C Commerce Developer Comm-Dev-101 Exam Dumps: Updated Questions & Answers (September 2026)

For a client-side AJAX endpoint whose response will be consumed by JavaScript,res.json()is the standard SFRA response method. It serializes the supplied data into a JSON response, allowing the client-side callback to update only the necessary part of the existing page without performing full server-side page rendering.

Salesforce ' s SFRA documentation explicitly states thatres.json(data)outputs a JSON object and ishelpful for creating AJAX service endpoints executed from client-side scripts. In contrast,res.render(templateName, data)renders an ISML template and produces markup intended for page or fragment rendering.

res.print()is a low-level text-output operation and does not provide the structured response contract that JSON gives client-side application logic.

An AJAX controller commonly returns information such as success status, validation errors, updated totals, URLs, messages, or calculated values as JSON. JavaScript then selectively updates the DOM based on those fields, preserving the rest of the page.

Study Guide reference:Application Development — SFRA controllers, AJAX endpoints, response object,res.json(),res.render(), and client/server interaction.

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

A site requires adefault currencyas part of its fundamental configuration. When creating a B2C Commerce site, Business Manager asks the administrator to select the default currency together with other basic site properties such as taxation policy. Salesforce explicitly documents the site-creation step: select a default currency; a site can support multiple currencies, but only one is the default.

The default currency also initializes the shopper ' s session currency when they first access the storefront unless application logic selects another allowed currency. This affects pricing, shipping, promotions, checkout calculations, and order creation.

A default payment method or payment processor is not an equivalent mandatory site-creation setting. Payment methods are configured based on the merchant ' s business requirements, and processors are associated with specific transaction-handling implementations. A storefront may support multiple payment methods/processors and their configuration can occur independently after the site itself is created.

Study Guide reference:B2C Commerce Setup — site creation, default currency, multi-currency sites, taxation, and initial storefront configuration.

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

B2C Commerce custom attributes are defined through the platform ' smetadata system, not dynamically declared by application JavaScript. Therefore, the first step is to create the required attribute definition in Business Manager on the appropriate extensible system object or custom-object type.

Salesforce documents the process under Administration > Site Development > System Object Types or Custom Object Types. The developer selects the target object, opens Attribute Definitions, clicks New, and defines the attribute ID, display name, and data type.

Once the attribute exists, it can be assigned to an attribute group where required for Business Manager visibility, populated through Business Manager or integrations, and accessed through the object ' scustomproperty in application code.

Option B is incorrect because source code cannot create an undeclared persistent custom attribute merely by referencing a property name. Option C also comes later because application logic needs the metadata definition to exist before reliably reading or writing the value.

The type and characteristics of the attribute should be designed carefully because changing an existing attribute ' s type can cause stored values to be lost.

Study Guide reference:Data Management Using Business Manager Usage — System Object Types, Custom Object Types, Attribute Definitions, attribute groups, and custom metadata.

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

Thevarattribute of an < isloop > statement defines the variable that represents the current object from the collection during each iteration. In this example,items= " ${pdict.Basket.products} " supplies the iterable collection, whilevar= " product " assigns each current collection member to the variable namedproduct. Therefore, inside the loop body, the current product is referenced directly asproduct.

Salesforce ' s ISML documentation defines the loop variable as the identifier through which the current element in the iterable collection is accessed. The separatestatus= " loopstatus " variable represents loop metadata, such as iteration position and related state; it is not the product itself.

Option B is incorrect because declaringvar= " product " does not create aproductproperty insidepdict. Option C also misuses the status variable:loopstatusis an iteration-status object rather than a direct array index intended to retrieve the current item. Using the explicitly declared loop variable produces clearer, idiomatic, and maintainable ISML.

Study Guide reference:Application Development — ISML templates, < isloop > , pipeline dictionary access, loop variables, and storefront rendering.

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

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.

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

The critical distinction is betweenstatic-content cachingandpage caching. The < iscache > ISML tag governs page-cache behavior for dynamically rendered storefront pages. In contrast, the Business Manager TTL setting for static content applies to static resources and does not control the page cache established through < iscache > . Consequently, changing static-content TTL settings would not necessarily affect the cached ISML response that is implicated in the production problem.

Option B is incorrect because B2C Commerce does not resolve multiple < iscache > directives by choosing the longest duration. Salesforce documents that the more restrictive behavior applies; where multiple cache declarations contribute to a page, the shortest applicable caching period governs rather than the highest.

Option A is too absolute. Page-cache invalidation can occur as part of relevant deployment or replication activity, so manual invalidation is not universally required in every hot-fix scenario.

The developer must therefore identify which cache layer is involved and avoid assuming that a static-content TTL adjustment changes the < iscache > -controlled page-cache entry.

Study Guide reference:Application Development — ISML page caching, < iscache > , static-content TTL, cache invalidation, and production troubleshooting.

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

The service credential is the correct B2C Commerce configuration object for an environment-specific service endpoint. Service credentials can hold connection information such as the URL and, where applicable, authentication credentials. This allows administrators or developers to change the sandbox endpoint through Business Manager without modifying cartridge code.

Salesforce ' s Service Framework documentation describes the service configuration as being associated with a service profile and credential, and the credential contains the service URL used to connect to the remote system. The API representation ofServiceCredentiallikewise exposes the URL as part of that configuration.

Creating a custom global preference for the endpoint would duplicate functionality already provided by the platform and would require additional application code to read and apply that preference. Option C also confuses service monitoring/status functionality with endpoint configuration. The service-status area is intended for operational information and service behavior rather than being the canonical storage location for the configured endpoint.

Using the credential URL field keeps connectivity information externalized from source code and allows different URLs to be maintained independently in development, staging, and production environments.

Study Guide reference:B2C Commerce Setup — Service Framework configuration, services, profiles, credentials, and environment-specific endpoints.

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

Custom storefront scripts arecode artifacts, not Business Manager metadata objects. Consequently, among the supplied options, B is the technically correct first step: create or define the required JavaScript/CommonJS script module within the project code structure.

Salesforce documents that B2C Commerce script modules are.js,.ds, or.jsonfiles and are normally stored in cartridges, commonly undercartridge/scripts. Modules expose public functionality throughexportsand are loaded withrequire(). Controllers and other server-side components can then import and invoke that reusable module.

Business Manager does not provide a general mechanism for creating arbitrary SFRA application scripts. Business Manager manages configuration, metadata, jobs, services, catalogs, and related platform data; deployable application logic belongs in cartridges/code versions.

Option C is less precise because the script/module itself must first be established in the codebase before its exported behavior can be consumed.

Study Guide reference:Application Development — CommonJS modules,cartridge/scripts, JavaScript modules,require(), exports, and cartridge-based application code.

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

Page-Includeis explicitly protected withserver.middleware.include, meaning it is designed to execute as aremote include, not as a shopper ' s top-level browser request. Salesforce ' s SFRA Page controller documentation describesPage-Includeas an endpoint triggered when content assets are embedded within a rendered page and identifiesserver.middleware.includeas its middleware.

The appropriate ISML mechanism is therefore:

< isinclude url= " ${URLUtils.url( ' Page-Include ' , ' cid ' , ' about-us ' )} " >

Using theurlattribute makes < isinclude > perform a remote include. Salesforce documents that this causes the web adapter to execute another request and insert the endpoint ' s returned content into the surrounding template.

Option A creates a shopper-clickable top-level URL, which fails the include middleware condition and explains the error described in the scenario. Option C is not the remote-include tag.

Study Guide reference:Application Development —Page-Include,server.middleware.include, remote includes, < isinclude url > , and SFRA content rendering.

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

Category-page refinements andkeyword-search refinementsuse different refinement contexts. A definition attached to Clothing can work correctly when the shopper navigates directly into the Clothing category because that category supplies the refinement context. A general storefront keyword search, however, does not automatically use the Clothing category ' s local refinement definition.

Salesforce ' s official guidance specifically states:to create search refinements for keyword search, create them for the root category of the storefront catalog.

Therefore, ifNewnessexists only on Clothing, it can appear during category navigation but fail to appear when a shopper types " Clothing " into storefront search. Configuring the refinement at Women would still not establish it as the catalog-level keyword-search refinement. Option C also introduces a conflict that the scenario does not establish.

This distinction is important when merchants want consistent refinements across broad keyword search versus category-specific browsing. Root-level definitions provide the catalog-wide search context, while child-category definitions customize refinement behavior for navigation within specific merchandising branches.

Study Guide reference:Data Management Using Business Manager Usage — Search Refinement Definitions, Root category, keyword search, category browsing, and refinement inheritance.

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