Authentic Salesforce Certification Exam Comm-Dev-101 Questions Answers

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.

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

Custom storefront scripts arecode artifacts, not Business Manager metadata objects. Consequently, among the supplied options, B is the technically correct first step: create or define the required JavaScript/CommonJS script module within the project code structure.

Salesforce documents that B2C Commerce script modules are.js,.ds, or.jsonfiles and are normally stored in cartridges, commonly undercartridge/scripts. Modules expose public functionality throughexportsand are loaded withrequire(). Controllers and other server-side components can then import and invoke that reusable module.

Business Manager does not provide a general mechanism for creating arbitrary SFRA application scripts. Business Manager manages configuration, metadata, jobs, services, catalogs, and related platform data; deployable application logic belongs in cartridges/code versions.

Option C is less precise because the script/module itself must first be established in the codebase before its exported behavior can be consumed.

Study Guide reference:Application Development — CommonJS modules,cartridge/scripts, JavaScript modules,require(), exports, and cartridge-based application code.

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

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.

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