Free Practice Questions for Salesforce Comm-Dev-101 Exam

Logger.getLogger(fileNamePrefix, category)

The first argument determines the custom named-log prefix, while the second determines the logging category used for filtering. Salesforce documents this API explicitly and states that custom named loggers use the suppliedfileNamePrefixto identify the generated custom log.

Accordingly, if the omitted code segment specifiesloggersFileas thefileNamePrefix, the generated custom-log name begins withcustom-loggersFile, matching option A.

The source question, however, omits the actual referenced logger configuration and code segment. Therefore, the file itself does not provide enough visible information to deriveloggersFileindependently; the answer depends on the configuration that was evidently present in the original question version. The selected answer is consistent with Salesforce logger naming semantics and the source ' s marked answer.

Study Guide reference:Application Development —dw.system.Logger,getLogger(fileNamePrefix, category), named custom logs, categories, and custom log-file naming.

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

The analytics snippet issite-specific merchant-managed configuration, so a custom Site Preference is the cleanest design. The developer can extend theSitePreferencessystem object with an HTML-type custom attribute and expose it in a custom preference group. Each of the North American, European, and Asian sites can then maintain its own value independently.

Salesforce documents that custom site preferences are created by adding custom attributes to theSitePreferencessystem object and assigning those attributes to preference groups that merchants can edit through Business Manager. Values are maintained independently in each site context.

Option B hard-codes regional analytics logic into ISML. That would require code deployment whenever the third-party analytics provider changes a snippet, defeating the requirement that merchants independently maintain the values. Option C misuses Service Profiles, which configure outbound Service Framework behavior such as timeouts and rate limits; they are not storage containers for arbitrary HTML or JavaScript fragments.

The storefront can retrieve the current site ' s configured preference and output it at the required rendering location.

Study Guide reference:Data Management Using Business Manager Usage — SitePreferences, custom preferences, multi-site configuration, HTML attributes, and merchant-managed settings.

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

SFRA uses thePage-Showendpoint to render a content asset as a full storefront page. The endpoint accepts the query-string parametercid, which identifies the content asset to display. Consequently, the content-link expression must generate the equivalent of:

Page-Show?cid=about-us

and option A provides the correct syntax.

Salesforce ' s current SFRAPage.jsdocumentation identifiesPage-Showas the endpoint that renders a content asset in a full storefront page and explicitly documentscidas the content asset ID parameter. Salesforce also documents special content-link functions for links embedded inside content assets, allowing merchant-managed rich content to reference storefront resources without hard-coding complete URLs.

Content-ShowandContent-Pageare not the SFRA full-page content endpoints shown in these choices. Additionally, B does not passcidas the required parameter name.

Using the URL generation function rather than a literal storefront URL preserves correct host, locale, URL-rule, and deployment behavior.

Study Guide reference:Application Development — content assets, content links,$url(),Page-Show,cid, and SFRA content-page rendering.

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

For a client-side AJAX endpoint whose response will be consumed by JavaScript,res.json()is the standard SFRA response method. It serializes the supplied data into a JSON response, allowing the client-side callback to update only the necessary part of the existing page without performing full server-side page rendering.

Salesforce ' s SFRA documentation explicitly states thatres.json(data)outputs a JSON object and ishelpful for creating AJAX service endpoints executed from client-side scripts. In contrast,res.render(templateName, data)renders an ISML template and produces markup intended for page or fragment rendering.

res.print()is a low-level text-output operation and does not provide the structured response contract that JSON gives client-side application logic.

An AJAX controller commonly returns information such as success status, validation errors, updated totals, URLs, messages, or calculated values as JSON. JavaScript then selectively updates the DOM based on those fields, preserving the rest of the page.

Study Guide reference:Application Development — SFRA controllers, AJAX endpoints, response object,res.json(),res.render(), and client/server interaction.

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

A task-oriented custom job step controls its execution result by returning adw.system.Statusobject. BecauseNO_FILES_FOUNDis explicitlynot an error condition, the status object ' s severity must beStatus.OK, withNO_FILES_FOUNDsupplied as the custom status code.

Salesforce ' s custom-job-step documentation states that a task-oriented script module can returndw.system.Statusto control the step ' s exit status. When the Status object ' s error flag is false and its code is a custom value, that custom value becomes the step status and job processing can continue unless the job flow defines a transition for it.

