Comm-Dev-101 Exam Questions & Answers

Business Manager'sCatalog Import & Exportfunctionality can perform anExport Specific Productsoperation. The merchant or developer can select the relevant Master catalog and use product-search criteria to identify the products associated with the required storefront-category assignments.

Salesforce documents that Catalog Export can export selected products directly from Business Manager. TheExport Specific Productsmode contains the selected products and the category assignments belonging to those products. The documented Business Manager location isMerchant Tools > Products and Catalogs > Import & Export > Catalog Export.

This is preferable to Site Import & Export because that feature packages site configuration/data units for movement between instances; it is not primarily designed to generate a filtered product feed based on storefront assignments.

The separation of Master and Storefront catalogs is important. The Master catalog owns the product data, while the Storefront catalog's category assignments identify which subset is merchandised through that storefront. Exporting specific Master-catalog products based on those assignments produces the required subset without manually curating every product.

Study Guide reference:Data Management Using Business Manager Usage --- Catalog Import & Export, Export Specific Products, Master catalogs, Storefront catalogs, and category assignments.

A Page Designer Page Type consists of a metadata definition plus a corresponding JavaScript implementation. The rendering behavior itself belongs in the page-typeJavaScript file, which must expose arender()function.

Salesforce states that the script file must have the same base name and location as the Page Designer meta-definition file, using.jsrather than.json. The script'srenderfunction receives aPageScriptContextand must return the resulting markup as a string. It commonly renders an ISML template usingdw.util.Template, and the template can in turn render the page's regions.

The metadata JSON describes the Page Type's declarative configuration---such as its attributes and regions---but does not implement rendering through a'render'property. A conventional SFRA controller route can invokePageMgr.renderPage()to initiate rendering, but that controller does not define the actual Page Type rendering logic.

This separation allows Page Designer to manage page composition while the JavaScript implementation controls the output representation.

Study Guide reference:Application Development --- Page Designer Page Types, page metadata,render()functions,PageScriptContext, and Page Designer rendering.

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

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.

For a Business Manager extension to become visible and usable, its cartridge must participate in theBusiness Manager cartridge path, and the user must have the Business Manager module permission required to access the extension. Salesforce explicitly states that Business Manager extension cartridges must be added to the BM cartridge path, and extension functionality is secured through roles and permissions.

The extension does not need to be added to the Storefront site's cartridge path merely to make its Business Manager menu/module available. A code version containing the cartridge must of course be deployed and active generally, but activation alone does not grant access to the new Business Manager module.

There is atyping inconsistency in option A: the stem names the cartridgeplugin_bm_extension, whereas option A sayscustom_bm_extension. The technically correct action represented by A is to addplugin_bm_extensionto the Business Manager cartridge path and grant the appropriate roles/permissions.

Study Guide reference:B2C Commerce Setup --- Business Manager extensions, BM cartridge path, module permissions, roles, and extension deployment.