Free Practice Questions for Salesforce Comm-Dev-101 Exam

The cartridge ' s root-levelpackage.jsonuses the " hooks " property to point to the hook registration file. In the standard SFRA cartridge structure, the hook-registration file resides under:

cartridge/scripts/hooks.json

Therefore, the correct relative path is:

{ " hooks " : " ./cartridge/scripts/hooks.json " }

Salesforce ' s SFRA hook documentation confirms thatpackage.jsonuses thehookskeyword to identify the hook file and that the referenced hook file then maps extension-point names to script implementations.

Option B omits thecartridgeportion of the normal directory structure, so it points to the wrong location. Option C uses JavaScript-object syntax rather than valid JSON because thehooksproperty name is unquoted. Apackage.jsonfile must contain valid JSON.

Thehooks.jsonfile contains entries with the extension-pointnameand correspondingscriptmodule. Once the cartridge is deployed and active on the appropriate cartridge path, registered hooks can participate in storefront or platform extension points.

Study Guide reference:Application Development — hook registration,package.json,hooks.json, cartridge structure, CommonJS hook modules, and extension points.

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

ASynonym Dictionarygroups terms that should be treated as equivalent during storefront search. If several words are configured in the same synonym group, searching for any member expands the query to the other terms, producing the same combined result set.

Salesforce ' s official Synonyms documentation uses almost exactly this example:bag,purse, andpocketbookare configured together, and searching for any one of them generates a query equivalent tobag OR purse OR pocketbook. The result set therefore contains matches for all configured synonyms.

Addingtoteto that group extends the same behavior. Hypernyms and hyponyms represent hierarchical semantic relationships rather than strict or near-equivalence. For example, a broad term can be a hypernym of more specific concepts, and a specific term can be a hyponym of a broader term. Those relationships are useful for search expansion with different semantic direction, but they are not the correct mechanism when every term should produce the same results.

Study Guide reference:Data Management Using Business Manager Usage — Search Dictionaries, Synonyms, query expansion, Hypernyms/Hyponyms, and storefront search relevance.

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

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.

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

B2C Commerce Shipping Methods supportproduct exclusions, allowing merchants to prevent a shipping method from being offered when the shipment contains products that cannot be delivered using that method. Business Manager provides product-blocklist and allowlist configuration in the Shipping Method definition.

Salesforce explicitly documents that administrators can exclude products that cannot be shipped through a particular shipping method. The same configuration also supportsaddress exclusions, which makes option B false. Furthermore, Salesforce provides a Product Surcharge Cost section where surcharge shipping costs can be defined for specific product groups, making option C false.

Product exclusion rules can use qualifiers, operators, values, and catalog context. If at least one product in the shipment is excluded and no applicable exception restores eligibility, the shipping method is not presented as an available choice. This capability keeps shipping restrictions declarative and merchant-manageable instead of requiring custom checkout code.

The shipping configuration also supports customer groups, shipping cost tables, fixed product costs, product surcharges, and address inclusion/exclusion rules.

Study Guide reference:Data Management Using Business Manager Usage — Shipping Methods, product exclusions, address exclusions, product surcharges, and Business Manager shipping configuration.

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

No additional action is required when the product slot is already configured, active, scheduled, assigned products, and its rendering template iterates throughslotcontent.content.

Salesforce documents thatslotcontentis an implicit object available inside an ISML template used as a slot rendering template. Itscontentproperty maps toSlotContent.getContent()and returns the collection produced by the evaluated slot configuration. Salesforce specifically demonstrates product slots by iterating over this collection to render returned products.

Therefore, < isloop > is fully valid in a content-slot rendering template. Option C incorrectly claims that loops are prohibited.

A recommender is also optional, not mandatory. B2C Commerce can populate product slots from explicitly selected products, recommendations, or other supported merchandising configuration. If products have already been configured directly, a recommender does not have to be introduced.

The rendering template simply receives the slot execution result and iterates its returned product collection.

Study Guide reference:Data Management Using Business Manager Usage — Content Slots,slotcontent, Product slot content types, rendering templates, < isloop > , and merchant slot configuration.

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

The required workflow creates a new shipment for a gift item and then modifies shipment information associated with the basket. The OCAPI basket shipment hooks corresponding to those two operations aredw.ocapi.shop.basket.shipment.beforePOSTanddw.ocapi.shop.basket.shipment.beforePATCH.

Salesforce ' s OCAPI hook documentation definesshipment.beforePOSTas the extension point executed before creation of a shipment andshipment.beforePATCHas the extension point executed before modification of an existing shipment. Those operations align directly with the described solution: establish the separate shipment and then apply the necessary changes before final basket validation.

The alternatives involvingbeforeDELETEorafterDELETEare inconsistent with the scenario because no shipment needs to be deleted. The requirement is to separate a gift product into its own shipment, not remove a shipment from the basket.

The concludingvalidateBaskethook provides the final validation stage after the basket/shipment changes have been processed, allowing custom logic to ensure that the resulting basket remains valid.

Study Guide reference:Application Development — OCAPI Shop API hooks, basket extension points, shipment creation and modification, and basket validation.

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

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.

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

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.

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

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.

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

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.

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