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

Uploading a cartridge to an instance does not automatically make its code available to a storefront. B2C Commerce resolves application resources according to thecartridge path configured for the relevant site. Consequently, the new custom cartridge must be added to that storefront site ' s cartridge path, normally in the correct precedence position relative to SFRA base and other cartridges.

Salesforce ' s cartridge documentation describes two distinct steps: upload the cartridge code and register the cartridge with the applicable site through its cartridge path. Site configuration is performed from the site ' s settings, where the cartridge path controls which controllers, templates, scripts, models, and other cartridge resources can participate in storefront execution.

Rebuilding indexes is unrelated unless the customization specifically changes indexed catalog/search data. An index rebuild does not register executable storefront code. Likewise, configuring the Business Manager application ' s cartridge path would affect Business Manager customizations rather than the customer-facing storefront identified in the question.

Cartridge ordering is also significant because B2C Commerce searches the path according to precedence, enabling custom cartridges to extend or override functionality from cartridges located farther to the right.

Study Guide reference:B2C Commerce Setup — cartridges, site cartridge paths, SFRA deployment, and cartridge precedence.

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

The Request Log usesin-memory loggingon supported non-production instances. The " Log Files " checkboxes control whether a particular severity is persisted into a physical custom log file; they are not required merely to make the message visible in the Request Log Viewer.

However, the category filter still matters.myLogCategoryis currently configured at INFO, so DEBUG—the lower-severity level—is filtered out. The developer therefore must change the category ' s threshold toDEBUG. Salesforce explains that configured levels represent minimum severity and that DEBUG in-memory logging supports theShow Request Logfeature without necessarily creating a debug log file.

Checking the DEBUG target would generate persistentcustomdebugoutput where supported, but that is separate from the stated requirement to inspect the Request Log. Therefore option C performs an unnecessary operation and option B does not change the category threshold.

Study Guide reference:Application Development — Custom Log Settings, category thresholds, DEBUG severity, in-memory logging, and Storefront Toolkit Request Log.

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

OCAPI is designed to expose B2C Commerce resources to external applications and integration systems through RESTful APIs. A warehouse management system that needs to update inventory is therefore a strong OCAPI use case because inventory is enterprise data maintained by an external operational system and must be synchronized into Commerce.

Salesforce describes the OCAPI Data API as providing external applications with programmatic access to Commerce resources and administrative data operations. Inventory integration is a standard example of synchronizing Commerce with external inventory or fulfillment systems.

Extending a System Object Type definition with new attributes is a platform metadata/configuration activity normally performed through Business Manager or supported metadata import mechanisms, not an ordinary OCAPI runtime integration. Showing customer information on the storefront ' s native My Account page is also normally handled internally by SFRA controllers, models, templates, and the B2C Commerce Script API rather than calling OCAPI from the same storefront application.

Using OCAPI for the warehouse system preserves a clear integration boundary: the external application authenticates through the API and exchanges inventory data without being coupled to storefront presentation code.

Study Guide reference:Application Development — OCAPI, external-system integrations, inventory synchronization, Data API usage, and storefront versus integration architecture.

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

Logger.getLogger( ' contact ' )creates or retrieves a logger associated with thecontactcategory. Calling.debug()on that logger writes the message at DEBUG severity, subject to the configured category and log-target rules.

B2C Commerce custom logging uses hierarchical category names patterned after log4j. Categories can be activated at particular severity levels inAdministration > Operations > Custom Log Settings. Salesforce explains that child categories inherit applicable settings from their parent categories unless they have more specific configuration.

Option B uses the generic staticLogger.debug()call and does not explicitly associate the statement with the required customcontactcategory. Option C refers to a nonexistentcustomLogger()API.

The category-specific approach is operationally superior when troubleshooting a third-party integration because administrators can selectively enable DEBUG logging forcontactwithout enabling extensive debugging across unrelated application code. Once the issue is diagnosed, that category ' s verbosity can be reduced again.

Study Guide reference:Application Development —dw.system.Logger, custom categories, DEBUG logging, Service Framework diagnostics, and hierarchical logging configuration.

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

