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

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.

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

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.

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

In SFRA controllers, theserver.formsAPI provides access to form definitions and converts the corresponding B2C Commerce form into the JSON-style form representation used by SFRA. Because the definition is namednewsletter.xml, the form is retrieved by its definition ID,newsletter, using:

server.forms.getForm( ' newsletter ' )

Current SFRA base-controller source repeatedly demonstrates this exact pattern—for example,server.forms.getForm( ' profile ' ),server.forms.getForm( ' address ' ), andserver.forms.getForm( ' billing ' ).

Option B is incorrect because the property isserver.forms, plural, notserver.form. Option C incorrectly supplies the generated HTML/form namespace prefixdwfrm_. That prefix can appear in submitted HTTP parameter names, butgetForm()expects the form-definition name itself.

The form definition establishes field structure, metadata, validation requirements, and localization behavior. Once retrieved throughserver.forms.getForm(), the controller can pass the resulting form model to an ISML template, inspect its values, validate submitted information, or clear/reset it as required.

Study Guide reference:Application Development — SFRA forms, XML form definitions,server.forms.getForm(), validation, and controller-to-template form handling.

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

Thevarattribute of an < isloop > statement defines the variable that represents the current object from the collection during each iteration. In this example,items= " ${pdict.Basket.products} " supplies the iterable collection, whilevar= " product " assigns each current collection member to the variable namedproduct. Therefore, inside the loop body, the current product is referenced directly asproduct.

Salesforce ' s ISML documentation defines the loop variable as the identifier through which the current element in the iterable collection is accessed. The separatestatus= " loopstatus " variable represents loop metadata, such as iteration position and related state; it is not the product itself.

Option B is incorrect because declaringvar= " product " does not create aproductproperty insidepdict. Option C also misuses the status variable:loopstatusis an iteration-status object rather than a direct array index intended to retrieve the current item. Using the explicitly declared loop variable produces clearer, idiomatic, and maintainable ISML.

Study Guide reference:Application Development — ISML templates, < isloop > , pipeline dictionary access, loop variables, and storefront rendering.

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

Custom storefront scripts arecode artifacts, not Business Manager metadata objects. Consequently, among the supplied options, B is the technically correct first step: create or define the required JavaScript/CommonJS script module within the project code structure.

Salesforce documents that B2C Commerce script modules are.js,.ds, or.jsonfiles and are normally stored in cartridges, commonly undercartridge/scripts. Modules expose public functionality throughexportsand are loaded withrequire(). Controllers and other server-side components can then import and invoke that reusable module.

Business Manager does not provide a general mechanism for creating arbitrary SFRA application scripts. Business Manager manages configuration, metadata, jobs, services, catalogs, and related platform data; deployable application logic belongs in cartridges/code versions.

Option C is less precise because the script/module itself must first be established in the codebase before its exported behavior can be consumed.

Study Guide reference:Application Development — CommonJS modules,cartridge/scripts, JavaScript modules,require(), exports, and cartridge-based application code.

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

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.

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

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.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

Category-page refinements andkeyword-search refinementsuse different refinement contexts. A definition attached to Clothing can work correctly when the shopper navigates directly into the Clothing category because that category supplies the refinement context. A general storefront keyword search, however, does not automatically use the Clothing category ' s local refinement definition.

Salesforce ' s official guidance specifically states:to create search refinements for keyword search, create them for the root category of the storefront catalog.

Therefore, ifNewnessexists only on Clothing, it can appear during category navigation but fail to appear when a shopper types " Clothing " into storefront search. Configuring the refinement at Women would still not establish it as the catalog-level keyword-search refinement. Option C also introduces a conflict that the scenario does not establish.

This distinction is important when merchants want consistent refinements across broad keyword search versus category-specific browsing. Root-level definitions provide the catalog-wide search context, while child-category definitions customize refinement behavior for navigation within specific merchandising branches.

Study Guide reference:Data Management Using Business Manager Usage — Search Refinement Definitions, Root category, keyword search, category browsing, and refinement inheritance.

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

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.

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

This requirement can be implemented declaratively through the shipping method ' s existingproduct exclusion/allow-list configuration, avoiding unnecessary SFRA customization.

Salesforce explicitly supports both product blocklists and product allowlists for shipping methods. Its official example closely mirrors this scenario: suppose free shipping excludes all televisions, but the merchant wants a Brand-XYZ television to qualify. The administrator adds the Brand-XYZ product or rule as an exception in the Product Exclusion configuration, effectively removing those matching products from the exclusion set and allowing the shipping method.

That is preferable to adding custom logic inshippingMethod.jsorCheckoutShippingServices. Business Manager configuration is maintainable by merchants, can be changed without a code deployment, and aligns directly with a temporary three-month merchandising requirement.

The terminology can appear counterintuitive because the allow-list exception is configured inside the broaderProduct Exclusioninterface. Conceptually, the initial inclusion defines which products are blocked, while the nested exclusion identifies exceptions that are taken back out of that blocklist.

Study Guide reference:Data Management Using Business Manager Usage — shipping methods, product exclusions, product allowlists, Business Manager shipping configuration, and configuration-over-code best practices.

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

