Salesforce Comm-Dev-101 Practice Test Questions Answers

TheFATALlogging level is the special severity level that thedw.system.LogAPI identifies as always enabled under normal logging operation. It represents severe conditions for which developers should always be able to emit diagnostic information.

Salesforce ' sdw.system.LogAPI documentation explicitly states thatFatal log messages are always enabledand can optionally be distributed through email notification configuration. INFO, by contrast, depends on the configured logging threshold and target settings. ERROR also participates in the configurable category hierarchy and does not carry the same API-level guarantee expressed for FATAL.

B2C Commerce custom logging uses a log4j-style hierarchy. Categories inherit logging behavior from parent categories unless a more specific rule applies. For example, an INFO threshold permits INFO, WARN, ERROR, and FATAL. A WARN threshold permits WARN, ERROR, and FATAL. Salesforce also supports configuring log targets separately from filters.

FATAL should be reserved for genuinely severe application conditions rather than routine diagnostic output, because excessive high-severity logging obscures operational incidents and reduces the diagnostic value of the logs.

Study Guide reference:Application Development —dw.system.Log, logging severity, custom log categories, FATAL logging, and production diagnostics.

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

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.

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

< 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.

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

CSRF validation must occurwhen the state-changing request is submitted, before protected business logic executes. In SFRA this is implemented as middleware in the controller ' s POST route, using the appropriate CSRF middleware—validateRequestfor standard submissions orvalidateAjaxRequestfor AJAX-based requests.

Salesforce ' s SFRA Forms documentation specifically states that CSRF protection is supplied as middleware and demonstrates CSRF checks as middleware steps. The underlyingdw.web.CSRFProtection.validateRequest()API verifies that the request contains the system-generated token and that the token has not expired.

Generating the token in the template only establishes the client-side value; it does not provide security unless the receiving POST endpoint validates it. Placing validation only in the form-display route would validate the wrong request. Performing validation in a persistence model is also too late because request security should be enforced before mutation logic is invoked.

Study Guide reference:Application Development — CSRF protection, SFRA middleware, POST routes,validateRequest,validateAjaxRequest, and secure form processing.

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

Theurlform of < isinclude > performs aremote include. In this example,URLUtils.url( ' Account-Header ' , ' mobile ' , true)constructs a URL for theAccount-Headerendpoint and supplies that URL to < isinclude > . B2C Commerce therefore makes a separate request to the generated endpoint and inserts the resulting response into the surrounding page.

Salesforce distinguishes this behavior from a local template include. A local include uses thetemplateattribute and incorporates another ISML template within the current rendering context. By contrast, an < isinclude > that specifiesurlis explicitly classified as a remote include and can execute another controller or pipeline endpoint.

Option B is therefore incorrect because the code does not use the local-template syntax. Option C is also incorrect:URLUtils.url()does construct a URL, but placing that URL in theurlattribute of < isinclude > does not render an anchor or navigational link. It causes the endpoint ' s output to be included in the current response.

Study Guide reference:Application Development — ISML includes, remote includes,URLUtils, controller endpoints, and composable storefront rendering.

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