Salesforce Comm-Dev-101 Salesforce Certified B2C Commerce Developer Exam Practice Test

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.

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

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.

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

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.

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

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.

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

Ifdw.order.calculateTaxis already registered byapp_storefront_base, the custom controller doesnotneed to register the hook again. It only needs to invoke the existing extension point throughdw.system.HookMgr.callHook().

Salesforce ' s SFRA hook documentation distinguishes registration from invocation: the implementing cartridge registers the extension point through its hook configuration, while application code calls registered hooks through HookMgr.

More importantly, the currentapp_storefront_basecalculation implementation demonstrates the exact call:

HookMgr.callHook( ' dw.order.calculateTax ' , ' calculateTax ' , basket);

Adding another entry tohooks.jsonorpackage.jsonis only required when a cartridge is providing/registering a hook implementation, not merely consuming an implementation that is already registered.

Study Guide reference:Application Development —dw.system.HookMgr,callHook(),dw.order.calculateTax, hook registration versus invocation, and SFRA basket calculation.

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

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.

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

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.

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

server.prepend()adds one or more middleware functions to thebeginning of an existing route ' s middleware chain. The developer should therefore explicitly provide whatever middleware is required by the new prepended behavior. Those requirements do not have to be limited to middleware already present in the base route.

Salesforce ' s SFRA Server API definesprepend(name, arguments)as modifying a route by prepending additional middleware. The supplied functions run before the original middleware chain, after whichnext()allows processing to continue through the remaining route steps.

Option B is unnecessarily restrictive. A custom prepended step can use existing Salesforce middleware or its own middleware if the functionality requires it. Option C would fundamentally alter route execution: omittingnext()stops the chain, preventing the original consent, cache, controller, and page-metadata middleware from executing unless terminating the route is deliberately intended.

The normal extension pattern is therefore to prepend the needed custom middleware, perform the additional processing, and callnext()so that inherited route functionality continues normally.

Study Guide reference:Application Development — SFRAserver.prepend(), middleware chains, route extension,next(), and controller customization.

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

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.

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

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.

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

Within the Payment Methods module, the first step in establishing a new payment method record is to clickNewand create the payment method. The method requires a unique ID and can then be configured with its descriptive, activation, applicability, and processor-related settings.

Salesforce ' s official payment-method procedure states that administrators navigate to Merchant Tools > Site Ordering > Payment Methods and clickNew to create a payment method, after which the method ' s settings are entered and applied.

Payment methods can depend on previously defined payment processors, and Salesforce notes that payment methods rely on processors already created where processing integration is required. However, option A is not universally the first action for creating a new payment method because a suitable processor can already exist and can be shared by multiple payment methods.

Option C occurs after the payment-method entity has been created.

The distinction is architectural: the payment method represents the shopper-facing payment option, while the processor identifies the underlying technical transaction-processing implementation.

Study Guide reference:Data Management Using Business Manager Usage — Payment Methods, Payment Processors, method creation, configuration, and checkout payment architecture.

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

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.

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

If a service is being classified as unavailable because legitimate responses are taking longer than the configured timeout, increasing the service timeout can reduce timeout-generated failures. B2C Commerce service profiles define the number of milliseconds the platform waits for a service response before treating the operation as an error.

Salesforce ' s Service Framework documentation states that the configured timeout is used for connection and socket operations. If no response arrives within the configured interval, the service operation fails. Thedw.svc.ResultAPI further identifiesTIMEOUTas an explicit reason forSERVICE_UNAVAILABLE.

Option B changes error-propagation behavior;throwOnErrordetermines how a failed result is surfaced to application code, but it does not make the external service more available. Option C can improve exception handling and prevent uncaught application failures, but wrapping the call intry/catchdoes not alter Service Framework availability metrics or prevent timeouts.

The timeout should still be increased cautiously. Excessive timeouts can worsen shopper-facing latency and interact poorly with circuit-breaker behavior.

Study Guide reference:Application Development — Service Framework, service profiles, connection/socket timeouts, Service Status monitoring, and service availability.

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

SFRA supportslocale-specific form structuresby placing form definitions with the same filename into locale-specific directories below the cartridge ' sformsdirectory. Because the Indian storefront uses English but needs a different registration structure from the U.S. storefront, the correct locale isen_IN, and the correct path is:

cartridge/forms/en_IN/profile.xml