CallingsetFilteredByFolder(false)tells theContentSearchModelthat search results mustnot be restricted by folder membership. This is specifically important for Page Designer because Page Designer pages and components are persisted as content-related objects but can exist outside the conventional folder structure used for ordinary content assets.

Salesforce ' s Script API states explicitly thatsetFilteredByFolder(false)must be used to return content assets that don ' t belong to a folder, including Page Designer content. The SFRA Page Designer development documentation uses the same statement insetupContentSearchso that Page Designer content can participate in storefront content search.

Option B reverses the actual behavior: the method isn ' t extending the model to add folder filtering; it is disabling folder filtering. Option C is likewise opposite to the purpose. The change broadens the searchable content population rather than preventing pages or components from appearing.

Additional Page Designer attributes still need the appropriate searchable metadata where attribute-value searching is required, but removing the folder restriction is the necessary step for discovering otherwise un-foldered Page Designer content.

Study Guide reference:Application Development — Page Designer,ContentSearchModel, storefront content search, searchHelpers, and searchable Page Designer content.

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

Order failure informationis appropriate operational data for diagnostic logging when it is implemented without exposing protected shopper information. Checkout failures, error codes, integration outcomes, or non-sensitive order-processing context can provide developers and support teams with the information needed to diagnose failed purchases.

Passwords must never be written to application logs. Likewise, complete credit-card information is sensitive payment data subject to stringent PCI controls and should not be placed into custom log files. Salesforce specifically warns developers to filter sensitive or private data—such as credit-card numbers—from service logs, and B2C Commerce payment APIs treat cardholder and financial information as PCI-sensitive data.

Option B would create an obvious credential-disclosure risk because anyone with log access could potentially recover customer authentication data. Option C would unnecessarily persist cardholder information outside the platform ' s protected payment-data handling mechanisms.

The proper logging strategy captures enough contextual data to diagnose checkout problems while excluding passwords, full payment credentials, authentication secrets, and similar sensitive values.

Study Guide reference:Application Development — secure logging, checkout diagnostics, PCI considerations, payment data handling, and protection of customer credentials.

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

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.

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

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.

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

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.

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

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.

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

PageMgr.serializePage()is specifically designed to serialize a Page Designer page into JSON. Salesforce ' sdw.experience.PageMgrAPI distinguishesrenderingfromserialization:renderPage()generates page markup, whereasserializePage()traverses the Page Designer page and its visible components and produces the page representation as a JSON string.

The serialized result can contain the page ID, type ID, content data, custom serialization output, regions, nested components, and component data. This makes it appropriate for applications that need a machine-readable description of the Page Designer composition rather than server-rendered HTML.

Option B first produces rendered markup and then stringifies that value, which does not transform the Page Designer structure into the supported page JSON representation. Option C simply renders the page as markup.

The exact current API exposes overloads that accept a page ID plus parameter information, including parameter strings and aspect-attribute maps where applicable. The key examination distinction is thatserialization usesserializePage, while HTML/markup generation usesrenderPage.

Study Guide reference:Application Development — Page Designer,dw.experience.PageMgr,serializePage(), JSON serialization, andrenderPage().

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

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.

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

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

The appropriate ISML mechanism is therefore:

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

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

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

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

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

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.

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

Authentication details for a Service Framework integration belong in aService Credential, not in custom site preferences or resource bundles. The credential is specifically designed to hold the external service URL, username, and password required for basic authentication.

Salesforce ' s Service Framework documentation states that the service credential is used for basic authentication. Business Manager ' s Service Credentials configuration stores the endpoint URL and the authentication information associated with the remote service. The Script API representation exposesURL,user, andpasswordproperties from the ServiceCredential object.

Placing usernames in site preferences fragments integration configuration and exposes values through a mechanism not designed for service credentials. Storing an endpoint in a.propertiesfile is similarly inappropriate because properties files are normally used for localized application messages rather than environment-specific connectivity configuration.

