Salesforce Updated Comm-Dev-101 Exam Questions and Answers by navy

AnINFOmessage is written only when the configured logging threshold permits INFO-level events and INFO output is enabled for the relevant custom log destination. Setting the root level toDEBUGpermits DEBUG and all higher-severity messages, including INFO, WARN, ERROR, and FATAL. Enabling theInfolog-file option ensures that INFO messages are written to the applicable log file.

Salesforce ' s logging documentation explains that custom DEBUG and INFO logging can be enabled through Business Manager ' s custom log configuration and that the selected log levels control which messages are persisted. The logger ' s threshold behavior also means that a DEBUG root threshold includes INFO-level events because INFO has a higher severity.

The “logging global preference” described in options B and C is not the relevant mechanism for solving this custom logger configuration issue. Either of those options would also omit one of the two necessary controls described in option A.

Thus the developer should configure both the permitted log-level threshold and the INFO file output, then execute the code again and inspect the generated custom log through Log Center or WebDAV.

Study Guide reference:Application Development — custom logging, log levels, Business Manager log configuration, and WebDAV diagnostics.

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

A site requires adefault currencyas part of its fundamental configuration. When creating a B2C Commerce site, Business Manager asks the administrator to select the default currency together with other basic site properties such as taxation policy. Salesforce explicitly documents the site-creation step: select a default currency; a site can support multiple currencies, but only one is the default.

The default currency also initializes the shopper ' s session currency when they first access the storefront unless application logic selects another allowed currency. This affects pricing, shipping, promotions, checkout calculations, and order creation.

A default payment method or payment processor is not an equivalent mandatory site-creation setting. Payment methods are configured based on the merchant ' s business requirements, and processors are associated with specific transaction-handling implementations. A storefront may support multiple payment methods/processors and their configuration can occur independently after the site itself is created.

Study Guide reference:B2C Commerce Setup — site creation, default currency, multi-currency sites, taxation, and initial storefront configuration.

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

In SFRA controllers, theserver.formsAPI provides access to form definitions and converts the corresponding B2C Commerce form into the JSON-style form representation used by SFRA. Because the definition is namednewsletter.xml, the form is retrieved by its definition ID,newsletter, using:

server.forms.getForm( ' newsletter ' )

Current SFRA base-controller source repeatedly demonstrates this exact pattern—for example,server.forms.getForm( ' profile ' ),server.forms.getForm( ' address ' ), andserver.forms.getForm( ' billing ' ).

Option B is incorrect because the property isserver.forms, plural, notserver.form. Option C incorrectly supplies the generated HTML/form namespace prefixdwfrm_. That prefix can appear in submitted HTTP parameter names, butgetForm()expects the form-definition name itself.

The form definition establishes field structure, metadata, validation requirements, and localization behavior. Once retrieved throughserver.forms.getForm(), the controller can pass the resulting form model to an ISML template, inspect its values, validate submitted information, or clear/reset it as required.

Study Guide reference:Application Development — SFRA forms, XML form definitions,server.forms.getForm(), validation, and controller-to-template form handling.

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

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.

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