Comm-Dev-101 Salesforce Certified B2C Commerce Developer Free Practice Exam Questions (2026 Updated)

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.

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

< isif > is appropriate forconditional presentation logicinside an ISML template. Showing or hiding a page fragment according to information already provided to the view—such as whether the current shopper is authenticated—is exactly the kind of lightweight rendering decision for which < isif > is intended.

Salesforce explicitly states that < isif > , < iselseif > , and < iselse > provide conditional template constructs but should containno business logic, only conditional visualization of data. SFRA customization guidance reinforces this architectural separation by stating that business logic generally does not belong inapp_storefront_basetemplates; templates should concentrate on rendering.

Option B therefore violates SFRA separation-of-concerns practices because involved business logic belongs in controllers, models, helpers, or services. Option C is also unsuitable because routing and redirects are HTTP response-control operations that should be performed by the controller rather than an ISML presentation template.

Study Guide reference:Application Development — ISML conditional rendering, < isif > , template responsibilities, controllers, and separation of business logic from presentation.

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

CSRF validation must occurwhen the state-changing request is submitted, before protected business logic executes. In SFRA this is implemented as middleware in the controller ' s POST route, using the appropriate CSRF middleware—validateRequestfor standard submissions orvalidateAjaxRequestfor AJAX-based requests.

Salesforce ' s SFRA Forms documentation specifically states that CSRF protection is supplied as middleware and demonstrates CSRF checks as middleware steps. The underlyingdw.web.CSRFProtection.validateRequest()API verifies that the request contains the system-generated token and that the token has not expired.

Generating the token in the template only establishes the client-side value; it does not provide security unless the receiving POST endpoint validates it. Placing validation only in the form-display route would validate the wrong request. Performing validation in a persistence model is also too late because request security should be enforced before mutation logic is invoked.

Study Guide reference:Application Development — CSRF protection, SFRA middleware, POST routes,validateRequest,validateAjaxRequest, and secure form processing.

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

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.

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

The required workflow creates a new shipment for a gift item and then modifies shipment information associated with the basket. The OCAPI basket shipment hooks corresponding to those two operations aredw.ocapi.shop.basket.shipment.beforePOSTanddw.ocapi.shop.basket.shipment.beforePATCH.

Salesforce ' s OCAPI hook documentation definesshipment.beforePOSTas the extension point executed before creation of a shipment andshipment.beforePATCHas the extension point executed before modification of an existing shipment. Those operations align directly with the described solution: establish the separate shipment and then apply the necessary changes before final basket validation.

The alternatives involvingbeforeDELETEorafterDELETEare inconsistent with the scenario because no shipment needs to be deleted. The requirement is to separate a gift product into its own shipment, not remove a shipment from the basket.

The concludingvalidateBaskethook provides the final validation stage after the basket/shipment changes have been processed, allowing custom logic to ensure that the resulting basket remains valid.

Study Guide reference:Application Development — OCAPI Shop API hooks, basket extension points, shipment creation and modification, and basket validation.

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

Before application code can create or manipulate instances of a new custom-object type, the object ' smetadata definition must exist in B2C Commerce. Among the provided options, A represents that required first step.

More precisely, the developer creates aCustom Object Type definitionin Business Manager under Administration > Site Development > Custom Object Types. Salesforce documents that a custom object type must be defined before custom object instances can be created. The definition establishes the ID, key attribute, storage scope, replication behavior, custom attributes, and attribute groups.

Only after this metadata exists can code use APIs such asCustomObjectMgr.createCustomObject()to create persistent instances or read and update their attributes.

Option B reverses the platform ' s metadata-driven architecture: application JavaScript does not define a new custom-object schema. Option C is also premature because runtime handling logic cannot reliably use an object type that has not yet been established.

In a managed implementation, the definition should normally be created on staging and replicated as Object Definitions rather than manually recreated in production.

Study Guide reference:Data Management Using Business Manager Usage — Custom Object Types, object definitions, attributes, storage scope, replication, and CustomObjectMgr.

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

Option A correctly combines the two standard B2C Commerce APIs needed for the link:URLUtils.url()generates the URL for theAccount-Showcontroller route, whileResource.msg()retrieves the localized display text from theaccountresource bundle.

