Comm-Dev-101 Salesforce Certified B2C Commerce Developer Questions and Answers

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.

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

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.

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

Template decorators provide a standard mechanism for extracting shared page structure—such as headers, navigation, wrappers, footers, and common layout markup—into reusable ISML templates. A child template uses < isdecorate > to select a decorator, and the decorator uses < isreplace/ > to identify the location where the child ' s page-specific content is inserted.

Salesforce describes < isdecorate > as the ISML mechanism for decorating enclosed content with another template and defines < isreplace/ > as the placeholder where the decorated content is inserted. A typical use case is wrapping different page bodies with a common header and footer.

This architecture directly reduces repeated layout code and improves maintainability because a shared element can be changed in the decorator rather than edited across many individual pages.

Option B misuses < isscript > ; script tags are intended for executable template scripting, not reusable page composition. Option C doesn ' t represent the standard decorator-based technique requested by the question and can encourage fragmented template composition when a reusable layout is the underlying requirement.

Study Guide reference:Application Development — ISML templates, template decorators, < isdecorate > , < isreplace > , reusable presentation structure, and maintainable storefront design.

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

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.

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

Server-side script variables do not persist between independent request executions. B2C Commerce therefore provides theSessionobject as the appropriate request-session mechanism for maintaining shopper-specific state across calls.

Salesforce specifically identifies the Session API as providing access to thecurrent customer, whether that customer isauthenticated, session custom attributes, andcustom privacy attributes. These capabilities map directly to every requirement in the question.

A client-side cookie is inappropriate for reproducing server-maintained authentication and customer state. It would also expose application-controlled values to client modification and duplicate information already securely managed by the Commerce session. An SFRA controller does not automatically preserve its own JavaScript variables across requests; each request executes within a separate script context.

Session data should nevertheless remain lightweight. Long-lived or business-critical information that must survive beyond the shopper ' s browser session belongs in persistent business objects rather than session attributes. Privacy attributes have specific lifecycle semantics and are particularly appropriate for tracking consent and related shopper preferences during the active session.

Study Guide reference:Application Development — Session API, shopper state, authentication state, privacy attributes, server-side JavaScript execution lifecycle, and scalable state management.

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

A storefront category intended to appear in navigation normally needs appropriate online configuration andavailable products assigned to it. Salesforce ' s category-management guidance specifically notes that to show a category in storefront menu navigation, available products must be assigned to the category and the relevant menu-navigation configuration must be enabled.

This makes option A the relevant cause among the supplied choices. A newly created category that contains no available merchandise can fail to appear where expected in the storefront navigation structure.

Option C is incorrect because sorting determines ordering, not whether a category exists or is eligible to appear. Option B is too broad in the context of the scenario. An offline storefront catalog would affect storefront catalog availability generally, rather than explaining why this newly created category alone cannot be seen.

Product/category visibility in B2C Commerce depends on several related configuration elements: product assignments, category online state, catalog-to-site assignment, navigation settings, and updated search indexes where applicable. Salesforce also confirms that products must be assigned to categories and the catalog assigned to the site for storefront visibility.

Study Guide reference:Data Management Using Business Manager Usage — catalogs, categories, product assignments, storefront navigation, and product availability.

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

The taxation policy is selected when a B2C Commerce site is created. It is not an ordinary editable site preference that administrators can unlock later. This eliminates options B and C.

The uploaded question set identifies creation of a replacement Gross-taxation site as the Business Manager-based answer. Current Salesforce documentation adds an important operational qualification:the taxation policy is configured at site creation and only B2C Commerce/Salesforce Support can change it on an existing site.

Therefore, among the three choices, A is the only viable Business Manager-only approach because a newly created site can be configured with Gross taxation at creation. However, in a real production implementation, deleting/recreating a mature site can have major configuration and data implications; contacting Salesforce Support to change the existing site ' s taxation policy is the current documented operational route.

A taxation-policy change also requires reviewing price data because gross and net policies interpret product and service prices differently.

Study Guide reference:B2C Commerce Setup — site creation, Net/Gross taxation policy, immutable site settings, and tax configuration.

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

