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

The B2C Commerce Service Framework provides arate limiterspecifically for controlling the maximum number of outbound service calls permitted during a defined time interval. This configuration belongs to theService Profileassociated with the service. The profile exposes values equivalent to the maximum permitted calls and the rate-limit interval in milliseconds.

Salesforce documents that the Service Profile controls timeout, rate-limit, and circuit-breaker behavior. The rate limiter is evaluated before every service invocation. If the configured maximum number of calls has already been reached within the interval, B2C Commerce prevents another remote request and returns service-unavailable behavior instead.

This mechanism counts service invocations irrespective of whether the previous remote calls succeeded or failed, which directly matches the requirement to restrict overall calls per second. A circuit breaker is different: it reacts specifically to accumulated failures. Option C incorrectly treats this as a general platform quota, while option A refers to configuration that is not the standard Service Framework mechanism.

Study Guide reference:Application Development — Service Framework, Service Profiles, rate limiting, circuit breakers, and external integration governance.

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

Therootcategory is the parent of all custom logger categories, includingproducts. Therefore, the WARN threshold configured at root applies to theproductslogger unless a more specific category configuration overrides it.

B2C Commerce logging severity is hierarchical: enabling a particular level also enables all higher-severity levels. Salesforce gives the explicit example that when WARN is enabled for a category,WARN and ERRORmessages are logged for that category and its subcategories. Root configuration likewise applies to all custom categories.

Consequently,log.warn()andlog.error()both qualify for persistence.log.info()does not because INFO is below WARN in the severity hierarchy. The exact text placed inside the INFO call doesn ' t matter; logging eligibility is determined by the API method/severity, not whether the message string contains the word " warn. "

This hierarchical configuration allows administrators to maintain a conservative production logging threshold while selectively enabling more detailed logging for particular categories when troubleshooting.

Study Guide reference:Application Development —dw.system.Logger, log categories, root logger hierarchy, severity thresholds, and custom logging configuration.

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

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.

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

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.

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

The two-argumentLogger.getLogger()method accepts afile-name prefixfollowed by alogging category. Here,loggerFileis the requested custom file-name prefix andcategory1.euis the category.

Salesforce ' s Script API defines the signature asLogger.getLogger(fileNamePrefix, category). Custom log files created through this mechanism are stored as custom logs, so their actual generated filename begins with thecustom-naming convention followed by the developer-supplied prefix. Salesforce also states that repeated calls using the same file-name prefix use the same associated custom logger/file.

The WARN message passes filtering becausecategory1.euinherits its logging threshold from parent categorycategory1, which is enabled at WARN. B2C Commerce custom logging is hierarchical, so parent-category rules apply to descendant categories unless overridden.

Therefore, the WARN entry is written to the custom log beginning withcustom-loggerFile.

Study Guide reference:Application Development — Logger file prefixes, custom log files, category inheritance, WARN filtering, andLogger.getLogger().

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

A storefront filter is represented in B2C Commerce product search as asearch refinement. Therefore, after creating or selecting an appropriate product attribute, the administrator must create a Search Refinement Definition that associates the refinement with that attribute and the appropriate category/search context.

Merely marking an attribute searchable is not equivalent to defining it as a refinement. " Searchable " primarily determines participation in keyword-search behavior, while a refinement definition instructs the search system to expose attribute values as shopper-selectable filters. The attribute must also contain values on relevant products and be represented in the search index for the refinement to produce useful values.

Changingproductsearchrefinebar.ismlis not normally required. SFRA retrieves available refinements dynamically from the Product Search Model, so configured refinements can appear through the standard refinement components without hard-coding each attribute into the template.

Salesforce confirms that custom Product attributes can be created forsite search, search refinements, or sorting rules, demonstrating that refinement configuration is a distinct use of the attribute.

Study Guide reference:Data Management Using Business Manager Usage — Search Refinement Definitions, custom Product attributes, search indexing, and storefront product filtering.

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

Remote includes have anindependent caching policyfrom the page in which they are embedded. This allows a predominantly cacheable page to contain a dynamic section that must be evaluated separately for each request.

Salesforce explicitly describes this architecture: a surrounding page can remain fully cached while a remote include issues another request whose response is not cached. The web tier inserts the dynamically generated include into the cached page frame. The < isinclude > documentation similarly states that the remotely included URL can have a different caching policy and gives the specific example of embedding an uncached dynamic HTML snippet into an otherwise completely cached page.

Therefore, the presence of an uncached remote include doesnotinvalidate caching for the parent response. This is precisely one of the principal reasons to use remote includes for shopper-specific information such as login state, minicart information, rapidly changing inventory data, or other fragments with a shorter cache lifecycle.

Option C has no basis in the cache model; caching is not conditioned simply on whether the shopper is returning.

Study Guide reference:Application Development — page caching, remote includes, independent cache policies, Web Adapter processing, and dynamic storefront fragments.

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

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.

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

The configuration currently authorizes only HTTPGET, which is a read operation. Adding products to a basket changes server-side state and is performed through an OCAPI operation that usesPOST. The client ' s permitted-method list must therefore includepost.

OCAPI authorization is resource- and method-specific. Even thoughwrite_attributes: " (**) " permits all writable attributes for an otherwise authorized write request, it doesnotauthorize a missing HTTP method. The HTTP method itself must be explicitly listed in the resource configuration. Salesforce ' s OCAPI documentation identifies POST as a method used to create resources or execute actions that modify server state.

Option B changes the attribute selector but still leaves the client without POST permission, so the request remains unauthorized. Option C adds OPTIONS, which is associated with HTTP capability/CORS behavior and does not perform the basket modification.

Thus:

" methods " :[ " get " , " post " ]

allows the existing read access while also authorizing the required write operation.

Study Guide reference:Application Development — OCAPI configuration, resource permissions, HTTP methods, basket APIs, and read/write authorization.

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

Among the supplied choices, B is the only approach consistent with robust B2C Commerce integration design: the application must inspect service results, preserve useful diagnostic information, and implement controlled error behavior rather than blindly proceeding.

However, " log all responses " must be interpreted according to Salesforce ' s secure logging practices. Raw responses mustnotbe persisted indiscriminately when they contain passwords, access tokens, personal information, payment data, or other sensitive content. B2C Commerce ' s Service Framework provides logging controls such as response/request filtering specifically so that sensitive information can be removed before it reaches diagnostic logs.

Ignoring a failed API response, as in A, can produce corrupt application state or misleading storefront behavior. Option C is equally problematic because silently converting failures into successful responses prevents calling code and shoppers from receiving appropriate failure handling.

A correct production implementation examines the Service Framework result, logs sanitized diagnostic context where appropriate, implements fallback behavior when the business process allows it, and returns a controlled application response.

Study Guide reference:Application Development — Service Framework, external API integrations, service result handling, secure logging, exception management, and graceful failure behavior.

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