The Salesforce Script API definesURLUtils.url()as a method for generating Commerce URLs for controller or pipeline actions using the current request/site context.Resource.msg(key, bundleName, defaultMessage)resolves a localized message from the specified resource bundle, which is exactly what${Resource.msg( ' myaccount ' , ' account ' ,null)}does.

Option B is invalid becauseURLUtilsisn ' t called directly as a function andResourceMgr.getProperties()isn ' t the standard ISML localization expression shown here. Option C similarly uses a nonexistentURLUtils.get()method and suppliesrequest.locale()in the position whereResource.msg()expects the default message, not an explicit locale selector.

Using the standard URL and resource APIs also keeps the template compatible with configured URL rules and localization.

Study Guide reference:Application Development — ISML expressions,URLUtils,Resource.msg(), controller routes, localization, and storefront navigation links.

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

B2C Commerce can contain multiple uploadedcode versions, but only the currently active version is executed. Therefore, if the cartridge path has already been verified and the files appear to be uploaded successfully, the next critical check is whether the expected code version is actually active.

Salesforce ' s cartridge guidance explains that code is uploaded into code-version directories and that the active version determines which uploaded cartridge code is executed. Salesforce ' s SFRA troubleshooting guidance specifically recommends switching code versions when uploaded changes do not appear on the server.

A search-index rebuild would be relevant to product, category, content-search, or refinement changes, but it does not activate newly modified controller, template, model, or script code. Option C is redundant because the scenario explicitly says that the Storefront site cartridge path has already been checked; the Business Manager application ' s cartridge path concerns Business Manager customizations rather than this storefront-code issue.

A typical diagnostic sequence is therefore: verify upload, verify storefront cartridge path and ordering, verify active code version, and if necessary reactivate the expected version.

Study Guide reference:B2C Commerce Setup — code versions, cartridge deployment, cartridge paths, active code selection, and sandbox troubleshooting.

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

The configuration currently authorizes only HTTPGET, which is a read operation. Adding products to a basket changes server-side state and is performed through an OCAPI operation that usesPOST. The client ' s permitted-method list must therefore includepost.

OCAPI authorization is resource- and method-specific. Even thoughwrite_attributes: " (**) " permits all writable attributes for an otherwise authorized write request, it doesnotauthorize a missing HTTP method. The HTTP method itself must be explicitly listed in the resource configuration. Salesforce ' s OCAPI documentation identifies POST as a method used to create resources or execute actions that modify server state.

Option B changes the attribute selector but still leaves the client without POST permission, so the request remains unauthorized. Option C adds OPTIONS, which is associated with HTTP capability/CORS behavior and does not perform the basket modification.

Thus:

" methods " :[ " get " , " post " ]

allows the existing read access while also authorizing the required write operation.

Study Guide reference:Application Development — OCAPI configuration, resource permissions, HTTP methods, basket APIs, and read/write authorization.

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

Because the storefront already has the standard credit-card payment method, the additional requirement is to makeAmerican Express an accepted card typewithin that payment-method configuration. B2C Commerce distinguishes the general payment method (CREDIT_CARD) from the specific credit/debit card brands accepted through it.

Salesforce ' s Payment Methods documentation directs administrators to the Credit/Debit Cards configuration associated specifically with the defaultCREDIT_CARDpayment method. This is where supported card types are managed.

A payment processor is the technical processing implementation associated with payment methods. American Express does not need to become a completely separate payment processor merely because the merchant wants to accept that card brand. The actual processor must of course support American Express, but the storefront-facing card availability is configured under the credit-card payment-method/card-type configuration.

Option C is incorrect because card brands are not enabled by creating arbitrary Site Preferences.

This architecture keeps payment presentation and processing responsibilities separate: payment methods and accepted card types govern what the shopper can select, while payment processors govern authorization, capture, and other transaction handling.

Study Guide reference:Data Management Using Business Manager Usage — payment methods, credit/debit card types, payment processors, and checkout configuration.

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

B2C Commerce customer lists areorganization-level objects that can be assigned to multiple sites. Each individual site can use exactly one assigned customer list, but multiple sites can reference the same list. Salesforce documents this relationship explicitly.

To configure RefArch to use RefArchGlobal ' s customer list, the administrator edits the RefArch site configuration and selectsRefArchGlobalas its Customer List. Salesforce ' s storefront-site configuration documentation identifies Customer List as a configurable field on the site ' s General tab.

