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

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.

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

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.

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

A content slot configuration determines bothwhat type of content is selectedandwhich template renders that content. The current slot is configured to produce products based on a merchandising rule. To convert it to a slot that displays a specific content asset, the merchant must change the configuration ' s content type and choose an appropriate rendering template capable of rendering the selected content asset.

Salesforce explains that content slots can display products, categories, content assets, static HTML, and other merchandising content. Slot configurations control the content to show, the scheduling or targeting rules, and the rendering template used to produce the resulting storefront markup.

The existing slot itself does not need to be deleted because its physical location in the page is defined by the < isslot > declaration in the storefront template. Merchants can create or modify multiple configurations against the same slot. Likewise, simply altering a default setting does not convert product-oriented configuration into content-asset configuration.

Study Guide reference:Data Management Using Business Manager Usage — content slots, slot configurations, content types, rendering templates, and personalized merchandising.

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

The two-argumentLogger.getLogger()method accepts afile-name prefixfollowed by alogging category. Here,loggerFileis the requested custom file-name prefix andcategory1.euis the category.

Salesforce ' s Script API defines the signature asLogger.getLogger(fileNamePrefix, category). Custom log files created through this mechanism are stored as custom logs, so their actual generated filename begins with thecustom-naming convention followed by the developer-supplied prefix. Salesforce also states that repeated calls using the same file-name prefix use the same associated custom logger/file.

The WARN message passes filtering becausecategory1.euinherits its logging threshold from parent categorycategory1, which is enabled at WARN. B2C Commerce custom logging is hierarchical, so parent-category rules apply to descendant categories unless overridden.

Therefore, the WARN entry is written to the custom log beginning withcustom-loggerFile.

Study Guide reference:Application Development — Logger file prefixes, custom log files, category inheritance, WARN filtering, andLogger.getLogger().

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

The appropriate responsibility of < isif > isconditional presentation. Evaluating a Boolean already present inpdictand choosing between different pieces of markup is exactly the intended ISML use case.

Salesforce ' s official < isif > documentation is explicit that < isif > , < iselseif > , and < iselse > containno business logic; they provide conditional visualization of data. The condition can use Pipeline Dictionary variables and other expressions that resolve to Boolean behavior.

Option B therefore violates the separation of concerns used by SFRA. Complex business rules should be computed before template rendering—typically in controllers, helpers, models, or other server-side modules—and only their resulting data should be passed to ISML. Option C is also incorrect because redirecting a request is controller responsibility. A template should not control HTTP routing or authentication flow.

The supplied question ' s correct use is consequently showing a different < div > based on an already computed Boolean.

Study Guide reference:Application Development — ISML, < isif > ,pdict, conditional visualization, controller responsibilities, and separation of presentation from business logic.

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

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.

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

OCAPI Shop API search suggestions use thesuggestion.product.image:view_typesetting to determine which B2C Commerce image view type is returned with product suggestions. Salesforce documents the reserved property and givessmallas an example configured view type. Critically, this is not an automatic fallback value.

Salesforce explicitly states that ifview_typeisnot configured or refers to an unknown view type, the image properties are omitted from the response. Therefore, option A precisely matches the API behavior.

Options B and C incorrectly assume that the platform substitutes a default image view type. It does not. The developer must configure a valid image view type that exists in the catalog ' s image configuration if search-suggestion responses are expected to contain image data.

This configuration is especially important for autocomplete interfaces because the application might render product thumbnails beside suggested product names. Without a valid configured view type, the response can still contain suggestion data, but the expected image properties are absent.

Study Guide reference:Application Development — OCAPI Shop API,/search_suggestion, image view types, OCAPI settings, and search-suggestion response customization.

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

The controller passes the form object tores.render()under the property namenewsletterForm. SFRA merges render data into the response ViewData, and the resulting information is made available to the ISML template throughpdict. Therefore the correct template reference is:

pdict.newsletterForm

The resulting expressions become:

pdict.newsletterForm.attributes

and

pdict.newsletterForm.email.attributes

The form ' sattributesproperty contains generated form-level HTML attributes, while theemailfield exposes its own generated attributes and state.

Option B uses the form-definition name rather than the property name chosen by the controller. Option C omits thepdictaccess expected in the supplied ISML pattern.

Study Guide reference:Application Development — SFRA forms,server.forms.getForm(), ViewData,pdict, form attributes, and controller-to-template data binding.

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

ThePerpetualflag exists specifically to indicate that a product represented by a B2C Commerce inventory record should be considered continually in stock rather than constrained by an allocation quantity. This makes it the appropriate setting for a digitally issued gift voucher whose supply is effectively unlimited.

Salesforce ' s inventory documentation definesPerpetualas the flag indicating that the product isalways in stock. TheProductInventoryRecordScript API likewise states that theperpetualproperty determines whether a product is perpetually in stock.

Setting an artificially large allocation is inferior because that number is still finite and can create misleading inventory data. Option C is also inappropriate:stockLevelis a calculated value based on allocation and turnover rather than a Business Manager control that should be forced to an arbitrary maximum.

When the perpetual flag is active under standard B2C Commerce inventory management, availability logic treats the product as available irrespective of normal decrementing stock calculations.

Study Guide reference:Data Management Using Business Manager Usage — inventory records, perpetual inventory, product availability, allocation, and Business Manager inventory configuration.

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

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.

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