Vce Comm-Dev-101 Questions Latest

Therootcategory is the parent of all custom logger categories, includingproducts. Therefore, the WARN threshold configured at root applies to theproductslogger unless a more specific category configuration overrides it.

B2C Commerce logging severity is hierarchical: enabling a particular level also enables all higher-severity levels. Salesforce gives the explicit example that when WARN is enabled for a category,WARN and ERRORmessages are logged for that category and its subcategories. Root configuration likewise applies to all custom categories.

Consequently,log.warn()andlog.error()both qualify for persistence.log.info()does not because INFO is below WARN in the severity hierarchy. The exact text placed inside the INFO call doesn ' t matter; logging eligibility is determined by the API method/severity, not whether the message string contains the word " warn. "

This hierarchical configuration allows administrators to maintain a conservative production logging threshold while selectively enabling more detailed logging for particular categories when troubleshooting.

Study Guide reference:Application Development —dw.system.Logger, log categories, root logger hierarchy, severity thresholds, and custom logging configuration.

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

Logger.getLogger( " contact " )returns a logger associated with the custom categorycontact. Invoking.debug()on that logger writes the message at DEBUG severity under the specified category, assuming the corresponding category configuration permits DEBUG logging.

Salesforce ' sdw.system.LoggerAPI documents the one-argumentgetLogger(String)method as returning the logger for the supplied category. It also exposes DEBUG, INFO, WARN, ERROR, and other severity operations on the resulting logging object.

Option B uses the static root-style debug call and therefore does not explicitly bind the entry to the requested custom category. Option A is invalid becauseLogger.customLogger()is not a supported Script API method.

Category-based logging is useful for service integrations because Business Manager administrators can selectively increase diagnostic verbosity for a specific subsystem such ascontactwithout globally enabling excessive DEBUG output. Category rules can also be hierarchical, allowing narrower categories such ascontact.submitorcontact.response.

Study Guide reference:Application Development —dw.system.Logger,getLogger(), custom logging categories, DEBUG severity, and Service Framework diagnostics.

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

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.

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

OCAPI is designed to expose B2C Commerce resources to external applications and integration systems through RESTful APIs. A warehouse management system that needs to update inventory is therefore a strong OCAPI use case because inventory is enterprise data maintained by an external operational system and must be synchronized into Commerce.

Salesforce describes the OCAPI Data API as providing external applications with programmatic access to Commerce resources and administrative data operations. Inventory integration is a standard example of synchronizing Commerce with external inventory or fulfillment systems.

Extending a System Object Type definition with new attributes is a platform metadata/configuration activity normally performed through Business Manager or supported metadata import mechanisms, not an ordinary OCAPI runtime integration. Showing customer information on the storefront ' s native My Account page is also normally handled internally by SFRA controllers, models, templates, and the B2C Commerce Script API rather than calling OCAPI from the same storefront application.

Using OCAPI for the warehouse system preserves a clear integration boundary: the external application authenticates through the API and exchanges inventory data without being coupled to storefront presentation code.

Study Guide reference:Application Development — OCAPI, external-system integrations, inventory synchronization, Data API usage, and storefront versus integration architecture.

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