TheFATALlogging level is the special severity level that thedw.system.LogAPI identifies as always enabled under normal logging operation. It represents severe conditions for which developers should always be able to emit diagnostic information.

Salesforce ' sdw.system.LogAPI documentation explicitly states thatFatal log messages are always enabledand can optionally be distributed through email notification configuration. INFO, by contrast, depends on the configured logging threshold and target settings. ERROR also participates in the configurable category hierarchy and does not carry the same API-level guarantee expressed for FATAL.

B2C Commerce custom logging uses a log4j-style hierarchy. Categories inherit logging behavior from parent categories unless a more specific rule applies. For example, an INFO threshold permits INFO, WARN, ERROR, and FATAL. A WARN threshold permits WARN, ERROR, and FATAL. Salesforce also supports configuring log targets separately from filters.

FATAL should be reserved for genuinely severe application conditions rather than routine diagnostic output, because excessive high-severity logging obscures operational incidents and reduces the diagnostic value of the logs.

Study Guide reference:Application Development —dw.system.Log, logging severity, custom log categories, FATAL logging, and production diagnostics.

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

Washing instructions are product-specific business data, so the value should be modeled as acustom attribute on the Product system object. Because the displayed instructions can differ by storefront locale, the custom attribute should be configured as localizable.

Salesforce ' s B2C Commerce metadata system allows custom attributes to be created on extensible system objects such as Product. Localizable custom attribute definitions count against the Product object ' s supported custom-attribute quota, confirming that Product attributes can participate in localized data modeling.

Option A is inappropriate because resource bundles are designed for application UI strings such as labels, messages, and validation text. They are not a scalable source for product-specific PIM data such as care instructions. Option C is also incorrect because localization is configured on eligible attributes, not by marking the entire Product system object " localizable. "

A PIM integration can populate locale-specific values of the washing-instructions attribute, after which the PDP retrieves the appropriate value under the active storefront locale.

Study Guide reference:Data Management Using Business Manager Usage — Product custom attributes, localizable product data, PIM integration, system object metadata, and localized PDP content.

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

Server-side script variables do not persist between independent request executions. B2C Commerce therefore provides theSessionobject as the appropriate request-session mechanism for maintaining shopper-specific state across calls.

Salesforce specifically identifies the Session API as providing access to thecurrent customer, whether that customer isauthenticated, session custom attributes, andcustom privacy attributes. These capabilities map directly to every requirement in the question.

A client-side cookie is inappropriate for reproducing server-maintained authentication and customer state. It would also expose application-controlled values to client modification and duplicate information already securely managed by the Commerce session. An SFRA controller does not automatically preserve its own JavaScript variables across requests; each request executes within a separate script context.

Session data should nevertheless remain lightweight. Long-lived or business-critical information that must survive beyond the shopper ' s browser session belongs in persistent business objects rather than session attributes. Privacy attributes have specific lifecycle semantics and are particularly appropriate for tracking consent and related shopper preferences during the active session.

Study Guide reference:Application Development — Session API, shopper state, authentication state, privacy attributes, server-side JavaScript execution lifecycle, and scalable state management.

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

In SFRA ' s MVC-style architecture, a controller owns the HTTP request/response workflow. Consequently, generating aJSON HTTP responseis an appropriate controller responsibility. The SFRA response API exposesres.json(data)specifically for this purpose and Salesforce notes that it is useful for AJAX service endpoints called by client-side code.

The other two choices describe responsibilities that belong more appropriately to the model/ViewModel layer. Salesforce explains that SFRA models obtain data from B2C Commerce Script API objects and convert those objects intopure serializable JavaScript objectssuitable for views. Models also encapsulate storefront-oriented business logic. Controllers request or coordinate the required data and pass it through the model layer rather than becoming the primary object-transformation layer themselves.

This separation improves testability and maintainability. Controllers stay focused on routing, request validation, response selection, redirects, rendering, and JSON output, while models isolate the transformation of Commerce platform objects into view-friendly structures.

Study Guide reference:Application Development — SFRA MVC architecture, controllers, ViewModels,res.json(), Script API objects, and separation of concerns.

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

Ifdw.order.calculateTaxis already registered byapp_storefront_base, the custom controller doesnotneed to register the hook again. It only needs to invoke the existing extension point throughdw.system.HookMgr.callHook().

Salesforce ' s SFRA hook documentation distinguishes registration from invocation: the implementing cartridge registers the extension point through its hook configuration, while application code calls registered hooks through HookMgr.

More importantly, the currentapp_storefront_basecalculation implementation demonstrates the exact call:

HookMgr.callHook( ' dw.order.calculateTax ' , ' calculateTax ' , basket);

Adding another entry tohooks.jsonorpackage.jsonis only required when a cartridge is providing/registering a hook implementation, not merely consuming an implementation that is already registered.