Keeping secrets in Service Credentials also allows development, staging, and production environments to maintain different endpoints and credentials without changing cartridge source.

Study Guide reference:B2C Commerce Setup — Service Framework, Service Credentials, authentication, URLs, environment-specific configuration, and external REST services.

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

Creating attribute definitions on a Custom Object Type is not always sufficient to make those attributes available in the Business Manager editing interface. The attributes must be assigned to anAttribute Group, which controls how they are organized and presented to Business Manager users.

Salesforce ' s business-object configuration guidance explains that custom object types can be given custom attributes through their attribute definitions and that attributes can be organized into groups for administrative presentation.

Therefore, if the object type itself appears but its fields do not appear when creating or editing an instance, the developer should verify the Attribute Grouping configuration and add the required attributes to a group.

Changing the underlying data type does not address whether the fields are presented to the administrator. Option C mixes two separate custom-object concepts: storage scope determines whether object instances are site-specific or organization-wide, while replication determines whether they move between instances. Neither setting controls whether an attribute appears on the Business Manager edit form.

Study Guide reference:Data Management Using Business Manager Usage — Custom Object Types, attribute definitions, attribute groups, Business Manager presentation, storage scope, and replication.

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

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.

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

No additional action is required when the product slot is already configured, active, scheduled, assigned products, and its rendering template iterates throughslotcontent.content.

Salesforce documents thatslotcontentis an implicit object available inside an ISML template used as a slot rendering template. Itscontentproperty maps toSlotContent.getContent()and returns the collection produced by the evaluated slot configuration. Salesforce specifically demonstrates product slots by iterating over this collection to render returned products.

Therefore, < isloop > is fully valid in a content-slot rendering template. Option C incorrectly claims that loops are prohibited.

A recommender is also optional, not mandatory. B2C Commerce can populate product slots from explicitly selected products, recommendations, or other supported merchandising configuration. If products have already been configured directly, a recommender does not have to be introduced.

The rendering template simply receives the slot execution result and iterates its returned product collection.

Study Guide reference:Data Management Using Business Manager Usage — Content Slots,slotcontent, Product slot content types, rendering templates, < isloop > , and merchant slot configuration.

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

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

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

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

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

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

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

A cartridge that registers B2C Commerce hooks traditionally uses apackage.jsonfile at the cartridge root and points its " hooks " property to the hook registration file located under the cartridge ' s scripts directory. The correct relative path is therefore:

" ./cartridge/scripts/hooks.json "

Salesforce ' s SFRA documentation describes the hook-registration pattern as a root-levelpackage.jsonaccompanied byhooks.jsonundercartridge/scripts. The cartridge containing the implementation must also participate in the relevant site ' s cartridge configuration for the extension to be available.

Option B is not valid JSON syntax because JSON property names and string values must be quoted. Option C uses the wrong relative location;scriptsis below the cartridge directory, not directly below the package root.

Thehooks.jsonfile then maps extension-point names to implementing script modules. Runtime code can invoke those extension points through mechanisms such asHookMgr.callHook(), while the registration metadata tells B2C Commerce which implementation is associated with each hook.

Study Guide reference:Application Development — hooks,package.json,hooks.json, extension-point registration, cartridge structure, and extensibility architecture.

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

When an existing SFRA route already performs the required core processing and the developer only needs to add functionality after that processing,server.append()is the appropriate route-extension mechanism.

Salesforce documents thatserver.appendadds middleware after an existing route ' s middleware chain. The original middleware executes first, followed by the appended middleware. A common documented use case is adding or modifying properties in the route ' sviewDataobject without duplicating the existing controller implementation.

server.extend()is important when a custom controller inherits routes frommodule.superModule, but it is not by itself the operation that adds a new step to a specific route. Option B replaces more behavior than necessary and increases coupling to the underlying implementation.

With an appended function, the developer can retrieve ViewData usingres.getViewData(), add the required properties, update it throughres.setViewData(), and callnext().

The technique preserves the base route and minimizes custom code, supporting upgrade-safe SFRA development.