Salesforce states that when form structure varies by locale—for example, fields differ by country—developers create separate folders named for each locale and place a form definition of thesame nameinside those folders. If no locale-specific definition exists, B2C Commerce falls back to the definition informs/default.

Option B incorrectly applies the locale identifier to the filename. Form localization uses directories, not aprofile_en_IN.xmlnaming convention. Option C also uses an invalid structure because it does not provide the language-country locale identifier or the required locale directory.

This solution allows both sites to remain English-language storefronts while using different field structures appropriate to their countries.

Study Guide reference:Application Development — SFRA forms, locale-specific form definitions,forms/en_IN, localization, and registration-form customization.

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

For a Business Manager extension to become visible and usable, its cartridge must participate in theBusiness Manager cartridge path, and the user must have the Business Manager module permission required to access the extension. Salesforce explicitly states that Business Manager extension cartridges must be added to the BM cartridge path, and extension functionality is secured through roles and permissions.

The extension does not need to be added to the Storefront site ' s cartridge path merely to make its Business Manager menu/module available. A code version containing the cartridge must of course be deployed and active generally, but activation alone does not grant access to the new Business Manager module.

There is atyping inconsistency in option A: the stem names the cartridgeplugin_bm_extension, whereas option A sayscustom_bm_extension. The technically correct action represented by A is to addplugin_bm_extensionto the Business Manager cartridge path and grant the appropriate roles/permissions.

Study Guide reference:B2C Commerce Setup — Business Manager extensions, BM cartridge path, module permissions, roles, and extension deployment.

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

dw.svc.LocalServiceRegistry.createService()is the supported API for creating and configuring a Service Framework service instance from a service definition established in Business Manager.

Salesforce ' s Script API states thatLocalServiceRegistryis responsible for managing Service instances and documents the method:

createService(serviceID, configObj)

The method takes the configured service ID and a callback/configuration object, then returns the corresponding Service instance.

The callback object can define functions such ascreateRequest,parseResponse,filterLogMessage,mockCall, or other service-type-specific behavior. Application code subsequently invokes.call()on the returned service.

There is nodw.svc.LocalServiceInstanceclass providing the method in option B. Likewise,getDefaultService()is not the standard LocalServiceRegistry creation method represented by the current Service Framework API.

The LocalServiceRegistry design keeps the service object local to the script invocation while relying on Business Manager for service, profile, and credential configuration. This separates deployable integration code from environment-specific URLs, authentication credentials, timeout values, and operational policies.

Study Guide reference:Application Development —dw.svc.LocalServiceRegistry,createService(), Service Framework, callbacks, service profiles, and remote integrations.

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

AnINFOmessage is written only when the configured logging threshold permits INFO-level events and INFO output is enabled for the relevant custom log destination. Setting the root level toDEBUGpermits DEBUG and all higher-severity messages, including INFO, WARN, ERROR, and FATAL. Enabling theInfolog-file option ensures that INFO messages are written to the applicable log file.

Salesforce ' s logging documentation explains that custom DEBUG and INFO logging can be enabled through Business Manager ' s custom log configuration and that the selected log levels control which messages are persisted. The logger ' s threshold behavior also means that a DEBUG root threshold includes INFO-level events because INFO has a higher severity.

The “logging global preference” described in options B and C is not the relevant mechanism for solving this custom logger configuration issue. Either of those options would also omit one of the two necessary controls described in option A.

Thus the developer should configure both the permitted log-level threshold and the INFO file output, then execute the code again and inspect the generated custom log through Log Center or WebDAV.

Study Guide reference:Application Development — custom logging, log levels, Business Manager log configuration, and WebDAV diagnostics.

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

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.

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

Creating a Search Refinement Definition alone is insufficient. The attribute being used as the refinement source must contain meaningful values on the applicable products and those values must be represented in the product search index. Otherwise, the search engine has no refinement values from which to construct storefront filters.

Salesforce states this prerequisite directly in its Search Refinement documentation:before creating refinements based on attribute values, ensure that the attribute has data and is indexed.

TheSearchablesetting referenced in option B is associated with whether an attribute participates in keyword-style search behavior; it is not the primary requirement for an attribute-based refinement already defined in the refinement configuration. Option C is also unnecessary in standard SFRA. The existing refinement rendering logic obtains available refinements dynamically from the search result model, so developers do not normally modifyproductsearchrefinebar.ismlmerely because another configured refinement was added.

After changing indexed product data or searchable/refinement configuration, the appropriate product search index must also be rebuilt so that the storefront operates against current indexed values.

