Free Salesforce Comm-Dev-101 Practice Exam with Questions & Answers | Set: 3

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 includes several platform-defined payment methods, such asCREDIT_CARD,GIFT_CERTIFICATE,BANK_TRANSFER, and other standard methods. These default definitions are part of the platform configuration and therefore cannot simply be deleted. If a merchant does not want to expose one of these methods on the storefront, the appropriate administrative action is to disable it.

Salesforce ' s Business Manager documentation explicitly states thata default payment method cannot be deleted and can only be disabled. It also confirms that administrators can drag column headers to alter the payment-method sort order, which directly eliminates option C. There is likewise no five-payment-method limit corresponding to option B.

Payment methods are managed independently from payment processors. A payment method represents the shopper-facing way of paying, while a payment processor represents the processing implementation associated with that method. Maintaining the platform-defined method while disabling it preserves configuration integrity and permits the method to be reactivated later without recreating its system definition.

Study Guide reference:Data Management Using Business Manager Usage — Payment Methods, payment configuration, default payment methods, activation and deactivation.

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

A custom object is the most appropriate persistent data structure because the requirement applies toboth registered and guest shoppers. A Profile-based solution cannot satisfy the requirement reliably because anonymous/guest customers do not have a persistent registered customer profile. Storing customer email lists directly on Product records would also create an inappropriate product-to-shopper coupling and potentially large mutable collections on product system objects.

B2C Commerce custom objects are intended to extend the persistent commerce data model for application-specific requirements. Developers can define custom object types with custom attributes, including multi-valuedSet of Stringattributes, and choose organization or site storage scope.

A custom back-in-stock object can therefore persist the shopper ' s email address plus one or more interested SKUs independently of authentication status. Subsequent job or inventory-update logic can identify subscriptions when inventory becomes available and trigger the notification process.

This design also keeps notification-subscription data separate from core customer and product objects, reducing unintended effects on standard platform data models and supporting anonymous shoppers cleanly.

Study Guide reference:Data Management Using Business Manager Usage — custom object types, custom attributes, persistent business data, guest shoppers, and application-specific data modeling.

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

American Express is acredit-card type used under the existingCREDIT_CARDpayment method, rather than a new payment processor or Site Preference. Therefore, the appropriate Business Manager action is to manage the supported Credit/Debit Cards associated with the credit-card payment method.

Salesforce documents that merchants manage payment methods underMerchant Tools > Site Ordering > Payment Methodsand that the Credit/Debit Cards page manages card types specifically in the context of the defaultCREDIT_CARDpayment method.

A payment processor represents the integration that processes transactions; American Express itself is not created as a payment processor simply because that card network should be accepted. Likewise, Site Preferences are not the mechanism used to enable supported card brands.

The underlying payment processor must, of course, support American Express transactions, but storefront card eligibility is configured through the credit/debit card configuration associated with the credit-card payment method. Card configuration can additionally restrict cards according to countries, currencies, customer groups, or payment ranges.

Study Guide reference:Data Management Using Business Manager Usage — Payment Methods, CREDIT_CARD, Credit/Debit Cards, card types, and payment processors.

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

No additional action is required when the product slot is already configured, active, scheduled, assigned products, and its rendering template iterates throughslotcontent.content.

Salesforce documents thatslotcontentis an implicit object available inside an ISML template used as a slot rendering template. Itscontentproperty maps toSlotContent.getContent()and returns the collection produced by the evaluated slot configuration. Salesforce specifically demonstrates product slots by iterating over this collection to render returned products.

Therefore, < isloop > is fully valid in a content-slot rendering template. Option C incorrectly claims that loops are prohibited.

A recommender is also optional, not mandatory. B2C Commerce can populate product slots from explicitly selected products, recommendations, or other supported merchandising configuration. If products have already been configured directly, a recommender does not have to be introduced.

The rendering template simply receives the slot execution result and iterates its returned product collection.

Study Guide reference:Data Management Using Business Manager Usage — Content Slots,slotcontent, Product slot content types, rendering templates, < isloop > , and merchant slot configuration.

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

B2C Commerce assigns exactly one customer list to each site, but the same customer list can be assigned to multiple sites. Therefore, RefArch does not need a separate copy of the RefArchGlobal customer records. The site configuration must simply be changed so thatRefArchGlobal is selected as RefArch ' s assigned Customer List.