Study Guide reference:Application Development — SFRA controller customization,server.append(), middleware chains, ViewData,module.superModule, and route extensibility.

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

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.

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

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.

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

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.

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

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.

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

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.

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

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.

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

For anen_CArequest, B2C Commerce first attempts to resolve the requested resource bundle for the country-specific locale. Because there is noaccount_en_CA.properties, the resource lookup falls back to the language-specific English bundle,account_en.properties. That file definesweight.unit=stones, so the rendered message is " Your parcel weighs 10 stones. "

The SalesforceResourceAPI explains that localized strings are loaded from properties resource bundles according to the current request locale. Resource bundles can include a base file, a language-specific file, and country-specific variants. Salesforce ' s localization guidance also identifies the general hierarchy of country locale → language locale → default resources.

account_en_US.propertiesisn ' t selected becauseen_USis a different country-specific locale. It isn ' t the fallback parent ofen_CA; both shareenas their language parent.

The baseaccount.propertiesvalue would be used only if no applicable value were resolved through the more specific English bundle.

Study Guide reference:Application Development — localization, resource bundles,Resource.msg(), locale resolution, and template resources.

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

WARNis the appropriate severity because the operation technically succeeded, yet the result is abnormal enough to require attention and could produce undesirable side effects. A warning signals a recoverable or unexpected condition without incorrectly classifying the operation as an outright failure.

Salesforce logging guidance identifies custom WARN logs as appropriate for warnings in application areas such as integrations and payment processing that can impact users. WARN messages are also available under normal production logging configurations, making them suitable for operational conditions that administrators should be able to investigate.

DEBUG is intended for detailed development/troubleshooting information and is disabled for persistent production logging by default. It would therefore understate a potentially consequential condition. ERROR should represent an operation or state that actually failed or cannot be processed successfully; the question explicitly states that the operation succeeded.

Using the correct severity improves alerting, log filtering, and incident analysis while preventing routine recoverable situations from being mistaken for application failures.

Study Guide reference:Application Development —dw.system.Logger, WARN/DEBUG/ERROR severity, Service Framework troubleshooting, and operational logging practices.

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

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.

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

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

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

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

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

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

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

The new requirement is additive: the existingCart-Showbehavior should continue running, and the client cartridge only needs to add adataLayerproperty to the response. SFRA ' s preferred mechanism for this type of extension is toappend middleware to the existing routeand enrich its ViewData.

Salesforce documentsserver.appendas a controller-customization mechanism that executes the existing middleware chain and then adds an additional step. A common use is precisely to retrieve and update the current ViewData with extra properties that are needed during rendering.

This also preserves cartridge independence. Throughmodule.superModule, the client cartridge resolves the applicable controller immediately to its right on the cartridge path. If the LINK cartridge exists, its customized route participates. If it is later removed, resolution can fall through to the next implementation, such asapp_storefront_base, while the client ' s appended data-layer logic remains unchanged.

Replacing the entire route unnecessarily couples the client implementation to existing logic and duplicates behavior that SFRA ' s extension model already provides.

Study Guide reference:Application Development — SFRA controller extension,server.append,module.superModule, ViewData, cartridge precedence, and upgrade-safe customization.

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

server.append()extends an existing SFRA route by adding middlewareafter the existing middleware chain. It does not replace or bypass the middleware already defined onHome-Show. Therefore, the consent-tracking middleware, cache middleware, and original route logic execute first; after they callnext(), the appended custom function executes.

Salesforce explicitly describesserver.appendas a customization mechanism that causes the original middleware chain to execute together with the additional appended step. It is commonly used when a cartridge must enrich an existing route without duplicating or replacing the base implementation.

The custom controller does not need to repeatconsentTracking.consentorcache.applyDefaultCachesimply because those functions are already part of the inherited route. Option B would become relevant if a middleware filtering condition itself rejected the request, but the absence of those declarations in the appended step does not inherently produce a parameter-mismatch error.

The resulting execution order is therefore: original middleware and base route logic, followed by the appended custom logic.