Study Guide reference:Data Management Using Business Manager Usage — search refinements, product attributes, search indexing, refinement definitions, and storefront filtering.

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

B2C Commerce allowsmultiple modules to be registered for the same extension point, including multiple registrations in a singlehooks.jsonfile. Salesforce explicitly documents this behavior. When the extension point is invoked, all registered modules are executed rather than stopping after the first implementation.

Option B is incorrect as stated for modules registered together in one hook configuration: Salesforce states that the developer cannot explicitly control their execution order through the registration itself. Across cartridges, however, hook execution follows cartridge-path order, so cartridge precedence can affect the sequence in which implementations from different cartridges execute. Option C is also incorrect because Salesforce specifies that when multiple hook modules are called,the last hook ' s return valueis the return value that is ultimately used—not the first hook ' s return value. All registered implementations still execute even if earlier implementations return values.

This behavior is important when several cartridges extend the same business process. Developers must design hooks to coexist without assuming that their implementation is the only one registered.

Study Guide reference:Application Development — SFRA hooks,hooks.json, extension points, HookMgr, cartridge-path execution, and multiple hook implementations.

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

CustomObjectMgr.createCustomObject()expects two parameters for this use case: thecustom object type IDfollowed by thekey valuefor the new instance. Salesforce defines the relevant signature as:

createCustomObject(type, keyValue)

Therefore, ' NewsletterSubscription ' is supplied first as the custom object type andnewsletterForm.email.valueis supplied second as the unique key value. This makes option A correct.

The key attribute has already been established in the metadata definition of theNewsletterSubscriptioncustom object type. The API therefore does not require the developer to pass the literal attribute nameemailas a separate parameter. This makes option C invalid. Option B reverses the expected argument order and would attempt to interpret the email value as the custom object type name.

Custom-object keys must be unique within the object ' s applicable storage scope. Because creation changes persistent business data, the operation must also execute within an appropriate transaction when performed through server-side application code.

Study Guide reference:Application Development —dw.object.CustomObjectMgr, custom-object creation, custom-object keys, persistent business objects, and transaction handling.

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

The two-argument overload ofLogger.getLogger()has the signaturegetLogger(fileNamePrefix, category). Therefore, inLogger.getLogger( " products " , " export " ),productsis the developer-defined filename prefix andexportis the logging category.

Salesforce documents that custom application log files begin withcustom, while the suppliedfileNamePrefixidentifies the named custom log file. Consequently, the resulting filename begins withcustom-products, making option B correct. The category valueexportcontrols filtering through the custom-log category hierarchy but does not replace the filename prefix.

The configured root level of INFO also permits thislog.info()message because INFO is at the configured threshold. Higher-severity WARN, ERROR, and FATAL entries would likewise pass the root filter unless a more specific category rule superseded it.

This distinction between filename prefix and category is significant in production diagnostics. The prefix controls which named custom file receives the entries, while categories provide hierarchical filtering and operational control through Business Manager.

Study Guide reference:Application Development —dw.system.Logger, custom named logs, filename prefixes, categories, and log-level filtering.

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

Logger.getLogger(fileNamePrefix, category)

The first argument determines the custom named-log prefix, while the second determines the logging category used for filtering. Salesforce documents this API explicitly and states that custom named loggers use the suppliedfileNamePrefixto identify the generated custom log.

Accordingly, if the omitted code segment specifiesloggersFileas thefileNamePrefix, the generated custom-log name begins withcustom-loggersFile, matching option A.

The source question, however, omits the actual referenced logger configuration and code segment. Therefore, the file itself does not provide enough visible information to deriveloggersFileindependently; the answer depends on the configuration that was evidently present in the original question version. The selected answer is consistent with Salesforce logger naming semantics and the source ' s marked answer.

Study Guide reference:Application Development —dw.system.Logger,getLogger(fileNamePrefix, category), named custom logs, categories, and custom log-file naming.

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

For an independent external web application, the appropriate legacy B2C Commerce integration surface is theShop API Product Search resource. The application can retrieve structured product-search results for the desired category and use that data to construct a completely different presentation layer.

Salesforce ' s OCAPI documentation defines the Shop APIGET /product_searchresource and corresponding product-search extension points. The resource returns structured Product Search Result data rather than storefront-rendered HTML. This separation is important because the new application can independently control CSS, layout, rendering technology, and interaction behavior instead of attempting to reuse or scrape the existing storefront.