Salesforce describes a customer list as a collection of registered customers associated with a site and explicitly states that multiple sites can share a customer list. A site itself can use only one customer list at a time.

Option A would create or import data rather than establish the required shared-list relationship. That introduces duplication rather than true shared customer profiles. Option B is also incorrect because this relationship isn ' t enabled through a generic " Customer List Sharing " global preference. The appropriate configuration is the customer-list assignment on the site.

Shared customer lists are especially useful for multi-site implementations where customers should maintain one registration/profile across multiple storefronts.

Study Guide reference:B2C Commerce Setup — multi-site configuration, customer lists, shared customer profiles, and site-level customer-list assignment.

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

B2C Commerce imposes a daily size quota on custom logs to prevent unlimited logging from consuming storage or degrading instance performance. Once the applicable custom-log size limit is reached, additional custom logging issuspended until the next logging dayrather than rolling immediately to another unlimited file.

Current Salesforce documentation states that each application server can write up to the defined daily amount into the custom debug, info, fatal, error, and warn logs, and that logging is suspended until the next day once the limit is reached. The logging day is based on GMT.

Option A describes normal archival/retention handling rather than quota behavior. Existing log files can later be compressed and moved according to retention policy, but reaching the daily file-size quota doesn ' t simply bypass the quota by opening another unrestricted file. Option B is also incorrect because B2C Commerce doesn ' t delete the current log merely to continue writing.

Developers should therefore avoid excessive diagnostic logging, particularly in frequently executed storefront code, and choose appropriate log levels and categories.

Study Guide reference:Application Development — custom logging quotas, log-file management, Business Manager log settings, WebDAV logs, and production diagnostics.

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

The required information is structured application data that is specific to one site but must move consistently from staging to production. Asite-scoped, replicable Custom Objectis therefore the correct model.

Salesforce custom-object definitions provide two relevant controls.Storage Scopedetermines whether custom-object instances are organization-wide or site-specific, whileData Replicationdetermines whether custom-object data can participate in replication between environments. Salesforce specifically documents that custom objects can be local to a site and that custom object types can be configured as replicable.

The developer can define one object per country with attributes such as country code, price book ID, flag image URL, display name, and ordering information. The storefront can query these records to construct the country selector dynamically.

Option A attempts to overload the Locale system object with business configuration that is not fundamentally locale metadata. Option C stores structured application configuration in content assets, which are primarily merchandising/content entities and would be less suitable for strongly structured programmatic lookup.

Study Guide reference:Data Management Using Business Manager Usage — Custom Objects, site-specific storage scope, data replication, structured application configuration, and multi-country storefront design.

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

A task-oriented B2C Commerce Job step can return adw.system.Statusobject to control the Job Framework ' s exit status. BecauseNO_FILES_FOUNDis explicitly anon-errorcondition, the developer should construct a Status usingStatus.OKand supplyNO_FILES_FOUNDas the custom status code.

Salesforce documents that whenStatus.isError()is false and the returned status code is custom, the Job Framework preserves that custom code and continues execution unless the job flow has a transition that handles it differently.

Option A returns an arbitrary object rather than adw.system.Status. Option C also returns a plain JavaScript object; Salesforce states that a returned object that is not aStatusresults in the ordinaryOKstatus rather than establishing the desired custom status code.

Study Guide reference:Application Development — Job Framework, task-oriented job steps,dw.system.Status, custom status codes,Status.OK, and job transitions.

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

B2C Commerce can store multiple code versions simultaneously, but only theactive code versionsupplies the storefront ' s templates, controllers, scripts, and static code resources. If recently uploaded cartridge changes do not appear, verifying that the expected code version is active is therefore a fundamental troubleshooting step.

Salesforce ' s Code Deployment documentation states that all templates, pipelines, scripts, and images are taken from the active version. It also specifically recommends checking that the cartridge was uploaded to the current code version when storefront changes do not appear. Salesforce ' s SFRA troubleshooting guidance further recommends switching code versions and reactivating the intended version when changes are not reflected on the server.

A search-index rebuild is relevant to indexed product, category, content, or search configuration—not to changes in JavaScript controllers or ISML templates. Cartridge-path configuration should also be verified, but the source ' s earlier scenario already uses that check before checking the active version.

Study Guide reference:B2C Commerce Setup — Code Deployment, active code versions, cartridge deployment, storefront troubleshooting, and version activation.

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