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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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.

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

When the requirement is simply to add information to an existing route ' sviewData,server.append()is the most targeted SFRA customization mechanism. The original route executes first, after which the appended middleware can callres.getViewData(), add or modify properties, and then callres.setViewData().

Salesforce ' s official SFRA customization guidance uses this exact pattern:server.appendmodifies an existing route by adding middleware that enriches theviewDataobject used for rendering. The documentation states that the original middleware chain and appended middleware both execute.

Replacing the callback is unnecessarily invasive when existing route behavior remains valid.server.extend()has a different purpose: it inherits a server object ' s routes from the super module so that those routes can then be customized; it is not itself the specific operation that adds a post-processing step to an existing route.

Therefore, the developer should extend the controller module as necessary andappendmiddleware to the relevant route to add the new ViewData property.

Study Guide reference:Application Development — SFRAserver.append, ViewData,getViewData(),setViewData(), controller extensibility, and route middleware.

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

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.

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

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.

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

B2C Commerce provides a dedicatedAvailability Low Ranking Thresholdsetting for exactly this search-merchandising requirement. It is configured in Business Manager under Search Preferences and specifies the availability percentage at or below which products should be pushed toward the end of search results.

Salesforce gives the example that a threshold of0.3causes products with availability of 0.3 or lower to be ranked lower in storefront search. This preserves product discoverability while prioritizing merchandise that has healthier inventory.

Option A is unnecessarily destructive and operationally inefficient. Hiding products through an hourly job changes catalog state and can create delays or merchandising side effects. It also does not distinguish between temporarily low inventory and true unavailability. Option C confuses availability ranking with Searchable Attribute boost configuration. The platform already exposes a specific preference for low-availability ranking, so custom boosting is unnecessary.

This feature is particularly useful when merchants want low-stock merchandise still discoverable but not prominently ranked, balancing inventory awareness with conversion-oriented search results.

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

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

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.

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

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

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

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

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

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

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

ProductSearchModel.getProductSearchHits()retrieves product hits from B2C Commerce ' sproduct search indexrather than performing direct product-database iteration. Search-index access is designed for scalable storefront product discovery because the index is optimized for search, refinement, sorting, and high-volume retrieval.

Salesforce ' s Script API explicitly recommends iteratingProductSearchHitobjects rather than loading Products directly from search results. The oldergetProducts()method is deprecated because loading full Product objects for every result is significantly more expensive from a performance perspective; Salesforce recommendsgetProductSearchHits()instead.

ProductAvailabilityModel.isOrderable()determines the orderability of a particular product within its inventory/availability context; it is not a general indexed search mechanism.ProductIndexModel.getOrderableProductsOnly()is not the appropriate supported method represented by the current Product Search API.

A common efficient storefront pattern is to configure aProductSearchModel, execute the search, iterate its search hits, and load only the product data actually needed for the current page.

Study Guide reference:Application Development — ProductSearchModel, ProductSearchHit, search indexes, scalable product retrieval, and storefront search performance.

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

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.

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

Search settingsandPromotionsare both site-level business configurations that have dedicated import/export functionality within the site ' s Merchant Tools area. Therefore, when the developer needs to import different configurations for two sites on the same instance, these files can be handled through each site ' s corresponding Merchant Tools modules.

Salesforce ' s B2C Commerce import/export guidance distinguishes site-specific data from organization-level metadata. Promotions are managed through the site ' sMerchant Tools > Online Marketing > Import & Exportfunctionality, while search information can be managed through the site ' s search import/export capabilities.

System type extensions, by contrast, modify system-object metadata and are administered at the organization level through Site Development/System Object configuration and organization-level import mechanisms. They are not independently site-specific Merchant Tools data. This makes both options B and C incorrect because each contains system type extensions.

The distinction is operationally important in a multi-site instance. Site-specific merchandising/search configuration can vary independently by storefront, whereas extensions to system object definitions affect the shared platform metadata available across the organization.

Study Guide reference:Data Management Using Business Manager Usage — site import/export, promotions, search configuration, system-object extensions, and multi-site administration.

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

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

Therefore, the correct generated URL is equivalent to:

Page-Show?cid=about-us

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

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

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

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

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.

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

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.

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

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.

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

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.

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

The call syntax shown is valid:CustomObjectMgr.createCustomObject(type, keyValue)accepts the object type followed by the unique key value. The issue is persistence. A custom object is a persistent business object, so creation or modification must occur within a B2C Commerce database transaction.

Salesforce ' sTransactiondocumentation states thatbefore a persistent business object can be created, changed, or deleted, a transaction must be started. Changes become durable only after that transaction is successfully committed. The usual SFRA implementation pattern isTransaction.wrap(function () { ... });, although explicitbegin()andcommit()operations are also supported.

Atry/catchblock provides exception handling but does not establish transactional persistence, so option B does not solve the fundamental issue. Option C is incorrect because the API does not accept a third argument representing the key attribute name. The object ' s metadata already establishes which attribute is its key.

Transactions should cover only the minimum necessary mutation logic to reduce locking and maintain efficient storefront processing.

Study Guide reference:Application Development — persistent objects,CustomObjectMgr,dw.system.Transaction, transaction boundaries, and custom-object persistence.

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

B2C Commerce assigns exactly one customer list to each site, but the same customer list can be assigned to multiple sites. Therefore, RefArch does not need a separate copy of the RefArchGlobal customer records. The site configuration must simply be changed so thatRefArchGlobal is selected as RefArch ' s assigned Customer List.

