Developers Comm-Dev-101 Passing Score

For anen_CArequest, B2C Commerce first attempts to resolve the requested resource bundle for the country-specific locale. Because there is noaccount_en_CA.properties, the resource lookup falls back to the language-specific English bundle,account_en.properties. That file definesweight.unit=stones, so the rendered message is " Your parcel weighs 10 stones. "

The SalesforceResourceAPI explains that localized strings are loaded from properties resource bundles according to the current request locale. Resource bundles can include a base file, a language-specific file, and country-specific variants. Salesforce ' s localization guidance also identifies the general hierarchy of country locale → language locale → default resources.

account_en_US.propertiesisn ' t selected becauseen_USis a different country-specific locale. It isn ' t the fallback parent ofen_CA; both shareenas their language parent.

The baseaccount.propertiesvalue would be used only if no applicable value were resolved through the more specific English bundle.

Study Guide reference:Application Development — localization, resource bundles,Resource.msg(), locale resolution, and template resources.

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

For a Business Manager extension to become visible and usable, its cartridge must participate in theBusiness Manager cartridge path, and the user must have the Business Manager module permission required to access the extension. Salesforce explicitly states that Business Manager extension cartridges must be added to the BM cartridge path, and extension functionality is secured through roles and permissions.

The extension does not need to be added to the Storefront site ' s cartridge path merely to make its Business Manager menu/module available. A code version containing the cartridge must of course be deployed and active generally, but activation alone does not grant access to the new Business Manager module.

There is atyping inconsistency in option A: the stem names the cartridgeplugin_bm_extension, whereas option A sayscustom_bm_extension. The technically correct action represented by A is to addplugin_bm_extensionto the Business Manager cartridge path and grant the appropriate roles/permissions.

Study Guide reference:B2C Commerce Setup — Business Manager extensions, BM cartridge path, module permissions, roles, and extension deployment.

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

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.

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

This requirement can be implemented declaratively through the shipping method ' s existingproduct exclusion/allow-list configuration, avoiding unnecessary SFRA customization.

Salesforce explicitly supports both product blocklists and product allowlists for shipping methods. Its official example closely mirrors this scenario: suppose free shipping excludes all televisions, but the merchant wants a Brand-XYZ television to qualify. The administrator adds the Brand-XYZ product or rule as an exception in the Product Exclusion configuration, effectively removing those matching products from the exclusion set and allowing the shipping method.

That is preferable to adding custom logic inshippingMethod.jsorCheckoutShippingServices. Business Manager configuration is maintainable by merchants, can be changed without a code deployment, and aligns directly with a temporary three-month merchandising requirement.

The terminology can appear counterintuitive because the allow-list exception is configured inside the broaderProduct Exclusioninterface. Conceptually, the initial inclusion defines which products are blocked, while the nested exclusion identifies exceptions that are taken back out of that blocklist.

Study Guide reference:Data Management Using Business Manager Usage — shipping methods, product exclusions, product allowlists, Business Manager shipping configuration, and configuration-over-code best practices.

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