Comm-Dev-101 Exam Dumps - Salesforce Developers Questions and Answers

A custom object is the most appropriate persistent data structure because the requirement applies toboth registered and guest shoppers. A Profile-based solution cannot satisfy the requirement reliably because anonymous/guest customers do not have a persistent registered customer profile. Storing customer email lists directly on Product records would also create an inappropriate product-to-shopper coupling and potentially large mutable collections on product system objects.

B2C Commerce custom objects are intended to extend the persistent commerce data model for application-specific requirements. Developers can define custom object types with custom attributes, including multi-valuedSet of Stringattributes, and choose organization or site storage scope.

A custom back-in-stock object can therefore persist the shopper ' s email address plus one or more interested SKUs independently of authentication status. Subsequent job or inventory-update logic can identify subscriptions when inventory becomes available and trigger the notification process.

This design also keeps notification-subscription data separate from core customer and product objects, reducing unintended effects on standard platform data models and supporting anonymous shoppers cleanly.

Study Guide reference:Data Management Using Business Manager Usage — custom object types, custom attributes, persistent business data, guest shoppers, and application-specific data modeling.

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

Custom storefront scripts arecode artifacts, not Business Manager metadata objects. Consequently, among the supplied options, B is the technically correct first step: create or define the required JavaScript/CommonJS script module within the project code structure.

Salesforce documents that B2C Commerce script modules are.js,.ds, or.jsonfiles and are normally stored in cartridges, commonly undercartridge/scripts. Modules expose public functionality throughexportsand are loaded withrequire(). Controllers and other server-side components can then import and invoke that reusable module.

Business Manager does not provide a general mechanism for creating arbitrary SFRA application scripts. Business Manager manages configuration, metadata, jobs, services, catalogs, and related platform data; deployable application logic belongs in cartridges/code versions.

Option C is less precise because the script/module itself must first be established in the codebase before its exported behavior can be consumed.

Study Guide reference:Application Development — CommonJS modules,cartridge/scripts, JavaScript modules,require(), exports, and cartridge-based application code.

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

B2C Commerce imposes a daily size quota on custom logs to prevent unlimited logging from consuming storage or degrading instance performance. Once the applicable custom-log size limit is reached, additional custom logging issuspended until the next logging dayrather than rolling immediately to another unlimited file.

Current Salesforce documentation states that each application server can write up to the defined daily amount into the custom debug, info, fatal, error, and warn logs, and that logging is suspended until the next day once the limit is reached. The logging day is based on GMT.

Option A describes normal archival/retention handling rather than quota behavior. Existing log files can later be compressed and moved according to retention policy, but reaching the daily file-size quota doesn ' t simply bypass the quota by opening another unrestricted file. Option B is also incorrect because B2C Commerce doesn ' t delete the current log merely to continue writing.

Developers should therefore avoid excessive diagnostic logging, particularly in frequently executed storefront code, and choose appropriate log levels and categories.

Study Guide reference:Application Development — custom logging quotas, log-file management, Business Manager log settings, WebDAV logs, and production diagnostics.

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

SFRA ' s response object provides thesetViewData()method specifically for adding data to the view-data object that will be available during rendering. Therefore, option A follows the supported controller pattern: callres.setViewData()with the additional object, render the template, and then invokenext()to continue the middleware chain.

Salesforce ' s SFRA documentation explains thatsetViewData(data)adds or merges data into the response ' s view-data object. This behavior is particularly important for an appended route because earlier middleware may already have established view data.setViewData()allows the appended function to add its contribution without replacing the response object ' s internal handling.

Directly assigningres.viewData, as shown in option B, bypasses the supported response API and is not the documented SFRA mechanism. Option C is also invalid because route appending expects a middleware function; data cannot be supplied by chaining an object through.append()after rendering.

This pattern is central to cartridge extensibility because multiple middleware functions can progressively enrich a response while preserving previously established data and route behavior.

Study Guide reference:Application Development — SFRA controllers, response objects, middleware chains,setViewData(), and template rendering.

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

initServiceClientis the SOAP-specific callback among the listed choices. The B2C Commerce Service Framework uses callback functions to construct requests, execute or mock service interactions, and interpret responses. For SOAP integrations, the framework requires initialization of the underlying SOAP service client so that the generated service objects and SOAP-specific behavior can be prepared before invocation.

Salesforce ' sServiceCallbackAPI documentation specifically describesinitServiceClientas a method that normally does not need to be implemented except for SOAP services. By contrast,createRequestis broadly applicable because HTTP, FTP, SOAP, and other service implementations can require request construction. Mocking is also not inherently SOAP-specific; a service can be placed into mock mode regardless of whether the real endpoint uses SOAP or another protocol.

