Pass the Salesforce Developers Comm-Dev-101 Questions and answers with ExamsMirror

Whether a location is a single-brand store is a characteristic of the individualStorerecord. The clean data model is therefore to add a Boolean custom attribute to the Store system object, for examplesingleBrand. The storefront ' s store-locator model or template can inspect that value and apply the appropriate CSS class when rendering each location.

B2C Commerce ' s metadata framework allows extensible system objects to receive custom attributes throughAdministration > Site Development > System Object Types. Salesforce specifically identifiesStoreas an extensible persistent object, and its Business Object documentation describes how custom attributes are created on system objects.

Creating a custom object, as proposed in option B, would introduce a second data structure and require a relationship between that object and the Store record. That is unnecessary when Store itself is extensible. Option C is also unsuitable because a site preference represents site-wide configuration rather than a property that varies from one physical store to another.

Using a Boolean also provides simple, deterministic rendering logic:truereceives the single-brand styling;falsereceives the normal presentation.

Study Guide reference:Data Management Using Business Manager Usage — system object types, Store metadata, custom attributes, Business Manager configuration, and storefront data modeling.

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

B2C Commerce can contain multiple uploadedcode versions, but only the currently active version is executed. Therefore, if the cartridge path has already been verified and the files appear to be uploaded successfully, the next critical check is whether the expected code version is actually active.

Salesforce ' s cartridge guidance explains that code is uploaded into code-version directories and that the active version determines which uploaded cartridge code is executed. Salesforce ' s SFRA troubleshooting guidance specifically recommends switching code versions when uploaded changes do not appear on the server.

A search-index rebuild would be relevant to product, category, content-search, or refinement changes, but it does not activate newly modified controller, template, model, or script code. Option C is redundant because the scenario explicitly says that the Storefront site cartridge path has already been checked; the Business Manager application ' s cartridge path concerns Business Manager customizations rather than this storefront-code issue.

A typical diagnostic sequence is therefore: verify upload, verify storefront cartridge path and ordering, verify active code version, and if necessary reactivate the expected version.

Study Guide reference:B2C Commerce Setup — code versions, cartridge deployment, cartridge paths, active code selection, and sandbox troubleshooting.

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

B2C Commerce provides a dedicatedAvailability Low Ranking Thresholdsetting for exactly this search-merchandising requirement. It is configured in Business Manager under Search Preferences and specifies the availability percentage at or below which products should be pushed toward the end of search results.

Salesforce gives the example that a threshold of0.3causes products with availability of 0.3 or lower to be ranked lower in storefront search. This preserves product discoverability while prioritizing merchandise that has healthier inventory.

Option A is unnecessarily destructive and operationally inefficient. Hiding products through an hourly job changes catalog state and can create delays or merchandising side effects. It also does not distinguish between temporarily low inventory and true unavailability. Option C confuses availability ranking with Searchable Attribute boost configuration. The platform already exposes a specific preference for low-availability ranking, so custom boosting is unnecessary.

This feature is particularly useful when merchants want low-stock merchandise still discoverable but not prominently ranked, balancing inventory awareness with conversion-oriented search results.

Study Guide reference:Data Management Using Business Manager Usage — Search Preferences, Availability Low Ranking Threshold, product availability, and search-result ranking.

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

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.

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

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.

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

Custom Object attributes must be assigned to anAttribute Groupbefore Business Manager can expose them in the Custom Object editing interface. Defining an attribute creates its metadata, but grouping controls its administrative presentation.

Salesforce explicitly states that after creating custom-object attributes, developers must add them to an Attribute Group in order to manage the custom object through Business Manager. Salesforce also notes that the custom object ' s key attribute must be included in an attribute group; otherwise, administrators cannot create instances of the custom object definition through the Custom Object module.

Option A is unrelated. Changing the data type modifies how an attribute stores information and can even destroy existing values, but it does not solve the Business Manager visibility issue. Option C confuses attribute presentation with custom-object scope and replication. Site-specific storage determines where object instances exist, while replication configuration governs movement between instances; neither causes fields to appear in the editor.

The correct workflow is therefore to define the attributes, create the appropriate Attribute Group, assign the desired fields—including the key—to the group, and then manage object instances through the site ' s Custom Objects module.

Study Guide reference:Data Management Using Business Manager Usage — Custom Object Types, Attribute Definitions, Attribute Groups, Custom Object Editor, and Business Manager metadata.

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

SFRA storestemplate resource bundlesin the cartridge ' stemplates/resourcesdirectory. Locale selection is represented in the propertiesfilename, rather than by creating a separatefrsubdirectory for ordinary SFRA resource bundles.

For example, a default bundle might be:

account.properties

while its French translation would be:

account_fr.properties

Both belong under:

cartridge/templates/resources

Salesforce ' s localization documentation explicitly states that template resource bundles are stored in/templates/resourcesand gives examples such asaccount_en_GB.properties,account_en_US.properties, andaccount_en.properties. Thedw.web.Resourcedocumentation likewise describes resource bundles as properties files with a common name located in thetemplate/resourcesdirectory.

Option B omits the required template-resource location. Option C incorrectly assumes that locale resolution for properties bundles uses a dedicatedfrfolder. Locale-specifictemplatescan use locale directories, but localized properties bundles follow the filename-suffix convention.

This separation permits one common set of ISML templates to reference resource keys while B2C Commerce automatically resolves the appropriate translated properties bundle for the active request locale.

Study Guide reference:Application Development — localization, template resource bundles,.propertiesfiles, locale fallback, andResource.msg().

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

The intended activity is product-level merchandising data, so the first requirement is acustom attribute on the Product system object. Values such as tennis, jogging, and basketball can then be populated for the applicable products. The second requirement is to expose that indexed attribute as aSearch Refinement Definitionfor the categories where shoppers should be able to use it.

Salesforce ' s search-refinement model supports attribute-based refinements that restrict product-search results according to values stored on products. A search refinement definition identifies the attribute that should participate in refinement behavior. Salesforce also provides System Object Type configuration for defining custom attributes on extensible system objects such as Product.

There is no need for a separate “ProductRefinement” custom attribute type as proposed in option B. Option C ' sviewtypeis unrelated to defining searchable product characteristics; presentation modes do not create catalog data or refinement dimensions.

After the attribute and refinement are configured, the product data must contain appropriate values and the relevant search index must include them.

Study Guide reference:Data Management Using Business Manager Usage — Product custom attributes, catalog metadata, search refinements, and search indexing.

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

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.

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

Every Page Designer component type has aJSON meta definition. That metadata describes the configurable structure exposed to Page Designer, including attributes and, for container/layout components, theregions into which merchants can place other components.

Salesforce documentation states that each page type and component type requires a JSON meta definition file. For component types, the file describes merchant-configurable attributes and can define regions. Salesforce ' s example of a three-column layout component represents each column as a region in that component ' s metadata.

The JSON file does not itself define the CSS responsive behavior of the rendered component; responsive visual structure belongs to the component ' s rendering/template implementation and associated styling. Nor does the JSON meta definition contain the complete business and rendering logic. Traditional Page Designer component types have a corresponding script implementation that performs rendering, obtains application data when appropriate, and sends content to the template.

The metadata file is therefore declarative: it describes what Page Designer understands about the component and what configuration merchants can manipulate.

Study Guide reference:Application Development — Page Designer component types, JSON meta definitions,region_definitions, component attributes, and Page Designer architecture.

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