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

Custom DEBUG messages are subject to theCustom Log Settingsfilters. If the script logs against a custom category but that category is not active at DEBUG severity, the messages are filtered and will not appear in the in-memory request logging used during non-production debugging.

Salesforce states that custom DEBUG and INFO logging are disabled by default and are configured throughAdministration > Operations > Custom Log Settings. The root/category hierarchy determines which custom messages pass the logging filter.

Therefore, the developer should enable the applicable category at DEBUG level. There is no Site Preference or Global Preference checkbox named " Enable custom logging in Request Log " that replaces this logging-category configuration.

On non-production instances, debug-level custom output can participate in in-memory logging associated with request diagnostics without necessarily requiring persistent debug log files. This makes category configuration particularly important when using the Storefront Toolkit Request Log for focused troubleshooting.

Developers should restore less verbose settings after diagnosing the issue because broad DEBUG logging can produce large volumes of data and make important diagnostic messages harder to isolate.

Study Guide reference:Application Development — Custom Log Settings, DEBUG categories, Storefront Toolkit Request Log, in-memory logging, and custom logging filters.

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

Template decorators provide a standard mechanism for extracting shared page structure—such as headers, navigation, wrappers, footers, and common layout markup—into reusable ISML templates. A child template uses < isdecorate > to select a decorator, and the decorator uses < isreplace/ > to identify the location where the child ' s page-specific content is inserted.

Salesforce describes < isdecorate > as the ISML mechanism for decorating enclosed content with another template and defines < isreplace/ > as the placeholder where the decorated content is inserted. A typical use case is wrapping different page bodies with a common header and footer.

This architecture directly reduces repeated layout code and improves maintainability because a shared element can be changed in the decorator rather than edited across many individual pages.

Option B misuses < isscript > ; script tags are intended for executable template scripting, not reusable page composition. Option C doesn ' t represent the standard decorator-based technique requested by the question and can encourage fragmented template composition when a reusable layout is the underlying requirement.

Study Guide reference:Application Development — ISML templates, template decorators, < isdecorate > , < isreplace > , reusable presentation structure, and maintainable storefront design.

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

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.

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

TheMerchant Tools > Content > Import & Exportmodule is specifically associated with content libraries, folders, andcontent assets. Salesforce documents that content and content-library data use thelibrary.xsdimport/export schema and are handled from this Business Manager location.

Content slots are imported and exported through the separateMerchant Tools > Online Marketing > Import & Exportmodule usingslot.xsd. Products and catalogs are likewise administered throughMerchant Tools > Products and Catalogs > Import & Exportusingcatalog.xsd. Salesforce ' s official Import and Export Object Cheatsheet clearly differentiates these locations and schemas.

The distinction matters because B2C Commerce import/export mechanisms are organized around object domains rather than providing one universal site import screen for every object. Content assets belong to libraries and can include text, markup, links, images, and other merchandising content. They can also be exported from one library and imported into another.

Therefore, among the supplied choices, Content assets are the object type that belongs to the Content Import & Export module.

Study Guide reference:Data Management Using Business Manager Usage — content libraries, content assets, import/export schemas, Business Manager modules, and data migration.

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

SFRA storefront source contains several types of front-end assets that require preprocessing before the cartridge is deployed for normal use. JavaScript source is compiled or bundled through thecompile:jstask, SCSS source must be transformed into browser-consumable CSS throughcompile:scss, and the required font resources are copied into the generated static asset structure throughcompile:fonts. Therefore, option C represents the appropriate first-time SFRA asset build sequence.

compile:htmlis not part of the standard SFRA storefront asset compilation process. ISML templates are server-side templates and are uploaded as cartridge resources rather than being converted into static HTML by an npm compilation step. Likewise,npm run cleanremoves generated build artifacts; it does not substitute for producing the CSS and font assets required by the storefront.

After the assets and cartridge code are built and uploaded, the cartridges must also be registered through the site ' s cartridge path so that B2C Commerce can resolve and execute them. Salesforce ' s SFRA configuration guidance describes the cartridge deployment and site-registration workflow.

Study Guide reference:Application Development — SFRA project structure, front-end asset compilation, cartridge deployment, and storefront development workflow.

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

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.

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

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.

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

B2C Commerce can store multiple code versions simultaneously, but only theactive code versionsupplies the storefront ' s templates, controllers, scripts, and static code resources. If recently uploaded cartridge changes do not appear, verifying that the expected code version is active is therefore a fundamental troubleshooting step.

Salesforce ' s Code Deployment documentation states that all templates, pipelines, scripts, and images are taken from the active version. It also specifically recommends checking that the cartridge was uploaded to the current code version when storefront changes do not appear. Salesforce ' s SFRA troubleshooting guidance further recommends switching code versions and reactivating the intended version when changes are not reflected on the server.

A search-index rebuild is relevant to indexed product, category, content, or search configuration—not to changes in JavaScript controllers or ISML templates. Cartridge-path configuration should also be verified, but the source ' s earlier scenario already uses that check before checking the active version.

Study Guide reference:B2C Commerce Setup — Code Deployment, active code versions, cartridge deployment, storefront troubleshooting, and version activation.

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

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.

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

A task-oriented B2C Commerce Job step can return adw.system.Statusobject to control the Job Framework ' s exit status. BecauseNO_FILES_FOUNDis explicitly anon-errorcondition, the developer should construct a Status usingStatus.OKand supplyNO_FILES_FOUNDas the custom status code.

Salesforce documents that whenStatus.isError()is false and the returned status code is custom, the Job Framework preserves that custom code and continues execution unless the job flow has a transition that handles it differently.

Option A returns an arbitrary object rather than adw.system.Status. Option C also returns a plain JavaScript object; Salesforce states that a returned object that is not aStatusresults in the ordinaryOKstatus rather than establishing the desired custom status code.

Study Guide reference:Application Development — Job Framework, task-oriented job steps,dw.system.Status, custom status codes,Status.OK, and job transitions.

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