Comm-Dev-101 Exam Dumps - Salesforce Certified B2C Commerce Developer

Inventory administration is a merchant-data integration concern and belongs to theOCAPI Data API, not the shopper-oriented Shop API. In addition, most Data API resources are organization-specific and therefore useGlobalOCAPI permissions. The/inventory_lists/*resource is the relevant resource family for managing inventory lists through the Data API.

Salesforce explains that the Data API provides create/read/update/delete access to administrative system resources, while OCAPI settings define which resource paths and HTTP methods a client is allowed to use. The current Commerce API documentation likewise identifies Inventory Lists as administrative inventory resources.

Options B and C use/product/*/inventory, which is not the appropriate Data API inventory-list resource shown for this architecture. Option B additionally selects the Shop API and site context, which do not match a warehouse-management integration updating backend inventory data.

The configuredget,put, andpatchpermissions enable the external integration to retrieve inventory information and perform complete or partial updates, subject to authentication and the resource schema.

Study Guide reference:Application Development — OCAPI Data API, inventory lists, Global OCAPI configuration, resource permissions, and warehouse integrations.

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

< isif > is appropriate forconditional presentation logicinside an ISML template. Showing or hiding a page fragment according to information already provided to the view—such as whether the current shopper is authenticated—is exactly the kind of lightweight rendering decision for which < isif > is intended.

Salesforce explicitly states that < isif > , < iselseif > , and < iselse > provide conditional template constructs but should containno business logic, only conditional visualization of data. SFRA customization guidance reinforces this architectural separation by stating that business logic generally does not belong inapp_storefront_basetemplates; templates should concentrate on rendering.

Option B therefore violates SFRA separation-of-concerns practices because involved business logic belongs in controllers, models, helpers, or services. Option C is also unsuitable because routing and redirects are HTTP response-control operations that should be performed by the controller rather than an ISML presentation template.

Study Guide reference:Application Development — ISML conditional rendering, < isif > , template responsibilities, controllers, and separation of business logic from presentation.

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

B2C Commerce includes several platform-defined payment methods, such asCREDIT_CARD,GIFT_CERTIFICATE,BANK_TRANSFER, and other standard methods. These default definitions are part of the platform configuration and therefore cannot simply be deleted. If a merchant does not want to expose one of these methods on the storefront, the appropriate administrative action is to disable it.

Salesforce ' s Business Manager documentation explicitly states thata default payment method cannot be deleted and can only be disabled. It also confirms that administrators can drag column headers to alter the payment-method sort order, which directly eliminates option C. There is likewise no five-payment-method limit corresponding to option B.

Payment methods are managed independently from payment processors. A payment method represents the shopper-facing way of paying, while a payment processor represents the processing implementation associated with that method. Maintaining the platform-defined method while disabling it preserves configuration integrity and permits the method to be reactivated later without recreating its system definition.

Study Guide reference:Data Management Using Business Manager Usage — Payment Methods, payment configuration, default payment methods, activation and deactivation.

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

B2C Commerce can contain multiple uploadedcode versions, but only the currently active version is executed. Therefore, if the cartridge path has already been verified and the files appear to be uploaded successfully, the next critical check is whether the expected code version is actually active.

Salesforce ' s cartridge guidance explains that code is uploaded into code-version directories and that the active version determines which uploaded cartridge code is executed. Salesforce ' s SFRA troubleshooting guidance specifically recommends switching code versions when uploaded changes do not appear on the server.

A search-index rebuild would be relevant to product, category, content-search, or refinement changes, but it does not activate newly modified controller, template, model, or script code. Option C is redundant because the scenario explicitly says that the Storefront site cartridge path has already been checked; the Business Manager application ' s cartridge path concerns Business Manager customizations rather than this storefront-code issue.

A typical diagnostic sequence is therefore: verify upload, verify storefront cartridge path and ordering, verify active code version, and if necessary reactivate the expected version.

Study Guide reference:B2C Commerce Setup — code versions, cartridge deployment, cartridge paths, active code selection, and sandbox troubleshooting.

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

Page-Includeis explicitly protected withserver.middleware.include, meaning it is designed to execute as aremote include, not as a shopper ' s top-level browser request. Salesforce ' s SFRA Page controller documentation describesPage-Includeas an endpoint triggered when content assets are embedded within a rendered page and identifiesserver.middleware.includeas its middleware.

The appropriate ISML mechanism is therefore:

< isinclude url= " ${URLUtils.url( ' Page-Include ' , ' cid ' , ' about-us ' )} " >

Using theurlattribute makes < isinclude > perform a remote include. Salesforce documents that this causes the web adapter to execute another request and insert the endpoint ' s returned content into the surrounding template.

Option A creates a shopper-clickable top-level URL, which fails the include middleware condition and explains the error described in the scenario. Option C is not the remote-include tag.

Study Guide reference:Application Development —Page-Include,server.middleware.include, remote includes, < isinclude url > , and SFRA content rendering.

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