If a service is being classified as unavailable because legitimate responses are taking longer than the configured timeout, increasing the service timeout can reduce timeout-generated failures. B2C Commerce service profiles define the number of milliseconds the platform waits for a service response before treating the operation as an error.

Salesforce ' s Service Framework documentation states that the configured timeout is used for connection and socket operations. If no response arrives within the configured interval, the service operation fails. Thedw.svc.ResultAPI further identifiesTIMEOUTas an explicit reason forSERVICE_UNAVAILABLE.

Option B changes error-propagation behavior;throwOnErrordetermines how a failed result is surfaced to application code, but it does not make the external service more available. Option C can improve exception handling and prevent uncaught application failures, but wrapping the call intry/catchdoes not alter Service Framework availability metrics or prevent timeouts.

The timeout should still be increased cautiously. Excessive timeouts can worsen shopper-facing latency and interact poorly with circuit-breaker behavior.

Study Guide reference:Application Development — Service Framework, service profiles, connection/socket timeouts, Service Status monitoring, and service availability.

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

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.

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

PageMgr.serializePage()is specifically designed to serialize a Page Designer page into JSON. Salesforce ' sdw.experience.PageMgrAPI distinguishesrenderingfromserialization:renderPage()generates page markup, whereasserializePage()traverses the Page Designer page and its visible components and produces the page representation as a JSON string.

The serialized result can contain the page ID, type ID, content data, custom serialization output, regions, nested components, and component data. This makes it appropriate for applications that need a machine-readable description of the Page Designer composition rather than server-rendered HTML.

Option B first produces rendered markup and then stringifies that value, which does not transform the Page Designer structure into the supported page JSON representation. Option C simply renders the page as markup.

The exact current API exposes overloads that accept a page ID plus parameter information, including parameter strings and aspect-attribute maps where applicable. The key examination distinction is thatserialization usesserializePage, while HTML/markup generation usesrenderPage.

Study Guide reference:Application Development — Page Designer,dw.experience.PageMgr,serializePage(), JSON serialization, andrenderPage().

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

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.

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

CSRF validation must occurwhen the state-changing request is submitted, before protected business logic executes. In SFRA this is implemented as middleware in the controller ' s POST route, using the appropriate CSRF middleware—validateRequestfor standard submissions orvalidateAjaxRequestfor AJAX-based requests.

Salesforce ' s SFRA Forms documentation specifically states that CSRF protection is supplied as middleware and demonstrates CSRF checks as middleware steps. The underlyingdw.web.CSRFProtection.validateRequest()API verifies that the request contains the system-generated token and that the token has not expired.

Generating the token in the template only establishes the client-side value; it does not provide security unless the receiving POST endpoint validates it. Placing validation only in the form-display route would validate the wrong request. Performing validation in a persistence model is also too late because request security should be enforced before mutation logic is invoked.

Study Guide reference:Application Development — CSRF protection, SFRA middleware, POST routes,validateRequest,validateAjaxRequest, and secure form processing.

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

Template decorators provide a standard mechanism for extracting shared page structure—such as headers, navigation, wrappers, footers, and common layout markup—into reusable ISML templates. A child template uses < isdecorate > to select a decorator, and the decorator uses < isreplace/ > to identify the location where the child ' s page-specific content is inserted.

Salesforce describes < isdecorate > as the ISML mechanism for decorating enclosed content with another template and defines < isreplace/ > as the placeholder where the decorated content is inserted. A typical use case is wrapping different page bodies with a common header and footer.

This architecture directly reduces repeated layout code and improves maintainability because a shared element can be changed in the decorator rather than edited across many individual pages.

Option B misuses < isscript > ; script tags are intended for executable template scripting, not reusable page composition. Option C doesn ' t represent the standard decorator-based technique requested by the question and can encourage fragmented template composition when a reusable layout is the underlying requirement.

Study Guide reference:Application Development — ISML templates, template decorators, < isdecorate > , < isreplace > , reusable presentation structure, and maintainable storefront design.

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

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.

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

< isdecorate > is the correct ISML construct for applying a reusable page layout to multiple templates. A decorator template can contain the common page shell, header, navigation, footer, scripts, and structural markup, while the individual child page contains only page-specific content.

Salesforce explicitly identifies a common header-and-footer layout as atypical use casefor < isdecorate > . The decorator template contains < isreplace/ > , which marks the position where the child template ' s enclosed content is inserted.

Option A is therefore not the tag normally placed around each page ' s content; < isreplace/ > belongs inside the decorator template itself. Option C can insert another template fragment, but using repeated includes for headers and footers does not provide the same centralized page-layout structure and composition semantics.

Decorator-based design improves maintainability because common markup is maintained once. If the header or footer changes, developers update the decorator rather than making the same structural changes across every individual storefront page.

Study Guide reference:Application Development — ISML decorators, < isdecorate > , < isreplace > , template reuse, common layouts, and storefront maintainability.

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

B2C Commerce custom attributes are defined through the platform ' smetadata system, not dynamically declared by application JavaScript. Therefore, the first step is to create the required attribute definition in Business Manager on the appropriate extensible system object or custom-object type.

Salesforce documents the process under Administration > Site Development > System Object Types or Custom Object Types. The developer selects the target object, opens Attribute Definitions, clicks New, and defines the attribute ID, display name, and data type.

Once the attribute exists, it can be assigned to an attribute group where required for Business Manager visibility, populated through Business Manager or integrations, and accessed through the object ' scustomproperty in application code.

Option B is incorrect because source code cannot create an undeclared persistent custom attribute merely by referencing a property name. Option C also comes later because application logic needs the metadata definition to exist before reliably reading or writing the value.

The type and characteristics of the attribute should be designed carefully because changing an existing attribute ' s type can cause stored values to be lost.

Study Guide reference:Data Management Using Business Manager Usage — System Object Types, Custom Object Types, Attribute Definitions, attribute groups, and custom metadata.

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

TheStorefront Toolkitis the appropriate starting point because this is a storefront rendering and data-presentation defect rather than a reporting or performance-analysis problem. The toolkit provides developer-facing information about the storefront page and helps identify the templates and application components involved in generating what the shopper sees. Salesforce specifically documents the Storefront Toolkit as a mechanism for identifying which portions of a storefront page are associated with particular templates.

With the wrong customer ' s address appearing on the Account Addresses page, the developer should first determine which template, controller route, remote include, or cached fragment is producing the displayed information. That narrows the investigation to the responsible application layer before examining the underlying customer/session logic.

The Reports and Dashboards module is intended for business and operational reporting and would not normally expose a template-level rendering defect. Pipeline Profiler is primarily concerned with execution and performance profiling, so it is more suitable when diagnosing slow pipelines or execution bottlenecks rather than incorrect shopper-specific content.

Study Guide reference:Work With a B2C Site — Storefront Toolkit, storefront troubleshooting, template identification, and diagnosing rendered customer-specific content.

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