SFRA applies storefront page-caching policy throughmiddleware, andcache.applyDefaultCacheis the standard middleware function used for a route that can safely use the default caching duration. Middleware is inserted into the controller route before the route ' s main callback, exactly as shown in option A.

This approach is preferable to embedding legacy-style cache directives directly into page templates because SFRA centralizes request behavior—caching, consent, authentication, CSRF validation, and similar concerns—in middleware chains. Salesforce ' s SFRA architecture describes routes as ordered middleware functions and showscache.applyDefaultCachein standard storefront routes. The existingPage-Includeroute, for example, explicitly declaresserver.middleware.includefollowed bycache.applyDefaultCache.

Option C is syntactically inconsistent with the SFRA server API becauseapplyDefaultCache()is middleware, not a method chained onto the result ofserver.get(). Option B can configure ISML cache behavior in other architectures, but it is not the preferred SFRA controller-level implementation requested here.

Study Guide reference:Application Development — SFRA middleware, page caching,cache.applyDefaultCache, controller routes, and caching best practices.

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

OCAPI permissions are configured againstresource IDs, not against one particular inventory-list identifier embedded in an individual request. In the example URL, the principal API resource family isinventory_lists;ecom-inventoryis merely the identifier of the particular inventory list being accessed.

Therefore, the developer should inspect the OCAPI Data API settings for a resource rule covering theinventory_listsresource path, such as an appropriate/inventory_lists/...pattern, and verify that the required HTTP method and attribute selectors have been permitted.

Theclient_ididentifies the external application whose permissions are being evaluated, but it does not identify the inventory API resource being enabled. Similarly,ecom-inventoryis instance/business data and should not be confused with the API resource family.

This distinction is central to OCAPI authorization. A client configuration associates a client ID with resource path patterns, allowed HTTP methods, andread_attributes/write_attributesselectors. Requests are authorized only when they match an enabled resource and method.

Study Guide reference:Application Development — OCAPI Data API, inventory-list resources, resource IDs, client permissions, HTTP methods, and inventory integrations.

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

OCAPI Shop API search suggestions use thesuggestion.product.image:view_typesetting to determine which B2C Commerce image view type is returned with product suggestions. Salesforce documents the reserved property and givessmallas an example configured view type. Critically, this is not an automatic fallback value.

Salesforce explicitly states that ifview_typeisnot configured or refers to an unknown view type, the image properties are omitted from the response. Therefore, option A precisely matches the API behavior.

Options B and C incorrectly assume that the platform substitutes a default image view type. It does not. The developer must configure a valid image view type that exists in the catalog ' s image configuration if search-suggestion responses are expected to contain image data.

This configuration is especially important for autocomplete interfaces because the application might render product thumbnails beside suggested product names. Without a valid configured view type, the response can still contain suggestion data, but the expected image properties are absent.

Study Guide reference:Application Development — OCAPI Shop API,/search_suggestion, image view types, OCAPI settings, and search-suggestion response customization.

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

Business Manager ' sCatalog Import & Exportfunctionality can perform anExport Specific Productsoperation. The merchant or developer can select the relevant Master catalog and use product-search criteria to identify the products associated with the required storefront-category assignments.

Salesforce documents that Catalog Export can export selected products directly from Business Manager. TheExport Specific Productsmode contains the selected products and the category assignments belonging to those products. The documented Business Manager location isMerchant Tools > Products and Catalogs > Import & Export > Catalog Export.

This is preferable to Site Import & Export because that feature packages site configuration/data units for movement between instances; it is not primarily designed to generate a filtered product feed based on storefront assignments.

The separation of Master and Storefront catalogs is important. The Master catalog owns the product data, while the Storefront catalog ' s category assignments identify which subset is merchandised through that storefront. Exporting specific Master-catalog products based on those assignments produces the required subset without manually curating every product.

Study Guide reference:Data Management Using Business Manager Usage — Catalog Import & Export, Export Specific Products, Master catalogs, Storefront catalogs, and category assignments.

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

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.

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

Remote includes have anindependent caching policyfrom the page in which they are embedded. This allows a predominantly cacheable page to contain a dynamic section that must be evaluated separately for each request.