Option A returns an arbitrary object rather than a B2C CommerceStatus. Option C similarly returns a plain JavaScript object. Salesforce specifically notes that if a script returns an object that isnotadw.system.Status, the Job Framework treats the execution as ordinaryOK; the custom code isn ' t established through that object.

new Status(Status.OK, ' NO_FILES_FOUND ' )is therefore the correct implementation.

Study Guide reference:Application Development — Job Framework, custom job steps,steptypes.json,dw.system.Status, custom exit codes, and task-oriented script modules.

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

B2C Commerce localizesform structure through locale-specific folders, not by appending the locale to the form-definition filename. For a U.S. English form, the developer createsforms/en_US/and places anaddress.xmlform definition inside it.

Salesforce ' s SFRA Forms documentation explicitly states that when a form ' s structure differs by locale—for example, state fields in one country and province fields in another—the cartridge should contain separate locale directories beneathforms, with each directory containing a form definition of thesame name. If a locale-specific definition is absent, the default form definition is used.

en_USfollows the Salesforce locale naming convention using language and country codes. Option B incorrectly changes the filename toaddress_en_US.xmlinstead of creating the required locale directory. Option C omits the language component and therefore does not use a valid locale ID for this purpose.

The copied U.S. file can then be modified independently to contain the state abbreviation options.

Study Guide reference:Application Development — localized forms,forms/en_US, XML form definitions, address localization, and locale-specific storefront behavior.

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

The rendering template is already using the standard B2C Commerce product-slot model correctly. Within a slot rendering template,slotcontentis an implicit object representing the evaluated slot configuration. For product-type slot content,slotcontent.contentexposes the collection of products returned by the slot execution.

Salesforce ' s < isslot > documentation explicitly demonstrates iterating overslotcontent.contentwhen the slot ' s content type is Product. It also identifiesslotcontentas an implicit object available specifically to slot rendering templates and maps itscontentproperty toSlotContent.getContent().

Therefore, < isloop > is not only allowed but is the normal mechanism for rendering several products returned by a slot. A recommender is unnecessary because the scenario states that products have already been directly configured in an active and correctly scheduled slot. Recommender-based slot content is another valid content-selection method, but it is not mandatory for a manually configured product slot.

Study Guide reference:Data Management Using Business Manager Usage — Content Slots, SlotContent, product slot rendering, < isloop > , scheduling, and slot templates.

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

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

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

B2C Commerce customer lists areorganization-level objects that can be assigned to multiple sites. Each individual site can use exactly one assigned customer list, but multiple sites can reference the same list. Salesforce documents this relationship explicitly.

To configure RefArch to use RefArchGlobal ' s customer list, the administrator edits the RefArch site configuration and selectsRefArchGlobalas its Customer List. Salesforce ' s storefront-site configuration documentation identifies Customer List as a configurable field on the site ' s General tab.

Importing the customer list into RefArch would create or transfer customer data rather than establish the intended shared-list assignment. It would not implement genuine shared customer profiles.

Option B is also incorrect because there is no generic " Customer List Sharing " global preference that enables this behavior. Sharing is accomplished by assigning the same customer list to more than one site.

Study Guide reference:B2C Commerce Setup — Customer Lists, shared customer profiles, multi-site configuration, site General settings, and customer-list assignment.

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

The appropriate inventory configuration is thePerpetualflag on the product ' s inventory record. Salesforce uses this setting to represent merchandise that should be treated as continuously in stock rather than becoming unavailable when its ATS reaches zero.

Salesforce ' s inventory-development documentation identifies a product with the perpetual flag as a product that isalways in stock. This provides a clear platform-level representation of unlimited or non-depleting availability.

Option B is an unreliable workaround. A very large allocation is still finite, can eventually be depleted, and introduces misleading stock information into inventory reporting and integrations. Option A does not identify the actual standard Business Manager inventory setting represented by the B2C Commerce inventory model.

When standard B2C Commerce inventory management is being used, the perpetual flag directly changes the product ' s availability behavior. Implementations using Omnichannel Inventory must instead follow the inventory semantics of that system, but for the B2C Commerce inventory configuration tested here, Perpetual is the correct setting.

Study Guide reference:Data Management Using Business Manager Usage — Inventory Lists, Product Inventory Records, Perpetual inventory, ATS, and product availability.

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