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

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.

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

Creating a Search Refinement Definition alone is insufficient. The attribute being used as the refinement source must contain meaningful values on the applicable products and those values must be represented in the product search index. Otherwise, the search engine has no refinement values from which to construct storefront filters.

Salesforce states this prerequisite directly in its Search Refinement documentation:before creating refinements based on attribute values, ensure that the attribute has data and is indexed.

TheSearchablesetting referenced in option B is associated with whether an attribute participates in keyword-style search behavior; it is not the primary requirement for an attribute-based refinement already defined in the refinement configuration. Option C is also unnecessary in standard SFRA. The existing refinement rendering logic obtains available refinements dynamically from the search result model, so developers do not normally modifyproductsearchrefinebar.ismlmerely because another configured refinement was added.

After changing indexed product data or searchable/refinement configuration, the appropriate product search index must also be rebuilt so that the storefront operates against current indexed values.

Study Guide reference:Data Management Using Business Manager Usage — search refinements, product attributes, search indexing, refinement definitions, and storefront filtering.

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

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 logging uses ahierarchical category model. When WARN is enabled onproduct, WARN and all higher-severity levels are available forproductand descendant categories. A more specific configuration onproduct.importcan then lower that subcategory ' s threshold to DEBUG.

Salesforce gives essentially this exact example in its server-side JavaScript documentation: when WARN is enabled forproductand DEBUG is configured forproduct.import, WARN and ERROR are logged for the parent and its subcategories, whileproduct.importadditionally logs DEBUG and INFO.

The reason is that the configured level is aminimum severity threshold. DEBUG is lower than INFO, WARN, ERROR, and FATAL, so selecting DEBUG permits the entire severity range for that category. The more specific child-category setting overrides the inherited parent threshold for that branch.

This hierarchical design lets administrators keep broad logging conservative while temporarily increasing diagnostic detail for one subsystem such as product import processing.

Study Guide reference:Application Development — custom logging hierarchy, parent/child categories, log-level inheritance, DEBUG, INFO, WARN, and granular 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.

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

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.

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