Salesforce explicitly describes this architecture: a surrounding page can remain fully cached while a remote include issues another request whose response is not cached. The web tier inserts the dynamically generated include into the cached page frame. The < isinclude > documentation similarly states that the remotely included URL can have a different caching policy and gives the specific example of embedding an uncached dynamic HTML snippet into an otherwise completely cached page.

Therefore, the presence of an uncached remote include doesnotinvalidate caching for the parent response. This is precisely one of the principal reasons to use remote includes for shopper-specific information such as login state, minicart information, rapidly changing inventory data, or other fragments with a shorter cache lifecycle.

Option C has no basis in the cache model; caching is not conditioned simply on whether the shopper is returning.

Study Guide reference:Application Development — page caching, remote includes, independent cache policies, Web Adapter processing, and dynamic storefront fragments.

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

< isdecorate > is the correct ISML construct for applying a reusable page layout to multiple templates. A decorator template can contain the common page shell, header, navigation, footer, scripts, and structural markup, while the individual child page contains only page-specific content.

Salesforce explicitly identifies a common header-and-footer layout as atypical use casefor < isdecorate > . The decorator template contains < isreplace/ > , which marks the position where the child template ' s enclosed content is inserted.

Option A is therefore not the tag normally placed around each page ' s content; < isreplace/ > belongs inside the decorator template itself. Option C can insert another template fragment, but using repeated includes for headers and footers does not provide the same centralized page-layout structure and composition semantics.

Decorator-based design improves maintainability because common markup is maintained once. If the header or footer changes, developers update the decorator rather than making the same structural changes across every individual storefront page.

Study Guide reference:Application Development — ISML decorators, < isdecorate > , < isreplace > , template reuse, common layouts, and storefront maintainability.

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

A task-oriented custom job step controls its execution result by returning adw.system.Statusobject. BecauseNO_FILES_FOUNDis explicitlynot an error condition, the status object ' s severity must beStatus.OK, withNO_FILES_FOUNDsupplied as the custom status code.

Salesforce ' s custom-job-step documentation states that a task-oriented script module can returndw.system.Statusto control the step ' s exit status. When the Status object ' s error flag is false and its code is a custom value, that custom value becomes the step status and job processing can continue unless the job flow defines a transition for it.

Option A returns an arbitrary object rather than a B2C CommerceStatus. Option C similarly returns a plain JavaScript object. Salesforce specifically notes that if a script returns an object that isnotadw.system.Status, the Job Framework treats the execution as ordinaryOK; the custom code isn ' t established through that object.

new Status(Status.OK, ' NO_FILES_FOUND ' )is therefore the correct implementation.

Study Guide reference:Application Development — Job Framework, custom job steps,steptypes.json,dw.system.Status, custom exit codes, and task-oriented script modules.

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

A Page Designer Page Type consists of a metadata definition plus a corresponding JavaScript implementation. The rendering behavior itself belongs in the page-typeJavaScript file, which must expose arender()function.

Salesforce states that the script file must have the same base name and location as the Page Designer meta-definition file, using.jsrather than.json. The script ' srenderfunction receives aPageScriptContextand must return the resulting markup as a string. It commonly renders an ISML template usingdw.util.Template, and the template can in turn render the page ' s regions.

The metadata JSON describes the Page Type ' s declarative configuration—such as its attributes and regions—but does not implement rendering through a " render " property. A conventional SFRA controller route can invokePageMgr.renderPage()to initiate rendering, but that controller does not define the actual Page Type rendering logic.

This separation allows Page Designer to manage page composition while the JavaScript implementation controls the output representation.

Study Guide reference:Application Development — Page Designer Page Types, page metadata,render()functions,PageScriptContext, and Page Designer rendering.

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

The intended activity is product-level merchandising data, so the first requirement is acustom attribute on the Product system object. Values such as tennis, jogging, and basketball can then be populated for the applicable products. The second requirement is to expose that indexed attribute as aSearch Refinement Definitionfor the categories where shoppers should be able to use it.