Importing the customer list into RefArch would create or transfer customer data rather than establish the intended shared-list assignment. It would not implement genuine shared customer profiles.

Option B is also incorrect because there is no generic " Customer List Sharing " global preference that enables this behavior. Sharing is accomplished by assigning the same customer list to more than one site.

Study Guide reference:B2C Commerce Setup — Customer Lists, shared customer profiles, multi-site configuration, site General settings, and customer-list assignment.

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

TheStorefront Toolkitis the appropriate starting point because this is a storefront rendering and data-presentation defect rather than a reporting or performance-analysis problem. The toolkit provides developer-facing information about the storefront page and helps identify the templates and application components involved in generating what the shopper sees. Salesforce specifically documents the Storefront Toolkit as a mechanism for identifying which portions of a storefront page are associated with particular templates.

With the wrong customer ' s address appearing on the Account Addresses page, the developer should first determine which template, controller route, remote include, or cached fragment is producing the displayed information. That narrows the investigation to the responsible application layer before examining the underlying customer/session logic.

The Reports and Dashboards module is intended for business and operational reporting and would not normally expose a template-level rendering defect. Pipeline Profiler is primarily concerned with execution and performance profiling, so it is more suitable when diagnosing slow pipelines or execution bottlenecks rather than incorrect shopper-specific content.

Study Guide reference:Work With a B2C Site — Storefront Toolkit, storefront troubleshooting, template identification, and diagnosing rendered customer-specific content.

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

Page Designer regions can define restrictions governing which component types merchants are permitted to place inside them. Therefore, the correct concept represented by option A is to configure acomponent-type exclusionin the layout component ' s JSON metadata rather than modifying every disallowed component.

Salesforce ' s Page Designer documentation shows this mechanism directly: a region definition can usecomponent_type_exclusionto specify that particular component types aren ' t allowed within that region. This centralizes containment rules within the layout or page type that owns the region.

There is an important terminology detail in the supplied question: the official Page Designer metadata property documented by Salesforce iscomponent_type_exclusion(singular), whereas option A printscomponent_type_exclusions. The question content has been preserved exactly as supplied, but A clearly represents the intended official mechanism.

Option B suggests an unsupported/inaccurately named inclusion property in this context. Option C incorrectly pushes the restriction into individual asset-component metadata, which would tightly couple child components to a particular layout and make reuse difficult.

Study Guide reference:Application Development — Page Designer meta definitions, layout components, region definitions, component restrictions, andcomponent_type_exclusion.

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

initServiceClientis the SOAP-specific callback among the listed choices. The B2C Commerce Service Framework uses callback functions to construct requests, execute or mock service interactions, and interpret responses. For SOAP integrations, the framework requires initialization of the underlying SOAP service client so that the generated service objects and SOAP-specific behavior can be prepared before invocation.

Salesforce ' sServiceCallbackAPI documentation specifically describesinitServiceClientas a method that normally does not need to be implemented except for SOAP services. By contrast,createRequestis broadly applicable because HTTP, FTP, SOAP, and other service implementations can require request construction. Mocking is also not inherently SOAP-specific; a service can be placed into mock mode regardless of whether the real endpoint uses SOAP or another protocol.

The distinction is therefore architectural rather than merely syntactic. SOAP requires a generated or initialized service client capable of working with SOAP operations and associated service definitions, whereas ordinary HTTP integrations commonly operate directly through URL, request body, headers, and response parsing callbacks.

Study Guide reference:Application Development — Service Framework,dw.svc, service callbacks, SOAP service integration, and external-system connectivity.

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

Inventory administration is a merchant-data integration concern and belongs to theOCAPI Data API, not the shopper-oriented Shop API. In addition, most Data API resources are organization-specific and therefore useGlobalOCAPI permissions. The/inventory_lists/*resource is the relevant resource family for managing inventory lists through the Data API.

Salesforce explains that the Data API provides create/read/update/delete access to administrative system resources, while OCAPI settings define which resource paths and HTTP methods a client is allowed to use. The current Commerce API documentation likewise identifies Inventory Lists as administrative inventory resources.

Options B and C use/product/*/inventory, which is not the appropriate Data API inventory-list resource shown for this architecture. Option B additionally selects the Shop API and site context, which do not match a warehouse-management integration updating backend inventory data.

