Free Salesforce Comm-Dev-101 Practice Exam with Questions & Answers | Set: 2

dw.svc.LocalServiceRegistry.createService()is the supported API for creating and configuring a Service Framework service instance from a service definition established in Business Manager.

Salesforce ' s Script API states thatLocalServiceRegistryis responsible for managing Service instances and documents the method:

createService(serviceID, configObj)

The method takes the configured service ID and a callback/configuration object, then returns the corresponding Service instance.

The callback object can define functions such ascreateRequest,parseResponse,filterLogMessage,mockCall, or other service-type-specific behavior. Application code subsequently invokes.call()on the returned service.

There is nodw.svc.LocalServiceInstanceclass providing the method in option B. Likewise,getDefaultService()is not the standard LocalServiceRegistry creation method represented by the current Service Framework API.

The LocalServiceRegistry design keeps the service object local to the script invocation while relying on Business Manager for service, profile, and credential configuration. This separates deployable integration code from environment-specific URLs, authentication credentials, timeout values, and operational policies.

Study Guide reference:Application Development —dw.svc.LocalServiceRegistry,createService(), Service Framework, callbacks, service profiles, and remote integrations.

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

A Page Designer Page Type consists of a metadata definition plus a corresponding JavaScript implementation. The rendering behavior itself belongs in the page-typeJavaScript file, which must expose arender()function.

Salesforce states that the script file must have the same base name and location as the Page Designer meta-definition file, using.jsrather than.json. The script ' srenderfunction receives aPageScriptContextand must return the resulting markup as a string. It commonly renders an ISML template usingdw.util.Template, and the template can in turn render the page ' s regions.

The metadata JSON describes the Page Type ' s declarative configuration—such as its attributes and regions—but does not implement rendering through a " render " property. A conventional SFRA controller route can invokePageMgr.renderPage()to initiate rendering, but that controller does not define the actual Page Type rendering logic.

This separation allows Page Designer to manage page composition while the JavaScript implementation controls the output representation.

Study Guide reference:Application Development — Page Designer Page Types, page metadata,render()functions,PageScriptContext, and Page Designer rendering.

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

TheMerchant Tools > Content > Import & Exportmodule is specifically associated with content libraries, folders, andcontent assets. Salesforce documents that content and content-library data use thelibrary.xsdimport/export schema and are handled from this Business Manager location.

Content slots are imported and exported through the separateMerchant Tools > Online Marketing > Import & Exportmodule usingslot.xsd. Products and catalogs are likewise administered throughMerchant Tools > Products and Catalogs > Import & Exportusingcatalog.xsd. Salesforce ' s official Import and Export Object Cheatsheet clearly differentiates these locations and schemas.

The distinction matters because B2C Commerce import/export mechanisms are organized around object domains rather than providing one universal site import screen for every object. Content assets belong to libraries and can include text, markup, links, images, and other merchandising content. They can also be exported from one library and imported into another.

Therefore, among the supplied choices, Content assets are the object type that belongs to the Content Import & Export module.

Study Guide reference:Data Management Using Business Manager Usage — content libraries, content assets, import/export schemas, Business Manager modules, and data migration.

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

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.

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

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.

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

Adding the CSRF token to the rendered form is only one half of the protection mechanism. The server-side controller handling the request must also validate that token. In SFRA, this is normally implemented through the CSRF protection middleware supplied with the storefront framework. Therefore, adding the appropriatecsrfProtectionmiddleware to the controller route is the correct response.

Salesforce ' s SFRA guidance demonstrates controller routes using CSRF middleware such ascsrfProtection.validateAjaxRequestor the appropriate request-validation middleware before processing protected form submissions. The underlying CSRF API generates and validates tokens to verify that a state-changing request originated from the expected storefront interaction.

Merely extending token validity would weaken the intended security behavior and does not correct a route that fails to perform validation correctly. Deleting a supposed allow list similarly does not implement the required request-verification sequence.

The proper architecture is therefore: generate a token, render it into the client request or form, transmit it back during submission, and validate it server-side before executing protected business logic.

Study Guide reference:Application Development — SFRA middleware, CSRF protection, secure controller routes, forms, and request validation.

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

B2C Commerce localizesform structure through locale-specific folders, not by appending the locale to the form-definition filename. For a U.S. English form, the developer createsforms/en_US/and places anaddress.xmlform definition inside it.

Salesforce ' s SFRA Forms documentation explicitly states that when a form ' s structure differs by locale—for example, state fields in one country and province fields in another—the cartridge should contain separate locale directories beneathforms, with each directory containing a form definition of thesame name. If a locale-specific definition is absent, the default form definition is used.

en_USfollows the Salesforce locale naming convention using language and country codes. Option B incorrectly changes the filename toaddress_en_US.xmlinstead of creating the required locale directory. Option C omits the language component and therefore does not use a valid locale ID for this purpose.

The copied U.S. file can then be modified independently to contain the state abbreviation options.

Study Guide reference:Application Development — localized forms,forms/en_US, XML form definitions, address localization, and locale-specific storefront behavior.

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

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.

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

For a newly added product to participate correctly in storefrontproduct search, the product must be online, marked searchable, and represented in a current product search index. Salesforce ' s official indexing documentation states that a product appears in search results only when it issearchable, online, and assigned to at least one online category. The scenario already states that the product has been added to the Storefront catalog, so the remaining examination requirements are the online/searchable flags and an updated index.

A product does not have to be a child of a master product; standalone products are completely valid B2C Commerce merchandise. A price is commercially important, but price is not the platform criterion that makes a product eligible for the search index. Product pricing is separately incorporated into search indexes from applicable price books.

Therefore, A is the technically supported choice. After catalog changes, the product index must reflect the new assignment and current searchable/online status.

Study Guide reference:Data Management Using Business Manager Usage — Product visibility, online/searchable flags, Storefront catalogs, categories, and Product Search indexing.

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

ProductSearchModel.getProductSearchHits()retrieves product hits from B2C Commerce ' sproduct search indexrather than performing direct product-database iteration. Search-index access is designed for scalable storefront product discovery because the index is optimized for search, refinement, sorting, and high-volume retrieval.

Salesforce ' s Script API explicitly recommends iteratingProductSearchHitobjects rather than loading Products directly from search results. The oldergetProducts()method is deprecated because loading full Product objects for every result is significantly more expensive from a performance perspective; Salesforce recommendsgetProductSearchHits()instead.

ProductAvailabilityModel.isOrderable()determines the orderability of a particular product within its inventory/availability context; it is not a general indexed search mechanism.ProductIndexModel.getOrderableProductsOnly()is not the appropriate supported method represented by the current Product Search API.

A common efficient storefront pattern is to configure aProductSearchModel, execute the search, iterate its search hits, and load only the product data actually needed for the current page.

Study Guide reference:Application Development — ProductSearchModel, ProductSearchHit, search indexes, scalable product retrieval, and storefront search performance.

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