Salesforce ' s search-refinement model supports attribute-based refinements that restrict product-search results according to values stored on products. A search refinement definition identifies the attribute that should participate in refinement behavior. Salesforce also provides System Object Type configuration for defining custom attributes on extensible system objects such as Product.

There is no need for a separate “ProductRefinement” custom attribute type as proposed in option B. Option C ' sviewtypeis unrelated to defining searchable product characteristics; presentation modes do not create catalog data or refinement dimensions.

After the attribute and refinement are configured, the product data must contain appropriate values and the relevant search index must include them.

Study Guide reference:Data Management Using Business Manager Usage — Product custom attributes, catalog metadata, search refinements, and search indexing.

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

The < isslot > tag is the B2C Commerce ISML mechanism for defining a storefront location that a merchant can configure through Business Manager. Settingcontext= " category " scopes the slot configuration to a category, whilecontext-object= " ${pdict.ProductSearchResult.category} " supplies the specific category object used to resolve the appropriate slot configuration.

This design allows the same slot ID,category-banner, to appear on multiple category pages while maintaining independent configurations because the category context differentiates each placement. Salesforce documents that an < isslot > can useglobal,category, orfoldercontext. For category-scoped slots,context-objectis mandatory and must resolve to the applicable category. Business Manager consequently groups and manages category-slot configurations by category.

< isbanner > is not the B2C Commerce content-slot tag, and < iscontent > controls response/content characteristics rather than creating a merchant-configurable slot.

This approach separates storefront placement from merchant content configuration: the developer defines the slot location once, while the merchant controls the actual banner configuration independently for each category.

Study Guide reference:Data Management Using Business Manager Usage — Content Slots, category context, < isslot > , context objects, and Business Manager merchandising.

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

Washing instructions areproduct data, not static interface text. Because the information comes from the PIM and varies by product, it belongs on the Product system object as a custom product attribute. Marking that attribute aslocalizableallows the product to store different instruction values for each configured storefront locale.

Salesforce ' s metadata framework permits developers to create custom attributes on extensible system objects such as Product and configure additional attribute characteristics according to their selected data type. B2C Commerce product data supports localized attribute values so that presentation content can vary according to the active locale.

A resource bundle is appropriate for static application strings such as field labels, button text, and messages. It would be unsuitable for potentially thousands of product-specific washing-instruction values arriving from a PIM. Option C is also incorrect: localization is configured on appropriate individual attributes rather than by turning the entire Product system object into a " localizable " object.

The PDP can then read the resolved localized Product custom attribute for the shopper ' s current locale.

Study Guide reference:Data Management Using Business Manager Usage — Product custom attributes, localizable attributes, PIM-fed product data, and localized PDP content.

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

B2C Commerce includes several platform-defined payment methods, such asCREDIT_CARD,GIFT_CERTIFICATE,BANK_TRANSFER, and other standard methods. These default definitions are part of the platform configuration and therefore cannot simply be deleted. If a merchant does not want to expose one of these methods on the storefront, the appropriate administrative action is to disable it.

Salesforce ' s Business Manager documentation explicitly states thata default payment method cannot be deleted and can only be disabled. It also confirms that administrators can drag column headers to alter the payment-method sort order, which directly eliminates option C. There is likewise no five-payment-method limit corresponding to option B.

Payment methods are managed independently from payment processors. A payment method represents the shopper-facing way of paying, while a payment processor represents the processing implementation associated with that method. Maintaining the platform-defined method while disabling it preserves configuration integrity and permits the method to be reactivated later without recreating its system definition.

Study Guide reference:Data Management Using Business Manager Usage — Payment Methods, payment configuration, default payment methods, activation and deactivation.

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

B2C Commerce automatically supplies system attributes such ascreationDate; the developer does not need to create another custom creation-date field. The relevant Business Manager presentation mechanism isattribute grouping.

Salesforce explains that attributes displayed in Business Manager are organized through attribute groups and that an attribute generally must belong to a group to appear on applicable Business Manager object pages. For custom object definitions, the Attribute Grouping configuration determines which attributes administrators can view or manage through the Custom Object Editor.