Study Guide reference:Application Development — SFRA route inheritance,server.append(), middleware chains, controller customization, and cartridge precedence.

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

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.

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

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

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

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

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

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

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

B2C Commerce localizesform structure through locale-specific folders, not by appending the locale to the form-definition filename. For a U.S. English form, the developer createsforms/en_US/and places anaddress.xmlform definition inside it.

Salesforce ' s SFRA Forms documentation explicitly states that when a form ' s structure differs by locale—for example, state fields in one country and province fields in another—the cartridge should contain separate locale directories beneathforms, with each directory containing a form definition of thesame name. If a locale-specific definition is absent, the default form definition is used.

en_USfollows the Salesforce locale naming convention using language and country codes. Option B incorrectly changes the filename toaddress_en_US.xmlinstead of creating the required locale directory. Option C omits the language component and therefore does not use a valid locale ID for this purpose.

The copied U.S. file can then be modified independently to contain the state abbreviation options.

Study Guide reference:Application Development — localized forms,forms/en_US, XML form definitions, address localization, and locale-specific storefront behavior.

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

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 cartridge ' s root-levelpackage.jsonuses the " hooks " property to point to the hook registration file. In the standard SFRA cartridge structure, the hook-registration file resides under:

cartridge/scripts/hooks.json

Therefore, the correct relative path is:

{ " hooks " : " ./cartridge/scripts/hooks.json " }

Salesforce ' s SFRA hook documentation confirms thatpackage.jsonuses thehookskeyword to identify the hook file and that the referenced hook file then maps extension-point names to script implementations.

Option B omits thecartridgeportion of the normal directory structure, so it points to the wrong location. Option C uses JavaScript-object syntax rather than valid JSON because thehooksproperty name is unquoted. Apackage.jsonfile must contain valid JSON.

Thehooks.jsonfile contains entries with the extension-pointnameand correspondingscriptmodule. Once the cartridge is deployed and active on the appropriate cartridge path, registered hooks can participate in storefront or platform extension points.

Study Guide reference:Application Development — hook registration,package.json,hooks.json, cartridge structure, CommonJS hook modules, and extension points.

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

ASynonym Dictionarygroups terms that should be treated as equivalent during storefront search. If several words are configured in the same synonym group, searching for any member expands the query to the other terms, producing the same combined result set.

Salesforce ' s official Synonyms documentation uses almost exactly this example:bag,purse, andpocketbookare configured together, and searching for any one of them generates a query equivalent tobag OR purse OR pocketbook. The result set therefore contains matches for all configured synonyms.

Addingtoteto that group extends the same behavior. Hypernyms and hyponyms represent hierarchical semantic relationships rather than strict or near-equivalence. For example, a broad term can be a hypernym of more specific concepts, and a specific term can be a hyponym of a broader term. Those relationships are useful for search expansion with different semantic direction, but they are not the correct mechanism when every term should produce the same results.

Study Guide reference:Data Management Using Business Manager Usage — Search Dictionaries, Synonyms, query expansion, Hypernyms/Hyponyms, and storefront search relevance.

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

The decisive setting is " methods " :[ " put " ]. Salesforce ' s OCAPI HTTP-method specification definesPUTas a method that can create a resource when the addressed resource does not yet exist and replace/update the resource when it already exists.DELETE is a separate HTTP methodand must be explicitly authorized to remove a resource.

OCAPI settings also state that themethodsproperty acts as the HTTP-method permission filter for the matching resource ID. If only PUT is listed, the client has no DELETE permission simply becausewrite_attributesis broad.write_attributes: " (**) " controls which document properties an authorized write request can contain; it does not implicitly add other HTTP operations.

Therefore, among the supplied choices, A is the supported answer. PUT permits coupon creation at the addressed resource and can also replace/update an existing addressed coupon. Options B and C are invalid because both explicitly claim DELETE capability even though " delete " is absent from the methods list. C additionally overstates access to coupon-code operations.

Study Guide reference:Application Development — OCAPI settings, HTTP PUT, DELETE authorization, resource permissions, and Coupons Data API.

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

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.

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

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.

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

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.

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