Study Guide reference:Application Development —dw.system.HookMgr,callHook(),dw.order.calculateTax, hook registration versus invocation, and SFRA basket calculation.

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

Theurlform of < isinclude > performs aremote include. In this example,URLUtils.url( ' Account-Header ' , ' mobile ' , true)constructs a URL for theAccount-Headerendpoint and supplies that URL to < isinclude > . B2C Commerce therefore makes a separate request to the generated endpoint and inserts the resulting response into the surrounding page.

Salesforce distinguishes this behavior from a local template include. A local include uses thetemplateattribute and incorporates another ISML template within the current rendering context. By contrast, an < isinclude > that specifiesurlis explicitly classified as a remote include and can execute another controller or pipeline endpoint.

Option B is therefore incorrect because the code does not use the local-template syntax. Option C is also incorrect:URLUtils.url()does construct a URL, but placing that URL in theurlattribute of < isinclude > does not render an anchor or navigational link. It causes the endpoint ' s output to be included in the current response.

Study Guide reference:Application Development — ISML includes, remote includes,URLUtils, controller endpoints, and composable storefront rendering.

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

Reusable cross-route request logic is exactly whatSFRA middleware functionsare intended to provide. A middleware function receivesreq,res, andnext, performs the required check, and can either continue the chain, redirect the shopper, modify response state, or otherwise control request processing.

Salesforce describes each SFRA route as a middleware chain whose individual steps use the standard(req, res, next)signature. Reusable functions can be inserted into multiple routes, allowing authentication checks, consent validation, feature eligibility, parameter validation, and similar concerns to be implemented once and consistently reused.

Option B technically repeats functionality by appending a separate function to every route, but it does not provide the clean reusable abstraction requested by the scenario. Option C addresses cartridge inheritance rather than reusable route-level validation.module.superModuleis used when extending a module from another cartridge; it is not a substitute for a middleware function shared among several routes.

Centralizing the checks in middleware also makes later changes safer: the validation logic is updated in one place rather than independently across numerous controller endpoints.

Study Guide reference:Application Development — SFRA routing, middleware chains, reusable middleware,req/res/next, redirects, and controller design best practices.

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

TheOrderable Products Onlysearch setting filters unorderable merchandise from storefront search results. Salesforce ' s search-pipeline documentation defines the behavior directly: the setting excludes unorderable products—identified in the documented rule as products whose inventory record hasATS = 0—from search results.

The setting operates on search-result eligibility; it does not generally make the product detail route cease to exist. Therefore, option C incorrectly converts a search filtering preference into PDP routing behavior.

Option B is also incorrect as a general statement because backorderable products can still be considered orderable even when immediate physical stock is unavailable, depending on their inventory configuration and availability model. The important concept isorderability, not simply whether inventory is being fulfilled immediately from on-hand stock.

This setting is commonly used when merchants do not want search pages populated with merchandise shoppers cannot purchase. Because orderability participates in indexed search behavior, administrators should also ensure that the relevant product search indexes are current after inventory/search configuration changes.

Study Guide reference:Data Management Using Business Manager Usage — product search preferences, Orderable Products Only, ATS, inventory availability, and storefront search-result filtering.

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

The rendering template is already using the standard B2C Commerce product-slot model correctly. Within a slot rendering template,slotcontentis an implicit object representing the evaluated slot configuration. For product-type slot content,slotcontent.contentexposes the collection of products returned by the slot execution.

Salesforce ' s < isslot > documentation explicitly demonstrates iterating overslotcontent.contentwhen the slot ' s content type is Product. It also identifiesslotcontentas an implicit object available specifically to slot rendering templates and maps itscontentproperty toSlotContent.getContent().

Therefore, < isloop > is not only allowed but is the normal mechanism for rendering several products returned by a slot. A recommender is unnecessary because the scenario states that products have already been directly configured in an active and correctly scheduled slot. Recommender-based slot content is another valid content-selection method, but it is not mandatory for a manually configured product slot.

Study Guide reference:Data Management Using Business Manager Usage — Content Slots, SlotContent, product slot rendering, < isloop > , scheduling, and slot templates.

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

When an SFRA controller inherits an existing route and usesserver.append()to add another middleware function, the appended function is addedafter the existing middleware chain. The developer does not need to repeat all of the middleware that already belongs to the base route.

Salesforce states directly thatserver.appendcauses a route to execute both theoriginal middleware chain and any additional appended steps. Therefore, provided the custom controller correctly extends the base server module and callsnext(), the original route executes first and the appended custom code executes afterward.

Omitting the existing middleware declarations from the appended function does not itself generate a parameter-mismatch runtime error. The inherited route retains its consent, cache, authentication, metadata, or other middleware steps. Option C reverses the execution sequence expected from an append operation.

Study Guide reference:Application Development — SFRAserver.append(), route inheritance, middleware chains,module.superModule, and controller extension.

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