The platform automatically createsUUID,creationDate, andlastModifiedas system metadata for custom objects. Therefore, option B is inappropriate if interpreted as defining another creation-date attribute, and option C refers to a visibility flag that is not the mechanism described by the custom-object metadata model.

The important conceptual distinction is betweenattribute existenceandBusiness Manager presentation.creationDatealready exists; placing the required system information into the appropriate attribute-group presentation structure is what makes it usable in the administrative interface.

Study Guide reference:Data Management Using Business Manager Usage — Custom Object Types, system attributes, attribute groups, and Business Manager presentation.

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

SFRA storestemplate resource bundlesin the cartridge ' stemplates/resourcesdirectory. Locale selection is represented in the propertiesfilename, rather than by creating a separatefrsubdirectory for ordinary SFRA resource bundles.

For example, a default bundle might be:

account.properties

while its French translation would be:

account_fr.properties

Both belong under:

cartridge/templates/resources

Salesforce ' s localization documentation explicitly states that template resource bundles are stored in/templates/resourcesand gives examples such asaccount_en_GB.properties,account_en_US.properties, andaccount_en.properties. Thedw.web.Resourcedocumentation likewise describes resource bundles as properties files with a common name located in thetemplate/resourcesdirectory.

Option B omits the required template-resource location. Option C incorrectly assumes that locale resolution for properties bundles uses a dedicatedfrfolder. Locale-specifictemplatescan use locale directories, but localized properties bundles follow the filename-suffix convention.

This separation permits one common set of ISML templates to reference resource keys while B2C Commerce automatically resolves the appropriate translated properties bundle for the active request locale.

Study Guide reference:Application Development — localization, template resource bundles,.propertiesfiles, locale fallback, andResource.msg().

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

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.

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

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.

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

In SFRA ' s MVC-style architecture, a controller owns the HTTP request/response workflow. Consequently, generating aJSON HTTP responseis an appropriate controller responsibility. The SFRA response API exposesres.json(data)specifically for this purpose and Salesforce notes that it is useful for AJAX service endpoints called by client-side code.

The other two choices describe responsibilities that belong more appropriately to the model/ViewModel layer. Salesforce explains that SFRA models obtain data from B2C Commerce Script API objects and convert those objects intopure serializable JavaScript objectssuitable for views. Models also encapsulate storefront-oriented business logic. Controllers request or coordinate the required data and pass it through the model layer rather than becoming the primary object-transformation layer themselves.

This separation improves testability and maintainability. Controllers stay focused on routing, request validation, response selection, redirects, rendering, and JSON output, while models isolate the transformation of Commerce platform objects into view-friendly structures.

Study Guide reference:Application Development — SFRA MVC architecture, controllers, ViewModels,res.json(), Script API objects, and separation of concerns.

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

Custom Object attributes must be assigned to anAttribute Groupbefore Business Manager can expose them in the Custom Object editing interface. Defining an attribute creates its metadata, but grouping controls its administrative presentation.

Salesforce explicitly states that after creating custom-object attributes, developers must add them to an Attribute Group in order to manage the custom object through Business Manager. Salesforce also notes that the custom object ' s key attribute must be included in an attribute group; otherwise, administrators cannot create instances of the custom object definition through the Custom Object module.

Option A is unrelated. Changing the data type modifies how an attribute stores information and can even destroy existing values, but it does not solve the Business Manager visibility issue. Option C confuses attribute presentation with custom-object scope and replication. Site-specific storage determines where object instances exist, while replication configuration governs movement between instances; neither causes fields to appear in the editor.

The correct workflow is therefore to define the attributes, create the appropriate Attribute Group, assign the desired fields—including the key—to the group, and then manage object instances through the site ' s Custom Objects module.

Study Guide reference:Data Management Using Business Manager Usage — Custom Object Types, Attribute Definitions, Attribute Groups, Custom Object Editor, and Business Manager metadata.

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

The appropriate responsibility of < isif > isconditional presentation. Evaluating a Boolean already present inpdictand choosing between different pieces of markup is exactly the intended ISML use case.

