Salesforce Comm-Dev-101 Practice Exam Questions & Answers

B2C Commerce assigns exactly one customer list to each site, but the same customer list can be assigned to multiple sites. Therefore, RefArch does not need a separate copy of the RefArchGlobal customer records. The site configuration must simply be changed so thatRefArchGlobal is selected as RefArch's assigned Customer List.

Salesforce describes a customer list as a collection of registered customers associated with a site and explicitly states that multiple sites can share a customer list. A site itself can use only one customer list at a time.

Option A would create or import data rather than establish the required shared-list relationship. That introduces duplication rather than true shared customer profiles. Option B is also incorrect because this relationship isn't enabled through a generic 'Customer List Sharing' global preference. The appropriate configuration is the customer-list assignment on the site.

Shared customer lists are especially useful for multi-site implementations where customers should maintain one registration/profile across multiple storefronts.

Study Guide reference:B2C Commerce Setup --- multi-site configuration, customer lists, shared customer profiles, and site-level customer-list assignment.

Creating attribute definitions on a Custom Object Type is not always sufficient to make those attributes available in the Business Manager editing interface. The attributes must be assigned to anAttribute Group, which controls how they are organized and presented to Business Manager users.

Salesforce's business-object configuration guidance explains that custom object types can be given custom attributes through their attribute definitions and that attributes can be organized into groups for administrative presentation.

Therefore, if the object type itself appears but its fields do not appear when creating or editing an instance, the developer should verify the Attribute Grouping configuration and add the required attributes to a group.

Changing the underlying data type does not address whether the fields are presented to the administrator. Option C mixes two separate custom-object concepts: storage scope determines whether object instances are site-specific or organization-wide, while replication determines whether they move between instances. Neither setting controls whether an attribute appears on the Business Manager edit form.

Study Guide reference:Data Management Using Business Manager Usage --- Custom Object Types, attribute definitions, attribute groups, Business Manager presentation, storage scope, and replication.

CallingsetFilteredByFolder(false)tells theContentSearchModelthat search results mustnot be restricted by folder membership. This is specifically important for Page Designer because Page Designer pages and components are persisted as content-related objects but can exist outside the conventional folder structure used for ordinary content assets.

Salesforce's Script API states explicitly thatsetFilteredByFolder(false)must be used to return content assets that don't belong to a folder, including Page Designer content. The SFRA Page Designer development documentation uses the same statement insetupContentSearchso that Page Designer content can participate in storefront content search.

Option B reverses the actual behavior: the method isn't extending the model to add folder filtering; it is disabling folder filtering. Option C is likewise opposite to the purpose. The change broadens the searchable content population rather than preventing pages or components from appearing.

Additional Page Designer attributes still need the appropriate searchable metadata where attribute-value searching is required, but removing the folder restriction is the necessary step for discovering otherwise un-foldered Page Designer content.

Study Guide reference:Application Development --- Page Designer,ContentSearchModel, storefront content search, searchHelpers, and searchable Page Designer content.

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.

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.

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.

The appropriate inventory configuration is thePerpetualflag on the product's inventory record. Salesforce uses this setting to represent merchandise that should be treated as continuously in stock rather than becoming unavailable when its ATS reaches zero.

Salesforce's inventory-development documentation identifies a product with the perpetual flag as a product that isalways in stock. This provides a clear platform-level representation of unlimited or non-depleting availability.

Option B is an unreliable workaround. A very large allocation is still finite, can eventually be depleted, and introduces misleading stock information into inventory reporting and integrations. Option A does not identify the actual standard Business Manager inventory setting represented by the B2C Commerce inventory model.

When standard B2C Commerce inventory management is being used, the perpetual flag directly changes the product's availability behavior. Implementations using Omnichannel Inventory must instead follow the inventory semantics of that system, but for the B2C Commerce inventory configuration tested here, Perpetual is the correct setting.

Study Guide reference:Data Management Using Business Manager Usage --- Inventory Lists, Product Inventory Records, Perpetual inventory, ATS, and product availability.