The configuredget,put, andpatchpermissions enable the external integration to retrieve inventory information and perform complete or partial updates, subject to authentication and the resource schema.

Study Guide reference:Application Development — OCAPI Data API, inventory lists, Global OCAPI configuration, resource permissions, and warehouse integrations.

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

Content slotsare the Business Manager merchandising mechanism designed to present content—including images, content assets, products, categories, and static HTML—in predefined areas of the storefront. An image uploaded into the content image area can therefore be referenced by content or slot configuration and displayed through a storefront content slot.

Salesforce describes content slots as predefined storefront areas where merchants can display products, categories, content assets, static HTML, and marketing graphics. Slot configurations can also be scheduled and targeted without changing storefront application code.

Option B refers to product imagery associated with catalog products. Uploading an image through the content image mechanism does not automatically make it a product-image assignment. Option C is unrelated: payment methods configure checkout payment choices rather than storefront presentation assets.

Content assets can reference images stored in the content-related static file area, and content slots provide the merchandising placement used to show such content in designated storefront areas.

This separation allows merchants to manage promotional imagery independently from product catalog image data and deploy or schedule it through Business Manager.

Study Guide reference:Data Management Using Business Manager Usage — content images, content assets, content slots, slot configurations, and storefront merchandising.

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

SFRA storefront source contains several types of front-end assets that require preprocessing before the cartridge is deployed for normal use. JavaScript source is compiled or bundled through thecompile:jstask, SCSS source must be transformed into browser-consumable CSS throughcompile:scss, and the required font resources are copied into the generated static asset structure throughcompile:fonts. Therefore, option C represents the appropriate first-time SFRA asset build sequence.

compile:htmlis not part of the standard SFRA storefront asset compilation process. ISML templates are server-side templates and are uploaded as cartridge resources rather than being converted into static HTML by an npm compilation step. Likewise,npm run cleanremoves generated build artifacts; it does not substitute for producing the CSS and font assets required by the storefront.

After the assets and cartridge code are built and uploaded, the cartridges must also be registered through the site ' s cartridge path so that B2C Commerce can resolve and execute them. Salesforce ' s SFRA configuration guidance describes the cartridge deployment and site-registration workflow.

Study Guide reference:Application Development — SFRA project structure, front-end asset compilation, cartridge deployment, and storefront development workflow.

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

SFRA ' s response object provides thesetViewData()method specifically for adding data to the view-data object that will be available during rendering. Therefore, option A follows the supported controller pattern: callres.setViewData()with the additional object, render the template, and then invokenext()to continue the middleware chain.

Salesforce ' s SFRA documentation explains thatsetViewData(data)adds or merges data into the response ' s view-data object. This behavior is particularly important for an appended route because earlier middleware may already have established view data.setViewData()allows the appended function to add its contribution without replacing the response object ' s internal handling.

Directly assigningres.viewData, as shown in option B, bypasses the supported response API and is not the documented SFRA mechanism. Option C is also invalid because route appending expects a middleware function; data cannot be supplied by chaining an object through.append()after rendering.

This pattern is central to cartridge extensibility because multiple middleware functions can progressively enrich a response while preserving previously established data and route behavior.

Study Guide reference:Application Development — SFRA controllers, response objects, middleware chains,setViewData(), and template rendering.

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

The analytics snippet issite-specific merchant-managed configuration, so a custom Site Preference is the cleanest design. The developer can extend theSitePreferencessystem object with an HTML-type custom attribute and expose it in a custom preference group. Each of the North American, European, and Asian sites can then maintain its own value independently.

Salesforce documents that custom site preferences are created by adding custom attributes to theSitePreferencessystem object and assigning those attributes to preference groups that merchants can edit through Business Manager. Values are maintained independently in each site context.

Option B hard-codes regional analytics logic into ISML. That would require code deployment whenever the third-party analytics provider changes a snippet, defeating the requirement that merchants independently maintain the values. Option C misuses Service Profiles, which configure outbound Service Framework behavior such as timeouts and rate limits; they are not storage containers for arbitrary HTML or JavaScript fragments.

The storefront can retrieve the current site ' s configured preference and output it at the required rendering location.

Study Guide reference:Data Management Using Business Manager Usage — SitePreferences, custom preferences, multi-site configuration, HTML attributes, and merchant-managed settings.

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