Salesforce ' s official < isif > documentation is explicit that < isif > , < iselseif > , and < iselse > containno business logic; they provide conditional visualization of data. The condition can use Pipeline Dictionary variables and other expressions that resolve to Boolean behavior.

Option B therefore violates the separation of concerns used by SFRA. Complex business rules should be computed before template rendering—typically in controllers, helpers, models, or other server-side modules—and only their resulting data should be passed to ISML. Option C is also incorrect because redirecting a request is controller responsibility. A template should not control HTTP routing or authentication flow.

The supplied question ' s correct use is consequently showing a different < div > based on an already computed Boolean.

Study Guide reference:Application Development — ISML, < isif > ,pdict, conditional visualization, controller responsibilities, and separation of presentation from business logic.

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

B2C Commerce can store multiple code versions simultaneously, but only theactive code versionsupplies the storefront ' s templates, controllers, scripts, and static code resources. If recently uploaded cartridge changes do not appear, verifying that the expected code version is active is therefore a fundamental troubleshooting step.

Salesforce ' s Code Deployment documentation states that all templates, pipelines, scripts, and images are taken from the active version. It also specifically recommends checking that the cartridge was uploaded to the current code version when storefront changes do not appear. Salesforce ' s SFRA troubleshooting guidance further recommends switching code versions and reactivating the intended version when changes are not reflected on the server.

A search-index rebuild is relevant to indexed product, category, content, or search configuration—not to changes in JavaScript controllers or ISML templates. Cartridge-path configuration should also be verified, but the source ' s earlier scenario already uses that check before checking the active version.

Study Guide reference:B2C Commerce Setup — Code Deployment, active code versions, cartridge deployment, storefront troubleshooting, and version activation.

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

Reusable cross-route request logic is exactly whatSFRA middleware functionsare intended to provide. A middleware function receivesreq,res, andnext, performs the required check, and can either continue the chain, redirect the shopper, modify response state, or otherwise control request processing.

Salesforce describes each SFRA route as a middleware chain whose individual steps use the standard(req, res, next)signature. Reusable functions can be inserted into multiple routes, allowing authentication checks, consent validation, feature eligibility, parameter validation, and similar concerns to be implemented once and consistently reused.

Option B technically repeats functionality by appending a separate function to every route, but it does not provide the clean reusable abstraction requested by the scenario. Option C addresses cartridge inheritance rather than reusable route-level validation.module.superModuleis used when extending a module from another cartridge; it is not a substitute for a middleware function shared among several routes.

Centralizing the checks in middleware also makes later changes safer: the validation logic is updated in one place rather than independently across numerous controller endpoints.

Study Guide reference:Application Development — SFRA routing, middleware chains, reusable middleware,req/res/next, redirects, and controller design best practices.

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

ThePerpetualsetting on a Product Inventory Record is designed for merchandise that should be considered continuously available without depending on a finite stock allocation. Digital gift vouchers are an appropriate example because the merchant can issue them without maintaining physical units.

Salesforce ' s inventory documentation identifies products configured with the perpetual flag asalways in stock. When perpetual inventory is enabled, normal ATS depletion is not used to make the product unavailable. This is fundamentally different from setting an artificially high allocation, which remains finite and introduces inaccurate inventory information.

Option B is also incorrect becausestockLevelis a calculated inventory value; it is not the administrative mechanism for representing an unlimited product supply. For a digitally generated item whose supply should never naturally reach zero, the inventory record should explicitly model that behavior instead of simulating it with a large quantity.

This configuration keeps availability semantics accurate and avoids unnecessary inventory maintenance.

Study Guide reference:Data Management Using Business Manager Usage — Product Inventory Records, Perpetual inventory, ATS, product availability, and digital/non-depleting products.

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

A content slot configuration determines bothwhat type of content is selectedandwhich template renders that content. The current slot is configured to produce products based on a merchandising rule. To convert it to a slot that displays a specific content asset, the merchant must change the configuration ' s content type and choose an appropriate rendering template capable of rendering the selected content asset.

Salesforce explains that content slots can display products, categories, content assets, static HTML, and other merchandising content. Slot configurations control the content to show, the scheduling or targeting rules, and the rendering template used to produce the resulting storefront markup.

