Pass the Salesforce Developers Comm-Dev-101 Questions and answers with ExamsMirror

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.

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

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.

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

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.

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

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.

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

SFRA uses thePage-Showendpoint to render a content asset as a full storefront page. The endpoint accepts the query-string parametercid, which identifies the content asset to display. Consequently, the content-link expression must generate the equivalent of:

Page-Show?cid=about-us

and option A provides the correct syntax.

Salesforce ' s current SFRAPage.jsdocumentation identifiesPage-Showas the endpoint that renders a content asset in a full storefront page and explicitly documentscidas the content asset ID parameter. Salesforce also documents special content-link functions for links embedded inside content assets, allowing merchant-managed rich content to reference storefront resources without hard-coding complete URLs.

Content-ShowandContent-Pageare not the SFRA full-page content endpoints shown in these choices. Additionally, B does not passcidas the required parameter name.

Using the URL generation function rather than a literal storefront URL preserves correct host, locale, URL-rule, and deployment behavior.

Study Guide reference:Application Development — content assets, content links,$url(),Page-Show,cid, and SFRA content-page rendering.

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

Before application code can create or manipulate instances of a new custom-object type, the object ' smetadata definition must exist in B2C Commerce. Among the provided options, A represents that required first step.

More precisely, the developer creates aCustom Object Type definitionin Business Manager under Administration > Site Development > Custom Object Types. Salesforce documents that a custom object type must be defined before custom object instances can be created. The definition establishes the ID, key attribute, storage scope, replication behavior, custom attributes, and attribute groups.

Only after this metadata exists can code use APIs such asCustomObjectMgr.createCustomObject()to create persistent instances or read and update their attributes.

Option B reverses the platform ' s metadata-driven architecture: application JavaScript does not define a new custom-object schema. Option C is also premature because runtime handling logic cannot reliably use an object type that has not yet been established.

In a managed implementation, the definition should normally be created on staging and replicated as Object Definitions rather than manually recreated in production.

Study Guide reference:Data Management Using Business Manager Usage — Custom Object Types, object definitions, attributes, storage scope, replication, and CustomObjectMgr.

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

B2C Commerce allowsmultiple modules to be registered for the same extension point, including multiple registrations in a singlehooks.jsonfile. Salesforce explicitly documents this behavior. When the extension point is invoked, all registered modules are executed rather than stopping after the first implementation.

Option B is incorrect as stated for modules registered together in one hook configuration: Salesforce states that the developer cannot explicitly control their execution order through the registration itself. Across cartridges, however, hook execution follows cartridge-path order, so cartridge precedence can affect the sequence in which implementations from different cartridges execute. Option C is also incorrect because Salesforce specifies that when multiple hook modules are called,the last hook ' s return valueis the return value that is ultimately used—not the first hook ' s return value. All registered implementations still execute even if earlier implementations return values.

This behavior is important when several cartridges extend the same business process. Developers must design hooks to coexist without assuming that their implementation is the only one registered.

Study Guide reference:Application Development — SFRA hooks,hooks.json, extension points, HookMgr, cartridge-path execution, and multiple hook implementations.

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

The Request Log usesin-memory loggingon supported non-production instances. The " Log Files " checkboxes control whether a particular severity is persisted into a physical custom log file; they are not required merely to make the message visible in the Request Log Viewer.

However, the category filter still matters.myLogCategoryis currently configured at INFO, so DEBUG—the lower-severity level—is filtered out. The developer therefore must change the category ' s threshold toDEBUG. Salesforce explains that configured levels represent minimum severity and that DEBUG in-memory logging supports theShow Request Logfeature without necessarily creating a debug log file.

Checking the DEBUG target would generate persistentcustomdebugoutput where supported, but that is separate from the stated requirement to inspect the Request Log. Therefore option C performs an unnecessary operation and option B does not change the category threshold.

Study Guide reference:Application Development — Custom Log Settings, category thresholds, DEBUG severity, in-memory logging, and Storefront Toolkit Request Log.

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

Among these choices, aproduct custom attributeprovides the cleanest and most maintainable data-driven solution. B2C Commerce allows the Product system object to be extended with custom attributes, enabling merchandising metadata such as a permitted region, market code, or eligibility classification to live with the product data rather than being hard-coded in controller logic.

The storefront or search-layer implementation can then evaluate that attribute against the shopper ' s applicable regional context and filter products accordingly. This approach scales better than embedding specific product IDs or regional rules directly into scripts.

Creating an entire catalog for every region may be justified when each market has substantially different assortments, categories, navigation, prices, or merchandising operations, but it is excessive for a requirement centered on a specific product ' s regional eligibility. Option C also places business data in code, making merchant maintenance and expansion harder.

The custom attribute should be modeled with an appropriate data type and, where needed, indexed if search-result filtering is involved.

Study Guide reference:Data Management Using Business Manager Usage — Product system object extensions, custom attributes, merchandising metadata, search filtering, and regional product eligibility.

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

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.

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