Salesforce Updated Comm-Dev-101 Exam Questions and Answers by alissa

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.

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

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().

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

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.

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

Uploading a cartridge to an instance does not automatically make its code available to a storefront. B2C Commerce resolves application resources according to thecartridge path configured for the relevant site. Consequently, the new custom cartridge must be added to that storefront site ' s cartridge path, normally in the correct precedence position relative to SFRA base and other cartridges.

Salesforce ' s cartridge documentation describes two distinct steps: upload the cartridge code and register the cartridge with the applicable site through its cartridge path. Site configuration is performed from the site ' s settings, where the cartridge path controls which controllers, templates, scripts, models, and other cartridge resources can participate in storefront execution.

Rebuilding indexes is unrelated unless the customization specifically changes indexed catalog/search data. An index rebuild does not register executable storefront code. Likewise, configuring the Business Manager application ' s cartridge path would affect Business Manager customizations rather than the customer-facing storefront identified in the question.

Cartridge ordering is also significant because B2C Commerce searches the path according to precedence, enabling custom cartridges to extend or override functionality from cartridges located farther to the right.

Study Guide reference:B2C Commerce Setup — cartridges, site cartridge paths, SFRA deployment, and cartridge precedence.

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