Pass the Salesforce Developers Comm-Dev-101 Questions and answers with CertsForce

A payment gatewayresponse/status codeis appropriate operational information for a checkout log because it can help diagnose authorization failures, processor errors, configuration problems, and transient integration issues without necessarily revealing sensitive payment credentials.

Passwords and credit-card information must not be placed into application logs. These values are highly sensitive and create substantial security and compliance exposure if persisted in WebDAV-accessible or Business Manager-accessible diagnostic files. B2C Commerce logging and service-integration practices require developers to keep sensitive shopper and payment information out of diagnostic output.

The correct pattern is to log identifiers and operational state sufficient to diagnose a failure—for example, a sanitized processor result code, service status, order-processing error identifier, or non-sensitive correlation ID—rather than the shopper ' s authentication secrets or raw payment details.

Salesforce ' s Service Framework guidance also supports filtering service logging so that sensitive information is excluded from request/response diagnostics.

Thus, option A provides useful diagnostic information while maintaining the appropriate security boundary.

Study Guide reference:Application Development — secure custom logging, checkout diagnostics, Service Framework logging, PCI-sensitive information, and credential protection.

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

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.

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

B2C Commerce assigns exactly one customer list to each site, but the same customer list can be assigned to multiple sites. Therefore, RefArch does not need a separate copy of the RefArchGlobal customer records. The site configuration must simply be changed so thatRefArchGlobal is selected as RefArch ' s assigned Customer List.

Salesforce describes a customer list as a collection of registered customers associated with a site and explicitly states that multiple sites can share a customer list. A site itself can use only one customer list at a time.

Option A would create or import data rather than establish the required shared-list relationship. That introduces duplication rather than true shared customer profiles. Option B is also incorrect because this relationship isn ' t enabled through a generic " Customer List Sharing " global preference. The appropriate configuration is the customer-list assignment on the site.

Shared customer lists are especially useful for multi-site implementations where customers should maintain one registration/profile across multiple storefronts.

Study Guide reference:B2C Commerce Setup — multi-site configuration, customer lists, shared customer profiles, and site-level customer-list assignment.

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

The Request Log usesin-memory loggingon supported non-production instances. The " Log Files " checkboxes control whether a particular severity is persisted into a physical custom log file; they are not required merely to make the message visible in the Request Log Viewer.

However, the category filter still matters.myLogCategoryis currently configured at INFO, so DEBUG—the lower-severity level—is filtered out. The developer therefore must change the category ' s threshold toDEBUG. Salesforce explains that configured levels represent minimum severity and that DEBUG in-memory logging supports theShow Request Logfeature without necessarily creating a debug log file.

Checking the DEBUG target would generate persistentcustomdebugoutput where supported, but that is separate from the stated requirement to inspect the Request Log. Therefore option C performs an unnecessary operation and option B does not change the category threshold.

Study Guide reference:Application Development — Custom Log Settings, category thresholds, DEBUG severity, in-memory logging, and Storefront Toolkit Request Log.

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

A storefront category intended to appear in navigation normally needs appropriate online configuration andavailable products assigned to it. Salesforce ' s category-management guidance specifically notes that to show a category in storefront menu navigation, available products must be assigned to the category and the relevant menu-navigation configuration must be enabled.

This makes option A the relevant cause among the supplied choices. A newly created category that contains no available merchandise can fail to appear where expected in the storefront navigation structure.

Option C is incorrect because sorting determines ordering, not whether a category exists or is eligible to appear. Option B is too broad in the context of the scenario. An offline storefront catalog would affect storefront catalog availability generally, rather than explaining why this newly created category alone cannot be seen.

Product/category visibility in B2C Commerce depends on several related configuration elements: product assignments, category online state, catalog-to-site assignment, navigation settings, and updated search indexes where applicable. Salesforce also confirms that products must be assigned to categories and the catalog assigned to the site for storefront visibility.

Study Guide reference:Data Management Using Business Manager Usage — catalogs, categories, product assignments, storefront navigation, and product availability.

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

The required workflow creates a new shipment for a gift item and then modifies shipment information associated with the basket. The OCAPI basket shipment hooks corresponding to those two operations aredw.ocapi.shop.basket.shipment.beforePOSTanddw.ocapi.shop.basket.shipment.beforePATCH.

Salesforce ' s OCAPI hook documentation definesshipment.beforePOSTas the extension point executed before creation of a shipment andshipment.beforePATCHas the extension point executed before modification of an existing shipment. Those operations align directly with the described solution: establish the separate shipment and then apply the necessary changes before final basket validation.

The alternatives involvingbeforeDELETEorafterDELETEare inconsistent with the scenario because no shipment needs to be deleted. The requirement is to separate a gift product into its own shipment, not remove a shipment from the basket.

The concludingvalidateBaskethook provides the final validation stage after the basket/shipment changes have been processed, allowing custom logic to ensure that the resulting basket remains valid.

Study Guide reference:Application Development — OCAPI Shop API hooks, basket extension points, shipment creation and modification, and basket validation.

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