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

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.

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

CustomObjectMgr.createCustomObject()expects two parameters for this use case: thecustom object type IDfollowed by thekey valuefor the new instance. Salesforce defines the relevant signature as:

createCustomObject(type, keyValue)

Therefore, ' NewsletterSubscription ' is supplied first as the custom object type andnewsletterForm.email.valueis supplied second as the unique key value. This makes option A correct.

The key attribute has already been established in the metadata definition of theNewsletterSubscriptioncustom object type. The API therefore does not require the developer to pass the literal attribute nameemailas a separate parameter. This makes option C invalid. Option B reverses the expected argument order and would attempt to interpret the email value as the custom object type name.

Custom-object keys must be unique within the object ' s applicable storage scope. Because creation changes persistent business data, the operation must also execute within an appropriate transaction when performed through server-side application code.

Study Guide reference:Application Development —dw.object.CustomObjectMgr, custom-object creation, custom-object keys, persistent business objects, and transaction handling.

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

Washing instructions are product-specific business data, so the value should be modeled as acustom attribute on the Product system object. Because the displayed instructions can differ by storefront locale, the custom attribute should be configured as localizable.

Salesforce ' s B2C Commerce metadata system allows custom attributes to be created on extensible system objects such as Product. Localizable custom attribute definitions count against the Product object ' s supported custom-attribute quota, confirming that Product attributes can participate in localized data modeling.

Option A is inappropriate because resource bundles are designed for application UI strings such as labels, messages, and validation text. They are not a scalable source for product-specific PIM data such as care instructions. Option C is also incorrect because localization is configured on eligible attributes, not by marking the entire Product system object " localizable. "

A PIM integration can populate locale-specific values of the washing-instructions attribute, after which the PDP retrieves the appropriate value under the active storefront locale.

Study Guide reference:Data Management Using Business Manager Usage — Product custom attributes, localizable product data, PIM integration, system object metadata, and localized PDP content.

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

dw.svc.LocalServiceRegistry.createService()is the standard Service Framework method for constructing a service instance from a service configured in Business Manager.

Salesforce ' s Script API defines:

LocalServiceRegistry.createService(serviceID, configObj)

The first argument identifies the configured Business Manager service, while the second supplies callbacks that define request construction, response parsing, logging filtering, mocking behavior, and other integration-specific behavior. The returned object is the actualServiceinstance used by application code.

Option B does not identify a supported creation API.LocalServiceInstanceis not the class developers instantiate to obtain configured B2C service objects. Option C likewise references a method that is not the documented LocalServiceRegistry creation mechanism.

A typical integration defines the service, profile, and credentials in Business Manager, callscreateService()in cartridge code, and subsequently invokes.call()on the returned service. This architecture externalizes environment-specific information—such as credentials, URLs, timeouts, and rate limits—from application source code.

Study Guide reference:Application Development — LocalServiceRegistry,createService(), Service Framework, service callbacks, profiles, credentials, and remote web-service integration.

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

< isdecorate > is the correct ISML construct for applying a reusable page layout to multiple templates. A decorator template can contain the common page shell, header, navigation, footer, scripts, and structural markup, while the individual child page contains only page-specific content.

Salesforce explicitly identifies a common header-and-footer layout as atypical use casefor < isdecorate > . The decorator template contains < isreplace/ > , which marks the position where the child template ' s enclosed content is inserted.

Option A is therefore not the tag normally placed around each page ' s content; < isreplace/ > belongs inside the decorator template itself. Option C can insert another template fragment, but using repeated includes for headers and footers does not provide the same centralized page-layout structure and composition semantics.

Decorator-based design improves maintainability because common markup is maintained once. If the header or footer changes, developers update the decorator rather than making the same structural changes across every individual storefront page.

Study Guide reference:Application Development — ISML decorators, < isdecorate > , < isreplace > , template reuse, common layouts, and storefront maintainability.

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

TheMerchant Tools > Content > Import & Exportmodule is specifically associated with content libraries, folders, andcontent assets. Salesforce documents that content and content-library data use thelibrary.xsdimport/export schema and are handled from this Business Manager location.

Content slots are imported and exported through the separateMerchant Tools > Online Marketing > Import & Exportmodule usingslot.xsd. Products and catalogs are likewise administered throughMerchant Tools > Products and Catalogs > Import & Exportusingcatalog.xsd. Salesforce ' s official Import and Export Object Cheatsheet clearly differentiates these locations and schemas.

The distinction matters because B2C Commerce import/export mechanisms are organized around object domains rather than providing one universal site import screen for every object. Content assets belong to libraries and can include text, markup, links, images, and other merchandising content. They can also be exported from one library and imported into another.

Therefore, among the supplied choices, Content assets are the object type that belongs to the Content Import & Export module.

Study Guide reference:Data Management Using Business Manager Usage — content libraries, content assets, import/export schemas, Business Manager modules, and data migration.

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

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.

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

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.

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

The decisive setting is " methods " :[ " put " ]. Salesforce ' s OCAPI HTTP-method specification definesPUTas a method that can create a resource when the addressed resource does not yet exist and replace/update the resource when it already exists.DELETE is a separate HTTP methodand must be explicitly authorized to remove a resource.

OCAPI settings also state that themethodsproperty acts as the HTTP-method permission filter for the matching resource ID. If only PUT is listed, the client has no DELETE permission simply becausewrite_attributesis broad.write_attributes: " (**) " controls which document properties an authorized write request can contain; it does not implicitly add other HTTP operations.

Therefore, among the supplied choices, A is the supported answer. PUT permits coupon creation at the addressed resource and can also replace/update an existing addressed coupon. Options B and C are invalid because both explicitly claim DELETE capability even though " delete " is absent from the methods list. C additionally overstates access to coupon-code operations.

Study Guide reference:Application Development — OCAPI settings, HTTP PUT, DELETE authorization, resource permissions, and Coupons Data API.

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

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.

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