The distinction is therefore architectural rather than merely syntactic. SOAP requires a generated or initialized service client capable of working with SOAP operations and associated service definitions, whereas ordinary HTTP integrations commonly operate directly through URL, request body, headers, and response parsing callbacks.

Study Guide reference:Application Development — Service Framework,dw.svc, service callbacks, SOAP service integration, and external-system connectivity.

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

Content slots are designed to support merchandising configurations that can vary according to customer groups and other scheduling or targeting criteria. B2C Commerce provides system customer groups includingRegisteredandUnregistered, which directly map to the two audiences described in the requirement. The merchant can therefore configure the homepage slot differently for those groups without embedding authentication logic inside content assets.

Salesforce ' s content-slot documentation describes slot configurations as merchant-controlled content assignments with scheduling and targeting behavior. Its personalized-merchandising guidance also explains that slot configurations can be selected according to customer-group membership. Salesforce defines Registered and Unregistered as built-in customer groups available for this type of targeting.

A content asset is primarily the content itself; it is not the correct place to implement audience-selection rules. Writing custom conditional code into the asset would also reduce merchant control and create unnecessary technical maintenance.

Using slot configuration keeps the content, targeting rule, and storefront rendering responsibilities appropriately separated and lets merchandisers change the experience through Business Manager.

Study Guide reference:Data Management Using Business Manager Usage — content slots, customer groups, personalized merchandising, and storefront content targeting.

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

The intended activity is product-level merchandising data, so the first requirement is acustom attribute on the Product system object. Values such as tennis, jogging, and basketball can then be populated for the applicable products. The second requirement is to expose that indexed attribute as aSearch Refinement Definitionfor the categories where shoppers should be able to use it.

Salesforce ' s search-refinement model supports attribute-based refinements that restrict product-search results according to values stored on products. A search refinement definition identifies the attribute that should participate in refinement behavior. Salesforce also provides System Object Type configuration for defining custom attributes on extensible system objects such as Product.

There is no need for a separate “ProductRefinement” custom attribute type as proposed in option B. Option C ' sviewtypeis unrelated to defining searchable product characteristics; presentation modes do not create catalog data or refinement dimensions.

After the attribute and refinement are configured, the product data must contain appropriate values and the relevant search index must include them.

Study Guide reference:Data Management Using Business Manager Usage — Product custom attributes, catalog metadata, search refinements, and search indexing.

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

When an existing SFRA route already performs the required core processing and the developer only needs to add functionality after that processing,server.append()is the appropriate route-extension mechanism.

Salesforce documents thatserver.appendadds middleware after an existing route ' s middleware chain. The original middleware executes first, followed by the appended middleware. A common documented use case is adding or modifying properties in the route ' sviewDataobject without duplicating the existing controller implementation.

server.extend()is important when a custom controller inherits routes frommodule.superModule, but it is not by itself the operation that adds a new step to a specific route. Option B replaces more behavior than necessary and increases coupling to the underlying implementation.

With an appended function, the developer can retrieve ViewData usingres.getViewData(), add the required properties, update it throughres.setViewData(), and callnext().

The technique preserves the base route and minimizes custom code, supporting upgrade-safe SFRA development.

Study Guide reference:Application Development — SFRA controller customization,server.append(), middleware chains, ViewData,module.superModule, and route extensibility.

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

A cartridge that registers B2C Commerce hooks traditionally uses apackage.jsonfile at the cartridge root and points its " hooks " property to the hook registration file located under the cartridge ' s scripts directory. The correct relative path is therefore:

" ./cartridge/scripts/hooks.json "

Salesforce ' s SFRA documentation describes the hook-registration pattern as a root-levelpackage.jsonaccompanied byhooks.jsonundercartridge/scripts. The cartridge containing the implementation must also participate in the relevant site ' s cartridge configuration for the extension to be available.

Option B is not valid JSON syntax because JSON property names and string values must be quoted. Option C uses the wrong relative location;scriptsis below the cartridge directory, not directly below the package root.

Thehooks.jsonfile then maps extension-point names to implementing script modules. Runtime code can invoke those extension points through mechanisms such asHookMgr.callHook(), while the registration metadata tells B2C Commerce which implementation is associated with each hook.

Study Guide reference:Application Development — hooks,package.json,hooks.json, extension-point registration, cartridge structure, and extensibility architecture.

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

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.

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