Score Higher on Verified Comm-Dev-101 | Salesforce Certified B2C Commerce Developer Exam Questions with Answers

Logger.getLogger( ' contact ' )creates or retrieves a logger associated with thecontactcategory. Calling.debug()on that logger writes the message at DEBUG severity, subject to the configured category and log-target rules.

B2C Commerce custom logging uses hierarchical category names patterned after log4j. Categories can be activated at particular severity levels inAdministration > Operations > Custom Log Settings. Salesforce explains that child categories inherit applicable settings from their parent categories unless they have more specific configuration.

Option B uses the generic staticLogger.debug()call and does not explicitly associate the statement with the required customcontactcategory. Option C refers to a nonexistentcustomLogger()API.

The category-specific approach is operationally superior when troubleshooting a third-party integration because administrators can selectively enable DEBUG logging forcontactwithout enabling extensive debugging across unrelated application code. Once the issue is diagnosed, that category ' s verbosity can be reduced again.

Study Guide reference:Application Development —dw.system.Logger, custom categories, DEBUG logging, Service Framework diagnostics, and hierarchical logging 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.

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

Because thedw.order.calculateTaxhook is alreadydefined and registered byapp_storefront_base, the custom controller does not need to register that implementation again. Its responsibility is to invoke the existing extension point throughdw.system.HookMgr.callHook(). Therefore, option A expresses the correct architectural pattern.

Salesforce ' s SFRA hook documentation separateshook registrationfromhook invocation. A cartridge that provides an implementation registers its hooks through its hook configuration, while consuming code calls the registered extension point withHookMgr.callHook(). B2C Commerce then resolves registered hook implementations from cartridges on the active cartridge path.

The current SFRA implementation itself invokes the tax extension point withHookMgr.callHook( ' dw.order.calculateTax ' , ' calculateTax ' , basket), demonstrating that calling code does not re-register the existing hook.

Accordingly, adding another hook location to the custom cartridge ' shooks.jsonorpackage.jsonmerely to call an already registered implementation is unnecessary. Registration is required for the cartridge implementing the hook, not every caller.

Study Guide reference:Application Development — hooks, HookMgr, extension-point registration, SFRA tax calculation, and cartridge extensibility.

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