The existing slot itself does not need to be deleted because its physical location in the page is defined by the < isslot > declaration in the storefront template. Merchants can create or modify multiple configurations against the same slot. Likewise, simply altering a default setting does not convert product-oriented configuration into content-asset configuration.

Study Guide reference:Data Management Using Business Manager Usage — content slots, slot configurations, content types, rendering templates, and personalized merchandising.

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

TheOrderable Products Onlysearch setting filters unorderable merchandise from storefront search results. Salesforce ' s search-pipeline documentation defines the behavior directly: the setting excludes unorderable products—identified in the documented rule as products whose inventory record hasATS = 0—from search results.

The setting operates on search-result eligibility; it does not generally make the product detail route cease to exist. Therefore, option C incorrectly converts a search filtering preference into PDP routing behavior.

Option B is also incorrect as a general statement because backorderable products can still be considered orderable even when immediate physical stock is unavailable, depending on their inventory configuration and availability model. The important concept isorderability, not simply whether inventory is being fulfilled immediately from on-hand stock.

This setting is commonly used when merchants do not want search pages populated with merchandise shoppers cannot purchase. Because orderability participates in indexed search behavior, administrators should also ensure that the relevant product search indexes are current after inventory/search configuration changes.

Study Guide reference:Data Management Using Business Manager Usage — product search preferences, Orderable Products Only, ATS, inventory availability, and storefront search-result filtering.

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

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

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

For a newly added product to participate correctly in storefrontproduct search, the product must be online, marked searchable, and represented in a current product search index. Salesforce ' s official indexing documentation states that a product appears in search results only when it issearchable, online, and assigned to at least one online category. The scenario already states that the product has been added to the Storefront catalog, so the remaining examination requirements are the online/searchable flags and an updated index.

A product does not have to be a child of a master product; standalone products are completely valid B2C Commerce merchandise. A price is commercially important, but price is not the platform criterion that makes a product eligible for the search index. Product pricing is separately incorporated into search indexes from applicable price books.

Therefore, A is the technically supported choice. After catalog changes, the product index must reflect the new assignment and current searchable/online status.

Study Guide reference:Data Management Using Business Manager Usage — Product visibility, online/searchable flags, Storefront catalogs, categories, and Product Search indexing.

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

dw.svc.LocalServiceRegistry.createService()is the standard Service Framework method for constructing a service instance from a service configured in Business Manager.

Salesforce ' s Script API defines:

LocalServiceRegistry.createService(serviceID, configObj)

The first argument identifies the configured Business Manager service, while the second supplies callbacks that define request construction, response parsing, logging filtering, mocking behavior, and other integration-specific behavior. The returned object is the actualServiceinstance used by application code.

Option B does not identify a supported creation API.LocalServiceInstanceis not the class developers instantiate to obtain configured B2C service objects. Option C likewise references a method that is not the documented LocalServiceRegistry creation mechanism.

A typical integration defines the service, profile, and credentials in Business Manager, callscreateService()in cartridge code, and subsequently invokes.call()on the returned service. This architecture externalizes environment-specific information—such as credentials, URLs, timeouts, and rate limits—from application source code.

Study Guide reference:Application Development — LocalServiceRegistry,createService(), Service Framework, service callbacks, profiles, credentials, and remote web-service integration.

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

ThePerpetualflag exists specifically to indicate that a product represented by a B2C Commerce inventory record should be considered continually in stock rather than constrained by an allocation quantity. This makes it the appropriate setting for a digitally issued gift voucher whose supply is effectively unlimited.

Salesforce ' s inventory documentation definesPerpetualas the flag indicating that the product isalways in stock. TheProductInventoryRecordScript API likewise states that theperpetualproperty determines whether a product is perpetually in stock.

Setting an artificially large allocation is inferior because that number is still finite and can create misleading inventory data. Option C is also inappropriate:stockLevelis a calculated value based on allocation and turnover rather than a Business Manager control that should be forced to an arbitrary maximum.

When the perpetual flag is active under standard B2C Commerce inventory management, availability logic treats the product as available irrespective of normal decrementing stock calculations.

