Salesforce Comm-Dev-101 - Salesforce Certified B2C Commerce Developer

Because the storefront already has the standard credit-card payment method, the additional requirement is to makeAmerican Express an accepted card typewithin that payment-method configuration. B2C Commerce distinguishes the general payment method (CREDIT_CARD) from the specific credit/debit card brands accepted through it.

Salesforce ' s Payment Methods documentation directs administrators to the Credit/Debit Cards configuration associated specifically with the defaultCREDIT_CARDpayment method. This is where supported card types are managed.

A payment processor is the technical processing implementation associated with payment methods. American Express does not need to become a completely separate payment processor merely because the merchant wants to accept that card brand. The actual processor must of course support American Express, but the storefront-facing card availability is configured under the credit-card payment-method/card-type configuration.

Option C is incorrect because card brands are not enabled by creating arbitrary Site Preferences.

This architecture keeps payment presentation and processing responsibilities separate: payment methods and accepted card types govern what the shopper can select, while payment processors govern authorization, capture, and other transaction handling.

Study Guide reference:Data Management Using Business Manager Usage — payment methods, credit/debit card types, payment processors, and checkout configuration.

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

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.

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

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

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

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

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

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

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

Locale configuration in B2C Commerce occurs attwo levels. First, the locale must be configured and activated for the organization/instance underAdministration > Global Preferences > Locales. Second, that active locale must be enabled for the particular storefront under the site ' sSite Preferences > Localesconfiguration.

Salesforce explicitly states that only globally activated locales can be used by storefronts. After organization-level locale configuration, administrators select the allowed locales for each individual site and designate an appropriate default locale.

Option B stops after global configuration and therefore doesn ' t make the locale an allowed locale of the specific storefront. Option C incorrectly introduces an alias as a prerequisite; URL aliases can be part of storefront URL strategy but aren ' t required to establish a locale itself.

After enabling the locale, developers and merchandisers must also provide localized resources/data as required—such as templates, properties bundles, catalog data, content, and search-index data. Search indexes should be generated for storefront locales where localized search functionality is required.

Study Guide reference:B2C Commerce Setup — organization locales, site locales, Global Preferences, Site Preferences, localization, and multi-language storefront configuration.

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

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

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

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

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

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

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

American Express is acredit-card type used under the existingCREDIT_CARDpayment method, rather than a new payment processor or Site Preference. Therefore, the appropriate Business Manager action is to manage the supported Credit/Debit Cards associated with the credit-card payment method.

Salesforce documents that merchants manage payment methods underMerchant Tools > Site Ordering > Payment Methodsand that the Credit/Debit Cards page manages card types specifically in the context of the defaultCREDIT_CARDpayment method.

A payment processor represents the integration that processes transactions; American Express itself is not created as a payment processor simply because that card network should be accepted. Likewise, Site Preferences are not the mechanism used to enable supported card brands.

The underlying payment processor must, of course, support American Express transactions, but storefront card eligibility is configured through the credit/debit card configuration associated with the credit-card payment method. Card configuration can additionally restrict cards according to countries, currencies, customer groups, or payment ranges.

Study Guide reference:Data Management Using Business Manager Usage — Payment Methods, CREDIT_CARD, Credit/Debit Cards, card types, and payment processors.

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

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

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

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

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

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

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

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

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

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

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