Search-Showis an SFRA controller designed to render the storefront search experience. Crawling its HTML creates unnecessary coupling to existing presentation markup and is not an integration architecture. A generic category endpoint can return category metadata, but the Product Search resource is designed to obtain product listing/search results.

Current platform note: Salesforce now marks OCAPI as deprecated for new implementations and recommends SCAPI for modern headless development, but the supplied certification question is explicitly testing the Shop OCAPI architecture.

Study Guide reference:Application Development — OCAPI Shop API, Product Search, headless/external storefront integrations, structured search results, and API-based storefront development.

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

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.

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

< isdecorate > is specifically designed for reusable page layouts. A page template wraps its page-specific content in < isdecorate template= " ... " > , while the decorator template defines the shared structural markup—typically the HTML shell, header, navigation, footer, and other common elements. The decorator contains < isreplace/ > at the position where the wrapped page-specific content is inserted.

Salesforce describes a typical < isdecorate > use case as decorating the page body with a common header and footer. This makes it the most effective mechanism for reducing repeated layout code across multiple storefront pages.

< isreplace > is not normally selected by the page that consumes the layout; it is placedinside the decorator templateto identify the insertion point. < isinclude > is useful for reusable partial templates but does not provide the same complete page-layout composition semantics.

Using decorators also improves maintainability: a change to the common header or footer is made once in the decorator rather than repeated across every page template.

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

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

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 B2C Commerce Service Framework provides native support for mocked services, so the developer should implement themockFullcallback and configure the service to operate in mock mode. This enables application development and testing before the external provider exposes the real endpoint.

Salesforce documents that when a service is operating in mocked mode, the framework can use its configured mock callback instead of making the live network request.mockFullis particularly useful because it can replace the full service execution sequence and return a controlledResultsuitable for testing dependent application logic.

A custom site preference is unnecessary because the Service Framework already contains an administrative mechanism for selecting mocked operation. Introducing application-specific conditionals or preferences duplicates platform functionality and makes the integration harder to administer consistently.

This approach also preserves separation of concerns: application code continues calling the same service abstraction, while environment configuration determines whether the real provider or the mock implementation is used. When the remote API becomes available, the service can be switched from mocked to live behavior without redesigning its callers.

Study Guide reference:Application Development — LocalServiceRegistry, Service Framework callbacks, mocking external integrations, and service testing.

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

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.

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

A custom object is the most appropriate persistent data structure because the requirement applies toboth registered and guest shoppers. A Profile-based solution cannot satisfy the requirement reliably because anonymous/guest customers do not have a persistent registered customer profile. Storing customer email lists directly on Product records would also create an inappropriate product-to-shopper coupling and potentially large mutable collections on product system objects.

B2C Commerce custom objects are intended to extend the persistent commerce data model for application-specific requirements. Developers can define custom object types with custom attributes, including multi-valuedSet of Stringattributes, and choose organization or site storage scope.

A custom back-in-stock object can therefore persist the shopper ' s email address plus one or more interested SKUs independently of authentication status. Subsequent job or inventory-update logic can identify subscriptions when inventory becomes available and trigger the notification process.

This design also keeps notification-subscription data separate from core customer and product objects, reducing unintended effects on standard platform data models and supporting anonymous shoppers cleanly.

Study Guide reference:Data Management Using Business Manager Usage — custom object types, custom attributes, persistent business data, guest shoppers, and application-specific data modeling.

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

AProduct Bundlerepresents several component products that are offered together as one orderable product. Salesforce distinguishes bundles from product sets specifically on purchasing behavior: a product bundle represents products sold together, while a product set is primarily a merchandising grouping that permits customers to select and purchase the individual members.

Salesforce ' s product-type documentation characterizes a Product Bundle as a product containing several products that areonly sold together, whereas a Product Set contains products that can be purchased together or separately.

A bundle also has its own product identity and bundle pricing/availability behavior. Availability normally depends on the availability of the bundled components unless bundle-specific inventory behavior is configured. A Variation Group is fundamentally different: it groups selected variation values belonging to a base product, such as several colors or styles, and does not represent a mandatory multi-product purchase.

Therefore, when the business concept is " these items constitute one sellable group, " a Bundle is the correct product model.

Study Guide reference:Data Management Using Business Manager Usage — Product Bundles, Product Sets, product types, bundled-product availability, and catalog configuration.

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

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.

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

