Comm-Dev-101 Exam Dumps - Salesforce Developers Questions and Answers

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.

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

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.

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

Order failure informationis appropriate operational data for diagnostic logging when it is implemented without exposing protected shopper information. Checkout failures, error codes, integration outcomes, or non-sensitive order-processing context can provide developers and support teams with the information needed to diagnose failed purchases.

Passwords must never be written to application logs. Likewise, complete credit-card information is sensitive payment data subject to stringent PCI controls and should not be placed into custom log files. Salesforce specifically warns developers to filter sensitive or private data—such as credit-card numbers—from service logs, and B2C Commerce payment APIs treat cardholder and financial information as PCI-sensitive data.

Option B would create an obvious credential-disclosure risk because anyone with log access could potentially recover customer authentication data. Option C would unnecessarily persist cardholder information outside the platform ' s protected payment-data handling mechanisms.

The proper logging strategy captures enough contextual data to diagnose checkout problems while excluding passwords, full payment credentials, authentication secrets, and similar sensitive values.

Study Guide reference:Application Development — secure logging, checkout diagnostics, PCI considerations, payment data handling, and protection of customer credentials.

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

B2C Commerce customer lists areorganization-level objects that can be assigned to multiple sites. Each individual site can use exactly one assigned customer list, but multiple sites can reference the same list. Salesforce documents this relationship explicitly.

To configure RefArch to use RefArchGlobal ' s customer list, the administrator edits the RefArch site configuration and selectsRefArchGlobalas its Customer List. Salesforce ' s storefront-site configuration documentation identifies Customer List as a configurable field on the site ' s General tab.

Importing the customer list into RefArch would create or transfer customer data rather than establish the intended shared-list assignment. It would not implement genuine shared customer profiles.

Option B is also incorrect because there is no generic " Customer List Sharing " global preference that enables this behavior. Sharing is accomplished by assigning the same customer list to more than one site.

Study Guide reference:B2C Commerce Setup — Customer Lists, shared customer profiles, multi-site configuration, site General settings, and customer-list assignment.

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

ThePayment Methodsconfiguration is the appropriate Business Manager location because payment-method applicability can be restricted according to criteria that include the shopper ' s billing country. The merchant can therefore configure the relevant payment method so that it is not available where the country condition excludes Denmark.

Salesforce ' s Business Manager documentation for payment methods describes configuration controls for availability based on customer groups, billing countries, and order-amount conditions. The underlying payment-management logic evaluates these configured applicability rules when determining which methods are available for the current basket and shopper context.

A payment processor represents the back-end processing integration or transaction handler associated with one or more payment methods; it is not the primary mechanism for defining a country ' s storefront eligibility. “Locale Payments” is not the appropriate Business Manager module for this requirement.

This separation is important: thepayment methoddescribes whether a shopper can select a payment option under particular storefront conditions, while thepayment processordetermines how an accepted payment is technically processed.

Study Guide reference:Data Management Using Business Manager Usage — payment methods, payment applicability, billing-country restrictions, payment processors, and checkout configuration.

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

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.

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

The B2C Commerce Service Framework provides native support for mocked services, so the developer should implement themockFullcallback and configure the service to operate in mock mode. This enables application development and testing before the external provider exposes the real endpoint.

Salesforce documents that when a service is operating in mocked mode, the framework can use its configured mock callback instead of making the live network request.mockFullis particularly useful because it can replace the full service execution sequence and return a controlledResultsuitable for testing dependent application logic.

A custom site preference is unnecessary because the Service Framework already contains an administrative mechanism for selecting mocked operation. Introducing application-specific conditionals or preferences duplicates platform functionality and makes the integration harder to administer consistently.

This approach also preserves separation of concerns: application code continues calling the same service abstraction, while environment configuration determines whether the real provider or the mock implementation is used. When the remote API becomes available, the service can be switched from mocked to live behavior without redesigning its callers.

Study Guide reference:Application Development — LocalServiceRegistry, Service Framework callbacks, mocking external integrations, and service testing.

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

The new requirement is additive: the existingCart-Showbehavior should continue running, and the client cartridge only needs to add adataLayerproperty to the response. SFRA ' s preferred mechanism for this type of extension is toappend middleware to the existing routeand enrich its ViewData.

Salesforce documentsserver.appendas a controller-customization mechanism that executes the existing middleware chain and then adds an additional step. A common use is precisely to retrieve and update the current ViewData with extra properties that are needed during rendering.

This also preserves cartridge independence. Throughmodule.superModule, the client cartridge resolves the applicable controller immediately to its right on the cartridge path. If the LINK cartridge exists, its customized route participates. If it is later removed, resolution can fall through to the next implementation, such asapp_storefront_base, while the client ' s appended data-layer logic remains unchanged.

Replacing the entire route unnecessarily couples the client implementation to existing logic and duplicates behavior that SFRA ' s extension model already provides.

Study Guide reference:Application Development — SFRA controller extension,server.append,module.superModule, ViewData, cartridge precedence, and upgrade-safe customization.

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

Among these choices, aproduct custom attributeprovides the cleanest and most maintainable data-driven solution. B2C Commerce allows the Product system object to be extended with custom attributes, enabling merchandising metadata such as a permitted region, market code, or eligibility classification to live with the product data rather than being hard-coded in controller logic.

The storefront or search-layer implementation can then evaluate that attribute against the shopper ' s applicable regional context and filter products accordingly. This approach scales better than embedding specific product IDs or regional rules directly into scripts.

Creating an entire catalog for every region may be justified when each market has substantially different assortments, categories, navigation, prices, or merchandising operations, but it is excessive for a requirement centered on a specific product ' s regional eligibility. Option C also places business data in code, making merchant maintenance and expansion harder.

The custom attribute should be modeled with an appropriate data type and, where needed, indexed if search-result filtering is involved.

Study Guide reference:Data Management Using Business Manager Usage — Product system object extensions, custom attributes, merchandising metadata, search filtering, and regional product eligibility.

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

Ifdw.order.calculateTaxis already registered byapp_storefront_base, the custom controller doesnotneed to register the hook again. It only needs to invoke the existing extension point throughdw.system.HookMgr.callHook().

Salesforce ' s SFRA hook documentation distinguishes registration from invocation: the implementing cartridge registers the extension point through its hook configuration, while application code calls registered hooks through HookMgr.

More importantly, the currentapp_storefront_basecalculation implementation demonstrates the exact call:

HookMgr.callHook( ' dw.order.calculateTax ' , ' calculateTax ' , basket);

Adding another entry tohooks.jsonorpackage.jsonis only required when a cartridge is providing/registering a hook implementation, not merely consuming an implementation that is already registered.

Study Guide reference:Application Development —dw.system.HookMgr,callHook(),dw.order.calculateTax, hook registration versus invocation, and SFRA basket calculation.

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