Study Guide reference:Data Management Using Business Manager Usage — inventory records, perpetual inventory, product availability, allocation, and Business Manager inventory configuration.

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

A payment gatewayresponse/status codeis appropriate operational information for a checkout log because it can help diagnose authorization failures, processor errors, configuration problems, and transient integration issues without necessarily revealing sensitive payment credentials.

Passwords and credit-card information must not be placed into application logs. These values are highly sensitive and create substantial security and compliance exposure if persisted in WebDAV-accessible or Business Manager-accessible diagnostic files. B2C Commerce logging and service-integration practices require developers to keep sensitive shopper and payment information out of diagnostic output.

The correct pattern is to log identifiers and operational state sufficient to diagnose a failure—for example, a sanitized processor result code, service status, order-processing error identifier, or non-sensitive correlation ID—rather than the shopper ' s authentication secrets or raw payment details.

Salesforce ' s Service Framework guidance also supports filtering service logging so that sensitive information is excluded from request/response diagnostics.

Thus, option A provides useful diagnostic information while maintaining the appropriate security boundary.

Study Guide reference:Application Development — secure custom logging, checkout diagnostics, Service Framework logging, PCI-sensitive information, and credential protection.

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

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.

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

In current SFRA, the endpoint that renders a content asset as a full storefront page isPage-Show, and it expects the content asset ID in thecidquery-string parameter. Salesforce ' s SFRA Page controller documentation explicitly definesPage-Showas rendering a content asset in a full storefront page and documentscidas the ID of the content asset.

Therefore, the correct generated URL is equivalent to:

Page-Show?cid=about-us

and the correct ISML link is option B as corrected above.

Content-Showis not the current SFRA full-page content endpoint used by the base Page controller, whileContent-Pageis not the corresponding route. Salesforce ' s Page Designer/link-builder documentation also demonstrates URL components in the form[ " Page-Show " , " cid " , " < id > " ].

Study Guide reference:Application Development —Page-Show,URLUtils.url(), content assets,cid, storefront links, and SFRA routing.

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

Because the performance degradation occurs specifically underproduction traffic and production conditions, Code Profiler should collect execution data from that environment. Development Mode records all requests with greater detail than the normal aggregated Production Mode, making it suitable for a short, focused diagnostic period.

Salesforce explains that when the Code Profiler mode is changed, existing results are flushed. In a production instance with sufficient real traffic, the administrator can wait for the problematic behavior to occur again and then refresh the profiler results.

Option B changes the mode but does not allow time for new requests to generate useful profiling data. Option C profiles a sandbox and may fail to reproduce the production-specific load characteristics. Extended Script Development Mode also carriessevere performance implications, so Salesforce recommends using it with particular caution in production scenarios.

Once data is collected, developers can inspect controller, script, API, template, and request timing to isolate the expensive custom execution path.

Study Guide reference:Application Development — Code Profiler, Development Mode, production performance diagnostics, controller/script profiling, and performance troubleshooting.

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

TheFATALlogging level is the special severity level that thedw.system.LogAPI identifies as always enabled under normal logging operation. It represents severe conditions for which developers should always be able to emit diagnostic information.

Salesforce ' sdw.system.LogAPI documentation explicitly states thatFatal log messages are always enabledand can optionally be distributed through email notification configuration. INFO, by contrast, depends on the configured logging threshold and target settings. ERROR also participates in the configurable category hierarchy and does not carry the same API-level guarantee expressed for FATAL.

B2C Commerce custom logging uses a log4j-style hierarchy. Categories inherit logging behavior from parent categories unless a more specific rule applies. For example, an INFO threshold permits INFO, WARN, ERROR, and FATAL. A WARN threshold permits WARN, ERROR, and FATAL. Salesforce also supports configuring log targets separately from filters.

FATAL should be reserved for genuinely severe application conditions rather than routine diagnostic output, because excessive high-severity logging obscures operational incidents and reduces the diagnostic value of the logs.

Study Guide reference:Application Development —dw.system.Log, logging severity, custom log categories, FATAL logging, and production diagnostics.

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