Among the supplied choices, B is the only approach consistent with robust B2C Commerce integration design: the application must inspect service results, preserve useful diagnostic information, and implement controlled error behavior rather than blindly proceeding.

However, " log all responses " must be interpreted according to Salesforce ' s secure logging practices. Raw responses mustnotbe persisted indiscriminately when they contain passwords, access tokens, personal information, payment data, or other sensitive content. B2C Commerce ' s Service Framework provides logging controls such as response/request filtering specifically so that sensitive information can be removed before it reaches diagnostic logs.

Ignoring a failed API response, as in A, can produce corrupt application state or misleading storefront behavior. Option C is equally problematic because silently converting failures into successful responses prevents calling code and shoppers from receiving appropriate failure handling.

A correct production implementation examines the Service Framework result, logs sanitized diagnostic context where appropriate, implements fallback behavior when the business process allows it, and returns a controlled application response.

Study Guide reference:Application Development — Service Framework, external API integrations, service result handling, secure logging, exception management, and graceful failure behavior.

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

ACommon Phraseis specifically intended for multi-word searches whose words must be interpreted together and in sequence. Configuringcar accessoriesas a common phrase withExact Matchreduces search noise and causes the phrase to be treated as a meaningful unit rather than allowing the generic termaccessoriesto broaden results toward unrelated accessory categories.

Salesforce defines common phrases as search terms containing two to five adjacent words in a specific order and explains that they are used to provide more targeted results for multi-word queries. With Exact Match mode, only products matching the exact phrase are returned for that phrase.

Option A is inappropriate because synonym relationships expand equivalent terminology; declaring household and technology as synonyms of car accessories would increase irrelevant matches instead of eliminating them. Option C introducesNOTexpressions into the dictionary value, which isn ' t the required way to define this common phrase.

This use case illustrates the distinction between search dictionaries: synonyms broaden equivalent terminology, whereas common phrases preserve the semantic significance of words occurring together.

Study Guide reference:Data Management Using Business Manager Usage — Search Dictionaries, Common Phrases, Exact Match search mode, synonyms, and storefront search relevance.

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

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.

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

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.

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

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.

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

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.

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

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.

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

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.

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

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

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

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

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

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

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

The controller passes the form object tores.render()under the property namenewsletterForm. SFRA merges render data into the response ViewData, and the resulting information is made available to the ISML template throughpdict. Therefore the correct template reference is:

pdict.newsletterForm

The resulting expressions become:

pdict.newsletterForm.attributes

and

pdict.newsletterForm.email.attributes

The form ' sattributesproperty contains generated form-level HTML attributes, while theemailfield exposes its own generated attributes and state.

Option B uses the form-definition name rather than the property name chosen by the controller. Option C omits thepdictaccess expected in the supplied ISML pattern.

Study Guide reference:Application Development — SFRA forms,server.forms.getForm(), ViewData,pdict, form attributes, and controller-to-template data binding.

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

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.

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

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.

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

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

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

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

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

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

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

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 required information is structured application data that is specific to one site but must move consistently from staging to production. Asite-scoped, replicable Custom Objectis therefore the correct model.

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

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

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

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

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

A shared content library allowsmultiple B2C Commerce sites to use the same collection of content assets and folders. Salesforce states directly that a shared library can be assigned to multiple sites, whereas a private library belongs to its owning site and cannot serve as another site ' s site library.

This enables organizations operating several storefronts or brands to centrally maintain common assets such as legal text, help pages, sizing information, promotional copy, and images while optionally using site-specific attributes to control whether particular assets are online or searchable on each site.

Content slots are not what the library itself shares. Slots are merchandising placements/configurations associated with storefront contexts, while content assets are stored in content libraries.

Study Guide reference:Data Management Using Business Manager Usage — content libraries, shared libraries, private libraries, content assets, and multi-site content management.

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

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

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

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

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

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

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

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.

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

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.

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

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.

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

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 taxation policy is selected when a B2C Commerce site is created. It is not an ordinary editable site preference that administrators can unlock later. This eliminates options B and C.

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

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

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

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

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

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.

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

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.

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

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.

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

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

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

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

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

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

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

The two-argumentLogger.getLogger()method accepts afile-name prefixfollowed by alogging category. Here,loggerFileis the requested custom file-name prefix andcategory1.euis the category.

Salesforce ' s Script API defines the signature asLogger.getLogger(fileNamePrefix, category). Custom log files created through this mechanism are stored as custom logs, so their actual generated filename begins with thecustom-naming convention followed by the developer-supplied prefix. Salesforce also states that repeated calls using the same file-name prefix use the same associated custom logger/file.

The WARN message passes filtering becausecategory1.euinherits its logging threshold from parent categorycategory1, which is enabled at WARN. B2C Commerce custom logging is hierarchical, so parent-category rules apply to descendant categories unless overridden.

Therefore, the WARN entry is written to the custom log beginning withcustom-loggerFile.

Study Guide reference:Application Development — Logger file prefixes, custom log files, category inheritance, WARN filtering, andLogger.getLogger().

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

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

For example, a default bundle might be:

account.properties

while its French translation would be:

account_fr.properties

Both belong under:

cartridge/templates/resources

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

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

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

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

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

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.

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

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.

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