Salesforce documents the two-argument form:

Logger.getLogger(fileNamePrefix, category)

The first argument controls the named log-file prefix, while the second controls category filtering. Custom application log files begin withcustom, and named logs therefore use the custom naming convention around the supplied file-name prefix.

That supportscustom-loggersFilewhenloggersFileis the configured file-name prefix. Option B would correspond to a different prefix (loggers), and C omits the custom-log naming convention.

Study Guide reference:Application Development —Logger.getLogger(fileNamePrefix, category), named custom logs, filename prefixes, and logging categories.

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

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

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

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

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

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

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

Logger.getLogger( " contact " )returns a logger associated with the custom categorycontact. Invoking.debug()on that logger writes the message at DEBUG severity under the specified category, assuming the corresponding category configuration permits DEBUG logging.

Salesforce ' sdw.system.LoggerAPI documents the one-argumentgetLogger(String)method as returning the logger for the supplied category. It also exposes DEBUG, INFO, WARN, ERROR, and other severity operations on the resulting logging object.

Option B uses the static root-style debug call and therefore does not explicitly bind the entry to the requested custom category. Option A is invalid becauseLogger.customLogger()is not a supported Script API method.

Category-based logging is useful for service integrations because Business Manager administrators can selectively increase diagnostic verbosity for a specific subsystem such ascontactwithout globally enabling excessive DEBUG output. Category rules can also be hierarchical, allowing narrower categories such ascontact.submitorcontact.response.

Study Guide reference:Application Development —dw.system.Logger,getLogger(), custom logging categories, DEBUG severity, and Service Framework diagnostics.

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

The maximum number of gift-wrapped products is asite-level configuration valuethat differs between the U.S. and European storefronts. A custom site preference is the appropriate model because each B2C Commerce site receives its ownSitePreferencesinstance and therefore can store a different numeric value.

Salesforce definesSitePreferencesspecifically as a container for custom site-level attributes and notes that there is logically one instance per site. Custom preferences can be created by extending theSitePreferencessystem object in Business Manager.

The developer can define a numeric preference such asmaxGiftWrapItems, allowing a merchant to configure 5 on the U.S. site and 3 on the European site. Application code can retrieve the value from the current site ' s preferences at runtime.

A content slot is intended for merchandising/presentation content, not application configuration. A Campaign controls scheduled marketing activity and promotions but is not an appropriate container for a persistent site-specific application limit.

Study Guide reference:Data Management Using Business Manager Usage — custom site preferences, SitePreferences system object, multi-site configuration, and merchant-adjustable application settings.

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

SFRA is designed around cartridge-based extension rather than direct modification of the base storefront code. When a developer needs to add another step to an existing registration workflow, the route should beextendedfrom a custom cartridge so that the standard implementation remains intact.

Salesforce ' s SFRA customization guidance describesmodule.superModule,server.extend,server.append,server.prepend, and route replacement as the supported mechanisms for customizing functionality from another cartridge. The exact technique depends on whether the additional operation must execute before, after, or instead of existing behavior.

Option A implies modifying the original controller directly, which is undesirable because upgrades or cartridge replacement can overwrite the changes. Option B copies base code, creating duplication and making later maintenance significantly harder.

Extending the route preserves the original implementation and keeps merchant-specific logic isolated in the custom cartridge. For a simple additional step that should execute after the existing route,server.append()is often appropriate; for access behavior or a fundamentally changed workflow, Salesforce recommends the corresponding supported extension/replacement pattern.

Study Guide reference:Application Development — SFRA controller extension, custom cartridges,module.superModule, route customization, and upgrade-safe development.

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

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.

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

Custom DEBUG messages are subject to theCustom Log Settingsfilters. If the script logs against a custom category but that category is not active at DEBUG severity, the messages are filtered and will not appear in the in-memory request logging used during non-production debugging.

Salesforce states that custom DEBUG and INFO logging are disabled by default and are configured throughAdministration > Operations > Custom Log Settings. The root/category hierarchy determines which custom messages pass the logging filter.

Therefore, the developer should enable the applicable category at DEBUG level. There is no Site Preference or Global Preference checkbox named " Enable custom logging in Request Log " that replaces this logging-category configuration.

On non-production instances, debug-level custom output can participate in in-memory logging associated with request diagnostics without necessarily requiring persistent debug log files. This makes category configuration particularly important when using the Storefront Toolkit Request Log for focused troubleshooting.