Salesforce describes a customer list as a collection of registered customers associated with a site and explicitly states that multiple sites can share a customer list. A site itself can use only one customer list at a time.

Option A would create or import data rather than establish the required shared-list relationship. That introduces duplication rather than true shared customer profiles. Option B is also incorrect because this relationship isn ' t enabled through a generic " Customer List Sharing " global preference. The appropriate configuration is the customer-list assignment on the site.

Shared customer lists are especially useful for multi-site implementations where customers should maintain one registration/profile across multiple storefronts.

Study Guide reference:B2C Commerce Setup — multi-site configuration, customer lists, shared customer profiles, and site-level customer-list assignment.

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

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

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

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

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

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

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.

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

The certification varies byproduct and site, so the data belongs directly on the Product system object as asite-specific custom attribute. A product can then have one default certification value and independent site-specific overrides for the U.S. and European storefronts.

Salesforce documents that products are organization-level entities shared across sites, but selected system and custom product attributes can be configured as site-specific. A site-specific attribute can hold a default value and per-site overrides, making it appropriate for information such as market-specific product presentation or compliance metadata.

The attribute should not be localizable if it is site-specific; Salesforce explicitly states that onlynon-localizablecustom product attributes can be site-specific.

Option B proposes a Certificate system object type that does not represent the product/site relationship described. Option C would create a site-wide value and therefore could not distinguish between different certificates for smartphones, hairdryers, and other products.

Study Guide reference:Data Management Using Business Manager Usage — Product custom attributes, site-specific attributes, multi-site product data, and PDP presentation.

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

A script must be part of theeffective storefront cartridge pathto participate in normal runtime module resolution. If the cartridge containing the script is not on that path, the storefront does not execute that copy of the module, so the debugger cannot bind the breakpoint to executable code in the current request context.

Salesforce describes the cartridge path as the lookup structure B2C Commerce uses to resolve controllers, scripts, templates, and other cartridge resources. The order is significant because the first matching implementation according to cartridge precedence is the one actually used.

Option C is incorrect because being a third-party cartridge does not inherently prevent script debugging. If that cartridge ' s source is deployed and its script participates in the active runtime, breakpoint behavior is governed by the normal debugging/runtime constraints rather than vendor ownership.

Option B is less appropriate to the wording " unable to resolve a specific breakpoint " : if the entire debugging session were inactive, debugging generally would not be functioning at all rather than selectively failing to resolve one script.

Study Guide reference:B2C Commerce Setup — Script Debugger, cartridge path resolution, cartridge precedence, active code, and breakpoint troubleshooting.

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

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.

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

SFRA ' s deployment and development tooling usesdw.jsonto provide the connection and authentication information required to communicate with the B2C Commerce instance. Among the options listed,usernameis the required credential-related parameter.

Salesforce ' s current tooling guidance confirms thatdw.jsoncontains B2C Commerce instance credentials and that WebDAV-based code deployment/file operations require a username plus authentication credential. Salesforce ' s SFRA build documentation similarly explains thatdw.jsonprovides the server-connection and code-version information used by command-line upload tooling and npm-driven development workflows.

A CSRF token isn ' t stored indw.json; CSRF tokens protect individual storefront HTTP requests and forms. A Site ID is also not the credential needed by the cartridge-upload scripts. Upload operations target the instance/code version rather than authenticate by storefront site ID.

In contemporary environments, Salesforce recommends secure access-key/OAuth-oriented authentication mechanisms where applicable, but the underlying exam concept remains that a username is part of the connection credential configuration used by these development/deployment tools.

Study Guide reference:B2C Commerce Setup —dw.json, SFRA development environment, npm/sgmf scripts, WebDAV authentication, and cartridge deployment.

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

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

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

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

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

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

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

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.

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

When an SFRA controller inherits an existing route and usesserver.append()to add another middleware function, the appended function is addedafter the existing middleware chain. The developer does not need to repeat all of the middleware that already belongs to the base route.

Salesforce states directly thatserver.appendcauses a route to execute both theoriginal middleware chain and any additional appended steps. Therefore, provided the custom controller correctly extends the base server module and callsnext(), the original route executes first and the appended custom code executes afterward.

Omitting the existing middleware declarations from the appended function does not itself generate a parameter-mismatch runtime error. The inherited route retains its consent, cache, authentication, metadata, or other middleware steps. Option C reverses the execution sequence expected from an append operation.

Study Guide reference:Application Development — SFRAserver.append(), route inheritance, middleware chains,module.superModule, and controller extension.

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

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.

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

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.

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

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.

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

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

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

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

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

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

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

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.

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

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.

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

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.

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

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

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

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

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

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

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.

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

Washing instructions are product-specific business data, so the value should be modeled as acustom attribute on the Product system object. Because the displayed instructions can differ by storefront locale, the custom attribute should be configured as localizable.

Salesforce ' s B2C Commerce metadata system allows custom attributes to be created on extensible system objects such as Product. Localizable custom attribute definitions count against the Product object ' s supported custom-attribute quota, confirming that Product attributes can participate in localized data modeling.

Option A is inappropriate because resource bundles are designed for application UI strings such as labels, messages, and validation text. They are not a scalable source for product-specific PIM data such as care instructions. Option C is also incorrect because localization is configured on eligible attributes, not by marking the entire Product system object " localizable. "

A PIM integration can populate locale-specific values of the washing-instructions attribute, after which the PDP retrieves the appropriate value under the active storefront locale.

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

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

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.

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

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.

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

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.

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

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

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

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

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

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

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

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.

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

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.

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