Comm-Dev-101 Salesforce Certified B2C Commerce Developer Free Practice Exam Questions (2026 Updated)

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.

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

This is a scheduled batch-processing requirement and therefore belongs in the B2C CommerceJob Framework. The developer should implement a custom job step, define its step type, and provide the corresponding CommonJS script that obtains order information, writes the CSV file, and stores the output in the required WebDAV location.

A custom job step can then be included in a Business Manager job and scheduled at the required interval. The script can use B2C Commerce APIs such as OrderMgr for order retrieval and file/CSV APIs for output generation. The job framework also provides status handling, execution history, step transitions, and operational monitoring, making it the appropriate architecture for periodic exports.

Option B is invalid because Business Manager does not use Unixcroncommands as the mechanism for storefront application scheduling. Scheduling is managed through B2C Commerce Jobs. Option C is unrelated: OCAPI provides external API access and the Customers resource would not be the correct architecture for periodic server-side order exports.

Study Guide reference:Application Development — Job Framework, custom job steps,steptypes.json, CommonJS job scripts, CSV exports, and WebDAV file processing.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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