Developers should restore less verbose settings after diagnosing the issue because broad DEBUG logging can produce large volumes of data and make important diagnostic messages harder to isolate.

Study Guide reference:Application Development — Custom Log Settings, DEBUG categories, Storefront Toolkit Request Log, in-memory logging, and custom logging filters.

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

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.

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

Whether a location is a single-brand store is a characteristic of the individualStorerecord. The clean data model is therefore to add a Boolean custom attribute to the Store system object, for examplesingleBrand. The storefront ' s store-locator model or template can inspect that value and apply the appropriate CSS class when rendering each location.

B2C Commerce ' s metadata framework allows extensible system objects to receive custom attributes throughAdministration > Site Development > System Object Types. Salesforce specifically identifiesStoreas an extensible persistent object, and its Business Object documentation describes how custom attributes are created on system objects.

Creating a custom object, as proposed in option B, would introduce a second data structure and require a relationship between that object and the Store record. That is unnecessary when Store itself is extensible. Option C is also unsuitable because a site preference represents site-wide configuration rather than a property that varies from one physical store to another.

Using a Boolean also provides simple, deterministic rendering logic:truereceives the single-brand styling;falsereceives the normal presentation.

Study Guide reference:Data Management Using Business Manager Usage — system object types, Store metadata, custom attributes, Business Manager configuration, and storefront data modeling.

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

B2C Commerce provides a dedicatedAvailability Low Ranking Thresholdspecifically for this merchandising requirement. The setting is available in Business Manager under Search Preferences and controls the availability percentage at or below which products are pushed toward the bottom of storefront search results.

Salesforce ' s documentation gives a direct example: entering0.3causes products whose availability is 0.3 or lower to be ranked lower in the search result set.

This is preferable to hiding low-stock or unavailable products using a scheduled job because it preserves normal catalog state and responds through the platform ' s search-ranking engine. A scheduled cleanup introduces latency, custom operational overhead, and unnecessary product-state mutations.

Option B is also not the correct mechanism. Searchable Attribute boost factors influence relevance weighting for indexed attributes; availability already has a purpose-built ranking preference.

Using the low-ranking threshold lets products remain discoverable while prioritizing inventory that is more likely to convert successfully.

Study Guide reference:Data Management Using Business Manager Usage — Search Preferences, Availability Low Ranking Threshold, product availability, inventory-aware ranking, and search merchandising.

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

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.

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

The required information is structured application data that is specific to one site but must move consistently from staging to production. Asite-scoped, replicable Custom Objectis therefore the correct model.

Salesforce custom-object definitions provide two relevant controls.Storage Scopedetermines whether custom-object instances are organization-wide or site-specific, whileData Replicationdetermines whether custom-object data can participate in replication between environments. Salesforce specifically documents that custom objects can be local to a site and that custom object types can be configured as replicable.

The developer can define one object per country with attributes such as country code, price book ID, flag image URL, display name, and ordering information. The storefront can query these records to construct the country selector dynamically.

Option A attempts to overload the Locale system object with business configuration that is not fundamentally locale metadata. Option C stores structured application configuration in content assets, which are primarily merchandising/content entities and would be less suitable for strongly structured programmatic lookup.

Study Guide reference:Data Management Using Business Manager Usage — Custom Objects, site-specific storage scope, data replication, structured application configuration, and multi-country storefront design.

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

At line 05,viewDatareceives a value but is never declared withvar. Consequently, it isn ' t established as a local variable in the middleware function ' s lexical scope. A debugger stopped inside that function therefore won ' t present it as the expected locally declared variable in the local inspection context.

B2C Commerce controllers are CommonJS JavaScript modules, and Salesforce emphasizes that module-scoped/private data and explicitly defined variables should be used rather than relying on unintended globals. Salesforce also recommends avoiding global variables in controller implementations.

The corrected line would be:

varviewData={name: ' my string ' };

Option B is incorrect becausecache.applyDefaultCacheis valid SFRA middleware and is routinely applied to GET routes. Option C is also false:viewDatais not a reserved B2C Script identifier. In fact, SFRA itself commonly uses the term ViewData for the data model passed to templates.

The defect is therefore ordinary JavaScript variable declaration/scope behavior rather than an SFRA caching or reserved-word issue.

Study Guide reference:Application Development — SFRA controllers, CommonJS JavaScript, variable scope, middleware, and Script Debugger troubleshooting.

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